← Back to the screen

Design system portfolio

Design record: Cinder

The four direction lines behind this page, the generator command that produced its tokens, and the pairs it was measured against.

The job queue for a research GPU cluster: sixty-four accelerators across eight nodes, eleven jobs running, nine waiting, and one that will never start.

The second brand specimen, and the opposite end of the corpus from tesla-brand. Where that reference publishes nine colours and four type sizes, this one publishes thirty-one colours and an eighteen-step ramp with front matter naming every token.

Where the style comes from

Transcribed from awesome-design-md/design-md/nvidia/DESIGN.md, read 2026-09-16, and emitted by:

python3 tools/brand_tokens.py nvidia-brand > systems/nvidia-brand/tokens.css
python3 tools/brand_tokens.py nvidia-brand --check
python3 tools/brand_tokens.py --self-test
DecisionTranscribed
Ramp#ffffff #f7f7f7 #cccccc #a7a7a7 #898989 #757575 #5e5e5e #1a1a1a #000000
Chromaticone: NVIDIA Green #76b900, pressed #5a8d00
Link#0046a4 on the white canvas, the brand green on the black one
Error#e52020
Type48 · 36 · 24 · 20 · 17 · 16 · 15 · 14 · 12 · 11 px
Weights400 and 700, and hierarchy is built from those two plus size
Radius2px, everywhere. "Never go to 0, never go past 4"
Spacing8px base, 64px section rhythm
Hold~1280px
Depthno shadow on any card or content surface
Modesa black canvas and a white one, alternating down one page
Motionnot published; hover states are a stated known gap

Three findings, each asserted by --check rather than described.

  1. The reference already solved the link problem, and differently in each mode. An inline link is #0046a4 on the white canvas and the brand green on the black one, and its Don't list then forbids that blue anywhere else: "not a button color, not a chrome color", and forbids substituting any other green for the brand green in a CTA. Solving accent-text would have invented a dark green for the light theme, which is exactly the substitution the brand rules out by name. Both values are pinned per theme and both were measured against the worst ground in their own.
  1. The brand red cannot quite carry a sentence on the recessed band. #e52020 reads 4.61:1 on white and 4.30:1 on the soft surface, so the page emits error-text solved at the same hue, #e1181b in light, #f5352f in dark. The fill keeps the published red; only the text value moves. This is the general case the generator's semantics mechanism was added for.
  1. Black text on the brand green reads 8.71:1; white on it reads 2.4:1. The reference's own on-primary is #000000, and the solver independently picks it. A specimen that put a white label on that green would be unreadable and would look, at a glance, like every other product.

The direction

The second state

The unplaceable job. It is the state a table-first console makes hardest, because a table's whole promise is that the rows are comparable, and this row is not comparable to the eight above it, it is in a different category wearing the same word.

This specimen is allowed red and the Tesla one is not, which is the most useful thing the two of them say side by side. Same family, same problem, opposite palettes: this reference publishes an error colour and a semantic layer, so the band uses it, and still does not rest on it, because the heading names the cause and the row carries the words "Cannot be placed".

Deviations from CONTRACT.md

Findings kept, with reasons

What the gates changed

Three findings were fixed rather than kept, and two of them improved the page:

Uplift, 2026-10-29

The archetype and the bold decision stand; the way the page proves the decision changed.

Round four

Round eight

Round nine

Scores on the ten heuristics, before and after (0 to 4): status 3 to 4, real world 3 to 3, control 3 to 3, consistency 3 to 3, error prevention 3 to 3, recognition 2 to 3, efficiency 2 to 3, minimalism 3 to 3, recovery 3 to 3, help 2 to 3. Total 28 to 32. Below 3 after: real world (the cluster, its group names and the A100 line are invented, so a real operator's own vocabulary is not tested), control (a pick has no undo beyond picking again), consistency (the pick bar is the one surface that is neither chapter nor lower page), error prevention (the slider and switch cannot be undone one step at a time, only restored whole).

Fixed, most serious first:

Checked and found right: 61 of 64 (eight nodes of eight, fen-08 holds five), eleven running and nine queued, 19 m to the next whole node (fen-02, job 4408), 3 h 12 m waited (192 minutes), the 4471 landing on fen-02 at +19 m when halved. The page carries no dates or weekdays.

Round ten

A second, colder read. Scores on the ten heuristics, before and after (0 to 4): status 4 to 4, real world 3 to 3, control 2 to 3, consistency 3 to 3, error prevention 3 to 3, recognition 3 to 3, efficiency 3 to 3, minimalism 3 to 3, recovery 2 to 3, help 2 to 3. Total 28 to 31 (round nine's 32 did not survive a read that tried to undo a commit and to click what looked clickable).

Fixed, most serious first:

Inventions: "Undo" as a one-step history of the one editable job (nothing in the brief names it); the figure sub-lines' wording; the receipt sentence. No new numbers: all come from the scheduler.

Left: the cluster's vocabulary is still invented (severity 1); the floor squares are clickable by mouse only (severity 1, the queue is the equivalent).

Round eleven (2026-11-10)

Inventions: the two label strings, and the control's place in the Queue header. No product fact, number or page added. Left: the two severity 1 notes (the phone sticky bar stays on the previous job after "Go to 4471"; no jump link from the lede to the verdict on a phone).

Round thirteen (2026-11-10)