pilot-puppylisted

# Pilot Puppy Use Pilot Puppy when work must survive sessions, hosts, or interruptions and a cold reader should know the Outcome, current move, proof, and next decision. Skip it for a factual answer or an obvious one-step edit with no handoff. ## Worklane boundary Pilot Puppy supports the project currently being worked on; it is not a global gate for every project. Its own open proof must not stop another product from shipping the highest-value reachable row in that product's canonical plan. “One bounded task” keeps a handoff reviewable—it does not make the fleet single-threaded or defer safe, obvious in-scope improvement. ## Start every cycle 1. Read repository instructions and the repository-owned `PLAN.md`. 2. Inspect the exact Git revision, worktree state, and proof named by the plan. 3. Resume an in-progress item; otherwise take the highest unblocked item. 4. Make one bounded, reversible change and run the real repository gate. 5. Record result, proof, uncertainty, and one exact resume move in `PLAN.md`. Never overwrite unexplained work or create a second queue. A commit, worker message, or receipt is not acceptance proof by itself. ## Delegate one task Use the active host directly for normal work. For a bounded handoff, use: ```bash pilot-puppy route \ --repo <exact-clean-worktree> --task-file <frozen-task> --task-id <id> \ --task-kind plan|hard-dev|dev|debug|review|lead \ --out <project>/.pilot-puppy/evidence/<id>.route.json pilot-puppy host run --host