Evaluate
Start with the narrative
Use the overview material when you need the adoption story, the positioning, and the business or standards rationale before implementation details.
Documentation Entry
Specification, conformance, guides, governance, and proof.
`/docs/` is now the curated starting point for the documentation experience. Existing deep links across `/about/`, `/getting-started/`, `/spec/`, `/reference/`, `/integrations/`, `/proof/`, and `/governance/` remain intact.
Start By Intent
Choose the slice of the corpus you actually need.
The docs corpus is broad. This entry page is here to shorten the path from intent to the correct source.
Implement
Start with the contract
Read the implementation guide, quick start, schemas, and conformance materials when you are building a real parser, issuer, or consumer.
Reference
Go directly to the normative anchors
Spec versions, resolver API details, governance, and the changelog remain the source of truth for public contract behavior.
Proof
Use the browser-visible evidence tier
The sandbox, harness, workbench, and journeys provide the concrete public proof that the standard is usable, inspectable, and testable.
Agents And Integrators
Documentation now sits beside an explicit discovery layer.
If you are a machine consumer or you are setting up machine-facing support, start with the public discovery files, then move into the docs sections that actually govern your use case.
Deep Route Stability
This is a new entry point, not a corpus rewrite.
The visible shift is about public comprehension and routing. It does not require breaking or renaming the existing standards and reference URLs that already circulate publicly.
/about/ /getting-started/ /spec/ /reference/ /proof/ /governance/