the convergent finding
Independently, all four pools land on the same moves — and they validate the SFDS law rather than challenge it. The most-trusted leaderboards (SWE-bench, Aider, Epoch) and the most-credible product systems (Linear, Vercel/Geist, Stripe) earn their credibility from exactly the restraint SFDS already codifies: flat color, hairline borders, square corners, mono for data, serif for headlines, one accent, light + dark. Nothing to reverse. The work is to sharpen: a surface-ladder for depth, tabular numerals, a per-accent role split, a machine-honest retro layer, and a validated data palette.
What to adopt
The leaderboard, as a credible instrument
- Own the quality × cost Pareto scatter — a fusion point alone in the top-left corner is the entire pitch in one frame (Artificial Analysis).
- A
Command column — the exact CLI to reproduce a row is the strongest "receipts" signal there is (Aider).
- Inline ± confidence intervals —
50.3 ±8 reads as measured, not marketed (LMArena, SWE-bench).
- A
Date column + frozen-vs-latest split — directly serves the weekly knock-down ritual (SWE-bench-Live).
- Identity = logo + name, never color — frees color entirely for magnitude; rank shows by position, not hue.
Trustworthy-minimal craft
- Depth from a surface-ladder, not shadows — Linear ships zero drop-shadows; 4–5 near-black surfaces + hairlines carry all hierarchy.
- Tabular numerals everywhere numbers appear — for a leaderboard this is load-bearing: scores align to the pixel, ranks don't reflow.
- Accent as punctuation, with a per-color role — gold = one job (the live/record signal), blue = another (interactive/reference); they never compete in one viewport.
- A tight weight band (400–600) + aggressive negative tracking on headlines — hierarchy from craft, not "bold everything."
- Docs as product — inline runnable examples, raw markdown served for agents + humans (Stripe).
Retro that reads as craft, not costume
- The monospace grid as the actual layout unit — columns snap to character cells; the alignment is the proof the constraint is real (the monospace web).
- Box-drawing / hairline tables for one signature leaderboard — "the machine drew this."
- Machine-honest receipts — a mono footer per card:
model · params · eval-set · commit · UTC. Exposing the machinery is the honesty move.
- The "0 days since last SOTA" counter as a live status readout — functional theater; the number actually updates. One per page.
- One blinking block cursor as the only animation. Restraint is the tell.
- Gold is amber-phosphor.
#d88507 sits in the real single-phosphor terminal lineage — so leaning retro is free authenticity, not costume (and it's why green/purple would read as cosplay).
What to avoid — the AI-tells
The 2026 "AI-generated" signature is a set of absent decisions. SFDS already forbids most; the ones marked NEW are additions the research surfaced.
Never (reads as AI / template)
- Purple / indigo / violet — the single loudest tell
- Blue→purple gradients, glow / gradient text
- Rounded-everything, soft ~0.1 shadows, glassmorphism NEW: blur
- Hero + 3 feature cards + bento grid
- Default shadcn skin, Inter as the only face
- NEW One-sided colored accent bar on a card
- NEW Weightless copy ("Build faster. Ship smarter.")
- NEW Centered-everything, uniform whitespace, no density contrast
- NEW Fake logos / fabricated metrics — fatal for a leaderboard
- NEW Forced dark-only; neon-terminal cosplay (Matrix-green/cyan, CRT scanlines)
Instead (reads as decided)
- Flat color, one accent used only for the story
- Depth from spacing, surfaces, and hairline rules
- Square edges, all-sides-equal borders, one edge language
- Real type hierarchy: serif headline, mono data, tight weights
- Asymmetric, document-like, generous whitespace
- Real data, real model names, dated + reproducible
- Retro that does work: aligned grid, box tables, honest status
- Motion only where it clarifies; one cursor, reduced-motion safe
Palette proposal
Brand signals — anchored to the 😱, per-mode
The gold + blue sampled from the emoji stay the brand's soul, but they carry meaning, and they need per-mode values because a single mid-tone can't clear contrast on both true-white and true-black.
LDtoken · rolenote
gain — gold#d88507 · #eaa524
The "live / record / winner" channel — the phosphor. Rationed so it stays an event. Borderline on white for small text → darken to ~#a8660b for small on light, or use large/bold only.
brand — blue#8fadde
The "cool / reference / interactive" channel. A light tint → dark-mode text & light-mode fill only; never small text on white.
gain-gradgold → blue
The one sanctioned gradient — reserved for the winner/delta signal only. Orange↔blue is the CVD-safe axis, so the gain read is accessible by construction (still back it with length/position).
Categorical data palette — 10 entities, colorblind-safe, no purple
The honest ceiling for a guaranteed colorblind-safe set is ~8 hues; getting to 10 without purple (the cheapest 9th–10th hue) means the first 8 are genuinely CVD-safe and 9–10 are backed by a redundant channel (marker shape / direct label). Built from Okabe-Ito + Paul Tol, with the saturated gold band vacated so no series is ever confused with the winner. Two coordinated sets — hue identity is constant per slot; lightness/chroma shift per mode.
LD# namerationale
1 · azure#3b6fb0 · #6f9fd8The CVD-stable anchor. Darker/more saturated than brand periwinkle so it never reads as brand-blue.
2 · green#4f9d3f · #6ac25aTrue green. Blue↔green is the most CVD-robust pair.
3 · vermillion#d84f38 · #f2704fWarm anchor at ~9° — clearly redder than gold, can't be the winner.
4 · cyan#33b1d4 · #56cdeaLightest cool; distinct from azure (darker) and teal (greener).
5 · rose#d95a97 · #f07db0Red-side pink at ~330° — NOT violet. The legitimate purple replacement.
6 · yellow-olive#b59a1f · #d8c34aDark yellow (pure yellow is invisible on white); greenish + dark to stay clear of gold. Replaces the old amber that collided with the brand.
7 · teal#1f8a86 · #3fb3aeDeep blue-green ~178°; distinct from green (bluer) + cyan (darker).
8 · brown#8a5a3c · #b98a63The muddy warm anchor; separates by lightness (L*≈45).
9 · slate#6b7785 · #98a4b2The neutral — "other / baseline / de-emphasized." Every 8+ set needs one.
10 · wine#9c3550 · #cd5e78Darkest saturated red ~345°. The hardest slot — validate the vermillion/brown/wine cluster under deuteranopia; back with markers.
usage rules (what keeps it honest past 8)
Reserve the gold band + brand periwinkle — no --cat-* occupies them. Order matters: assign 1→10, so a ≤5-series chart renders azure/green/vermillion/cyan/rose — maximally separated + brand-safe. Past ~8 series, stop adding color: group the tail into slate "Other," direct-label lines, or use small multiples. Validate every hex through Viz Palette (protan/deutan/tritan + ΔE), WCAG 1.4.11 ≥3:1 against both backgrounds, and a grayscale test — ideally wired into build.mjs as a CI gate.
Reference gallery
The strongest real examples, tagged with why they work. ↗ external
Trustworthy-minimal craft
Retro / terminal / refined-brutalist
Data-viz & accessibility canon
What this changes in SFDS
The research → concrete edits, staged for the next phase (after you react):
- Add tokens: a 4–5 step light/dark surface ladder; the 10
--cat-* colors above (per-mode); negative-tracking display values; tabular-nums enforced on all mono numerics; a per-accent role allow-list (gold vs blue); a narrow weight band; per-mode gold small-text darkening.
- Add anti-rules: one-sided accent border · hero+3-cards · weightless copy · glassmorphism/blur · glow-text · fake metrics · forced-dark-only · neon-terminal cosplay · centered-everything · uniform-whitespace.
- Add a retro layer: box-drawing table style, machine-honest receipts footer, the SOTA-counter status readout, one block cursor, block-glyph sparklines.
- Reconcile the docs (SYSTEM.md paths + post-pivot framing) and wire a palette CI gate into
build.mjs.