autonomous

/autonomous - End-to-end unattended run

<input_contract> Use when an explicit Product Brief, PRD/delta, or existing clarified project state authorizes unattended work. Use /autopilot instead when the reviewed product JSON queue already exists and the Foundation gate is already closed or truthfully not_required.

Preflight:

• .memory-bank/ exists, otherwise route /mb-init;
• authoritative PRD/brief/delta input exists;
• .memory-bank/workflows/{autonomy-policy,tier-policy,execute-loop,mb-sync}.md exist;
• an executor capable of isolated child contexts is available;
• repository safety policy permits code edits but no unapproved marketplace install, deployment, production write, secret read, or out-of-repo infrastructure change.

If a required workflow is missing, return HALT_POLICY_VIOLATION in the command response only, before creating/reusing the run protocol or making any other durable write. Name every missing path in the reason and state that no run protocol was started or changed; leave any existing .protocols/AUTONOMOUS-RUN/* untouched. The repair owner is the external DevRails installer: from an available DevRails checkout run node scripts/install-framework.mjs --bootstrap --target <project-path> --yes --sync, then resume /autonomous. Do not copy missing workflow rules inline.

If isolated child contexts are unavailable, return HALT_POLICY_VIOLATION with the next feature's fresh tasking, review, and /autonomous resume route. Do not create or change the run protocol or run tasking in the parent context.

If substantial code already exists, require/update the brownfield baseline via /map-codebase before applying the PRD delta.

Create/reuse:

• .protocols/AUTONOMOUS-RUN/plan.md;
• .protocols/AUTONOMOUS-RUN/status.md using the durable run checkpoint contract in .memory-bank/workflows/autonomy-policy.md#durable-run-checkpoint;
• .protocols/AUTONOMOUS-RUN/decision-log.md;
• .tasks/TASK-AUTONOMOUS/.

Record run metadata, scheduler mode, review coverage, blocking decisions, applied authoritative policies, queue summary linked to JSON records, failure budget, and terminal state/reason. The run protocol is resumable orchestration state, not a second task registry. </input_contract>

<hard_invariants>

• Follow tier policy #tier-obligations and #closure-authority; load #hard-write-boundary only for a task/parallel boundary and #tier-classification-and-escalation only for a tier gap. Follow autonomy policy #phase-ownership, #experimental-parallel-execution when opted in, #durable-run-checkpoint, #required-gates, #failure-budgets, #scheduler-failure-handling, #terminal-fallback, #run-state, and #terminal-states, plus execute-loop #planning-redesign-boundary, #fresh-feature-tasking-boundary, and the applicable mb-sync contract.
• Canonical queue execution is sequential.
• --experimental-parallel remains opt-in and uses only existing autonomy-policy isolation rules. Never infer independence from advisory touched_files.
• Queue/task metadata comes only from indexed JSON task records. Preserve task schema, IDs, lifecycle planned|ready|in_progress|blocked|done|done_for_prod|failed, tier, waves, Foundation dependencies, and hard runtime scopes.
• During the Foundation phase, /autonomous owns promotion, selection, and final lifecycle decisions only for indexed feature: "FT-000" records. After the Foundation gate is done, /autopilot owns those scheduler decisions only for product records. /exe owns ready -> in_progress for the concrete task selected by either scheduler. Neither phase may adopt or mutate the other phase's tasks.
• /autonomous must not restage /autopilot's product-queue algorithm or reinterpret its task transitions. /exe, /verify, /red-verify, and /mb-sync keep the ownership defined by tier policy #closure-authority.
• The active scheduler writes every task closure/failure/blocking decision, status, and evidence link to the authoritative .task.json before any sync boundary.
• /mb-sync reconciles already-written state once per wave unless an explicit current-wave durable-state dependency requires an early sync; it never chooses closure or promotion.
• Required reviews, lint, doctor, and tier-policy.md#tier-obligations gates are not bypassed.
• Preserve failure budgets and all existing terminal states; do not add a scheduler, status, lifecycle, or assumption registry. </hard_invariants>