SDPG-HUD // REV 02 All Systems
GROUND 01
BLUEPRINT
GROUND 02
CRT
The system's character, standing in the poster stage

Design

デザイン dɪ·ˈzaɪn
Insert Coin

A monochrome arcade targeting-HUD. Two grounds, one visual world, and no chroma anywhere.

Two things to hold on to. Emphasis is a filled block, never a colour - there is no accent hue to reach for. And status is encoded in form: filled is active, outline is idle, dashed is disabled or in flux. Read shapes, not hues.

The system is SDPG-HUD

Read this first

  1. These values are the system. Everything below is a token that exists in css/hud-core.css. Use them; do not invent parallel ones.
  2. Never add colour. The moment a hue appears, the whole encoding collapses - because form is carrying the meaning that colour usually carries, a single red breaks every other signal on the screen.
  3. Reach for a filled block before anything else. Emphasis, selection and active state are all one move: invert the surface.
  4. Both grounds, always. Blueprint and CRT are hand-authored, and nothing warns you if you only checked one. Hit Invert.
  5. Names are roles. --ink is the foreground, not the colour black - on the CRT ground it is near-white.
  6. No ad-hoc values. No raw hex, no one-off sizes, no new easing. If a token does not cover your case, that is a conversation about the system.
§01

Colour

No chroma

Ten role tokens and no accent. Each swatch below shows blueprint on the left, CRT on the right, so both grounds are visible without switching - though the Invert button is there and everything on this page responds to it.

inkForeground, and every filled surface.#15181C#E7E9EC
ink-700Prose and secondary text.#3A3E44#B9BDC3
gray-500Labels, captions, meta marks.#6B7076#9A9EA5
gray-400Icons at rest, faint marks.#8B9096#7C8087
gray-300Disabled edges and fills.#B3B7BD#565A61
gray-200The quietest visible fill.#D1D4D8#3A3D43
groundThe page itself. Carries the grid.#E6E8EA#0B0C0E
panelPanel surface, one step off ground.#F1F2F4#131418
panel-2Raised panel, and text on a filled block.#FAFBFB#191B1F
fieldInput surface. Recessed, never raised.#ECEEF0#1D2025

Derived - never declared twice

TokenDerivationRole
--lineink at 15%The hairline. Every border that is not load-bearing.
--line-strongink at 32%Panel edges and section rules.
--gridink at 6%The graph-paper ground, tiled behind everything.
--oninkThe filled surface of an active control.
--on-inkpanel-2 / groundText sitting on that filled surface.
The three derived neutrals are the reason the two grounds cost nothing. Because lines are mixed from ink rather than declared as their own hex, inverting the ramp inverts every border with it. Hardcode one hairline and it will be the single mark that stays dark on the CRT ground.
§02

Typography

Four voices

Three stacks doing four jobs, all from system fonts - nothing to download. Mono is the default, not the exception: the body font appears only inside running prose.

The four voices
Display · condensed heavy · uppercase
Specimen
Heading · mono · tracked wide
Section Heading
Body · humanist sans
Running prose is the one place a proportional face is allowed. Everything else on the surface is set in mono, which is what makes columns of data line up without a table.
Caption / data · mono
CH-01 · GROUND 02 · 19 009 304
Tokens
display2.6rem / 900Heroes and numerals. Tracking .02em, scaled 1.05 wide.
heading1.2rem / 700Mono, uppercase, tracking .2em.
body1rem / 400Leading 1.7, capped at 60ch.
caption.72remMono, uppercase, tracking .16em.
eyebrow.66remTracking .28em. The widest thing in the system.
label.62remTracking .2em. Panel and specimen labels.
Tracking widens as size shrinks - the opposite of the usual rule, and deliberate. Wide tracking on small mono is what makes a caption read as instrument labelling rather than as fine print.
§03

Space and layout

One column

One measure, one gutter, four breakpoints. The grid behind the page is decoration, not a layout grid - do not snap to it.

Scale
44px
88px
1414px
2222px
2626px
3434px
5858px
Measure and breaks
measure1120pxMax content width, centred, 22px gutter.
prose64chRunning text never runs wider.
bar44pxStatus bar height at every width.
break-lg820pxColumn grids collapse to one.
break-md720pxSecondary bar segments drop.
break-sm640pxSix-up motif grid becomes three-up; tickmarks go.
break-xs520pxBar keeps only the index and the controls.
Panels do not nest. A panel inside a panel produces two hairlines a few pixels apart, and at this line weight that reads as a rendering fault rather than as hierarchy. Split the content into two panels side by side instead.
§04

Form

Hairline

Corners stay nearly square. The silhouette comes from line weight and from bracket furniture, not from radius.

Radii
11px
22px
33px
44px
pill100px
Line weights
hairline1pxDividers, inactive edges, the grid.
edge1.5pxPanel and control borders. The default.
heavy2pxBrackets, focus, the outlined display face.
dashed1px dashedDisabled, unsaved, in-flux. A state, not a style.
There are no shadows. Depth is faked with brackets and with the one-step surface ramp. A drop shadow on the CRT ground turns into a grey smear, so the system simply never learned the trick.
§05

Motion

One loop

Almost nothing moves, and what does moves instantly. There is no easing curve in this system - transitions are linear and short enough that a curve would not be visible anyway.

TokenValueWhere
tint120msBackground and colour on buttons and icon buttons.
track150msThe toggle knob travelling, and its track filling.
press50msThe 1px downward nudge on a pressed button.
blink1.4s steps(1)The live indicator. Stepped, never faded - a CRT dot is on or off.
steps(1) is the whole motion philosophy in one value. A smooth fade would read as a modern web animation and break the register instantly. Everything that changes here snaps, because the hardware this system imitates could not interpolate.

prefers-reduced-motion kills the blink and every transition outright - there is nothing in the system whose meaning depends on movement.

§06

Screen

Enhancement only

One optional surface treatment: a phosphor sweep. A beam rotates and decays across the screen, scanlines cut it, grain sits on top, and range rings lock to the pointer. The pointer is the target - move it across the right-hand panel and the reticle follows on a spring.

Static fallback · grid and scanline
Live · move the pointer across it
UniformValueWhat it does
uSweep0.55 rad/sBeam rate. One revolution takes about eleven seconds, slow enough to read as instrumentation rather than as a spinner.
uPersist2.3Trail decay. Higher is a shorter tail - this is the phosphor, and it is the only thing that makes the sweep read as a sweep.
uScan0.14Scanline depth, at one cycle every two device pixels.
uGrain0.05Phosphor grain. Enough to kill banding, not enough to read as noise.
uRings / uRingGap3 / 0.075Range rings around the target, breathing on a 1.6s pulse.
uGround / uInktokensRead from the live values, so the treatment inverts with the ground like everything else.
springk 52 / d 9The reticle is followed on a spring, so it has mass and settles instead of snapping.
The no-chroma rule is structural here, not a matter of care. The shader accumulates a single intensity and its last line is mix(uGround, uInk, ink) - so the only colours it is capable of emitting are the two ground tokens and the greys between them. There is no way to leak a hue into this panel without rewriting that line, which is a far better guarantee than remembering not to.

Where it belongs: behind a hero, or filling an empty state or a panel that has nothing in it yet. Not behind a working surface - it is the decorative register, and it lives under the same quarantine as the gauges and the D-pad. Under prefers-reduced-motion it renders one settled frame and never starts the loop; with no WebGL2 the static panel on the left is the whole design.

§07

Components

Live - hover them

Every state below is real. Hover the buttons, drag the slider, click the toggles. Specimen labels are deliberately generic - see STANDARD.md R1.

Buttons
Inputs
Toggles
Filled is on Outline is off Click to flip
Badges
Solid Outline Neutral Tag Dashed Attention
Readouts
47Count
Capacity
HI SCORE19 009 304
The three badge states are the encoding in miniature. Solid, outline and dashed carry active, idle and disabled with no hue involved - and because they are shapes rather than colours they survive being printed, photocopied, or rendered by a reader who cannot distinguish red from green.
§08

Motifs

Recognisable at a glance

The marks that make the system identifiable. Icons are a single 1.7px stroke on a 24px box, with one deliberate exception - the pixel heart, which is drawn on a 9×7 grid and rendered with crispEdges.

Icon set
Target
Register
Warn
Block
Shuffle
Lock
Unlock
Copy
Done
Life
Prev
Next

The character

The system's character, full figure

The one figurative mark in an otherwise geometric system, and the only place a drawn image is allowed. It is desaturated to the ramp like everything else - the system has no chroma, and the character does not get an exemption.

placementposter stage onlyBottom-anchored, centred, standing in the stage. It belongs to the hero.
heightmin(90%, 780px)86% below 640px, so it keeps its feet on the band.
depthz-index 2Above the poster ground and below the wordmark - the type crosses in front of it.
filtergrayscale(1)Forced, not assumed. A colour source file must still land on the ramp.
pointernoneIt never intercepts a click; the stage behind it stays reachable.
One per page, and only on a poster. The character is what keeps the system from reading as pure instrumentation - but it earns that by being rare. Put it on a working surface and it stops being a mascot and starts being clutter, which is the same rule the gauges and the D-pad live under.

Furniture

Beyond the icons and the character, four pieces of furniture carry the register: the corner bracket on panels, the registration cross, the scanline wash, and the viewport frame pinned to the four corners of the window. Below, the decorative register at full strength - reserved for heroes, empty states and section furniture, never for working surfaces.

0.90Level
Dial
Gain
Navigate
Action
The decorative register has to stay quarantined. Gauges and D-pads are what make the system fun and what would make it unusable if they leaked into the working surfaces - a dense list of controls does not need a dial next to it. One console per page, at most, and never inside a form.
§09

Composition

Specimen

The parts assembled into one arrangement: a framed module holding a list of units, each with a label, a value and its controls, one of them held in the inverted state. Deliberately abstract - what matters is the rhythm, not what the rows contain.

MODULE // SPECIMEN REF 19 009 304
Unit 01 · Held alpha, bravo, charlie, delta
Unit 02 echo, foxtrot, golf
Unit 03 hotel, india, juliett
Unit 04 kilo, lima, mike
Grouped
01: alpha, bravo, charlie, delta

02: echo, foxtrot, golf

03: hotel, india, juliett

04: kilo, lima, mike
Flattened
alpha, bravo, charlie, delta,

echo, foxtrot, golf,

hotel, india, juliett,

kilo, lima, mike

Anatomy

PartAs builtWhy it is that
Framepanel + brkCorner brackets on two opposing corners only. Four would close the box and lose the instrument reading.
Module headcaption / captionIdentity left, reference right, both in the caption voice. The head never competes with the rows.
Unit row118px / 1fr / autoFixed label column so the values align down the list without a table.
Held rowinvertedThe whole surface fills. This is the only "selected" treatment the system has, and it is the same move as a solid button.
Controlsicon buttonsPer-row, right-aligned, outline at rest. The active one fills - matching the row's own encoding.
Outputtwo panesSame content at two grains. Mono makes the comparison legible without labels on every line.
Footer actionsolid buttonOne solid per module. A second would leave the reader with no primary.
Note what this specimen is not. It is not a screenshot of an application with the labels changed. The rows carry the NATO alphabet precisely because it means nothing - a reader takes away the structure rather than a guess at what the module was for.
§10

Rules

The refusals matter most
Do
  • Encode state in form: filled is active, outline is idle, dashed is disabled or in flux.
  • Reach for the inverted block for emphasis and selection. It is the whole vocabulary.
  • Author and check both grounds. Blueprint and CRT are hand-written, not derived.
  • Keep mono as the default and let the body face appear only in running prose.
  • Let the dashed edge mean something. It is a state, and spending it as decoration costs you a signal.
Do not
  • Add any hue. Not for errors, not for success, not "just this once" - form is already carrying that load.
  • Add a shadow. There is no elevation model; on the CRT ground a shadow is a grey smear.
  • Let the decorative register - gauges, D-pad, scanlines - onto a working surface.
  • Nest panels. Two hairlines a few pixels apart read as a rendering fault.
  • Give anything a radius above 4px, pills excepted. Round corners drain the instrument out of it.
  • Interpolate. The live dot steps; it never fades.
  • Run the phosphor sweep behind a working surface. It is decorative register, under the same quarantine as the gauges.