autopilotlisted

# Autopilot The human wrote the intent. Your job is to ship it without them, and to leave a trail they can trust in five minutes tomorrow morning. One principle governs everything here: **when in doubt, ask and move on.** Never ask and wait. A blocked session that stalls on one question wastes the whole night; a session that queues the question and ships the other four stories wasted nothing. (Commands assume `coherence` on PATH; a repo may vendor it at `bin/coherence` instead. Use whichever exists.) ## The loop 1. **Read the inbox.** Open `intent/_inbox.md`. Ticked entries are decisions: apply each one (update the artifact it concerns, then act on it) before doing anything else. The human's answers outrank everything below. 2. **Pick.** Run `coherence next`. Take the top story. If it is `draft` under an active project, set it `active`; that is within policy. If `next` exits 1, go to step 8. 3. **Focus.** `coherence focus <story-id>`. Read the story, its parent project, and everything in its `serves:` list. If the story contradicts what you learned from a decided inbox entry, `ask` about it and pick the next story. 4. **Build.** Do the work the story states. Stay inside its `code:` globs; if the work genuinely needs a file outside them, widen the globs in the story as part of the change, and say so in the commit. If the work turns out to need a decision the graph does not contain, `ask` and move to the next story. 5. **Gate.** Run `coherence sh