autopilotlisted

# Autopilot A thin autonomous **conductor** for large missions: autonomous scoping, self-drive, durable cross-session state/recovery, and a hard user `STOP` gate. It owns no lifecycle machinery itself; it delegates every bounded wave to `orchestrate` and every decision/software change to `implement`/`deliver`, then records the durable pointers. See Entry gate below for when to use this tier instead of `orchestrate`, `implement` or `diagnose`. It is **higher-authority** than `orchestrate`'s pre-scoped autonomous-implementation mode, which stops at a user PR gate; autopilot keeps going until a user writes `STATUS: STOP`. Claude Code and Codex are equal operators; Codex operators read [codex-operator.md](references/codex-operator.md) first. ## Entry gate Needs all of: an open-ended mission too large for one bounded wave, a survivable-crash requirement, and an explicit user STOP gate as the only clean exit; otherwise use a lighter-weight skill. ## Bootstrap 1. Run `scripts/bootstrap-autopilot.sh <mission-id>`, fill every CONFIG KNOB, then rerun to substitute/validate. See [state-contract.md](references/state-contract.md) for the file set and `.agent-run/<mission-id>/` location. 2. Use `orchestrate` for every bounded wave: it owns topology, provider routing, Agent Fabric transport, the review ladder and degradation. Delegate decisions/software change to `implement`/`deliver` and record the returned route/result in `QUEUE.md`. 3. Operate one iteration at a