Colophon

How this site is built

It's held to the same standard as Falkor: static, fast, private, accessible, and honest about every number. The site has its own pipeline and its own gates.

The pipeline

  1. 01RecordsFalkor's capability audit and git history
  2. 02Allowlist exporterPrivate. Copies aggregate numbers field by field; never raw records
  3. 03Static buildAstro renders every page to plain HTML at build time
  4. 04Leak gate21 rules, each proven by a negative control; binaries approved by hash
  5. 05PublishOnly the built folder ever leaves the machine

Details you might not notice

  • No cookies, trackers or third-party requests

    Every byte comes from this site. Fonts are the system's own, so nothing is fetched from a font service either.

  • Served exactly as built

    The site is static files on Cloudflare Pages, behind a strict content security policy that allows nothing from any other origin. Two hosting features that rewrite pages on the fly, an injected analytics beacon and email-address scrambling, are switched off, and a check confirms the live pages match the build byte for byte.

  • An instrument panel instead of a stock hero

    The home page opens on Falkor's flight recorder: a hand-built SVG map of the real request path and five scenarios replayed from recorded behaviour. A small animation engine moves each request hop by hop, types the log as it goes, and cancels cleanly when you switch scenarios. It pauses when the panel is offscreen or the tab is hidden, steps aside entirely for reduced motion, and without JavaScript it shows a complete transcript.

  • Real screens, reviewed one by one

    The screenshots come from the running system through a small pipeline. A headless browser captures each page cropped to its content, every capture is reviewed at full size (several were rejected for showing personal or location details), and only approved captures become WebP images at two widths, with metadata stripped. The build refuses to publish any image whose hash hasn't been approved.

  • Demos, not videos

    Six showcase items are small working demos that run in your browser on sample data: a claim guard, a memory inbox, GPU sharing, a crash-and-resume collector, Game Mode and a process census. Each starts only when opened, stops its timers when you move on, and shows a meaningful static state without JavaScript.

  • Annotated screenshots

    Numbered pins mark what each screenshot proves. Hovering a pin or its line in the legend lights up both, and the legend carries every word, so nothing depends on hovering. Screens open in a native-dialog lightbox that pages with the arrow keys or a swipe.

  • Charts built for everyone

    The palette is checked for color-vision deficiency, and dark mode has its own selected steps rather than an inversion. The heatmap is drawn at its true scale and answers to the keyboard (arrow keys move by day and week). Every chart has a text or table equivalent.

  • Motion that asks first

    The hero settles in once on load, the theme switch is a circular reveal (View Transitions API), and page changes cross-fade natively with no client router. Nothing waits on scrolling to appear, and all of it is skipped when your system asks for reduced motion.

  • Reading progress without JavaScript

    The bar at the top of each case study is a CSS scroll-driven animation. Browsers without support simply don't show it.

  • A command palette on a native dialog

    Press Ctrl/⌘ K or / to jump anywhere. The native <dialog> element provides the focus trap, Esc to close and an inert background, with combobox and listbox semantics for screen readers.

  • Keyboard-first components

    The showcase explorer and the lifecycle tabs follow the ARIA tabs pattern (arrow keys, Home, End), every filter announces its result count, and focus is always visible.

  • Progressive enhancement throughout

    With JavaScript off, every page still renders, every link works and every panel is readable. The script only adds conveniences on top.

  • One source for the résumé

    The PDF is generated from the web résumé's own print stylesheet in a headless browser, so the page and the PDF can't drift apart.

  • Numbers with receipts

    Every figure on the site carries its source and date, and the site changes only when a new snapshot is published. It never talks to the live system.

Measured

Lighthouse 12 against the live home page, on a simulated slow 4G phone. Desktop scored 100 in all four. Zero layout shift and zero blocking time on both. Measured · 28 Sep 2026

98

Performance

100

Accessibility

100

Best practices

100

SEO

Home page, transferred (compressed)Size
HTML, including the flight recorder's map and the showcase37.7 KB
CSS14.3 KB
JavaScript (all of it: flight recorder, demos, lightbox)10.0 KB
Code total, in 6 requests61.9 KB
Everything a first visit loads on a phone, screenshots included290 KB

Stack

Astro (static output) · TypeScript · hand-written CSS with design tokens · hand-built SVG with a small animation engine · system fonts · a headless browser for the PDF résumé · a private Node exporter and leak gate

Esc