Eight passes from vision to loop leverage.

Work through these in order. Each page gives a challenge, copyable prompt, visible build target, evidence to inspect, checkpoint, tiny drill, and a plain-language reason for the step. Keep the glossary appendix open when a term gets fuzzy. If you are not using Docker, finish the local setup appendix before Lesson 01.

All lessons

1. 01 Tour the repo and set the course

   Use Pi plus grill-with-docs to write VISION.md: what the local issue checker should do, which files it may edit, and when it must stop.

2. 02 Make bad input fail loudly

   Turn VISION.md into one local event file, one check command, tests, and a saved receipt from a real run.

3. 03 Show issue events in Lakebed

   Read the same local event file from Lesson 02 and show matching issue cards in Lakebed.

4. 04 See and control the check from Pi and Herdr

   Add a visible way to ask for status, run the local check, and see what happened.

5. 05 Claim one ready issue without changing product files

   Pick one ready issue, write a claim, run a dry-run, and prove no product files changed.

6. 06 Let cleanup propose one follow-up

   Let the checker propose one maintenance event, then prove it stops when the repo or queue is not safe to touch.

7. 07 Ask for review without handing over the repo

   Ask a small reviewer for help without letting another agent edit the app files.

8. 08 Compare a candidate check beside the current check

   Use the same event file and check command while a small TypeScript candidate check says the next state and reason. The current checker still decides.