Stage 3: Plan across repositories

Concept — agent orchestration and context isolation

You leave with — an orchestration plan and two agent briefs

Orchestration is not launching more agents. It is deciding who knows what, who does what, and who decides what.

Produce three artifacts

   docs/plans/orchestration-plan.md
   docs/agent-briefs/tta-implementation-brief.md
   docs/agent-briefs/processor-implementation-brief.md

Each implementation brief is a contract:

   ┌─────────────────────────────┬─────────────────────────────┐
   │ Outcome                     │ Tools allowed               │
   │ Authoritative inputs        │ Acceptance criteria owned   │
   │ Repository scope            │ Dependencies on the other   │
   │ Allowed areas               │ Expected return shape       │
   │ Excluded areas              │ Stop conditions             │
   └─────────────────────────────┴─────────────────────────────┘

Stop conditions matter far more than they look. A line like “if the specification is silent on X, stop and report rather than choosing” is what prevents an agent inventing a business rule at minute twenty-two, in a file nobody is watching closely, with complete confidence.

You may use the planner to propose a decomposition. It does not own the rulings. Which service is authoritative, which contract version you target, and what order things land in are yours.

The rollout question

Derive a sequence in which old and new can coexist safely.

Notice what that question is not. It is not “which side matters more”. It is “which combinations of deployed versions are safe while the change is in flight” — and a change can be perfectly correct in its final state while being unsafe halfway there.

⌘  python3 scripts/run_pair_verification.py --explain

◆ Predict #3 — reopen Prediction #1

You sealed an answer in Stage 0, blind. You now know the seam and the specification.

Would you change your answer? What did you not know when you made it?

Write the revision next to the original. Keep both — the gap between them is the lesson.

⌘  python3 .claude/scripts/validate_plan.py
⌘  /hand-off

---