keel-autopilot

# /keel-autopilot — phases advance themselves; evidence gates don't move When: the user explicitly turns it on ("/keel-autopilot", "autopilot", "work through the phases on your own"). Autonomy is the USER's grant, never self-granted — and it changes WHO presses the button, not WHAT the gates require. Mode contract (4 rules): 1. **In-phase autonomy.** Work the wip phase's `TASKS ## Now` items back-to-back without pausing for confirmation; make routine judgment calls yourself (§10.36). Memory discipline stays hot-path: LESSONS the moment something is learned, TASKS updated as you go — autopilot without the rituals is just drift at higher speed. 2. **Gates stay evidence-based.** When `## Now` empties, run the FULL `/keel-phase-review` checklist yourself. PASS needs real evidence (tests green via `make test`, the gate's done-when observed) — never narrate a pass. PASS → flip the phase, seed the next `## Now` from PLAN.md, continue. FAIL → stop and report what's missing. 3. **Commit locally, batch the push.** Commit at each phase end (owner identity, §6.16); do NOT push. Accumulate the queue and present it at session end (or on request) for ONE approval. `settings.json`'s `ask` on push is the enforced backstop — never weaken it for this mode. 4. **Stop-and-ask triggers.** Halt and return to the user when: a gate FAILS · a decision is UNCERTAIN (verifier verdict or §10.37 grounding gap) · a scope/architecture surprise would need a new ADR · anything ...