Use Reference
Use Reference when you need an exact value or contract. Use Guides for procedures and API Reference for endpoint behavior.
Find the Canonical Answer
Section titled “Find the Canonical Answer”| Question | Canonical page |
|---|---|
| What does this public term mean? | Glossary |
| Why did this request fail? | Error Codes |
| Which setting controls this behavior? | Configuration Keys |
| Which configuration source wins? | Configuration Order |
| What is the current default or limit? | Defaults and Limits |
| What exit status does automation receive? | CLI Exit Codes |
| Which runtimes and version combinations are supported? | Compatibility |
| Which packages and images belong to one release? | Release Map |
| Which bytes and JSON fields are interoperable? | Wire Contracts |
| How do I answer a likely product or operations question? | FAQ |
Read Values by Layer
Section titled “Read Values by Layer”- Product language is the terminology shown in the web console and SDK facades.
- Runtime configuration controls the CLI, SDK loaders, and deployed services.
- Protocol behavior covers HTTP fields, raw JWT claims, status codes, and schemas.
- Release behavior covers SemVer, package lockstep, images, and documentation versions.
Do not substitute a protocol name for its public product term. Public surfaces use Session ID and Delegation ID while raw Coordinator and JWT contracts retain fields such as agent_session_id and delegation_edge_id.
Source of Truth
Section titled “Source of Truth”Code, package manifests, deployment configuration, and checked-in schemas are authoritative. This section explains those sources; it does not create a second contract.
Next Step
Section titled “Next Step”Search FAQ for a question, or open Glossary before naming a product concept in code or documentation.