I3790 — The design book declares one mechanism, its tokens and its gate for code, charts, controls, embeds and shell blocks
Add one section to docs/DESIGN_SYSTEM.md per rendered element kind (code and syntax, charts, interactive controls, embeds, shell blocks) that names the one mechanism every surface uses, the design tokens it reads, the marker class a gate looks for, and the gate that refuses a second way, so a contributor learns the rule where the rest of the design system is written.
BLOCKED wave 1 · p1 · implementation profile · parallel safe
Blocked. This issue cannot start until I2747 is done. The status is derived from that, not declared.
Objective
Add one section to docs/DESIGN_SYSTEM.md per rendered element kind (code and syntax, charts, interactive controls, embeds, shell blocks) that names the one mechanism every surface uses, the design tokens it reads, the marker class a gate looks for, and the gate that refuses a second way, so a contributor learns the rule where the rest of the design system is written.
Why
On 2026-10-20 docs/DESIGN_SYSTEM.md did not mention syntax highlighting, syntax colours or the highlighter, and its kit section listed the terminal, copy, tabs and chart components without saying which surfaces must use them; nothing a contributor reads says that /ui and the Cockpit must not grow their own.
Current state
DESIGN_SYSTEM.md names the monospace stack (line 33), the contrast threshold (line 264) and the kit components (150-205); tokens.yaml has font.mono, sunken and series-1..8 and no syntax roles.
Desired state
Five sections, each with mechanism, tokens, marker class and gate, linked from the kit section; I2747's code-* roles are listed with their contrast pairs; the marker class for a highlighted block is the one I3002's copy control attaches to.
Scope
- docs/DESIGN_SYSTEM.md
- share/design/tokens.yaml
Dependencies
Acceptance criteria
- DESIGN_SYSTEM.md has a section for each of the five kinds naming mechanism, tokens, marker class and gate
- Every gate a section names exists and is registered in gates.yaml
Validation
- bin/majordomus plan validate
- scripts/ci/design-check
Evidence required
- design_book_names_existing_gates_case
Evidence
None recorded. Every token above needs a command or an artifact behind it before this issue can be completed; narrative is refused.
Timeline
- started
- —
- verified
- —
- completed
- —
Those three fields, the evidence above and the state of the dependencies are all the status is made of. There is no status field to disagree with them.
Canonical record: .ai/repo/project/issues/I3790.yaml. Read it back with majordomus plan show I3790.