Game Track · Demonstrator v1 · 20 Sep 2026 · Neo said go

Two weeks to a working demo

Everything else on this site is a proposal. This page is a build. In two weeks a real beginner sits at a Todak Workbench, makes Pong with the two AI desks, publishes it to the web, and Lan watches the prompts land in the classroom system. Ten minutes, live. It doubles as the first dry-run item the plan already calls for, so nothing is wasted if the answer afterwards is "not yet".

Open to the team since 20 Sep. Play around as a student or as a lecturer: Try the demo.

Short version

GoalA ten-minute live demo: open the Workbench, design with Astra, build with Claude Code, press Play in Godot, publish to the web, see the prompt journey, get the review report. Done means a beginner has done it, not us.
ScopeWeb only. One game, Pong. One lab PC. The pieces of the kit that the demo touches, and nothing else.
WhoClaude Code builds the backbone. Codex builds the sidebar and the Pong art. Claude Code directs and verifies. Neo picks the date and the beginner.
CostNo new cash. The two seats we have, tr-home for web builds during this dry run only, and one Academy Windows PC on the day.
LabelThe screen says "demonstrator, not the kit" the whole time, the way the animations say "animation, not a screenshot".

The ten minutes

Min	The beginner does	Lan sees	Built by
0–1	Signs in, opens "Todak Workbench". Sidebar: Week 3 · Pong, today's steps.	One window, no terminal.	Workbench profile, sidebar
1–3	Types into the one box: "paddles, a ball and a title screen, pixel style". The box says "sent to the design desk (Astra)".	Pictures land on the design board.	Todak desk, router, kit's design folder
3–6	Types "make the left paddle move with W and S". The box says "sent to the build desk (Claude Code)". Presses Play. The box then asks: what changed? One sentence unlocks the next step.	Code changes in the middle, Godot reloads, the paddle moves.	Todak desk, router, step gating, explain-back
6–8	Says "publish to web".	A link on course.neotodak.com with the beginner's name. Opens on Lan's phone.	Build and publish command, showcase
8–9	Opens the journey tab.	Every prompt from both desks, timestamped, in the classroom system.	Recording hooks, journey page
9–10	Says "review my game".	A one-page report: what passed, what to fix.	Reviewer

What gets built

Piece	What it is	Owner
Kit commands	One small tool the desks call: new game, run, build for web, publish, review, remember. Speaks Godot on Mac, Windows and Linux.	Claude Code
Shared instructions	One file both desks read, telling them the week, the game, the lanes and the rules.	Claude Code
Pong template	A Godot 4 project with the pieces the student assembles: paddles, ball, score, title screen, win state, sound, saved high score.	Claude Code (code) · Codex (art)
Project memory	The student's project brain: decisions and conventions saved and recalled by the Build desk.	Claude Code
Recording	Hooks that write every prompt from both desks to the classroom database with the student, game and week.	Claude Code
Showcase	A "play" area on course.neotodak.com that serves Godot web builds with the two headers they need.	Claude Code
Journey page	The lecturer's view in the classroom system: prompts per student, per game, both desks.	Claude Code
Reviewer	Runs the game headless, checks the "ships complete" list, writes a one-page report.	Claude Code
Todak sidebar	The panel in the Workbench: steps, design board, buttons, journey link, recording status.	Codex
Trainer's box	The trainer's page: the session's presentation, a live board of every student against the session's objective, and a box that answers questions about the room, runs the reviewer on a student's game, drafts feedback and sends notes into a student's box. Reads the course record only. Neo's idea, 21 Sep.	Claude Code
Todak desk (the one box)	A chat box in the sidebar that calls the kit's router: design requests to Astra, code to Claude Code, both in sequence when needed; shows the route and the reason; step gating and explain-back built in. Decided 21 Sep.	Claude Code (router) · Codex (the box)
Workbench profile and installer	The editor profile with both desks, the Godot tools and the sidebar; one script to install on a lab PC.	Claude Code · Codex reviews the feel

Not built: store publishing, Android or iPhone builds, the Mac mini, the genre menu beyond Pong, the browser-based Studio, Unity, the Academy accounts move. Those wait for the answer after the demo.

Day by day

Day	Done means
1–2	Repository up. Kit commands scaffold Pong, run it, build it for the web. Shared instructions in place. Codex briefed on the sidebar and the art.
3–4	Publish command puts a build on the showcase with a working link. Recording hooks write prompts to the classroom database. Reviewer produces a report for the Pong build.
5	Workbench profile and installer. Claude Code runs the whole ten minutes alone on a Mac, start to finish.
6–7	Codex's sidebar and art integrated. Journey page live. First run on a Windows PC. First beginner trial; the fix list from it.
8–9	Second beginner trial. Fixes. Rehearsal at demo speed. "Demonstrator" label on screen.
10	Demo day. Neo picks it.

What could bite

The Codex desk on Windows. A reported case of the Astra model missing from the Windows app's picker. Checked on day 6; the fallback is the Codex panel in the editor or Codex in the browser.
Godot web builds need two headers on the hosting site. Set once on the showcase, tested on day 3.
Windows testing. The build happens on Mac and Linux; the first Windows run is day 6. If the lab PC is not available, Neo's Windows machine stands in.
Recording both desks. Claude Code's hooks are documented; Codex's session transcripts are collected from disk. If either fails on the day, the journey page shows what was captured and says so.
A demo looks like a product. It is not. The label stays on screen.

Neo's two calls

1The demo date, about two weeks out.
2The beginner who sits in the chair: ideally Academy staff who has never coded.

Changelog

Day 4, later · 21 Sep 2026. The trainer's box is in the demonstrator at /trainer: the first-lab presentation, the live room against the objective (played · paddle moves · explained · ball bounces), and a box for "who hasn't…", "who is stuck", "show", "review", "note" and "draft feedback". Notes land in the student's box within twenty seconds.
Day 4 · 21 Sep 2026. The web demo became the first lab: the game is built in the background the moment a visitor starts and rebuilds itself after every code change; the desk greets by name and suggests plain requests; the PIN is gone (Neo's call, it's a demo). First lab v1 written for the meeting: box first or hard way first, and the memory question.
Day 3, evening · 21 Sep 2026. The web demo of the one box is live at course.neotodak.com/demo (team PIN): a fresh Pong per visitor, the box with route badges and reasons, and a viewer with the game, the code diff, the design board, steps and review, and the journey. Behind it, a demo server runs the kit with real Claude Code and Codex logins, one request at a time, with a daily allowance; it sits behind the fleet's public door and is temporary. Found and fixed on the way: the site's own proxy cuts calls at 30 seconds, so the page talks to the door directly.
Day 3, later · 21 Sep 2026. Codex delivered the Desk: the one box at the top of the sidebar, with route badges and reasons, "send to the other desk instead", the plan checklist, the explain-back mode and a remembered conversation; 24 tests. Packaged as sidebar 0.2.0; the installers now pick it up. Team steps updated.
Day 3 · 21 Sep 2026. Neo decided the student sees one box with two AIs behind it. The kit gained tgk ask: a router with a whole-game guard, step gating and explain-back, recording the route and reason. Codex briefed on the chat box in the sidebar. The demo script changed accordingly.
Day 2 · 20 Sep 2026. Opened to the team: Try the demo, a team showcase on GitHub Pages with a publish key, a team PIN for the journey page, and a team pack from Neo. The front page of course.neotodak.com became the presenting dashboard, and Codex Astra built The classroom, in 3D, an animated ten-stop tour of the whole program in English and Malay.
Day 2, early · 20 Sep 2026. Codex delivered the Todak sidebar (a small editor extension: game, steps, Run · Build · Publish · Review buttons, design board, recording status, recent prompts, review summary, the demonstrator label; 12 tests, no network, commands run in a real terminal) and the Pong pixel art (paddle, ball, title backdrop, icon, 5 KB in total). Packaged and installed into an isolated editor profile. Still to check by eye in a real editor window: that is day 5's dry run.
Day 1, late · 20 Sep 2026. The core moment of the demo works unaided: a real Claude Code run, reading only the kit's instruction file, made the paddle move with W and S, ran the review itself, ticked the step and saved its reasoning to the project brain, in two plain sentences to the student. A real Codex session's prompt was collected into the same journey.
Day 1, evening · 20 Sep 2026. Recording is live end to end: the Build desk hook records each prompt, the kit syncs prompts, builds, publishes and reviews to the course site, which stores them in a locked table in the Academy's own database, and the lecturer page at course.neotodak.com/journey shows them behind a PIN. The Workbench profile and the Mac, Linux and Windows installers are written.
Day 1 · 20 Sep 2026. Repository todak-game-kit up. The kit command scaffolds Pong, runs it, builds it for the web on Mac and on tr-home, reviews it headless (the two student steps show as not done until they are), keeps the project brain and records prompts. Reference solutions make the review pass 8 of 8. The showcase is live: course.neotodak.com/play, first test game published through tgk publish web. Codex briefed on the sidebar and the Pong art.
v1 · 20 Sep 2026. Build plan, on Neo's go. Progress is logged here as it happens.