Open. Talk. Build. See it run.

1. 1.

   Open the assistant.

   Mac or Windows. Three panes: canvas, workshop, me. It sits on the machine. It does not take the machine over.

2. 2.

   Talk to Simon.

   Pick a tool you actually want — calendar, contacts, email, fitness — or pitch your own. Sudo Powers are on: explain, translate, generate the boring bits, catch the error.

3. 3.

   Build in the workshop.

   Editor, sandboxed terminal, local Git. The code is beside the thing it runs. No separate IDE scavenger hunt on day one.

4. 4.

   See it live on the canvas.

   The feature you just wrote is the dashboard you open tomorrow. That’s the loop: talk, build, ship, look.

5. 5.

   The backlog ticks underneath.

   You see a feature list. I see Python, SQLite, APIs, Git, the seatbelt. Missing foundations get injected into the current job, not parked in a textbook. The map is always there if you want it.

6. 6.

   I break it. You explain it.

   I generate the steel frame. Then I pull a beam. If you can’t say why the floor dropped, you haven’t learned it. Transfer tasks: do it somewhere I didn’t decorate for you.

7. 7.

   Leave able to continue without me.

   I get quieter. The software stays yours. If billing stops, I may slumber. The assistant does not.

Want the whole map? You can see it. Hidden means how it’s taught, not a secret.