| name | autopilot-research |
| description | Use when a task needs a durable survey of new academic, technology, or market evidence before downstream specification or production. Not for repository-only project analysis, a simple factual lookup, or work already grounded by sufficient current evidence. |
| argument-hint | <query> [--mode academic|technology|market] [--depth shallow|medium|deep] [--intensity direct|quick|standard|strong|thorough|adversarial] [--no-clarify] [--no-figures] [--from search|analyze|report] |
| metadata | {"group":"entry","fam":"pre","invocation_class":"entry-router","modes":["academic","technology","market"],"blurb":"Shared upfront research that surveys academic, technology, or market sources before downstream routing.","use_when":"Use when a task needs a durable survey of new academic, technology, or market evidence before downstream specification or production.","not_for":"Not for repository-only project analysis, a simple factual lookup, or work already grounded by sufficient current evidence."} |
autopilot-research
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-research.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.
