Build

  • Framework — Next.js 16.3.2, App Router
  • Runtime — React 19.2.8
  • Language — TypeScript 5.9.3, strict
  • Animation — motion 13.1.1, loaded lazily and only inside the shell
  • Node — >=22.18.0
  • Commit — dc36e5fc21b5

Every route is a server component rendered ahead of the request, so the HTML a crawler, a reader-mode view and a printer receive is the same HTML a browser receives. The desktop — the boot screen, the windows, the task shelf, the command line — hydrates on top of that markup rather than producing it. Turn JavaScript off and the shell disappears; every document stays.

What it renders from

There is no content management system and no database. Everything on the site is a typed record in a registry under content/, validated on every build: routes must resolve, relations must point at something that exists, every metric must carry a definition and a date it was true, and a release build fails outright on an unfilled slot.

  • Canonical routes in the content graph — 43
  • Of those, indexable today — 43
  • Projects — 6
  • Notes — 7
  • Open-source projects — 16
  • Press items — 12
  • Career entries — 8
  • Ventures — 1
  • Tools — 12
  • Commands — 15
  • Question chips — 4
  • Actions — 32
  • Key bindings — 26

The consequence worth stating: Help is generated from the same command, action and key-binding registries the running desktop reads, so it cannot document a control that does not exist, and no control can be added without appearing there.

Third parties

Nothing on the critical path. No analytics, no tag manager, no consent banner, no third-party fonts, no embedded players, no chat widget, no cookies set by this site.

  • 4 runtime dependencies, and no others: motion, next, react, react-dom. Everything else in the tree is a build or test dependency and never reaches a browser.
  • The typefaces are downloaded at build time and served from this origin. The content security policy allows fonts, scripts, styles, images and connections from this origin only, so a font CDN could not be reached even if one were added by accident.
  • One optional path exists and it is off by default: the console can phrase an answer through a language model, server-side, only when a deployment has explicitly configured and acknowledged it. Deterministic search over the same registries is always the fallback and is labelled as such on screen. Privacy records exactly what that path sends and what it keeps.

Running cost follows from that shape: prerendered files on static hosting, no database, no per-request work on the documents themselves.

Typefaces

4 families, each doing one job, and no others are loaded. All of them are licensed under the SIL Open Font License 1.1 (opens in a new tab), which permits the self-hosting this site does.

  • VT323 (opens in a new tab) — the BIOS screen, chrome labels and the version chip. Designed by Peter Hunt. SIL Open Font License 1.1.
  • IBM Plex Mono (opens in a new tab) — the transcript, every interface label, and the eyebrows on documents. Designed by Mike Abbink and Bold Monday, for IBM. SIL Open Font License 1.1.
  • Instrument Serif (opens in a new tab) — display type on documents. Designed by Rodrigo Fuenzalida and Jordan Egstad. SIL Open Font License 1.1.
  • Newsreader (opens in a new tab) — running prose in every document, including this paragraph. Designed by Production Type. SIL Open Font License 1.1.

Lineage

The chrome is Windows 95: a teal desktop, a two-pixel bevel with no radius and no blur, a navy-to-blue title-bar gradient, and sticky-note bubbles in a single centred window. None of it is a screenshot — every bevel is four inset box-shadows and every glyph is drawn. The era stamp in the status bar reads 1995 because that is the year the vocabulary comes from.

What 1995 could not do, this does: two real themes, motion you can turn down or off, windows that cannot be lost off the edge of the screen, documents that print properly, and a help page that is generated rather than written. Help has the full accessibility statement.