role-model protocol and routing
The canonical role-model protocol and the routing semantics built on top of it.
This site explains two things in depth:
- the canonical role-model protocol under
protocol/ - the reference routing flow that consumes protocol artifacts and emits explainable decisions
The protocol is the source of truth. The router matters because it shows how endpoint identity, declared
capabilities, observed performance, roles, tasks, and policy become a concrete RouterDecision.
EndpointIdentity
What concrete endpoint the router can choose.
DeclaredCapabilityProfile
What the endpoint claims to support.
ObservedPerformanceProfile
What measurement says the endpoint actually does.
Role / Task / Binding context
Execution intent and endpoint-role compatibility.
RoutingPolicy
Hard constraints plus optimization intent.
RouterDecision
Eligibility, scores, chosen endpoint, fallbacks, and reasons.
Trace / Usage / Feedback
Execution artifacts that become future measured evidence.
What to read first
| If you want to understand... | Start here |
|---|---|
| what role-model actually standardizes | /introduction |
| the protocol vocabulary and object graph | /core-vocabulary, /protocol-object-model |
| endpoint identity and profile semantics | /protocol/endpoint-identity, /protocol/declared-capability-profiles, /protocol/observed-performance-profiles |
| how routing works end to end | /routing/how-routing-works-end-to-end |
| why a router accepted or rejected a candidate | /routing/eligibility-and-rejection, /reference/reason-codes-and-rejection-taxonomy |
| the field-level schema inventory | /reference/canonical-schemas-reference |
Site structure
- Overview explains the protocol boundary, vocabulary, object model, and lifecycle.
- Protocol defines the canonical objects and their field semantics.
- Routing explains how the reference router evaluates, scores, selects, and records outcomes.
- Reference collects schema-by-schema and reason-code reference material.
Canonical sources
protocol/README.mdprotocol/schemas/*.schema.jsondocs/decisions/0001-protocol-is-canonical.mddocs/decisions/0004-observed-performance-is-first-class.mddocs/protocol/*.mdrole-model-router/packages/core/**