Design for a world that stopped being afraid of its instruments.
You asked what a design looks like when humanity and technology are more aligned than they have ever been. Here is the uncomfortable part of that question: almost every visual language we have for "the future" was built to depict misalignment.
Heads-up displays, targeting reticles, telemetry, warning lamps, hazard chevrons, surveillance overlays, red alert. That furniture exists because the machine was an adversary, or a hazard, or a thing being aimed. Cyberpunk is the aesthetics of a bad relationship. Even the Orbital Memex we just built runs on it — a lamp bank, a REC light, a hazard ticker, and a stamp certifying the author is PRESUMED HARMLESS.
So the first move isn't to add futurity. It's to subtract the furniture of distrust and find out what's left holding the page up.
If no part of the system is adversarial, no part of it needs an alarm state. Retire the entire hazard vocabulary — sirens, chevrons, reticles, classification stamps, the red that means stop.
This is also why the palette had to move. Alarm red plus acid green is the hazard palette; it reads as danger because that is the job it was drawn for.
Seamless design hides agency, and hidden agency is exactly what you cannot audit. A system you trust is one that shows its joins: what was revised, what is uncertain, what a machine contributed and where.
Marginalia stops being decorative and becomes provenance. Revision state lives in the page, not in a badge nobody reads.
Alignment as a literal property of layout: legible to a person at sixty-six characters, and structurally parseable by a machine, with neither degraded for the other. No "machine-readable version" link — that link is a confession of failure.
Labels in plain words rather than codes, because a plain word is the one encoding both readers already share.
The radical gesture isn't rupture. It's that an 1843 cyanotype plate and a document from 2140 use the same grammar, because the grammar was right. Post-human is not post-history.
The reference set is two centuries of scientific publishing, not science fiction. Your moodboard already believed this — an 1870s apparatus plate sits four pages from a 2026 glitch poster.
Software's native tense is an eternal present: perpetually new, no patina, no trace of having been used. Instruments accrete. A design that can age asserts that the system has a past and expects a future.
Persistence and decay become real mechanics — phosphor afterglow, halftone erosion, the latent image that holds what it was shown until something reads it out.
Every colour must name a substance with a chemistry and a provenance. This is a constraint on you, not on the reader — you cannot drift into a trend palette if each hue has to justify itself as a material.
Five systems, in Plate 03. None of them is a screen colour. All of them will still exist when the screen doesn't.
A principle you can't spend is a slogan. Here is exactly what rule one costs the current site, and what takes each thing's place.
Console lamps are a mid-century way of saying watch this thing in case it turns on you. A blog does not need a status board.
→ A one-line register: what's here, when it changedDiagonal yellow-black is the single most literal warning mark in industrial design. It was carrying four sincere aspirations, which is a strange thing to fence off.
→ A standing line, set plainly, no stripesClassification theatre. It implies an authority that could have withheld the essay, which is the opposite of what publishing it means.
→ Revision count and date — real provenanceFunny once. But it's a joke whose premise is that a person needs clearing, and the whole brief is that we're past that.
→ Nothing. The page can end.The eye reads saturated red-orange as attend to this now whether or not you meant it. Spending it on plate numbers wastes the only true emergency signal you have.
→ A pigment that means ink, not stopA nice joke about living in a terminal. But it addresses the machine's filing system, not the reader's.
→ Plate numbers — the same joke, aimed at the archiveWhat survives the subtraction is the part that was never about threat: the grid, the numbering, the captions, the marginalia, the sense of a document that knows what it is. That's the system.
You were right that the first palette was overplayed. Vermilion-and-acid-green on near-black is the house style of every generated interface this year, and I walked straight into it. So the selection rule changed: a colour has to be a substance.
Each system below is a real material with a chemistry, a date, and a reason to have been used on a document. Switch between them here or in the console; every plate, wireframe and figure on this page re-inks itself.
Ferric ammonium citrate and potassium ferricyanide, exposed to sun. Anna Atkins used it in 1843 for the first book ever illustrated photographically — algae specimens, printed as plates. A pigment that is already a scientific document.
Tannin from oak galls plus iron sulphate. It goes down blue-black, oxidises to brown over decades, and slowly eats the paper it's written on. The ink of nearly every European manuscript, and the only one on this list that has a lifespan.
What copper does when you leave it out. Green, but a mineral green — blue-leaning, desaturated, the colour of a roof rather than a highlighter. Your green, without the emergency.
A toner that converts metallic silver in a gelatin print to silver selenide. It shifts the image toward aubergine and, incidentally, roughly doubles how long the print survives. Permanence that you can see.
The one screen-native entry, and the reason it earns a place: P7 is a two-layer phosphor that flashes blue on strike and decays to a long yellow-green afterglow. Watch the cover field in Latent — new strokes arrive blue and age into green. The animation isn't a filter; it's the material behaving.
Images are dithered at build time to the active pigment's two tones. This is what keeps every photograph on the site on-palette without a single CSS filter — and it's why a palette change is a one-file change.
Generative line for heroes and dividers — about sixty lines of canvas, no payload. Laika keeps her place in the rotation rather than carrying the whole hero on 296 KB of JSON.
The role split stays — you liked it, and it's what lets mono mean something instead of being the substrate. What changes is the candidates. Everything below is embedded here for real, so you're judging the letterforms, not a description of them.
Deliberately absent: Inter, Space Grotesk, Space Mono, JetBrains Mono, IBM Plex. All fine faces, all so heavily defaulted-to by generated design this year that they now read as a machine's handwriting rather than yours.
The cost, stated plainly. These are webfonts, which breaks the no-webfonts rule the site currently holds. Self-hosted and subset to the glyphs you actually use, the recommended trio is roughly 90 KB — about a third of what the Laika JSON costs today. I think it's worth it, but it's a real trade and it's yours to make. If the answer is no, the fallback is a system stack and the design still stands; it just loses some of its accent.
In Rev. A the light theme was really just the dark one with the glow switched off. You spotted the moment it appeared and liked it better than what I'd been building — which is fair, because it was the more disciplined design and it got there by accident.
Ink on bone. The printed register — papers, figures, anything that will be read on paper or projected in a lit room. One pigment, no second accent, no glow. The austerity is the point: on paper, a second hue almost always means you failed to make the hierarchy work with position and weight.
Light on ink. The read-out register — the site at night, decks in a dark room. Here a second tone is permitted, because a screen has a dimension paper doesn't: things can decay. The second tone is what the first one ages into, not a decorative partner.
Note — the page opens in whichever register matches your system theme, and the console overrides it. That's the intended behaviour on the site too: follow the reader, let them argue.
Rebuilt with the hazard furniture gone. Watch what replaced it: the rail states what's here, and the essay states how it came to be.
Fig. 6.1 — No lamps, no ticker, no stripes. The rail says what is here and when it moved; drafts say what state they're in, in words. The four aspirations that were behind hazard tape are now just written down.
There is a habit on the left of treating technology as something that happens to people rather than something people do, and it has cost us the only myth we ever had about it. Prometheus did not organize a strike. He stole a working artifact and handed it over.
The distinction matters because the two politics diverge almost immediately. One asks who owns the fire. The other asks whether anyone still knows how to make it.
Hesiod is careful about the sequence. The theft comes first, then the punishment, then — and this is the part that gets dropped — the fire stays. Nothing in the myth suggests it is ever taken back.
Fig. 6.2 — The classification stamp is replaced by provenance that is actually true: how many revisions, what changed and when, which sources, and where a machine helped. Rule two is only worth stating if the page is willing to be this specific.
Unchanged in principle from Rev. A, and still the reason the system is built this way round: the core is what travels, the finish is what stays home.
We characterise readout fidelity across three storage geometries and show that error-diffused sampling recovers tone structure lost to uniform quantisation at equivalent bit depth.
7.1 — Always Plate register, always one pigment. A plate.sty of about forty lines carries the colour defs, caption style, rule weights and corner marks.
7.2 — Three masters: title, apparatus, specimen. Decks pick their register by the room — Latent in the dark, Plate under lights.
7.3 — Each pigment records what it's made of. Swapping systems is editing one field; the substance line is what stops a future you from picking a colour because it looked nice in a screenshot.
Ordered by visible change per unit of work. The first two rungs are most of the design.
One file. The alias layer from the Orbital Memex work means every component you haven't touched follows automatically.
Display, prose, data. Self-host three subset woff2; demote mono to labels and code.
Lamps, ticker stripes, classification stamp, filepath captions. This is mostly deletion, which is the best kind of diff.
Revision count, sources, machine-assisted sections. The only schema change in the whole proposal, and the one rule two depends on.
A sibling to render-laika.py: images in, two-tone indexed PNGs out, keyed to the active pigment.
Flow field and wireframe solid as rotating plates; Laika joins them instead of carrying them.
Emit the CSS, the .sty and the deck theme from one file. Last, once the values stop moving.