This docs site explains Blue through concepts and examples. It should not duplicate the normative specifications. Use this page as the short map to source material.
The public specification repository is the source of truth for Blue 1.0 specifications:
Open the specification repository: bluecontract/blue-spec
The docs should link to this repository instead of hosting a copied specification page. A copied spec page will drift. A teaching page can explain concepts. A spec repository should define normative behavior.
Use these repositories for implementation-facing behavior:
| Repository | Use it for |
|---|---|
| bluecontract/blue-language-java | Parsing and serializing Blue YAML/JSON, resolving types and blueId references, schema validation, list controls, BlueId calculation, snapshots, patches, matching, and base processor foundations. |
| bluecontract/blue-bex-java | Executing Blue Expression Objects as deterministic Blue-data programs that return values, changesets, events, gas, and metrics. |
| bluecontract/blue-coordination-java | Registering and running executable Coordination contracts: operations, sequential workflows, Compute, document updates, triggered events, embedded scopes, checkpoints, and testable processing loops. |
| bluecontract/blue-js | TypeScript/JavaScript libraries for working with Blue content in Node.js and web-facing tooling. |
The flagship weekend package checkout example is embedded in the docs page:
Use the guided explanation first. Expand the full source block on that page when you need to inspect the complete reseller package document.
Docs should answer:
Specs should answer:
Keep that boundary. It makes the docs friendlier and the specs more reliable.