One Workbench, one box to type in, two AIs behind it, Godot beside them. Profit split: 50% Todak Studios, 20% Todak Academy, 30% student (Blueprint v2.1).
What the student sees is one box. Two chat panels were the first design; Neo and Lan both saw the problem: a beginner with little AI knowledge would not know which one to type into. So the Workbench has a single Todak desk. Behind it, a small router sends each request to the right AI, the design desk (Astra, through Codex) for artwork, sound and design documents, the build desk (Claude Code) for code, builds, reviews and publishing, or to both in sequence when a request needs both. The box always says which desk it used and why, and the student can send a request to the other desk with one click. That line is itself a lesson in what each AI is for. The two tools' own panels stay installed and appear from week 4, so nobody graduates without having seen the real tools.
12-second loop · Hover or focus to pause · Previous / Next step one beat
Animation, not a screenshot. The real Workbench is built in the kit phase.
One monitor works with a floating game window. Two 24-inch monitors are preferred. The projector shows the lecturer's Workbench for demos, then the class dashboard: steps, builds and showcase links. Personal prompt histories and assessment notes stay off it.
Hover or focus to pause · Step through with Previous / Next
Hover or focus to pause · Step through with Previous / Next
Hover or focus to pause · Step through with Previous / Next
Animation, not a screenshot. The real Workbench is built in the kit phase.
| When | What the student does and keeps |
|---|---|
| Day 1 · Week 1 | Sign into Claude, Astra and GitHub. Watch one demo loop; play, change and explain a practice scene. No Godot yet. Claude records the task and shows the first saved memory. Astra opens on day 2 or 3 for an idea card and moodboard. |
| Week 3 · Pong | Start from a template; add paddle, ball, score and title screen; publish. Astra draws the game art. Claude edits, tests and builds. Keep a web game with their name and explain the paddle script with both desks closed. |
| Week 10 · 3D final game | Astra: character sheet, storyboard, screen designs, icon, listing and gameplay improvements. Claude: character, camera, behaviour, tested changes, review and Play internal testing. Keep a playable slice on their phone, a fix list and twelve weeks of prompt growth. |
Neo's own worry, and the answer: "build me a 3D Pong" and learn nothing. The box is where the course rules live. Two raw panels cannot enforce any rule; one box can.
| Rule inside the box | What the student experiences |
|---|---|
| Routing, shown | "Sent to the design desk (Astra), because you asked for artwork." Or "to the build desk (Claude Code), because you asked the paddle to move." A wrong guess is one click to fix, and the student learns what each AI is good at. |
| Step gating | "Build me the whole game" gets: "Not in one go. You are on step 2, the paddle. Ask for that." Requests beyond the current step are done only as far as the step allows. |
| Explain it back | After every code change, the next change stays locked until the student tells the desk in one sentence what the last change did. Those sentences feed the walkthroughs and the viva. |
| Prompt scoring | "Do everything" prompts score low in the journey; specific, informed prompts score high. The lecturer sees the growth. |
| Recording | The box records every request itself, with the route and the reason, so the journey no longer depends on hooks or transcript scraping. |
| One login is enough | A student with only a Claude login, or only a ChatGPT login, still works: everything routes to the desk they have. Both logins remain the plan. |
| Under the hood | From week 4 the raw Claude Code and Codex panels appear beside the box, and the no-AI debugging drills begin, as before. |
Behind the box, the lanes are unchanged. Astra owns design: the design document, moodboards, character sheets, sprites, sounds, the title art, all as files in design/ and assets/. Claude Code owns the build: scaffolding, gameplay code with the student, project memory, builds, reviews, publishing, and merging Astra's work after tests. Work still crosses as files plus a short note. What changed is only what the student has to look at.
Where it runs. The box lives in the Todak sidebar and calls the kit's tgk ask command, which drives Claude Code and Codex on the student's own PC with their own logins. No server in the middle, no wrapper platform. The two tools' rich views are one click away.
| Time | Block | What happens | Design desk | Build desk | Godot |
|---|---|---|---|---|---|
| 0:00–0:15 | Demo | Lecturer shows the skill, result and explanation. | Open | Open | Open |
| 0:15–0:30 | Design warm-up | One paragraph and one picture with Astra. | Open | Closed | Closed |
| 0:30–1:45 | Guided build | Follow sidebar steps. Mentors circulate. Playtester runs after each step. | Open | Open | Open |
| 1:45–2:00 | Break | ||||
| 2:00–2:30 | AI-off walkthrough | Pairs explain code. From week 4, fix a mentor's fault without AI. | Closed | Closed | Open |
| 2:30–2:50 | Showcase | Three or four students play web builds. Two questions each. | Closed | Closed | Projector |
| 2:50–3:00 | Save | Save decisions and mark the day's best prompt. | Closed | Open | Closed |
| Piece | Build or use | Effort | Note |
|---|---|---|---|
| Claude Code panel and Windows desktop app | Use | 0 | Seat includes panel, desktop, terminal and web. |
| Codex (Astra) panel and Windows desktop app | Use | 0 | Dry run: check reported missing Astra model in some Windows app pickers. |
| Godot 4 editor and export templates | Use | 0 | Free live view. |
| Todak sidebar | Build | 2 weeks | Steps, design board, builds, journey; run/build/publish/review buttons call kit commands. |
| Workbench, lab setup, home installer | Build | 3 days | Panels, Godot tools, sidebar, kit and recording switch. |
| Lecturer dashboard | Build | 1 week | Student steps, builds, review queue, showcase. |
| Game Kit | Build | ~6 weeks, earlier estimate | Templates, memory, assets, build server, publisher desk, review, collector. Revised pilot estimate below. |
| Todak Studio browser app | Phase 2 | 2–3 months | Only if cohort 1 needs it; same kit commands. |
“Open one AI panel at a time.”
“Chat alone is not the deliverable.”
“Show one decision, its changed file and its result.”
| Point | Claude Code said | Astra said | What goes in the plan |
|---|---|---|---|
| Two desks | Both visible. | One open. | Weeks 1–6: sidebar selects one desk per block. Both together only from week 7. |
| Day 1 | Astra moodboard; Claude saves idea. | Play, change, explain; Astra closed. | Astra's day 1. Design desk opens day 2 or 3 of week 1. |
| Kit timing | About six weeks total; kit two. | Two weeks to demonstrate; six to ten more for a dependable pilot. Two experienced developers; lecturer tests weekly. Custom Studio: three to six months or more, plus maintenance. | Astra's estimate adopted. Blueprint v2.2 states ten to twelve weeks to a pilot. Templates for dry-run games first; menu grows each cohort. |
| Testing | Staff reference games. | Add four to six real beginners. | Both before cohort 1. Also test long prompts, restarts, offline queues and both interfaces. Verify work and records reached storage before shared-PC logout. |
| Recording failure | No record, no evidence. | Show saved/waiting; recover faults. | Deliberately switching recording off loses evidence. Faults get recovery, never a penalty. Status always visible (v2.2). |
| Competence | Review, oral defence, prompt growth. | Lecturer moderates AI scores; publication or bypass is not proof. | Gate decides publishing. Walkthroughs and oral defence decide passing. AI proposes; lecturer signs. |
| Class builds | Build on request. | Twenty simultaneous requests need a queue. | Sidebar shows queue position and progress. |
One Mac mini, controlled by us. Students never log into it. It exists so that iPhone builds and TestFlight are possible at all; a Windows PC cannot make an iPhone build.
Academy-owned pieces, per Home v1. September 2026 estimates at about RM4.75 per USD; confirm prices at purchase and usage in the dry run.
| Item | Cost / plan | What it covers |
|---|---|---|
| Claude Team + ChatGPT Business | Each: ~USD 20/month yearly or USD 25 monthly. Team starts at two seats. | Academy email and workspace; one person per seat. Admin adds/removes students; no shared login or password rotation. One invoice; no training on workspace content by default. Codex allowance matches Plus. |
| Both seats · 12 weeks | RM570–710/student; USD 120–150 over three months. | In the fee. 15 students: RM8.6k–10.7k; 20: RM11.4k–14.3k. Students leave with published games and a journey export. |
| Heavy weeks 7–11 | ~RM2.4k Claude buffer; Astra amount to confirm. | Five Claude Max seats for the final-game month. Astra: higher tiers or extra credits, tested in dry run. |
| Assets | Seats first; ~RM50/student for paid services. | Ideas, moodboards, storyboards, concepts, documents, presentations, slides and RUSH art covered by seats. Bulk images, 3D and sound use rented GPU hours: ~RM300–700/cohort. Kit queues and meters jobs. Paid 3D and Studios video tools for gaps; no student Meshy subscriptions. |
| Seats + assets | ~RM620–760/student per term. | Before teaching costs. |
| Mac mini M6 · 32 GB · 1 TB | ~RM6,000; range RM3.8k–7.5k. V1 lists it on apple.com/my; store price to confirm. | Neo buys; Academy asset. Education eligibility to check. Web, Windows, Mac, Linux, Android and iPhone builds, store uploads, automated playtests. Room for twenty students' build caches. |
| Other Mac configurations · 22 September 2026 lineup in v1 | M6 · 16 GB · 256 GB: RM3,799, education RM3,399. M5 Pro · 24 GB · 512 GB: RM7,499, education RM7,099. | Base M6: insufficient memory/disk. M5 Pro only for later local models. Standard 2.5 Gb Ethernet; no 10 Gb upgrade. |
| Mac setup | Academy IT room; Kenwingston fallback, own Cloudflare Tunnel. | RUSH/ApaNakMakan recipe: Xcode, Studios certificates in dedicated keychain, Android upload key in vault, Godot templates, kit build agent. No Neo network. |
| Academy Windows PCs | Already owned. Optional second monitor ~RM400 each. | Workbench; two 24-inch monitors preferred. |
| Site and code | RM0 hosting and GitHub. | course.neotodak.com stays as the base (Neo, 20 Sep); code in a todak-academy GitHub organisation (proposed). Private student repositories; builds run on the server. |
| Course database | RM0, then ~RM120/month (~USD 25). | Supabase project in the Todak organisation: students, progress, prompts, reviews, paperwork, memory. Shared across cohorts. |
| Kay .213 server | Already Academy-owned; RM0. | In the Kay rack. Prompt collector and publishing queue. |
| Kit, Workbench, sidebar, dashboard | Earlier ~8-week internal-work estimate; no cash charge. | Revised ten-to-twelve-week pilot estimate in section 06. |
| Consent, IP licence, NDA | Legal drafting: to quote. | Recording permission, publishing rights with 50/20/30 split, confidentiality. Reused each cohort. |
| Store publishing | RM0 existing Studios accounts; Steam optional, USD 100/game, recoupable. | Apple, Google Play, itch.io and Steam. See Stores v1 for Epic and Roblox. |
Licences: no game voices from Neo's personal voice engine, which is licensed for personal use only. Verify a commercial voice licence or use a licensed Todak service. Higgsfield is Neo's personal subscription, not shared by twenty students. Music and sound libraries must allow store releases.