Reference
Reference
Find terminology, maturity, source boundaries, common questions, and the route from explanatory pages to canonical and normative material.
This section helps you interpret the documentation correctly. It is not a duplicate of repo.blue or the normative specifications.
Terms
Glossary
Look up Blue document, BlueId, Root, Timeline, feeder, Mandate, PayNote, provider, and related terms.
QuestionsFAQ
Resolve common category errors and choose the right architecture for a use case.
Exact materialImplementations and source material
Move from explanatory documentation to exact repositories, fixtures, APIs, and release history.
Documentation hierarchy#
| Surface | What it should be authoritative for |
|---|---|
| language.blue | Explanation, concepts, tasks, patterns, and solution narratives |
| Playground | Demonstrated behavior of the deployed example and inspector |
| MyOS | Product behavior and operating experience |
| repo.blue | Canonical package nodes, exact types, dependencies, and BlueIds |
| Specification repositories | Normative algorithms, rules, and conformance requirements |
| Implementation repositories | APIs, source code, fixtures, releases, and implementation status |
When an explanatory page and an exact artifact differ, the page must defer to the canonical or normative source and identify the mismatch as a documentation issue.