@@ -24,11 +24,13 @@
 Two independent splines need not preserve `metric * throughput = constant` between
 measured knots. Pass `reciprocal_of='throughput'` (or the matching output/input
 throughput key) to spline that throughput and re-derive the metric. The live
-inference charts also expose tokens/$ as a separate metric; that purchasing-power
-metric is directly proportional to throughput. Pass `proportional_to='throughput'`
-(or the matching output/input throughput key) so it uses the same Pareto knots and
-spline as that throughput before applying the recovered multiplier. See
-docs/tco-calculator.md for a reproducible measurement.
+inference charts also expose tokens/$ and normalized token revenue as separate
+metrics; both are directly proportional to throughput. OpenRouter-priced revenue
+is proportional only when the input/output mix stays constant; otherwise spline
+the already-priced metric directly. Pass
+`proportional_to='throughput'` (or the matching output/input throughput key) so
+they use the same Pareto knots and spline as that throughput before applying the
+recovered multiplier. See docs/tco-calculator.md for a reproducible measurement.
 
 Usage as a module:
     from iso_interactivity import interpolate_metric, pareto_front_upper_left
@@ -221,9 +223,11 @@ def interpolate_metric(
     the chart code does not extrapolate. Blog tables should render this as
     `_unreachable_` in that row.
 
-    The Pareto frontier is built on (interactivity, throughput). For tokens/$,
-    `proportional_to` names the total/output/input throughput it scales; that
-    throughput also supplies the frontier knots so both curves stay aligned.
+    The Pareto frontier is built on (interactivity, throughput). For tokens/$ or
+    normalized token revenue (and revenue with a constant token mix),
+    `proportional_to` names the total/output/input
+    throughput it scales; that throughput also supplies the frontier knots so
+    both curves stay aligned.
 
     `reciprocal_of` names the throughput key a metric divides, for metrics of the
     form `constant / throughput` ($/M tok, J/token). Set it for those metrics:
@@ -232,8 +236,10 @@ def interpolate_metric(
     latency, and measured energy — whose numerator varies per point).
 
     `proportional_to` names the throughput key for metrics of the form
-    `throughput * constant` (tokens/$). That throughput is splined and the
-    recovered multiplier applied, matching the dashboard.
+    `throughput * constant` (tokens/$, normalized token revenue, and revenue
+    with a constant input/output mix). That
+    throughput is splined and the recovered multiplier applied, matching the
+    dashboard.
     """
     if not points:
         return None
@@ -318,7 +324,7 @@ def interpolate_metric(
 def _cli() -> None:
     """Stdin: {"points": [...], "target_iv": N, "metric_key": "...",
                "reciprocal_of": "throughput" for $/M tok and J/token,
-               "proportional_to": "throughput" for tokens/$}
+               "proportional_to": "throughput" for tokens/$ or revenue with a constant mix}
     Stdout: {"value": N or null}"""
     req = json.loads(sys.stdin.read())
     value = interpolate_metric(
 
@@ -47,3 +47,5 @@ jobs:
         run: bun run lint
       - name: Format check
         run: bun run fmt
+      - name: Typography gate
+        run: bun run check:typography
@@ -127,6 +127,7 @@ Static content routes (no DB):
 - **Linter**: oxlint — `bun run lint` / `bun run lint:fix`
 - **Formatter**: oxfmt — `bun run fmt` / `bun run fmt:fix`
 - **Type checking**: `bun run typecheck` (tsc --noEmit, strict mode)
+- **Typography gate**: `bun run check:typography` (CI + pre-commit) — no new arbitrary font sizes (`text-[11px]`) or letter-spacing (`tracking-[0.16em]`) in class strings, and no quoted font-size literals in `src/lib/d3-chart/`. Use `text-2xs`/`text-3xs`, `tracking-eyebrow`/`tracking-eyebrow-wide`/`tracking-heading`, the `<Heading>`/`<Eyebrow>` components, or `CHART_TYPE` from `@/lib/d3-chart/typography` (chart font sizes must stay in TS — CSS variables don't survive PNG export). Existing offenders live in `packages/app/scripts/typography-allowlist.json` and migrate on touch. See [Typography](./docs/typography.md).
 - **Node**: 24.x
 
 ## Environment Variables
@@ -225,6 +226,7 @@ Authoritative total / active parameter counts for every model in the dashboard.
 | Kimi-K2.6              | 1T    | 32B         | `moonshotai/Kimi-K2.6`              | HF model card                      |
 | Kimi-K2.7-Code         | 1T    | 32B         | `moonshotai/Kimi-K2.7-Code`         | HF model card                      |
 | Qwen3.5-397B-A17B      | 397B  | 17B         | `Qwen/Qwen3.5-397B-A17B`            | HF model card                      |
+| Qwen3.8-Flash-Next     | 176B  | 6B          | `Qwen/Qwen3.8-Flash-Next-FP8`       | HF model card                      |
 | GLM-5                  | 744B  | 40B         | `zai-org/GLM-5`                     | HF model card                      |
 | GLM-5.1                | 744B  | 40B         | `zai-org/GLM-5.1-FP8`               | HF model card (same base as GLM-5) |
 | MiniMax-M2.5           | 230B  | 10B         | `MiniMaxAI/MiniMax-M2.5`            | HF model card                      |
@@ -234,6 +236,7 @@ Authoritative total / active parameter counts for every model in the dashboard.
 
 **Common mislabel traps** (have all bitten this repo at least once — do not repeat):
 
+- **Qwen3.8-Flash-Next is 176B, not 125B.** The model card leads with "125B with 6B activated", but that is the main model only; the 51B n-gram embedding table brings the total to 176B. The separate 4B MTP head sits outside both figures. It is a Qwen4-architecture preview (GatedDeltaNet + Qwen Sparse Attention, 512 experts, 10 routed + 1 shared), not a Qwen3.5 point release, so it gets its own DB bucket.
 - **GLM-5 ≠ 355B.** 355B is GLM-4.5. GLM-5 jumped to 744B / 40B active (256-expert MoE with DSA).
 - **MiniMax-M2.5/M2.7 ≠ 456B.** 456B is the older MiniMax-Text-01 / M1 (32 large experts). The M2 series is a different architecture: 230B / 10B active, 256 small experts.
 - **DeepSeek-R1 is 671B, not 685B.** HF metadata shows 685B because the bundled MTP head adds ~14B; the core MoE is 671B / 37B active.
 
@@ -95,6 +95,8 @@ visible legend labels while retaining them in the legend item's accessible title
 The newest run with measured cases is checked by default; newer incomplete sweeps remain listed but
 cannot blank the initial explorer. Deletion is available per row or as one confirmed action for all
 currently shown runs; both paths keep the same tombstone semantics described above.
+The Runs card's suite filter narrows the table to runs containing EP or KV cases; a run containing
+both appears under both filters, and changing the filter does not alter the checked-run selection.
 
 ## The raw-rows exception
 
 
@@ -60,6 +60,7 @@ Returns `{ chartData: InferenceData[][], hardwareConfig: HardwareConfig }`.
 **`buildDerivedChartFields(entry, hwKey, requestedMetrics?)`** is the sole owner of inference and historical trend formulas. The full transform requests every benchmark-backed field. History requests only the selected metric and its interpolation dependencies, so it stays lightweight. Each emitted value uses `{ y: number; roof: boolean }`.
 
 - `tpPerGpu`, `outputTputPerGpu`, `inputTputPerGpu` — raw throughput from the entry (tok/s/gpu).
+- `tokenRevenuePerGpuHour` — gross revenue in $/GPU/hr. `buildDerivedChartFields` emits the normalized default (`tputPerGpu × 3,600 ÷ 1,000,000`, with input and output both priced at $1/M). `applyTokenRevenuePricing` can replace it with the selected model's current public OpenRouter prompt/completion prices. Aggregate rows use their measured input/output split; disaggregated rows derive a like-for-like split from fixed ISL:OSL or measured agentic prompt:generation totals because their raw input/output rates use different prefill/decode GPU denominators.
 - `tpPerMw` — `(tputPerGpu * 1000) / hardwarePower` (GPU power in kW, result in tok/s/MW).
 - Cost-per-million fields — GPU hourly cost divided by tokens-per-hour (in millions): `costh` / `costn` / `costr` for hyperscaler / neocloud / 3-year-rental pricing respectively. Three token variants exist: combined (`costh`/`costn`/`costr`), output-only (`costhOutput`/`costnOutput`/`costrOutput`), and input-only (`costhi`/`costni`/`costri`).
 - Tokens-per-dollar fields — tokens-per-hour divided by the same hourly costs. They are separate Y-axis metrics rather than a display toggle: combined (`tokensPerDollarH`/`N`/`R`), output-only (`outputTokensPerDollarH`/`N`/`R`), and input-only (`inputTokensPerDollarH`/`N`/`R`). This keeps existing `i_metric=y_cost*` links and cost semantics unchanged.
 
@@ -12,6 +12,7 @@ Design rationale and non-obvious conventions. See [CLAUDE.md](../CLAUDE.md) for
 - [TCO Calculator](./tco-calculator.md) — Why interpolation, composite keys, cost matrix, token type bugs, badge logic, state design
 - [Adding Entities](./adding-entities.md) — Step-by-step checklists for adding new models, GPUs, precisions, sequences, frameworks (ingest + constants + frontend), plus featuring a day-0 model (launch banner, modal, Quick Comparisons preset)
 - [Testing](./testing.md) — Requirements, quality standards, pre-commit checklist
+- [Typography](./typography.md) — Type tokens (text-2xs/3xs, named tracking), Heading/Eyebrow components, TS-based chart font sizes, and the check:typography ratchet gate + allowlist burndown
 - [Data Transforms](./data-transforms.md) — Full pipeline from BenchmarkRow to RenderableGraph: type hierarchy, hardware key construction, derived metrics, memoization strategy
 - [State Ownership](./state-ownership.md) — Which context owns which state, availability filtering cascade, comparison date mechanics, URL param sync
 - [Blog](./blog.md) — MDX content system, SEO features (OG images, RSS, llms.txt, JSON-LD), TOC sidebar, reading progress, heading links, analytics events
 
@@ -113,6 +113,7 @@ them.
 Axis and presentation state:
 
 - selected x-axis and y-axis metrics, percentile, and effective x-axis mode
+- token-revenue price source (`i_revenue`): normalized $1/M or the selected model's live OpenRouter catalog prices
 - scale, optimal-point, label, contrast, legend, and overlay controls
 
 Display changes stay in this domain. A contrast or label toggle therefore does not
 
@@ -167,13 +167,27 @@ at every interpolated point.
 compare interpolation models on a fixed snapshot, but they must not be presented
 as permanent impact figures for the changing live dataset.
 
-The `/inference` page also exposes tokens-per-dollar as separate Y-axis metrics;
-it does not replace the cost-per-million metrics. Historical trends for these
-purchasing-power metrics select Pareto knots from the matching total, output, or
-input throughput, spline that throughput, and apply the constant
-`3600 / $/GPU-hr` multiplier. Reusing the matching throughput frontier is
-essential: total-throughput knots are not necessarily the output- or
-input-throughput Pareto knots.
+The `/inference` page also exposes tokens-per-dollar and normalized token revenue
+as separate Y-axis metrics; neither replaces the cost-per-million metrics.
+Historical trends for these proportional metrics select Pareto knots from the
+matching throughput, spline that throughput, and apply the constant multiplier.
+Tokens-per-dollar uses `3600 / $/GPU-hr`; normalized token revenue uses
+`3600 / 1,000,000` at the axis's explicit `$1/M tok` sale price. Reusing the
+matching throughput frontier is essential: total-throughput knots are not
+necessarily the output- or input-throughput Pareto knots.
+
+The revenue axis defaults to pricing every input and output token at the same
+`$1/M tok` rate, making it a model-independent SLA comparison. Its OpenRouter
+option fetches the selected model's current public prompt/completion prices from
+`https://openrouter.ai/api/v1/models` and prices the streams separately. Aggregate
+rows use their measured input/output split. Disaggregated rows cannot use the raw
+per-prefill/per-decode rates together, so they apply the fixed ISL:OSL shape or
+the measured agentic prompt:generation mix to total tok/s/GPU. The OpenRouter
+option uses standard prompt/completion prices and does not apply cache discounts.
+
+Neither mode is the fleet lifecycle section's realized-revenue model: it does not
+model availability, rollout, or a user-supplied cached-input discount. Those
+business assumptions remain in Fleet Lifecycle below.
 
 ### The consistency guard
 
@@ -375,8 +389,9 @@ Four conventions the numbers depend on:
   energised, not from the moment they are loaded. So the opening rollout is paid for
   in full while it earns its way up from zero, which is what puts the first months
   below the rule and gives payback its meaning.
-- **The ramp is an assumption; the steps are not.** It defaults to a nominal
-  quarter (`c_ramp`), and 0 means every config takes effect instantly.
+- **The ramp is an assumption; the steps are not.** It defaults to half a month
+  (`c_ramp`) and moves in quarter-month increments; 0 means every config takes
+  effect instantly.
 - **Markers sit at the release instant** — the foot of each rollout, not its top —
   so every dot on the chart is a sweep the user can open.
 - **Interrupts are an availability haircut, not drawn events.** A 24-day MTBI
@@ -980,6 +995,6 @@ against that allowlist so a stale or hand-edited link falls back to `margin` rat
 than seeding an unknown metric).
 The first two default to
 `''` in `PARAM_DEFAULTS` because their real defaults are derived, not constant — see
-the comment there. The MW budget is
-`c_mw`, owned by `ThroughputCalculatorDisplay` and passed to both the fleet
-planner and this section so one input drives both.
+the comment there. The MW budget is `c_mw`, defaults to 10 MW, and is shared by
+the calculator and Fleet Lifecycle page so a budget set on either seeds the
+other.
@@ -0,0 +1,49 @@
+# Typography
+
+How text is sized and spaced in the app, and the ratchet gate that keeps it that way.
+
+## Tokens
+
+Defined in the `@theme` block of `packages/app/src/app/globals.css`:
+
+| Token                     | Class                   | Value            | Use for                                           |
+| ------------------------- | ----------------------- | ---------------- | ------------------------------------------------- |
+| `--text-2xs`              | `text-2xs`              | 0.6875rem (11px) | Micro labels one step below `text-xs`             |
+| `--text-3xs`              | `text-3xs`              | 0.625rem (10px)  | Densest labels: table meta, tooltips, log gutters |
+| `--tracking-eyebrow`      | `tracking-eyebrow`      | 0.16em           | Uppercase eyebrow/kicker labels                   |
+| `--tracking-eyebrow-wide` | `tracking-eyebrow-wide` | 0.2em            | Extra-wide uppercase labels                       |
+| `--tracking-heading`      | `tracking-heading`      | -0.04em          | Tightened display/hero headings                   |
+
+Rules of thumb:
+
+- Body and heading sizes use the standard Tailwind scale (`text-xs` … `text-6xl`). Do **not** add wrapper components for body text.
+- Never write `text-[11px]`, `text-[0.65rem]`, `tracking-[0.16em]`, etc. — the gate (below) blocks new arbitrary font sizes and letter-spacing values. `tracking-[0.1em]` is exactly `tracking-widest`; use the built-in.
+- The micro size tokens deliberately define **no paired line-height**: the arbitrary values they replaced set only `font-size` and inherited line-height, and dense tables depend on that. Don't add `--text-2xs--line-height` without re-checking those surfaces.
+- The custom tracking tokens are registered with tailwind-merge in `src/lib/utils.ts` (`extendTailwindMerge`); if you add a token, add it there too or `cn()` will keep conflicting classes.
+
+## Components
+
+- `<Heading>` (`src/components/ui/heading.tsx`) — cva-based visual heading levels (`display`, `page`, `section`, `card`, `label`) with the rendered tag chosen via `as`, so outline and visual size stay independent. New pages should use it instead of retyping size/weight/tracking recipes; existing headings migrate file-by-file as pages get touched — no sweep.
+- `<Eyebrow>` (`src/components/ui/eyebrow.tsx`) — the uppercase mono kicker label (`tone="brand" | "muted"`, `wide` for 0.2em tracking).
+
+Blog/article typography is owned by `@tailwindcss/typography` (`prose`) and is out of scope — don't migrate MDX content styles to these tokens.
+
+## Chart text
+
+Chart font sizes live in TypeScript, not CSS variables: `CHART_TYPE` in `src/lib/d3-chart/typography.ts`, with the `px()` helper for `.attr('font-size', …)`. The PNG export path (`useChartExport`) serializes the chart with html-to-image, which cannot resolve `var(--*)`; its `resolveCssVarsForExport()` only bakes color-type attributes, so a CSS-variable font-size silently collapses in exports. The shared export font stacks (`CHART_FONT_SANS`, `CHART_FONT_MINECRAFT`) live in the same module.
+
+OG-image renderers (Satori: `opengraph-image.tsx`, `og-image-render.tsx`, `compare-og.tsx`) draw on a fixed canvas and intentionally hardcode display sizes — they are exempt from all of this.
+
+## The ratchet gate
+
+`bun run check:typography` (wired into CI's lint workflow and lefthook pre-commit) scans `packages/app/src` for:
+
+1. `arbitrary-text-size` — `text-[<number>…]` in any `.ts`/`.tsx` (hex colors like `text-[#ed1c24]` are out of scope);
+2. `arbitrary-tracking` — any `tracking-[…]`;
+3. `chart-font-literal` — quoted `font-size` literals inside `src/lib/d3-chart/`.
+
+Per-file counts are compared against `packages/app/scripts/typography-allowlist.json`:
+
+- **A count above the allowlist (or a hit in an unlisted file) fails immediately** — fix it with a token, `CHART_TYPE`, or the standard scale.
+- **A count below the allowlist also fails**, telling you to run `bun run check:typography --update` — so the allowlist only ever shrinks. It doubles as the migration burndown; there is no deadline, offenders migrate when their file is next touched.
+- Matching logic lives in `src/lib/typography-gate.ts` (unit-tested); exemptions (OG renderers, tests, the gate itself) are defined there.
@@ -11,3 +11,6 @@ pre-commit:
 
     - name: typecheck
       run: bun run typecheck
+
+    - name: typography
+      run: bun run check:typography