@nurix/etna 0.18.20 → 0.18.22

package/data/harnesses/code/skills/design/references/personality.md

@@ -1,214 +1,159 @@
 # Personality — the look pipeline
 
-`design.md → derivation → token emission`. One resolved `design.md` (its two machine blocks — see
-[SCHEMA.md](../data/design-md/SCHEMA.md)) becomes three emitted files that *are* the state: no sidecar
-cache, no JSON. `derive-personality.mjs` runs the pipeline: `--check` is the coverage gate that must
-pass before `--emit` writes `personality.css`, `globals.css`, and the `<html>` attributes in `index.html`.
+`design-tokens artifact → --check → --emit`. A look travels as a **design-tokens artifact** — three
+DTCG JSON files whose grammar, payload, and resolution rules are the frozen transport schema,
+[SCHEMA.md](../data/design-tokens/SCHEMA.md). [`derive-personality.mjs`](../scripts/derive-personality.mjs)
+is the reference consumer: `--check` is the coverage gate that must pass before `--emit` writes
+`personality.css`, `globals.css`, and the `<html>` attributes. The emitted files *are* the state —
+no sidecar cache, no intermediate document. (The design.md format exists only as the library's
+curated documentation corpus, `data/design-md/library/`; the machine path reads token files.)
 
 The look comes entirely from the cascade. A surface composes in semantic tokens (`bg-card`,
-`text-foreground`) and reads its personality from the CSS variables this file emits. Switch the resolved
-`design.md`, re-emit, and every surface re-skins with zero JSX edits — the invariant the exemplars are
+`text-foreground`) and reads its personality from the CSS variables emission writes. Swap the
+artifact, re-emit, and every surface re-skins with zero JSX edits — the invariant the exemplars are
 validated against.
 
-## 1. The pipeline
+Every CSS and comment excerpt in this document is pasted from a real emission of the shipped Nurix
+default (`data/design-tokens/nurix/`); gate transcripts are from real runs, with scratch paths
+shown as `<artifact-dir>`.
+
+## 1. The pipeline — artifact in, CSS out
 
 ```
-resolved design.md ──▶ derive-personality.mjs --check ──▶ (green) ──▶ --emit src/styles/
-   (design-primitives          coverage gate:                            personality.css
-    + lever-manifest)          every primitive, dial, token             globals.css
-                               assigned or hinted, or exit 1            index.html <html> attrs
+design-tokens artifact ──▶ derive-personality.mjs --check ──▶ (green) ──▶ --emit <outdir>
+  design.tokens.json           the coverage gate (rules 1–12):             src/styles/personality.css
+  design.tokens.dark.json?     26 primitives + 2 dials + density tier      src/styles/globals.css
+  design.resolver.json         + 34 color roles + typography 3+6,          index-html-attributes.txt
+                               each assigned or hinted, or exit 1
 ```
 
-`--check` never best-efforts (D6/D29): if any of the 26 primitives, 2 dials, density tier, or 34 color
-tokens is unassigned and un-hinted it exits non-zero naming the offending keys, and the `tokens` phase
-gate stays shut. Emission runs only over a document that passed.
+```
+derive-personality.mjs <artifact-dir> [--check | --emit <outdir>] [--theme light|dark]
+```
 
-## 2. Derivation — design.md → primitives and tokens
+**The artifact.** Three files in one directory: `design.tokens.json` (the base set — primitives,
+color roles, typography, and the file-level `$extensions["com.nurix.design"]` payload carrying
+`product`, `provenance`, the dials, and the lever manifest), `design.tokens.dark.json` (only when
+the look has dark values), and `design.resolver.json`. The script resolves them in the resolver's
+deterministic order — concatenate the set files, overlay the selected theme context, resolve aliases
+after overlay — then validates or emits. File shapes, `$type` grammar, and payload spec live in
+[SCHEMA.md](../data/design-tokens/SCHEMA.md); this document covers what emission does with a
+resolved artifact.
 
-Hybrid: **deterministic wherever the document states a value; judgment-with-recorded-rationale for the
-gaps.** The `design-primitives` block already carries all 26 keys (names without the leading `--`) plus
-the dials, so the mapping is near 1:1.
+**`--check` never best-efforts.** It runs the schema's rules 1–12 and exits non-zero naming every
+offending path, so the fix is mechanical; the `tokens` phase gate (and the verify/pre-ship sweeps)
+stay shut until it is green. Over the shipped default, from the skill root,
+`node scripts/derive-personality.mjs data/design-tokens/nurix --check` prints:
 
-| design.md source | Emitted target | Rule |
-| --- | --- | --- |
-| the 24 static primitives (geometric · typographic · surface · iconography · layout · temporal) | `[data-style="<slug>"] { --<key>: <value> }` | 1:1 by name |
-| `density-gap`, `density-inset` | governed refs in `[data-style]`; base set by the tier | via the density mechanism (§7) |
-| `ease-enter`, `ease-exit`, `stagger-delay` (derived — *not* in the 26) | computed at emit | rules below |
-| `lever-manifest.color-tokens.light.<token>` (17 semantic + 17 substrate) | `:root, :root[data-theme="light"] { --<token>: <value> }` | 1:1 by name |
-| `verbosity` · `feedback` | `<html data-verbosity>` · `<html data-feedback>` | dial → attribute |
-| `density-tier` | `<html data-density>` → `[data-density]` base | tier → attribute |
-| `fonts.sans` / `fonts.mono` (equal `font-sans`/`font-mono`) | `@theme inline` font keys + the primitive | §4 |
-| `product-traits` | read by the front gate; **not** emitted to CSS | — |
-
-**Derived temporal** (SCHEMA: computed from `ease-default` and `duration-unit`, never authored, never
-gated):
-- `--ease-exit: var(--ease-default)` — departure mirrors the neutral curve.
-- `--ease-enter` → the emphasized-decelerate arrival curve `cubic-bezier(0.16, 1, 0.3, 1)` (fast in,
-  settles clean); reuse `ease-default` verbatim if it is already a decelerate curve.
-- `--stagger-delay` → `duration-unit × 0.15`, clamped `0–40ms`, emitted as a concrete ms; a snappier
-  tempo staggers less. (`50ms → 8ms`.)
+```
+check PASSED (data/design-tokens/nurix): rules 1–11 OK — 26 primitives, 34 color roles, typography 3+6, payload/manifest/parse-back OK — provenance=default, style=nurix, theme=light
+```
+
+Rule 12 (the emission precondition) is enforced at emit time; `--check` surfaces it as the
+outstanding-hint count (§3). A failing artifact names its gaps — this run is against a scratch copy
+of the default with one color token deleted:
+
+```
+check FAILED (<artifact-dir>): 1 issue(s)
+  - rule 4 — color.warning: missing
+```
 
-**Gaps → hint → write-back.** Where a value needs judgment the document carries a `hint:` line. A hint
-passes `--check` but not `--emit`: emission resolves each hint to a concrete value *and rewrites the line
-with its rationale* so the document stays self-explaining and re-derivable (`contrast-boost: 1.1  #
-derived: dense-grid brief → one step up (was hint)`). Judgment is recorded into the `design.md`, never
-silent — the full convention is [SCHEMA.md](../data/design-md/SCHEMA.md) §"hint convention". After
-resolution no bare `hint:` remains.
+**`--emit <outdir>`** runs only over a passing artifact and refuses while any token carries a hint
+(§3). It writes three files: `<outdir>/src/styles/personality.css`, `<outdir>/src/styles/globals.css`,
+and `<outdir>/index-html-attributes.txt` — the attribute set the project's `index.html` `<html>` tag
+must carry. In real use `<outdir>` is the project root.
 
-## 3. `src/styles/personality.css`
+### The emitted header is the cache record
 
-The token system. The header comment carries the resolved personality — this comment *is* the cache
-record. Values below are one project's (`meridian`, the SCHEMA worked example); the shape is invariant.
+There is no sidecar state file. The header comment of the emitted `personality.css` carries the
+active personality — dials, theme, and the artifact citation with its provenance — and the `<html>`
+attributes carry the same state in markup:
 
 ```css
 /* src/styles/personality.css — operator-UI personality tokens (emitted; do not hand-edit).
  *
- * Active personality — code is the cache. There is no JSON sidecar; these values
- * and the <html data-*> attributes in index.html ARE the state. To change the look,
- * edit the resolved design.md and re-run derive-personality.mjs --emit.
- *   style:     meridian   (<html data-style="meridian">)   — the project's own personality (rosterless)
- *   density:   dense       (<html data-density="dense">)
- *   verbosity: default     (<html data-verbosity="default">)
- *   feedback:  subtle       (<html data-feedback="subtle">)
- *   theme:     light         (<html data-theme="light">)     — light is the default; dark is opt-in
+ * Active personality — code is the cache. These values and the <html data-*>
+ * attributes in index.html are emitted from the design-tokens artifact. To change
+ * the look, edit design.tokens.json and re-run derive-personality.mjs --emit.
+ *   style:     nurix   (<html data-style="nurix">)   — the project's own personality (rosterless)
+ *   density:   standard   (<html data-density="standard">)
+ *   verbosity: default   (<html data-verbosity="default">)
+ *   feedback:  subtle   (<html data-feedback="subtle">)
+ *   theme:     light   (<html data-theme="light">)   — light is the default; dark is opt-in
+ *   artifact:  design.tokens.json (resolved via design.resolver.json)   — provenance: default, sourced 2026-07-04
  *
  * Semantic-token doctrine: components name purpose (bg-card, text-foreground, border-border);
  * this file resolves those names to values. Components never use dark: prefixes or literal colors.
  */
+```
 
-/* ── System baseline: the 26 primitives at neutral operator defaults. ──
- * The safety net if <html> ever carries no data-style. The project's real
- * values live in the single [data-style="meridian"] block below, which
- * overrides these. Improve/extract rewrites that block, never this baseline. */
-:root {
-  /* geometric */
-  --radius: 6px;
-  --shadow-intensity: 1;
-  --border-weight: 1px;
-  --density-base-gap: 1;                 /* the density tier writes this; see the density mechanism */
-  --density-base-inset: 1;
-  --density-gap: var(--density-base-gap);
-  --density-inset: var(--density-base-inset);
-  /* typographic */
-  --font-sans: "Inter", system-ui, sans-serif;
-  --font-mono: "JetBrains Mono", ui-monospace, monospace;
-  --font-weight-normal: 400;
-  --font-weight-strong: 600;
-  --heading-tracking: -0.01em;
-  /* temporal (+ derived) */
-  --duration-unit: 200ms;
-  --duration-fast: calc(var(--duration-unit) * 0.5);
-  --duration-normal: var(--duration-unit);
-  --duration-slow: calc(var(--duration-unit) * 2);
-  --ease-default: cubic-bezier(0.4, 0, 0.2, 1);
-  --ease-enter: cubic-bezier(0.16, 1, 0.3, 1);
-  --ease-exit: var(--ease-default);
-  --stagger-delay: 30ms;
-  /* surface */
-  --contrast-boost: 1;
-  /* iconography */
-  --icon-stroke: 1.75;
-  --icon-size-base: 16px;
-  /* operator layout */
-  --sidebar-width-expanded: 240px;
-  --sidebar-width-collapsed: 56px;
-  --topbar-height: 52px;
-  --side-panel-width: 480px;
-  --side-panel-width-rich: 640px;
-  --modal-width-max: 480px;
-  --form-max-width: 720px;
-  --table-row-height: 40px;
-  /* behavioral fallbacks (match verbosity=default + feedback=subtle) */
-  --label-display: inline-flex;
-  --helper-text-display: block;
-  --tooltip-delay: 500ms;
-  --feedback-press-scale: 0.99;
-  --focus-ring-width: 2px;
-  --focus-ring-offset: 1px;
-}
+Recovery therefore reads two things: the token artifact (the source) and the emitted attributes
+(the active state). `index-html-attributes.txt` from the same run:
 
-/* ── Semantic + substrate color tokens — light theme. ──
- * CASCADE CONTRACT 1 (§6): the doubled selector out-specifies the library's bare
- * :root defaults in @nurix/components/styles.css — but ONLY because <html> carries
- * data-theme="light". A bare :root here loses to the later library import. All 34
- * tokens are set (D6): no consumed token falls back to a shadcn-gray default. */
-:root,
-:root[data-theme="light"] {
-  /* semantic (17) */
-  --background: #ffffff;
-  --foreground: #0f172a;
-  --card: #ffffff;
-  --card-foreground: #0f172a;
-  --muted: #f1f5f9;
-  --muted-foreground: #64748b;
-  --border: #e2e8f0;
-  --input: #e2e8f0;
-  --ring: #6366f1;
-  --primary: #4f46e5;
-  --primary-foreground: #ffffff;
-  --accent: #eef2ff;
-  --accent-foreground: #4f46e5;
-  --destructive: #dc2626;
-  --destructive-foreground: #ffffff;
-  --success: #16a34a;
-  --warning: #d97706;
-  /* substrate (17, the D6 set) — popover/secondary/chart/sidebar the library consumes */
-  --popover: #ffffff;
-  --popover-foreground: #0f172a;
-  --secondary: #f1f5f9;
-  --secondary-foreground: #0f172a;
-  --chart-1: #4f46e5;
-  --chart-2: #0ea5e9;
-  --chart-3: #16a34a;
-  --chart-4: #d97706;
-  --chart-5: #dc2626;
-  --sidebar: #f8fafc;
-  --sidebar-foreground: #0f172a;
-  --sidebar-primary: #4f46e5;
-  --sidebar-primary-foreground: #ffffff;
-  --sidebar-accent: #eef2ff;
-  --sidebar-accent-foreground: #4f46e5;
-  --sidebar-border: #e2e8f0;
-  --sidebar-ring: #6366f1;
-}
-
-/* ── The project personality: the single [data-style] block (D3, rosterless). ──
- * Named after the project — not a preset. This materializes the design.md
- * design-primitives block: all 26 primitives + the derived temporal. It is the
- * one block improve/extract rewrites. density-gap/inset are governed refs (§7),
- * so the global tier and per-surface step still compose. */
-[data-style="meridian"] {
-  --radius: 6px;
-  --shadow-intensity: 0.5;
-  --border-weight: 1px;
-  --density-gap: var(--density-base-gap);
-  --density-inset: var(--density-base-inset);
-  --font-sans: "Inter", system-ui, sans-serif;
-  --font-mono: "JetBrains Mono", ui-monospace, monospace;
-  --font-weight-normal: 400;
-  --font-weight-strong: 600;
-  --heading-tracking: -0.01em;
-  --duration-unit: 50ms;
-  --duration-fast: 100ms;
-  --duration-normal: 150ms;
-  --duration-slow: 250ms;
-  --ease-default: cubic-bezier(0.4, 0, 0.2, 1);
+```html
+<!-- Personality state lives in these <html data-*> attributes — code is the cache.
+     The design-tokens artifact is the source. To change the look, edit design.tokens.json
+     and re-run derive-personality.mjs --emit; to nudge one axis, edit an attribute here. -->
+<html
+  lang="en"
+  data-style="nurix"
+  data-density="standard"
+  data-verbosity="default"
+  data-feedback="subtle"
+  data-theme="light"
+>
+```
+
+## 2. Derivation — token paths to emitted CSS variables
+
+Leaf names are law: a `primitive.*` or `color.*` token maps 1:1 to the CSS variable of the same
+name, without the leading `--`.
+
+| Artifact source | Emitted target | Rule |
+| --- | --- | --- |
+| `primitive.<name>` (24 static) | `[data-style="<slug>"] { --<name>: … }` | 1:1 by leaf name |
+| `primitive.density-gap` / `density-inset` | governed refs `var(--density-base-gap/inset)` in `[data-style]` | the density tier writes the base (§4) |
+| `color.<name>` (34) | `:root, :root[data-theme="light"] { --<name>: … }` | 1:1 by leaf name |
+| dark set `color.<name>` | `[data-theme="dark"] { --<name>: … }` | only when the dark file ships (§5) |
+| payload `product` | `<html data-style="<slug>">` | slugified (lowercase, non-alphanumeric runs → `-`) |
+| payload `verbosity` / `feedback` / `density-tier` | `<html data-verbosity / data-feedback / data-density>` | dial → attribute |
+| payload `product-traits` | read by the front gate; **not** emitted to CSS | — |
+| `primitive.font-sans` / `font-mono`, `font-weight-normal` | `[data-style]` **and** literals in `@theme inline` | §4, two-weight discipline / no self-reference |
+| `typography.family.*` / `typography.ramp.*` | data for emitters and exemplars | reaches CSS only through the primitives it aliases |
+| — (derived at emit) | `--ease-enter`, `--ease-exit`, `--stagger-delay` | computed from `ease-default` + `duration-unit` |
+
+**The preserved-css rule.** For every emitted value the emitters prefer the token's
+`$extensions["com.nurix.design"].css` — the exact source string — so output is byte-stable across
+convert/emit round trips (an aliased token takes its target's `.css`). Absent `.css`, the schema's
+deterministic serialization applies: `dimension`/`duration` as `<value><unit>`; `number`/`fontWeight`
+as the plain number; `cubicBezier` as `cubic-bezier(x1, y1, x2, y2)`; `fontFamily` as the families
+joined with `", "`, multi-word names double-quoted; `color` as the `hex` field when srgb, else
+`oklch(…)`. The parse-back check (rule 9) guarantees the two forms agree before anything is emitted.
+
+**Derived, never stored.** Three temporal variables are computed at emit from `ease-default` and
+`duration-unit` — they are not tokens, not authored, and not gated (do not add them to an artifact):
+
+- `--ease-exit: var(--ease-default)` — departure mirrors the neutral curve.
+- `--ease-enter` — the emphasized-decelerate arrival curve `cubic-bezier(0.16, 1, 0.3, 1)` (fast
+  in, settles clean); `ease-default` is reused verbatim when it is already a decelerate curve
+  (y1 ≥ 0.9).
+- `--stagger-delay` — `duration-unit × 0.15`, rounded, clamped 0–40ms; a snappier tempo staggers
+  less.
+
+Emitted into the `[data-style]` block, directly after `ease-default`:
+
+```css
+  --ease-default: cubic-bezier(0.4,0,0.2,1);
   --ease-enter: cubic-bezier(0.16, 1, 0.3, 1);   /* derived from ease-default */
   --ease-exit: var(--ease-default);              /* derived: departure mirrors the neutral curve */
   --stagger-delay: 8ms;                          /* derived: duration-unit × 0.15, clamped 0–40ms */
-  --contrast-boost: 1;
-  --icon-stroke: 1.75;
-  --icon-size-base: 16px;
-  --sidebar-width-expanded: 248px;
-  --sidebar-width-collapsed: 56px;
-  --topbar-height: 52px;
-  --side-panel-width: 420px;
-  --side-panel-width-rich: 640px;
-  --modal-width-max: 560px;
-  --form-max-width: 640px;
-  --table-row-height: 40px;
-}
+```
+
+**Dial semantics.** The payload's two behavioral dials become `<html>` attributes, and
+`personality.css` carries one block per dial value setting the behavioral variables the lifecycle
+and interaction layers read:
 
+```css
 /* ── Behavioral dials (D4) — orthogonal to the visual primitives. ── */
 [data-verbosity="full"]    { --label-display: inline-flex; --helper-text-display: block; --tooltip-delay: 800ms; }
 [data-verbosity="default"] { --label-display: inline-flex; --helper-text-display: block; --tooltip-delay: 500ms; }
@@ -217,82 +162,166 @@ record. Values below are one project's (`meridian`, the SCHEMA worked example);
 
 [data-feedback="subtle"]   { --feedback-press-scale: 0.99; --focus-ring-width: 2px; --focus-ring-offset: 1px; }
 [data-feedback="minimal"]  { --feedback-press-scale: 1;    --focus-ring-width: 1px; --focus-ring-offset: 0px; }
+```
 
-/* ── Density: global tier → base multipliers (D31). ──
- * The tier writes ONLY the base; --density-gap/inset resolve from it (above),
- * so a per-surface step can re-derive relative to the tier. See §7. */
-[data-density="dense"]    { --density-base-gap: 0.85; --density-base-inset: 0.85; }
-[data-density="standard"] { --density-base-gap: 1;    --density-base-inset: 1; }
-[data-density="spacious"] { --density-base-gap: 1.15; --density-base-inset: 1.15; }
+- `--label-display` / `--helper-text-display` — `compact`/`expert` verbosity collapse form labels
+  and helper text; `full`/`default` keep them. Field chrome reads these, not a JS branch.
+- `--tooltip-delay` — tightens with verbosity (`800ms → 0ms`).
+- `--feedback-press-scale`, `--focus-ring-width`, `--focus-ring-offset` — `minimal` feedback
+  flattens the press and thins the focus ring; `subtle` keeps the operator-default ring.
 
-/* ── Per-archetype density modifier (D31) — relative step on the tier, pure cascade, no JS. ──
- * A surface element carries data-density-step; it re-derives one step off the
- * inherited base (a log-stream runs tighter than a settings form inside the same
- * app). Reads --density-base-* (never itself) so it composes with the tier and
- * never absolutely overrides it. The recomputed --density-gap flows into the
- * library's p-*/gap-* through the @theme --spacing remap (§4). */
-[data-density-step="tighter"] { --density-gap: calc(var(--density-base-gap) * 0.85); --density-inset: calc(var(--density-base-inset) * 0.85); }
-[data-density-step="looser"]  { --density-gap: calc(var(--density-base-gap) * 1.15); --density-inset: calc(var(--density-base-inset) * 1.15); }
+The lifecycle pattern ([lifecycle.md](./lifecycle.md)) consumes the dials directly — empty-state
+richness scales with verbosity, confirmation depth rides feedback; focus and overlay discipline read
+the ring variables ([interaction.md](./interaction.md)). A component that must branch structurally
+on a dial reads the `<html>` attribute — it never duplicates the state. Density (`data-density`) is
+spatial chrome, not behavior — it composes with the dials, never replaces them (§4).
 
-/* ── Dark theme — OPT-IN ONLY. ──
- * Emitted only when the design.md ships a lever-manifest color-tokens.dark map.
- * Light stays the default; this block never appears for a light-only project.
-[data-theme="dark"] {
-  --background: #0f172a; --foreground: #f8fafc; ... all 34 tokens remapped ...
-} */
+## 3. Hints — provisional values that pass the gate but block emission
+
+Where a value needs judgment, the token carries a **valid provisional `$value`** plus
+`$extensions["com.nurix.design"].hint` — the intent in plain words (the full convention, with the
+JSON shape, is SCHEMA.md's hint section; payload fields are always concrete — hints exist only on
+tokens). Every gated token is in exactly one state:
+
+| State | Marker | `--check` | `--emit` |
+| --- | --- | --- | --- |
+| **assigned** | real value, no `hint` key | passes | emits |
+| **hinted** | `hint` key present | passes | **refuses**, naming every hinted path |
+| **missing** | token absent | fails, naming the key | — |
 
-/* ── Accessibility ── */
-@media (prefers-reduced-motion: reduce) {
-  :root, [data-style] {
-    --duration-unit: 0ms; --stagger-delay: 0ms;
-    --ease-default: linear; --ease-enter: linear; --ease-exit: linear;
-    --feedback-press-scale: 1;
-  }
-}
-@media (prefers-contrast: more) {
-  :root, [data-style] {
-    --contrast-boost: 1.15; --border-weight: 2px; --shadow-intensity: 0; --icon-stroke: 2;
-  }
-}
+A hinted artifact is checkable — the pass line counts the outstanding hints (this run: a scratch
+copy of the default with a hint added to `primitive.contrast-boost`):
+
+```
+check PASSED (<artifact-dir>): rules 1–11 OK — 26 primitives, 34 color roles, typography 3+6, payload/manifest/parse-back OK — provenance=default, style=nurix, theme=light, 1 hint(s) outstanding (emit will refuse)
+```
+
+— but not emittable. `--emit` over the same artifact:
+
+```
+emit REFUSED (<artifact-dir>): 1 unresolved hint(s) — rule 12: every gated token must be concrete before emission.
+  - primitive.contrast-boost: hint: nudge borders up a step so the dense table grid reads as a grid
+  Resolve each with judgment: set the real $value, delete the hint key, record the rationale in $description — then re-run --emit.
 ```
 
-## 4. `src/styles/globals.css`
+Resolving a hint is exactly that three-step: set the real `$value`, delete the `hint` key, record
+the rationale in the token's `$description` — so the resolved artifact stays self-explaining and
+re-derivable. Judgment is recorded, never silent.
 
-Wires personality into Tailwind v4. `main.tsx` imports this one file. The `@theme inline` keyword inlines
-each value into the generated utilities (so `bg-card` compiles to `background-color: var(--card)` and
-`--font-sans: var(--font-sans)` is *not* a circular `:root` write — it inlines into `.font-sans`).
+## 4. The substrate contracts — living with `@nurix/components`
+
+`@nurix/components/dist/styles.css` ships its own bare-`:root` token defaults and its own `@theme`
+radius scale. Two cascade contracts keep the personality in charge; both are hardened with the
+emitted in-CSS comments below and enforced by the code-and-token rules (`cod-*`) in
+[hard-rules.md](./hard-rules.md). The library's actual consumption is enumerated in
+[the substrate audit](../../../docs/history/brainstorms/design/u1-audit-report.md).
+
+**CASCADE CONTRACT 1 — the specificity/attribute pair.** The color tokens are emitted under a
+doubled selector, and `<html>` must carry `data-theme="light"`:
+
+```css
+/* ── Semantic + substrate color tokens — light theme. ──
+ * CASCADE CONTRACT 1: the doubled selector out-specifies the library's bare
+ * :root defaults in @nurix/components/styles.css — but ONLY because <html> carries
+ * data-theme="light". A bare :root here loses to the later library import. All 34
+ * tokens are set (D6): no consumed token falls back to a shadcn-gray default. */
+:root,
+:root[data-theme="light"] {
+```
+
+*Failure mode:* a bare `:root { --background: … }` is specificity `(0,1,0)` — the library's own
+`:root { --background: … }` is also `(0,1,0)` and imported *later*, so it wins and every surface
+silently reverts to shadcn gray. The `:root[data-theme="light"]` arm is `(0,2,0)` and out-wins — but
+only if `data-theme="light"` is actually on `<html>`; drop the attribute and the arm never matches,
+leaving only the losing bare `:root`. Both halves are load-bearing together.
+
+**CASCADE CONTRACT 2 — the four-step import order.** The emitted `globals.css` opens:
 
 ```css
 /* src/styles/globals.css — Tailwind v4 glue + @theme inline mappings (emitted). */
 
-/* CASCADE CONTRACT 2 (§6): this four-step order is LOAD-BEARING. The library's
+/* CASCADE CONTRACT 2: this four-step order is LOAD-BEARING. The library's
  * styles.css ships its own :root token defaults and its own @theme radius scale;
  * our @theme MUST come AFTER the import to win the radius scale and own every
- * mapping. rules/general.md (frontend section) states the same order — co-authority. */
+ * mapping. rules/frontend.md states the same order — co-authority. */
 @import "./personality.css";          /* 1. token source (must be first) */
 @import "tailwindcss";                /* 2. framework */
 @import "@nurix/components/styles.css"; /* 3. library (before our @theme) */
 
 @theme inline {                       /* 4. consumer theme — AFTER the library, so it wins */
-  /* radius scale — shadcn offsets on --radius, re-asserted so the CONSUMER owns it.
-   * A flat personality sets --radius: 0 → every step collapses to 0. */
-  --radius-sm: calc(var(--radius) - 4px);
-  --radius-md: calc(var(--radius) - 2px);
-  --radius-lg: var(--radius);
-  --radius-xl: calc(var(--radius) + 4px);
+```
 
+*Failure mode:* put `@theme inline` (or the whole consumer theme) *before* the library import and
+the library's own `@theme` radius scale (`--radius-lg: var(--radius)`, its own offsets) comes later
+and wins — the personality `--radius` stops driving the scale and archetype radius switching breaks.
+`rules/frontend.md` states this same order — co-authority, not a restatement to
+drift from. `@theme inline` inlines each value into the generated utilities (so `bg-card` compiles
+to `background-color: var(--card)`).
+
+**The gray-fallback trap — all 34 roles, always.** Beyond the 15 semantic color tokens it maps
+(888 semantic-token class uses), the library consumes **16 more shadcn tokens** — `--popover(-foreground)`,
+`--secondary(-foreground)`, `--chart-1..5`, and the `--sidebar` family — that silently fall back to
+the shadcn-gray defaults inside `dist/styles.css` when unset: popovers, menus, secondary buttons,
+sidebars, and charts render visibly off-palette next to personality surfaces. The artifact's
+substrate group carries 17 roles covering them, and emission sets all 34 color roles every time.
+`--color-destructive-foreground` is mapped explicitly in `@theme` because the library leaves it
+unmapped.
+
+**Coverage — every token the library consumes is emitted.**
+
+| Library consumes | How | Emitted at |
+| --- | --- | --- |
+| `--radius` (283 `rounded-*`) | direct primitive + `@theme` radius scale | `[data-style]` · `@theme` |
+| shadow (`shadow-xs/sm/md/lg`, 58) | `--shadow-*` alpha rides `--shadow-intensity` | `@theme` |
+| font weight (`font-medium/semibold/bold/normal`, 139) | two-weight map to `--font-weight-strong` | `@theme` |
+| tracking (`tracking-*`, 13) | `--tracking-tight/tighter → --heading-tracking` | `@theme` |
+| spacing (all `p-*`/`gap-*`) | `--spacing` density remap | `@theme` |
+| `font-mono` (9) / `font-sans` | literal font stacks | `@theme` |
+| 15 semantic colors (888 uses) | direct token values | `:root[data-theme=light]` |
+| `--success`, `--warning` | direct token values (library ignores today — upstream gaps) | `:root[data-theme=light]` |
+| `--destructive-foreground` (unmapped by library) | explicit `--color-destructive-foreground` map | `@theme` |
+| 17 substrate (`popover`/`secondary`/`chart-1..5`/`sidebar` family) | direct token values | `:root[data-theme=light]` |
+| `--sidebar-width` / `--sidebar-width-icon` | SidebarProvider `style` prop | shell (below) |
+
+**Density — global tier composed with a per-surface relative step.** Two composed levels, pure
+cascade, no JS. The payload's `density-tier` becomes `data-density` on `<html>`, and the emitted
+blocks write only the **base** multipliers; a surface carries `data-density-step` (from its
+surface-catalog `density-modifier`, [surface-catalog.md](../data/operator-pack/surface-catalog.md),
+emitted by `scaffold.mjs`) and re-derives one relative step off whatever tier the app runs:
+
+```css
+/* ── Density: global tier → base multipliers (D31). ──
+ * The tier writes ONLY the base; --density-gap/inset resolve from it (above),
+ * so a per-surface step can re-derive relative to the tier. */
+[data-density="dense"]    { --density-base-gap: 0.85; --density-base-inset: 0.85; }
+[data-density="standard"] { --density-base-gap: 1;    --density-base-inset: 1; }
+[data-density="spacious"] { --density-base-gap: 1.15; --density-base-inset: 1.15; }
+
+/* ── Per-archetype density modifier (D31) — relative step on the tier, pure cascade, no JS. ──
+ * A surface element carries data-density-step; it re-derives one step off the
+ * inherited base. Reads --density-base-* (never itself) so it composes with the
+ * tier and never absolutely overrides it. The recomputed --density-gap flows into
+ * the library's p-*/gap-* through the @theme --spacing remap. */
+[data-density-step="tighter"] { --density-gap: calc(var(--density-base-gap) * 0.85); --density-inset: calc(var(--density-base-inset) * 0.85); }
+[data-density-step="looser"]  { --density-gap: calc(var(--density-base-gap) * 1.15); --density-inset: calc(var(--density-base-inset) * 1.15); }
+```
+
+A log-stream inside a `standard` app resolves one step denser without pinning an absolute value.
+Both levels reach the library's internals through one `@theme` line — every library `p-*`/`gap-*`
+is `calc(var(--spacing) × N)`, and `--density-gap` resolves per element (respecting a
+`data-density-step` ancestor):
+
+```css
   /* density remap — the single line that scales ALL library spacing. Every p-*/gap-*
    * is calc(var(--spacing) × N); driving --spacing off --density-gap flows the tier
-   * AND the per-surface density step (§7) into the library's internals. */
+   * AND the per-surface density step into the library's internals. */
   --spacing: calc(0.25rem * var(--density-gap));
+```
 
-  /* shadow — alpha rides --shadow-intensity (matches the library's shadow-xs/sm/md/lg use) */
-  --shadow-2xs: 0 1px 2px 0 rgb(15 23 42 / calc(0.04 * var(--shadow-intensity)));
-  --shadow-xs:  0 1px 2px 0 rgb(15 23 42 / calc(0.06 * var(--shadow-intensity)));
-  --shadow-sm:  0 1px 3px 0 rgb(15 23 42 / calc(0.10 * var(--shadow-intensity))), 0 1px 2px -1px rgb(15 23 42 / calc(0.10 * var(--shadow-intensity)));
-  --shadow-md:  0 4px 6px -1px rgb(15 23 42 / calc(0.10 * var(--shadow-intensity))), 0 2px 4px -2px rgb(15 23 42 / calc(0.10 * var(--shadow-intensity)));
-  --shadow-lg:  0 10px 15px -3px rgb(15 23 42 / calc(0.10 * var(--shadow-intensity))), 0 4px 6px -4px rgb(15 23 42 / calc(0.10 * var(--shadow-intensity)));
+**The two-weight discipline.** Operator UI carries exactly two font weights; the `@theme` map folds
+the library's whole weight vocabulary onto them:
 
+```css
   /* font weight — two-weight discipline: medium/semibold/bold all resolve to the
    * single emphasis weight; operator UI carries no third weight. normal is emitted
    * as a literal because its theme key and the primitive share a name (no self-ref). */
@@ -300,205 +329,100 @@ each value into the generated utilities (so `bg-card` compiles to `background-co
   --font-weight-medium: var(--font-weight-strong);
   --font-weight-semibold: var(--font-weight-strong);
   --font-weight-bold: var(--font-weight-strong);
-
-  /* tracking — heading tightness reaches the library's tracking-* utilities */
-  --tracking-tighter: var(--heading-tracking);
-  --tracking-tight: var(--heading-tracking);
-
-  /* fonts — emitted as the literal stack: a font is not a runtime-toggled token, and
-   * the theme key shares a name with the personality primitive (no self-reference).
-   * personality.css carries the same --font-sans/--font-mono for direct var() use. */
-  --font-sans: "Inter", system-ui, sans-serif;
-  --font-mono: "JetBrains Mono", ui-monospace, monospace;
-
-  /* transitions */
-  --transition-fast: var(--duration-fast) var(--ease-default);
-  --transition-normal: var(--duration-normal) var(--ease-default);
-  --transition-slow: var(--duration-slow) var(--ease-default);
-  --transition-enter: var(--duration-normal) var(--ease-enter);
-  --transition-exit: var(--duration-fast) var(--ease-exit);
-
-  /* semantic + substrate color maps — all 34, so bg-popover / bg-chart-1 / bg-sidebar resolve.
-   * --color-destructive-foreground is mapped explicitly (D6): the library leaves it unmapped. */
-  --color-background: var(--background);
-  --color-foreground: var(--foreground);
-  --color-card: var(--card);
-  --color-card-foreground: var(--card-foreground);
-  --color-muted: var(--muted);
-  --color-muted-foreground: var(--muted-foreground);
-  --color-border: var(--border);
-  --color-input: var(--input);
-  --color-ring: var(--ring);
-  --color-primary: var(--primary);
-  --color-primary-foreground: var(--primary-foreground);
-  --color-accent: var(--accent);
-  --color-accent-foreground: var(--accent-foreground);
-  --color-destructive: var(--destructive);
-  --color-destructive-foreground: var(--destructive-foreground);
-  --color-success: var(--success);
-  --color-warning: var(--warning);
-  --color-popover: var(--popover);
-  --color-popover-foreground: var(--popover-foreground);
-  --color-secondary: var(--secondary);
-  --color-secondary-foreground: var(--secondary-foreground);
-  --color-chart-1: var(--chart-1);
-  --color-chart-2: var(--chart-2);
-  --color-chart-3: var(--chart-3);
-  --color-chart-4: var(--chart-4);
-  --color-chart-5: var(--chart-5);
-  --color-sidebar: var(--sidebar);
-  --color-sidebar-foreground: var(--sidebar-foreground);
-  --color-sidebar-primary: var(--sidebar-primary);
-  --color-sidebar-primary-foreground: var(--sidebar-primary-foreground);
-  --color-sidebar-accent: var(--sidebar-accent);
-  --color-sidebar-accent-foreground: var(--sidebar-accent-foreground);
-  --color-sidebar-border: var(--sidebar-border);
-  --color-sidebar-ring: var(--sidebar-ring);
-}
-
-/* dark variant — emitted ONLY when the project ships dark; redefines the library's
- * class-based dark to follow data-theme so the library's dark: utilities honor our
- * convention. Absent for a light-only project.
-@custom-variant dark (&:where([data-theme="dark"], [data-theme="dark"] *)); */
 ```
 
-## 5. `index.html`
+Fonts follow the same no-self-reference rule: `--font-sans`/`--font-mono` are emitted into `@theme`
+as literal stacks (a font is not a runtime-toggled token, and the theme key shares the primitive's
+name), while `personality.css` carries the same variables for direct `var()` use.
 
-Vite entry (no `layout.tsx`). The `<html>` attributes carry the personality state; the HTML comment is
-the cache record.
+**Sidebar width — the style-prop seam.** The library hardcodes `--sidebar-width` /
+`--sidebar-width-icon` as inline styles, overridable only via the provider's `style` prop — the one
+layout primitive that cannot reach the library through `@theme`. The shell wires the personality
+primitives in:
 
-```html
-<!-- Personality state lives in these <html data-*> attributes — code is the cache.
-     There is no sidecar JSON. To change the look, edit the resolved design.md and
-     re-run derive-personality.mjs --emit; to nudge one axis, edit an attribute here. -->
-<html
-  lang="en"
-  data-style="meridian"
-  data-density="dense"
-  data-verbosity="default"
-  data-feedback="subtle"
-  data-theme="light"
+```tsx
+<SidebarProvider
+  style={{
+    "--sidebar-width": "var(--sidebar-width-expanded)",
+    "--sidebar-width-icon": "var(--sidebar-width-collapsed)",
+  } as React.CSSProperties}
 >
-  <head>
-    <meta charset="UTF-8" />
-    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
-    <title>Meridian</title>
-  </head>
-  <body>
-    <div id="root"></div>
-    <script type="module" src="/src/main.tsx"></script>
-  </body>
-</html>
 ```
 
-## 6. The two cascade contracts and their failure modes
-
-Both are hardened with the in-CSS comments above and enforced by the code-and-token rules (`cod-*`) in
-[hard-rules.md](./hard-rules.md); the `scaffold` and `tokens` phase gates check them.
-
-**Contract 1 — the specificity/attribute pair.** Semantic + substrate tokens sit under
-`:root, :root[data-theme="light"]` **and** `<html>` carries `data-theme="light"`.
-*Failure mode:* a bare `:root { --background: … }` is specificity `(0,1,0)` — the library's own
-`:root { --background: … }` in `styles.css` is also `(0,1,0)` and imported *later*, so it wins and every
-surface silently reverts to shadcn gray. The `:root[data-theme="light"]` arm is `(0,2,0)` and out-wins —
-but only if `data-theme="light"` is actually on `<html>`; drop the attribute and the arm never matches,
-leaving only the losing bare `:root`. Both halves are load-bearing together.
-
-**Contract 2 — the import order.** `personality.css → tailwindcss → @nurix/components/styles.css →
-@theme inline`. *Failure mode:* put `@theme inline` (or the whole consumer theme) *before* the library
-import and the library's own `@theme` radius scale (`--radius-lg: var(--radius)`, its own offsets) comes
-later and wins — the personality `--radius` stops driving the scale and archetype radius switching breaks.
-The consumer `@theme` must come last. `rules/general.md` (frontend section) states this same order — it is
-co-authority, not a restatement to drift from.
+**Upstream gaps — expected, never worked around.** Some values live in `@nurix/components` JS, not
+CSS, so they do not follow tokens until the library adopts them. This is user-owned upstream work —
+never patched with brittle per-instance overrides:
 
-## 7. Density — global tier composed with a per-archetype relative step (D31)
-
-Two composed levels, pure cascade, no JS:
-
-1. **Global tier** — `density-tier` (spacious | standard | dense) from the `design.md` emits
-   `data-density` on `<html>`. `[data-density="…"]` writes only the **base** multipliers
-   (`--density-base-gap/inset`); `--density-gap/inset` resolve *from* the base. Switching the tier
-   re-tiers the whole surface coherently.
-2. **Per-archetype step** — a surface carries `data-density-step="tighter"|"looser"` (from its
-   surface-catalog `density-modifier`, [surface-catalog.md](../data/operator-pack/surface-catalog.md)),
-   emitted by `scaffold.mjs` onto the surface root. It re-derives `--density-gap/inset` as
-   `calc(base × 0.85|1.15)` — a **relative** step off whatever tier the app runs, reading
-   `--density-base-*` (never itself, so no circular reference and never an absolute override). A
-   log-stream inside a `standard` app resolves one step denser without pinning an absolute value.
-
-Both feed the library through `--spacing: calc(0.25rem * var(--density-gap))` in `@theme`: every library
-`p-*`/`gap-*` is `calc(var(--spacing) × N)`, and `--density-gap` resolves per element (respecting a
-`data-density-step` ancestor), so the tier and the step both reach the library's internal spacing. This
-composes *with*, never replaces, the behavioral dials (D4) — density is spatial chrome; verbosity/feedback
-are behavior.
-
-## 8. Dial wiring and the lifecycle
+- **Chart palettes** — the d3 family hardcodes oklch/hex and ignores `--chart-1..5`; color props are
+  per-instance overridable, but the defaults are upstream. Emit `--chart-1..5` regardless, so
+  adoption is a drop-in.
+- **Status literals** — `changes-list` and `statistics` hardcode emerald/amber/sky rather than
+  `--success`/`--warning`.
+- **Motion & icon stroke** — `duration: .2/.3` and `strokeWidth: 2/1.75` are JS numbers;
+  `--duration-*` and `--icon-stroke` reach consumer-emitted markup but not library internals.
+- **Filled-control foreground** — `text-white` pinned on filled primary/destructive; the mapped
+  `--destructive-foreground` waits on the library reading it.
 
-`data-verbosity` and `data-feedback` set behavioral variables the lifecycle and interaction layers read:
+The stance: emit the complete token surface so the library "just works" the moment it adopts each
+token; do not build an override layer that fights the library and rots.
 
-- `--label-display` / `--helper-text-display` — `compact`/`expert` verbosity collapse form labels and
-  helper text; `full`/`default` keep them. Field chrome reads these, not a JS branch.
-- `--tooltip-delay` — tightens with verbosity (`800ms → 0ms`).
-- `--feedback-press-scale`, `--focus-ring-width`, `--focus-ring-offset` — `minimal` feedback flattens the
-  press and thins the focus ring; `subtle` keeps the operator-default ring.
+## 5. Dark and themes — the base set is light
 
-The lifecycle pattern ([lifecycle.md](./lifecycle.md)) consumes the dials directly: empty-state richness
-scales with verbosity (`full` gets the acknowledge-value-action triad, `expert` gets one bare line);
-confirmation depth rides feedback. Focus and overlay discipline read the feedback ring variables
-([interaction.md](./interaction.md)). Components that must branch structurally on a dial read the `<html>`
-attribute — they never duplicate the state.
+The base token set **is** the light rendering — light is never omitted, and the resolver's `light`
+context is always the empty overlay. A look with dark values ships `design.tokens.dark.json` —
+exactly the `color` group, all 34 roles, nothing else — named by the resolver's `dark` context and
+overlaid per the resolution order. When it ships, emission adds a `[data-theme="dark"]` block
+remapping all 34 roles:
 
-## 9. Sidebar width via the SidebarProvider style prop
+```css
+/* ── Dark theme — OPT-IN ONLY (this look ships a dark overlay). ──
+ * design.tokens.dark.json remaps all 34 color tokens; <html data-theme="dark">
+ * opts in. Light stays the default. */
+[data-theme="dark"] {
+```
 
-The library hardcodes `--sidebar-width` / `--sidebar-width-icon` as inline styles, overridable only via the
-provider's `style` prop. The shell wires the personality primitives in:
+For a light-only artifact (the shipped default is one), the emitted file carries a placeholder
+comment instead:
 
-```tsx
-<SidebarProvider
-  style={{
-    "--sidebar-width": "var(--sidebar-width-expanded)",
-    "--sidebar-width-icon": "var(--sidebar-width-collapsed)",
-  } as React.CSSProperties}
->
+```css
+/* ── Dark theme — OPT-IN ONLY. ──
+ * Emitted only when the artifact ships a design.tokens.dark.json dark overlay.
+ * Light stays the default; this block never appears for a light-only project.
+[data-theme="dark"] {
+  --background: ...; --foreground: ...; ... all 34 tokens remapped ...
+} */
 ```
 
-This is the one layout primitive that cannot reach the library through `@theme` — the style prop is the
-supported seam.
+`--theme dark` selects the dark context and sets `<html data-theme="dark">` in the emitted
+attributes (the header's `theme:` line follows). The default is `light`; requesting dark from a
+light-only artifact fails cleanly —
+`node scripts/derive-personality.mjs data/design-tokens/nurix --check --theme dark` prints:
 
-## 10. Coverage checklist — every token the library consumes is emitted
-
-Enumerated against [the substrate audit](../../../docs/brainstorm/design/u1-audit-report.md). Emission
-sets each; none falls back to a shadcn-gray default (D6).
+```
+check FAILED (data/design-tokens/nurix): 1 issue(s)
+  - rule 1 — resolver: --theme dark requested but the resolver carries no dark context
+```
 
-| Library consumes | How | Emitted at |
-| --- | --- | --- |
-| `--radius` (283 `rounded-*`) | direct primitive + `@theme` radius scale | `[data-style]` · `@theme` |
-| shadow (`shadow-xs/sm/md/lg`, 58) | `--shadow-*` alpha rides `--shadow-intensity` | `@theme` |
-| font weight (`font-medium/semibold/bold/normal`, 139) | two-weight map to `--font-weight-strong` | `@theme` |
-| tracking (`tracking-*`, 13) | `--tracking-tight/tighter → --heading-tracking` | `@theme` |
-| spacing (all `p-*`/`gap-*`) | `--spacing` density remap | `@theme` |
-| `font-mono` (9) / `font-sans` | inlined font keys | `@theme` |
-| 15 semantic colors (888 uses) | direct token values | `:root[data-theme=light]` |
-| `--success`, `--warning` | direct token values (library ignores today — §11) | `:root[data-theme=light]` |
-| `--destructive-foreground` (unmapped by library) | explicit `--color-destructive-foreground` map | `@theme` |
-| 17 substrate (`popover`/`secondary`/`chart-1..5`/`sidebar` family) | direct token values | `:root[data-theme=light]` |
-| `--sidebar-width` / `--sidebar-width-icon` | SidebarProvider `style` prop | shell (§9) |
+The library's `dark:` utilities are class-based; a dark-shipping project redefines the variant to
+follow the attribute. `globals.css` carries the instruction as a comment, enabled only when dark
+ships:
 
-## 11. Upstream gaps — expected, never worked around
+```css
+/* dark variant — emitted ONLY when the project ships dark; redefines the library's
+ * class-based dark to follow data-theme so the library's dark: utilities honor our
+ * convention. Absent for a light-only project.
+@custom-variant dark (&:where([data-theme="dark"], [data-theme="dark"] *)); */
+```
 
-Some values live in `@nurix/components` JS, not CSS, so they do not follow tokens until the library adopts
-them. This is expected, filed as user-owned upstream work (D6) — **never** patched with brittle per-instance
-overrides:
+Components never use `dark:` prefixes or literal colors regardless — the semantic tokens remap and
+every surface follows (the semantic-token doctrine in the emitted header).
 
-- **Chart palettes** — the d3 family (`bar-graph`, `line-graph`, `pie-graph`, `sparkline`, …) hardcodes
-  oklch/hex and ignores `--chart-1..5`. Color props are per-instance overridable, but the defaults are
-  upstream. Emit `--chart-1..5` regardless, so adoption is a drop-in.
-- **Status literals** — `changes-list` and `statistics` hardcode emerald/amber/sky rather than
-  `--success`/`--warning`. Upstream token adoption is the fix.
-- **Motion & icon stroke** — `duration: .2/.3` and `strokeWidth: 2/1.75` are JS numbers; `--duration-*`
-  and `--icon-stroke` reach consumer-emitted markup but not library internals.
-- **Filled-control foreground** — `text-white` pinned on filled primary/destructive; the mapped
-  `--destructive-foreground` waits on the library reading it.
+## 6. Precedence and provenance — which artifact gets emitted
 
-The stance: emit the complete token surface now so the library "just works" the moment it adopts each token;
-do not build an override layer that fights the library and rots.
+Look resolution is project-first: a `project` or `extracted` artifact wins outright; a `library`
+entry serves only when the brief names or resembles the product and the user confirms; the Nurix
+default (`data/design-tokens/nurix/`) is worn when nothing else speaks. The origin is the payload's
+`provenance` field, and the emitted header's `artifact:` line records it alongside the `sourced`
+date — so the emitted CSS always says where its look came from. The full precedence table, payload
+spec, and per-value provenance convention (`$description`) are
+[SCHEMA.md](../data/design-tokens/SCHEMA.md).