← Back to the screen

Design system portfolio

Design record: Aldan Range

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

The launch manifest for a spaceport, on the week two vehicles hold overlapping windows on the same downrange corridor and the range can only clear one.

The fifth and last brand specimen, and the one that forced the generator's final mechanism.

Where the style comes from

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

python3 tools/brand_tokens.py spacex-brand > systems/spacex-brand/tokens.css
python3 tools/brand_tokens.py spacex-brand --check
python3 tools/brand_tokens.py --self-test
DecisionTranscribed
Ramp#ffffff #f0f0fa #e0e0e8 #5a5a5f #3a3a3f #0a0a0a #000000
Chromaticnone
Type80 · 60 · 48 · 16 · 13 · 12 px
Trackingpositive at every size: 1.6px at 80, 1.17px at 13, 0.32px at 16
Weights400 and 700
Radiinone. Nothing that is not a circle carries one
Depthnone. A near-black panel on black is the only lift
Modesnight first, with a full daylight palette beside it
Motionnot published

It is the only monochrome brand in this family, and that is not a simplification of the reference: it is the reference. Its primary is #000000, its link on dark is #ffffff, and the single chromatic value anywhere in the file is the browser's own default link blue, listed as a fallback. What marks a primary action here is an INVERSION rather than a hue.

That broke an assumption in the generator, which had treated the accent as one value shared by every theme. accent, on-accent and accent-text are now pinned per theme, and (the part that actually failed) the accent tint is solved from the pinned value rather than the declared one, because mixing black into a black canvas produces no visible wash and the solver correctly raised rather than returning something invisible.

The finding worth carrying. This palette has no legible mid-grey on dark. Its published ink-mute #5a5a5f reads 2.91:1 against the near-black panel, under what even a control outline owes, let alone body text, so the tertiary text tier on the night setting is the pale hairline colour instead. The dark page therefore has two text weights where the light one has three, and the design-notes panel says so.

The direction

The second state

The corridor conflict. An index's promise is that its entries are independent; this is the case where two of them are not, and neither is wrong. Both windows are valid, both vehicles are ready, and the range clears one vehicle at a time on that heading, so the page states the overlap, the next clear slot and the hour by which somebody owes a decision, rather than showing two rows that each look fine.

The pair it makes with ferrari-brand

Both references set an 80px display step. Ferrari closes the tracking to −0.028em; this one opens it to +0.02em and sets the whole thing in capitals. Same size, opposite decision, and the two pages do not look remotely alike because of it. It is the clearest thing this family says about what a type decision is actually worth.

Deviations from CONTRACT.md

Findings kept, with reasons

What the gates changed

craft_lint's no-press-state caught a mission tile that lit up on hover and did nothing when clicked, which is a card telling the reader a lie. The mission name is now a real link with its hit area stretched over the tile, so there is one link per mission rather than six, the hover belongs to something, and the focus ring is drawn on the tile rather than on four words inside it.

The uplift round (2026-10-29)

The page stopped being a list of tiles with a banner above it and became a range-control console. The archetype stays an index; the conflict is now an instrument the reader operates rather than a paragraph they read.

Boson findings read and left: target-size warnings on nav links, theme button and tile names (real boxes measure 46 to 51px tall; the probe measures a text run), the rotated "Shared corridor" label reported as overflowing (it is rotated 42 degrees), and keyboard_probe's focus-not-visible on the tile names and footer link, which paint correct focus rings when tabbed to (checked by screenshot and computed style). Launch-policy findings are site-level.

Round four

Round eight (2026-10-29)

Round nine (2026-11-09)

Judged as the range controller: move a window, read the manifest, resolve the conflict, by pointer and by keyboard; phone emulation at 360 and 390 (coarse pointer, 3x), 200% zoom, both display settings, 1920. No horizontal overflow at any width from 320 to 1920 in 10px steps. Heuristics before to after: 27 to 29 of 40.

Fixed, most serious first:

Left: the moved bar shrinks to 26px once it lands in the squeezed 21 hour stretch (the squeeze is the point of the axis break; severity 1), the phone manifest indents plain tiles by their padding (1), and the display button names the current setting rather than the action (1; its accessible name says both).

Round ten (2026-11-09)

Scored fresh on the ten heuristics, with every state driven (move, hold, clear, publish, reopen) by pointer, keyboard and 360 and 390 phone emulation (coarse pointer, 3x), in both settings, at 320 to 1920. Before: 3, 3, 2, 2, 2, 3, 3, 3, 3, 2, which is 26 of 40 on a stricter read than round nine's 29. After: 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, which is 30.

Fixed, most serious first:

Left: the theme button names the current display, not the action (1; its accessible name says both); the "Hold" verdict is explained by one line under the clock, not defined on its own (1); the sliver's label sits on the hatch behind a halo, busy but legible (1).

Round eleven (2026-11-10)

Defects, from an independent score of 34 of 40:

Invention: the strap wording for Hold and Clear, and the strip text for the clear and published states, all restating facts already on the page ("Corridor clear, no wait", "Week sent to six customers"). No new numbers, rules or products.

Left: the conflicted console is ink on a light page and ground on a dark one by design (the severity 1 note); the bold dock strip does not change that.

Round thirteen (2026-11-10)

Defects, from an independent score of 35 of 40 (ship verdict yes, with one note):

Invention: the wording "of 6, 1 on weather hold" (restates the manifest) and the 64 px and 12 px margins of the scroll band. No new numbers, rules or products.

Left: the fixed bar scrolls off the top when the moved one is dragged to the far end of the day (severity 1, by the rule above).

Round twenty-eight (2026-11-10)

Defects, from an independent score of 36 of 40 (ship yes, with one note):

Inventions: the wording of the refusal sentence (restates the wait and the Snap action already on the page); the "+1" moving under the pad name at 320; the 6 px step. No new numbers, rules or products.

Round thirty (2026-11-10)

Defects, from an independent score of 35 of 40 (ship yes, with one note):

Invention: the 700 px height threshold and the spacing values; no new words, numbers or states.

Left: at 320 wide the status tag and the snap label each wrap to a second line (the content is 222 px), so the dock there is 264 px, not the 236 px of 360. A slider sweep to 24 h with Corvid 9 still leaves 15 px of the moved bar under the dock at the far end at every phone height; it is identical on the previous file.

Round thirty-two (2026-11-10)

Defects, from an independent score of 35 of 40 (ship nearly, with one reservation):

Inventions: the 6 px inset and 3 px width of the ring; the 6 px tick and 20 px padding on short phones; the filled "Sent" block and the Manifest caption wording (both restate "sent to six customers" and the 04:12 Z already on the page). No new numbers, rules or products.

Round thirty-four (2026-11-10)

Defects, from an independent score of 37 of 40 (ship nearly, with one reservation):

Inventions: the lane boxes (hairline, the grid stroke) and the tick drawn with two borders on the sent status; the 2 px threshold for the bracket; the label position. No new words, numbers or states.

Round thirty-six (2026-11-10)

Defects, from an independent score of 37 of 40 (ship yes, with one note):

Inventions: the rule that the ask (Send pressed for) freezes the plan as the sent week does, and the document-level Escape. No new words, numbers or states. The "Move it in the console" prompt on tiles that have already cleared, before Send (severity 1 in the score), is unchanged: a cleared week can still be re-planned until it is asked for.

Round thirty-eight (2026-11-10)

Defects, from an independent score of 34 of 40 (ship yes, with one note):

Inventions: the 500 ms arming delay (the rule said about 500); focus to Cancel rather than Send; the row living in the console while a Review-raised confirm is open; on a phone the sent status in the console is dropped because the dock's first line already says "Sent to six customers". No new words except the two live announcements ("Send is ready.", "Reopen is ready."). A double Enter on Publish or Review now cancels, by design: the second press lands on Cancel.

Round forty (2026-11-10)

Defect, from an independent score of 36 of 40 (ship nearly, with one reservation):

Invention: the 16rem width of Cancel and its place at the right edge; the hidden-but-present plan controls while asking or sent on a wide screen (the phone already drops them). No new words, numbers or states.

Round forty-two (2026-11-10)

Defects, from an independent score of 35 of 40 (ship nearly, with two severity 2 defects and three cheap ones):

Inventions: the 48 px separation; the figure word "Sent" and the label "Manifest" on the clock; the two reopened captions (they restate the existing "customers keep the manifest already sent" and "sent to six customers"). The reopened flag lasts until the page is reloaded. No new numbers or states.

Round forty-four (2026-11-10)

Defects, from an independent score of 36 of 40 (ship with a note). Rounds thirty-eight, forty and forty-two each patched one width where a layout change put a control under the finger, and each re-score found another width or height. This round fixes the class, not the width.

Inventions: the 800 ms window (the rule said about 800); the guard also swallows the first press on Snap or Review when it lands inside the window, which includes the same control whose label changed (Snap becomes Review in place); the stage of four rows on a phone and Cancel at full width; Send at the top of the dock (the DOM order stays Cancel then Send, so on a phone Tab goes from the bottom button up to the top one, the safe answer first); Reopen at the left; no wrap for Snap and Reset on a phone; the sent facts row words (all existing). No new numbers or states. Not done: the 8 px by which a sent dock's first line is shorter than a clear one when the dock is in flow rather than pinned (Reopen still stands inside Review's old box).

Round forty-six (2026-11-10)

Defects, from an independent score of 36 of 40 (ship, with one reservation, severity 2, and two severity 1):

Inventions: none in words, numbers or states. The two status elements swap which one is shown on a phone in a sent week (both existing). The slider's row now holds the status and caption together; check that two lines never overlap there at very large text sizes (the row is 83 px at 320 and the pair is 52 px).

Round forty-eight (2026-11-10)

Defects, from an independent score of 37 of 40 (ship, with a note: one severity 2 and one severity 1):

Invention: the upward layout and its card (one stroke, the page ground, no new words); the 16 px inset. Not done: Review pressed with its top less than about 50 px from the top edge of the viewport at 768x1024, while the dock is in flow, leaves Send above the fold, because the scroll that would show it puts Send under the finger; the point is kept safe and the group is not shown. At 390, 360 and 320 the same press is brought into view flush (Send top 0 to 8).

Round fifty (2026-11-10)

Defects, from an independent score of 38 of 40 (ship, with a note: one severity 2, one severity 1):

Invention: the 8 px intent threshold and the 22 px grab radius (the thumb is 20 px wide, so the radius gives a 44 px target); the relative, not absolute, drag on touch; (any-pointer: coarse) as the condition, so a hybrid screen with a mouse is covered by the handler's mouse branch. No new words beyond the sent strap sentence. Cost, named: on a touch screen the slider can no longer be set by tapping the track. The taps that still move the plan are Snap, Reset and the tile links; the bar drag works at 768 and up and the keyboard works everywhere. WCAG 2.5.7 asks for a non-drag way to do what a drag does, and Snap and Reset are the only fixed-amount taps.

Round fifty, addendum: the hour steppers (WCAG 2.5.7)

The touch rule above made a drag the only way to set the slider on a touch screen. A drag needs a single-pointer alternative, so the slider now has one.

Invention: the one-hour step, the 12 px gap, and the disabled-at-the-end wording of the two names (no new product facts).

Round fifty-two (2026-11-10)

Defects, from an independent score of 35 of 40 (ship, with a note: four severity 1). Each was reproduced on the previous file before the edit (a, c and d at 320x568 and 1024x768 as reported; b at 1280x800).

Inventions: the 72rem upper edge of the two-row band (the 3-column track is 228 px at 72rem and falls below 200 under it); the margin and the 16 px guard in revealSent() (the same numbers reveal() uses); stepper focus treated like slider focus. No new words, numbers or states.

Proof. sweep.mjs, the round forty-four one, unchanged, on the final file: 37 viewports, 10 paths, 6 delays, 2,220 cells: 0 page errors, 0 first presses missed, 0 harmful; every delay column is 135 open-ask, 69 cancel, 166 none, so the only kinds are cancel, none and open-ask. Some wide-viewport cells were lost to a crashed tab under memory pressure from other sessions and were re-run at lower concurrency until none were lost. touch.mjs (CDP touch, 55 cells, unchanged): 55 of 55 in most runs; about one run in four has one miss, always the same cell (390x844, thumb at 700, drag +60 px: value unchanged, page scrolled 45 px). The harness sets 700, which starts the page's own 145 ms smooth scroll, waits 100 ms and then touches while the page is still moving; the browser takes the touch for the scroll and cancels the pointer (logged: pointerdown at 23 ms, scroll events to 143 ms, pointercancel at 105 ms). With the harness waiting 600 ms after the set the same cell is 8 of 8 clean, and in 12 isolated repeats at the original 100 ms it is 12 of 12 on this file and on the previous one. The previous file showed no miss in 8 runs of the full script, so the rate may be higher here; the cause I could find is timing, not the drag handler, and I did not find a change of mine on that path. The slider is 435 px at 1024, so the touch.mjs thumb drag of 60 px now moves 210 min there (450 before).