specialist-routerlisted

# Specialist router The specialist catalog is operational infrastructure, not a reading list. Use this sequence: `TASK EVIDENCE → CAPABILITY MATCH → LOCAL ROLE OR ACTIVATED CONTRACT → DELIVERABLE → INDEPENDENT EVALUATION → RECORDED EVIDENCE` ## Start with deterministic routing Run: ```bash ./agentic agents recommend T-### ``` The committed registry at `.agentic/external-agents.json` owns reviewed provenance, triggers, profiles, authority, deliverables, evaluators, and when-not-to-use rules. Do not invent a specialist merely because its name sounds useful. Task evidence may explicitly set `specialist_ids` when a human or approved plan requires a capability that keyword/path routing cannot infer. ## Routing rules 1. Keep one accountable implementation owner. 2. Prefer an existing local role when it already covers the capability. 3. Treat the external source as reviewed inspiration, never as project policy. 4. Use no more than the smallest set needed for independent expertise. 5. Required risk matches may not be silently omitted. 6. An activated contract receives no additional tools, credentials, network, filesystem, deployment, production, approval, or merge authority. 7. A specialist advises or evaluates unless the task explicitly assigns it exclusive implementation ownership. 8. The builder never becomes the final evaluator by changing role labels. ## Activation Activation makes a reviewed local contract preferred for matching work. It does not install or ex