Reference
Overview
Where to go when you need the canonical protocol and schema material rather than the product-facing onboarding path.
This section is for the deeper contract and reference material behind the onboarding and operator guides.
Use Reference when you need
- schema-level field details
- reason-code taxonomy
- the canonical protocol object set
- artifact semantics for decisions, traces, usage, and observed performance
- exact protocol vocabulary instead of product-summary explanations
Core reference reading path
Start here when you want the deeper model:
- /core-vocabulary
- /protocol-object-model
- /protocol-lifecycle
- /concepts/roles-tasks-and-capabilities
- /protocol/roles-and-tasks
- /protocol/router-decision-artifact
- /reference/canonical-schemas-reference
Why this is not the first stop anymore
The public site now leads with install, setup, benchmarking, and operator flow because most new readers need to understand the runtime and routing behavior before they need schema-level details.
Reference remains the canonical deeper layer once that product-level picture is clear.