Autopilot

<Purpose> Autopilot is the first-class canonical orchestrator for hands-off delivery. Its defining default chain is mandatory:

$deep-interview -> $ralplan -> $ultragoal

The chain is not a list of optional hints and Autopilot is not an alias for direct execution. Autopilot supervises each child stage in one recoverable session, carries durable artifacts forward, and continues through implementation verification until the requested outcome is complete or a genuine blocker is recorded. </Purpose>

<Use_When>

• The user explicitly invokes $autopilot.
• The user asks for end-to-end autonomous delivery from an idea, issue, or requirements seed.
• The work needs requirements clarification, consensus planning, durable execution, and evidence-backed completion as one supervised workflow. </Use_When>

<Default_Chain> Run or resume these stages in order:

1. deep-interview, clarify intent, scope, non-goals, constraints, acceptance criteria, and unresolved decisions. Produce a durable requirements/specification handoff. Deep Interview is a real stage; do not replace it with a one-question check or skip it merely because the task looks actionable.
2. ralplan, turn the clarified requirements into an execution-ready consensus plan with architecture, sequencing, test, and verification guidance. Preserve review evidence as lifecycle evidence, not host-issued security authority.
3. ultragoal, execute the approved plan through durable goals and ledger receipts, implementation, focused verification, cleanup, review, and terminal evidence.

$team, $code-review, and $ultraqa may be used inside the supervised execution when the active Ultragoal plan or verification boundary requires them. They do not replace or weaken the defining three-stage chain.