Daily workflow

Module 9 left you with a working migration team and an honest admission sitting right next to it: coordination cost rises faster than the work divides, and most of what you’ll actually do to stash doesn’t need a team at all. That’s the last piece. Nobody has added up what the whole harness cost, or whether it paid for itself. That’s this module’s slice of the one enemy this course has been naming since module 1 - the window is finite, and every default you added back yourself has been spending it too, the whole time, whether you were watching or not.

This module doesn’t add an eleventh piece. It’s a capstone: judge what you built against what it cost.

What has to be true by the end of it:

1. Every file in stash’s .pi/ traces back to the module that taught you to write it - no orphan files, nothing you can’t explain.
2. Every layer’s cost is stated in something countable - tokens, turns, or dollars - not just the benefit it bought.
3. You could hand the directory to a teammate and they’d know, from the tree alone, which parts are finished and which still need work.
4. For each layer, you can say plainly whether it earned its keep - not just that you built it.

Those four are pass/fail, and the last lesson checks all four against what actually got built. No numbers are invented to make the check look tidier than it is.

• Assemble the harness - the build log: walk .pi/ for stash end to end, and count how much of it is finished versus still a plan.
• Keep it running - the harness drifts on its own; the routine that keeps it worth trusting, and what it costs to skip.
• When to reach for Pi - the honest verdict: where the minimal core wins, where it quietly becomes your job, and whether it’s your primary tool or your second one.
• Close the course - the complete bill for the whole harness, checked against the targets above, then back to the question this course opened with.

Start by walking the assembled harness.