longshotlisted

<!-- Generated from https://github.com/nielsmadan/agentic-coding — edits here are overwritten. --> # Longshot Take a brief, settle its consequential decisions with the user, prepare the plan, then get final approval to start implementation and build without check-ins. **Preparation needs the user; implementation is autonomous.** Until the Phase 2 start gate is approved, stay read-only and wait for answers to every question you ask. Silence, an empty tool response, a preselected recommendation, elapsed time, and the initial longshot invocation are never answers or start approval. The autonomous contract below applies only after that gate, including its stop rules and troubleshooting advice. A fresh longshot run needs its own start approval; a previous run's ledger does not authorize new scope. ## The contract Approving the implementation start authorizes staging and implementation commits for the run's work in its writable repos, including on the primary repo's current branch. Honor any explicit limits the user gives. Do not ask for a separate commit confirmation. Final squashing requires its own approval under Phase 6. State it back to the user at the implementation start gate, verbatim in substance: 1. **Every question up front.** Finish the interrogation and planning, then wait for the user's final go-ahead. Announce implementation starting; only then are there no more questions except the four stops below. 2. **Rulings, not stalls.** Every conflict, gap, plan