Specification

The normative prose, in reading order. Where the JSON Schema or an example disagrees with it, the prose wins.

  1. Overview — What CoffeeJSON is, the design rules, and how to read the spec
  2. Document envelope — The top-level shape: the coffeejson version string, recipes[], beans[], tastings[]
  3. Recipe — Recipe fields: quantities, basis, steps, grind, gear, attribution, scaling
  4. Bean — Bean identity: roaster, origin, process, roast level, altitude
  5. Tasting — How a brewed cup turned out: the drinker's impression, and what an instrument read
  6. Vocabularies & registries — The controlled value sets, how they extend, and the fallback rules
  7. Versioning & conformance — Compatibility contract, reserved extensions, what conformance requires

Beside the specification

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.