The design language for the suite, rendered from a versioned source. The language text is canonical in the design language document in the repo’s docs/ tree; its constitution is merged law, and these pages carry it section by section. Where a page has a machine source — the design tokens, the decisions log, the haptics chapter — the page is generated from that source and CI fails if it drifts.

Every page carries a status badge: LAW, PROPOSAL, or CONCEPT. That is the roadmap-honesty rule applied to the docs themselves, and a CI gate checks each badge against the status its source document records.

• Foundations — tokens, colour/accent law, type, motion, haptics, sound, vector/resolution law, voice, themes & the dynamic base, appearance settings, the capability ladder.
• Device chapters — tray popover, full window, web, mobile touch, small/ambient.
• Components & patterns — anatomy, states, the friction ladder, the cheatsheet.
• Governance — performance budgets, security presentation, decisions log, roadmap labelling, how a rule becomes law, CI gates.