| name | autopilot-ship |
| description | Use when an application needs deployment or release configuration, readiness verification, and a ship checklist. Not for ordinary feature implementation or an unauthorized production deployment. |
| argument-hint | <task description (optional)> [--intensity direct|quick|standard|strong|thorough|adversarial] |
| metadata | {"group":"entry","fam":"app","invocation_class":"entry-router","modes":[],"blurb":"Prepare application deployment/release setup and a ship checklist.","use_when":"Use when an application needs deployment or release configuration, readiness verification, and a ship checklist.","not_for":"Not for ordinary feature implementation or an unauthorized production deployment."} |
autopilot-ship
This is a compact pre-approval entry router. Its manifest-owned frontmatter is
the authoritative discovery metadata; it intentionally contains no execution
procedure.
Pre-approval boundary
Use only this router, harness-manifest.json, and core/WORKFLOW.md ยง0.2 to
propose a route. Present the one-time confirmation in core/WORKFLOW.md ยง0.4
unless the same route and scope are already approved. Do not load references
before approval.
Post-approval owner contract
After approval, direct/quick sessions and the standard+ dispatch-depth-1 owner load
capabilities/autopilot-ship.md, then use the Reference Index below. Assigned
stage workers load only their assigned stage contracts.
Reference Index
| File | Load when | Obligation |
|---|
references/owner-execution.md | After approval, by the selected direct/quick session or dispatch-depth-1 owner | Read the complete execution procedure before material work. This is the router's only post-approval reference edge. |
Guard pointer
Follow the portable artifact, worktree, role, and verification guards in the
selected owner contract. Runtime projections must report unsupported mechanics
and must not claim physical instruction masking, token, billing, or cost
savings without verified evidence.
