What must be true
Bets you are coding on. Mark tested when a parent proves or kills it.
Dual-monitor companion · local preview
Code on the right.This desk on the left.
Clear places to go: this session, your project, tools, help, and a success checklist your coding AI should keep in memory. Not a pile of widgets. A path through the night.
Local desk
Step 1
This work session
Start the window. Set goals for this block. Stage notes sit beside the timer so you do not wander.
45 min · not started
Notes for this stage
Stage coach appears here.
Step 2
Your project under the lamp
Keep this short. The other screen is for code. This is who you serve.
Step 3
Tools to help
Stage-aware pegs from the Parent Workbench. Open beside your editor. No tab hunting.
Tools for this stage
Quick reaches
Idea jar (do not derail the lamp)
Step 4
Ask for help
Stuck is normal. One clear ask + a 15-minute unblock. Snap, community, or both.
Step 5
Success checklist · AI memory
These are the quiet rules of a good build. Keep them filled. Copy them into the AI on your other screen so it always remembers who you serve, what must be true, and what is already locked.
Locked choices
Nailed decisions. Stop re-deciding them every night.
Ship honesty checklist
Can a parent try this without you?
0 / 6
Success path (auto from your desk)
Paste this into your coding AI
Fill the project and checklist, then this block updates.
Step 6
Ship & community
Parent truth, open build log, helpers, and the showcase path when the checklist is honest.
Parent truth
Copy scrap
Open build log
Helpers & rewards
No helpers yet.
Showcase when ready
When the success checklist is honest and someone can try it, put it on the floor for parents in this community.