cross-agent-repair-routing

Topics in the source

• Cross-agent repair routing
• 1. Establish the authority map before touching anything
• 2. Ruling on the claim
• 3. Reproducing a defect report
• 4. The tree is shared and may already be published
• 5. Loop control
• 6. Escalate with a landing zone
• Pitfalls

You found a defect, you may not fix it (wrong write surface), and the tree is shared with other agents plus an automated publisher. This skill is the loop that gets it repaired without you overstepping or turning the thread into chatter. For the per-artifact detail behind each step, load delegated-work-acceptance (verify one sender's delivery) and report-claim-audit (audit a digest). For a defect that keeps coming back on one code path, references/fixing-a-defect-class.md turns the findings into an invariant the fixer must satisfy. Roles, not names: the front door classifies an incoming report and routes it; the builder owns the code path; the domain owner owns a subsystem's rules and review; the operator owns runtime/config landings, credentials, and session state. Your write surface is your own role contract; the defect belongs to whichever role owns the file, not to whoever noticed it. Read your own role contract and the fixer's: your write list, theirs, and what needs the operator. Operator-only lanes travel intact: runtime/config changes, shared-repo landings, commits, credential or session state. Never widen a request to "just fix it" because the fix is two lines. Write down

This is an excerpt. Refer to the complete source and its current requirements.