[pasilastbot]

Why

Greenfield projects with large Epics stall in the loop. In a real session, 50 prompts didn't move the work, because:

• a review had used both rounds;
• the packet was over the length limit;
• 18 suspended selections blocked new work;
• no human gate was left to answer.

None of these is enforced by the server. They are stops in the instructions (USER:2026-09-29, Pasi).

What autopilot is

A human grants it once, for a scope and until a date. It is recorded with its USER: source.

Rule	Normal	Autopilot
Entry gate	Human answers	Agent answers, citing the grant
Cold review	2 blocking rounds	1 pass, plus at most 1 narrow confirmation. Findings are folded into the packet as tests, or logged.
Preflight holds, refusals	Stop	Cleared once with the documented verb, or logged as a gap record, and the agent moves on
Product questions	Asked; the loop waits	Asked. A reversible one gets an assumed default that is recorded and continues. The agent waits only on data loss, security, money or outside contracts.
Tests first, evidence, sources	Required	Required
Merge, deploy, completion	Human	Human, at sprint end: one independent review and one page (built, assumed, logged, findings). Accept or reject per item.

Files

• PROCESS.md: §Autopilot under Work scope. One-line pointers from Authority, Gates and the cold-review round bound.
• skills/rdd-autopilot/SKILL.md: start, per-item loop, refusal handling, questions, sprint end.
• rdd-start routes to it and does not stop on preflight facts under a grant. rdd-cold-review notes the single pass. AGENTS.md and README.md list it.

Loop

This is process material, so it is meta-work for this repository and has no requirement record.

Rollout

Independent of #31 (small-change lane). Both add a subsection under Work scope, so the second one merged needs a trivial rebase. It reaches consumers when the modernpath CLI kit re-pins and a CLI release ships, after production promotion.

🤖 Generated with Claude Code