Specification
The normative prose, in reading order. Where the JSON Schema or an example disagrees with it, the prose wins.
- Overview — What CoffeeJSON is, the design rules, and how to read the spec
- Document envelope — The top-level shape: the
coffeejsonversion string,recipes[],beans[],tastings[] - Recipe — Recipe fields: quantities,
basis, steps, grind, gear, attribution, scaling - Bean — Bean identity: roaster, origin, process, roast level, altitude
- Tasting — How a brewed cup turned out: the drinker's impression, and what an instrument read
- Vocabularies & registries — The controlled value sets, how they extend, and the fallback rules
- Versioning & conformance — Compatibility contract, reserved extensions, what conformance requires
Beside the specification
- Integration guide — The consumer and producer checklists: intake, decode, fallback rules, preservation, authoring lint, share links
- Transport — Carrying a document in a URL or QR code: encoding, size limits, fallbacks
Every page here is also served as markdown at the same path with
.md, and the whole set as one file at
/llms-full.txt. The machine-readable schema
is at /schema/1.0.