Intent Router
Agents overview · Intent router overview · ① Route contract reference →
Implementation guides for Plane ① of the Agents Blueprint.
THE CLAIM
Route before the loop. The router owns dispatch and trace; the agentic app owns manifest pin and orchestration. The LLM never sees tools from routes that were not selected for this turn.
Five playbooks
| # | Playbook | One-line purpose |
|---|---|---|
| ① | Route contract reference | Field dictionary: route, activation_target, manifest, policy, retrieval, memory |
| ② | Route table lifecycle | Versioned contracts, storage patterns, promote and rollback |
| ③ | Layered classifier | Eligible routes, rules (channel / event), classifier, LLM fallback, safety |
| ④ | Wire agentic app | Front door, decide-only handoff, event bind, PGAR start |
| ⑤ | Routing eval CI | Golden set, release gates, incident replay |
Recommended path
- Route contract reference: define the row fields before writing classifier code
- Route table lifecycle: version, store, promote, roll back
- Routing eval CI: golden set in parallel with Layer ①-②
- Layered classifier: implement the pipeline
- Wire agentic app: route pin, async start,
correlation_id; app copies the freeze
Bridge reading: PGAR Agentic app · Eval Plane ①: Input · Manifest registry.
Who should read what
| Role | Start with | Then |
|---|---|---|
| AI platform | Route contract reference, Layered classifier | Wire agentic app |
| Domain squad | Route contract reference, Route table lifecycle | Routing eval CI |
| Governance | Routing eval CI | Eval Input plane |
Read next
① Route contract reference → · After wiring: Orchestration (Plane ②)