Data for sites and agents

Specification

1. Everything Brand decides is also data, generated on every build from the same source as the pages: /units.json (the register with colours, orders and the ring's geometry), /manifest.json (every published mark file, with its size), /tokens.json (the whole system in DTCG: colour, typography and shape), /tokens/contrast.json (every proven pairing), /fonts/fonts.json (every font file, its coverage and the fit test), /anatomy.json and /standards.json (what every site has and the standards the checker runs) and /llms.txt (the rules as plain text).
2. Addresses do not change: a file may gain fields, never lose or rename one without a decision. The web fonts carry a content hash in their name and the Office package the font version, so caches may keep them for a year.
3. Every file carries its generation date as version (version or generated). Numbered versioning and its changelog come with 5.4.
4. All are served with Access-Control-Allow-Origin: *, so any AKRIBIS site or tool reads them from another origin.
5. llms.txt is the rules for agents: the English specification of every proposed or ratified topic with its status, the open questions of the others, how to use the tokens and the marks, the register with its colours, the file index and the list of decisions. It is regenerated on every build and replaces the design part of Kanon.
6. The page and the data cannot disagree: this site's components read those same files, and the build fails if llms.txt names an address it did not publish.
7. Two more files (ADR-0031): /strings.json, the texts of the shared layer in the three languages (brand/strings.yaml), and /units.schema.json, the JSON Schema that units.json already named. The same data travels inside @akribis/site at the build's version.

To re-reason

• Numbered versioning and a changelog, with 5.4.
• Whether llms.txt should also carry the rules in Spanish and Portuguese, or one file per language.
• Schemas for manifest.json, fonts.json and strings.json.

Evidence to audit

• brand/src/llms.ts · brand/src/data.ts · public/_headers
• INN0VAR/kanon-standard · design-system.md (the design part llms.txt replaces)
• llmstxt.org (the file's convention: a title, a summary, sections with links)

Delivers

• units.json
• manifest.json
• tokens.json
• contrast.json
• fonts.json and llms.txt
• at stable addresses and with CORS.

Decision

• ADR-0022 Publish the brand as data at stable addresses, with llms.txt as the rules for agents Proposed
• ADR-0031 Deliver the shared layer of every site as one Astro package with a starter, and check each build inside it Proposed