knowledge-router · diff
git:20260715.f00df98 to git:20260716.fa2dea2
53 added, 17 removed. Audit A to A.
---
name: knowledge-router
- description: Route a question or source event to the right knowledge sources, owners, and follow-up skill.
+ description: Route one question or source event through a supplied knowledge catalog to validated source, owner, escalation, and follow-up skill references. Use for evidence discovery and ownership routing, not broad business-action fanout or answering the question itself.
runx:
category: ops
---
# Knowledge Router
- Route one question, source event, or support thread to the right knowledge
- sources and follow-up path.
+ Produce a validated retrieval and ownership route from a bounded source
+ catalog. This skill decides where evidence should come from and who owns the
+ answer; it does not answer the question or perform the follow-up operation.
- This skill is for triage and routing, not answering the question directly. It
- should tell a consuming graph where to look, who owns the domain, what evidence
- is already available, and which next skill should run.
+ `business-ops` routes a business signal across action lanes such as release,
+ outreach, spend, and proof. `knowledge-router` instead resolves references
+ inside an explicit knowledge catalog. Its deterministic validator rejects
+ invented sources, owners, and skills.
- Each route must name the supplied signal that justified its source match,
- owner, escalation, and next-skill recommendation. Keep the result as a concise
- dispatch note. Return `needs_more_context` when no route is supportable, and
- `manual_review` for legal, billing, security, or destructive requests.
+ ## Source catalog
+ Supply:
+
+ ```json
+ {
+ "sources": [
+ {"id": "auth-docs", "kind": "docs", "summary": "API authentication and key scopes"}
+ ],
+ "owners": [
+ {"id": "security-team", "domains": ["authentication"]}
+ ],
+ "skills": [
+ {"id": "research", "purpose": "Resolve a bounded source-backed question"}
+ ]
+ }
+ ```
+
+ Every selected reference must exist in the corresponding catalog collection.
+ The route may return no follow-up skill when more context or manual review is
+ the honest outcome.
+
+ ## Procedure
+
+ 1. Match the question or event to supplied source summaries and owner domains.
+ 2. Propose the smallest source set needed to resolve the question.
+ 3. Select an owner only when the catalog supports the ownership relationship.
+ 4. Select a follow-up skill only when its declared purpose matches the next job.
+ 5. Use `manual_review` for consequential legal, billing, security, privacy, or
+ destructive decisions—not merely because the topic belongs to those teams.
+ 6. Validate every source, owner, and skill reference deterministically.
+ 7. Return `needs_more_context` when no supported route exists.
+
## Output
- - `route`: selected knowledge or ownership domain and rationale.
- - `source_matches`: relevant sources with the matching signal.
- - `owner_recommendation`: owner or escalation target.
- - `next_skill`: the bounded follow-up capability, if one is justified.
+ - `route`: domain, rationale, and validated source references.
+ - `source_matches`: validated source references and matching signals.
+ - `owner_recommendation`: validated owner reference, rationale, and escalation
+ posture, or `null`.
+ - `next_skill`: validated skill reference and rationale, or `null`.
+ - `verdict`: `routed`, `needs_more_context`, `manual_review`, or the
+ deterministic validator's `refused` result for an invented reference.
+ - `validation`: catalog digest inputs, invalid-reference findings, and result.
## Inputs
- - `question` (required): user question, event, or thread summary to route.
- - `available_sources` (required): source catalog, docs, systems, or owner map.
- - `constraints` (optional): allowed systems, sensitivity, or preferred owner.
+ - `question` (required): question, event, or thread summary to route.
+ - `available_sources` (required): explicit `sources`, `owners`, and `skills`
+ collections.
+ - `constraints` (optional): allowed sources, sensitivity, excluded systems, or
+ preferred owners. Constraints are not authority.