🧭Lesson MapAI Engineer Loopcraft Workshop 2026
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
- 01 Set the rules before the first line of code
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.
- 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.
- 03 Make the queue visible and traceable
Read the same local event file from Lesson 02 and show matching issue cards in Lakebed.
- 04 Operate the check, and always know its state
Add a visible way to ask for status, run the local check, and see what happened.
- 05 Claim work without letting the agent touch your code
Pick one ready issue, write a claim, run a dry-run, and prove no product files changed.
- 06 Let the loop create work — and stop itself
Let the checker propose one maintenance event, then prove it stops when the repo or queue is not safe to touch.
- 07 Get a second opinion without giving up the repo
Ask a small reviewer for help without letting another agent edit the app files.
- 08 Shadow the next decision before you trust it
Use the same event file and check command while a small XState candidate machine says the next state and reason. The current checker still decides.