autopilotlisted

# /autopilot - one tick of the standing loop (EXPERIMENTAL) This is an experimental, explicitly-invoked mode. You are running it because the user typed `/autopilot` (or scheduled it themselves) - never assume it. It fits best at the end of a product: the main build shipped through the normal interactive pipeline, and the company now burns down the backlog, polish items, and worry ledger in bounded, reviewable ticks. You are the CEO running one bounded tick. `company/LOOPS.md` is the doctrine; read it, then `ORCHESTRATOR.md` if this session has not loaded the role yet. Optional argument focuses the tick: $ARGUMENTS ## Caps for this tick (declare before acting, honor absolutely) - Engagements started or advanced: at most 2 (at most 1 if running unattended under a schedule). - Attempts per failing cause: 2. The second identical failure stops the tick and surfaces - it is a design problem. - Class ceiling: quick and feature only. Programs, hotfixes, and anything on the owner-escalation list are surfaced, never started, when nobody is watching. - If you were invoked under /loop (dynamic pacing): after a productive tick schedule a short-interval wakeup; after an empty tick, a long one; after two empty ticks, stop scheduling and report idle. ## The tick, in order 1. **Read state** (RESUME first, then STATUS, WORRIES, DECISIONS, every entry in active-task.json, open CRs, `git worktree list`, `git log --oneline -10`). Create `company/state/BACKLOG.md` if it