Fusion Orchestration

Separate judgment from mechanical implementation. A lead investigates, decides, specifies, reviews, and verifies. An executor edits only the bounded scope in the lead's specification.

Route Deliberately

Do not force every task through Fusion:

• Keep a tiny, already-understood, single-file mechanical change in the normal writable session.
• Use Fusion when investigation, architectural judgment, multiple non-trivial writes, or independent review materially improve the result.
• Offer a durable PRD, ADR, or implementation plan only when persistent artifacts reduce substantial ambiguity. Never create a spec lifecycle merely because a change is large or risky.

Native Adapters

Prefer the installed native roles when the current tool exposes them: