Part 3 Quiz · The Body

Their files were owned disjointly, enforced by rule — neither maker could touch the other's paths, so a shared tree had nothing to collide over. The instant both need the same file, path ownership can't slice it in two: worktree, merged only when green.

Move the procedure into a skill (a SKILL.md with a when-to-use description); the prompt falls back to intent. Payoffs: consistency (every beat runs the same recorded move) and maintainability (correct the procedure once, and every later beat inherits the fix).

Few, focused tools — stops a confused beat from grabbing a delete_* that never should have been exposed. Idempotent writes — stops retries and double-fires from posting twice. Actionable errors — stops 3 am stalls on opaque failures the loop can't route around.

A self-grader only ever measures how much it agrees with itself: the blind spot that ships a bug is the same one approving the review. 100% means defects are being co-signed, not caught. Health actually looks like a separate checker now and then logging items_found > 0, actions_taken: 0.

Script < read-only LLM < human. The script wins outright whenever the check is a fact (links resolve, tests pass, schema validates) — free, opinionless, unarguable. Keep the LLM for judgment calls and the human for whatever truly needs someone accountable.