Status: CLOSED at error (R-7 rail, commit 150b6c7, 2026-05-16). The pre-flight "1,285 violations / 25.7× threshold" finding documented in §7.6 below was the initial sweep; the rail was subsequently drained via codemod (131 sites tokenized to scale tiers) and the epoch-shield/no-raw-typography rule promoted warn → error. npm run lint reports zero no-raw-typography violations across src/** as of verdict #66 (R-66, 2026-05-18). The §7.6 deferral analysis below is preserved verbatim as historical context — the §8.1 Phase 5 deferral plan was overtaken by events and does not apply; future stub maturation should focus on counter-examples, per-component citations, and the named-scale utility-class set (.text-display / .text-hero / …) which still emits only --type-eyebrow-* from tokens.css.

§7.6 maturation log

Per the Phase 1 go-condition in Design/0000-hig-diagnostic.md §7.6 step #4, the named-scale token shipment proceeded in four commits:

8f0a785 — Phase 1 P1: motion/radius/type token entries added to tokens.json; tokens.css + Tailwind extends regenerated. Type scale (display / hero / title / subtitle / body / caption / micro / eyebrow) now resolvable as token names in src/**.
b3cdfc2 — Phase 1 P2: globals.css retrofitted to consume named motion + type tokens (signature transitions, loading dots, message-in springs).
7023909 — Phase 1 P3 base: raw-rgba glow sweep on /app/page.tsx + /app/landing/page.tsx (out-of-scope for typography proper, but the same sweep pass).
9bbe8ae — Phase 1 P3 extension: residual raw-rgba shadow values across 6 component files tokenized to rgba(var(--semantic-{accent\|success}-rgb), α).
fee2275 — Phase 1 P4: this maturation log added (F-2 + F-6 §7.6 stubs converted to maturation logs documenting the P1–P3 commits and remaining P5 follow-ups).
c2634c3 — Phase 1 P5 motion sibling shipped (epoch-shield/no-raw-motion-values); see F-6.md §7.6. The type-side strict-fail companion is deferred with quantified evidence — details below.

Phase 1 P5 (type rule) — deferred with evidence

The §5 Phase 2 stop condition in Design/0000-hig-diagnostic.md reads verbatim: "if the lint sweep flags more than 50 violations across src/**, pause and triage — that's evidence the principle was widely violated and needs a documented allowlist before strict-fail. If under 50, fix in the same PR."

The pre-flight sweep in P5 found 1,285 raw type-value violations in src/**, which is 25.7× the Phase 2 threshold:

Surface	Pattern	Count
Font size	`text-[Npx]` Tailwind arbitrary classes	1,028
Letter-spacing	`tracking-[N]` Tailwind arbitrary classes	154
Line-height	`leading-[N]` Tailwind arbitrary classes	103
Total		1,285

Two prerequisites are unmet for strict-fail enforcement:

Token target incomplete. tokens.css emits --type-eyebrow-* only. The named scale this stub stipulates (display / hero / title / subtitle / body / caption / micro) is defined in tokens.json but not yet generated as --type-{scale}-{size,line-height,letter-spacing} custom properties or as .text-{scale} utility classes in Tailwind extends. Without the utility classes, migrating sites have nowhere to land.
Migration runway absent. With 1,285 sites and no destination utility classes, a strict-fail rule would block every build on day one with no mechanical path to green.

Per the §5 Phase 2 triage gate, P5 type enforcement is deferred to Phase 5 maturation work (per the §8.1 milestone), gated on:

(a) generating the full named-scale utility classes in tokens.css + Tailwind extends;
(b) per-cluster migration of the 1,285 raw sites to the named scale (route-by-route, mirroring the Tier B → C → D → A redraw cadence);
(c) the rule scaffold itself — intentionally not authored yet, because both the migration target and the sweep plan must land first per the triage gate.

The motion sibling shipped clean (0 violations) because the §7.2 globals.css retrofit had already drained the surface. The type surface has no equivalent retrofit yet.

Statement

Typography uses a named scale (display / hero / title / subtitle / body / caption / micro / eyebrow). Components reference scale names. No component sets a raw font-size, line-height, or letter-spacing value.

Why

The audit found inconsistent type sizing across screens that nominally share a content density: hero subtitles ranging 13–17px in the same product family, mobile body text dropping below 15px on screens whose desktop variant used 17px, eyebrow labels at four different letter-spacing values. The user reads the inconsistency as sloppiness even when no individual size is wrong. A named scale forces a designer to ask "is this body text or subtitle?" — a content question — instead of "is 15 or 17 right here?" — a measurement question. Content questions have one answer per scope; measurement questions don't.

The scale is also the contract for i18n fallback chains (§2.6): when a glyph in the primary face is missing, the same scale name resolves through the fallback chain. Raw values can't.

How

In Phase 1 (this stub), the scale is stipulated; the implementation lives in tokens.json shipping in Phase 2. The named-scale tokens are consumed via the <Eyebrow>, <Hero>, <HeroMeta>, and product primitives (Phase 1 Track B). The ESLint hex-ban rule (§5.4) extends to font-size and letter-spacing raw values outside the tokens file.

Phase 5 deepens this stub with the full scale specification, counter-examples (audit screens 28, 35, 81), and per-component citations.