Colophon

a site about measurement should survive being measured

frame time, last 600 frames — live, right now, on your machinemedian 0.0ms · p99 0.0ms · 0fps

decisions

Next.js 16 + TypeScriptserver components everywhere text lives; client islands only where pixels move

the trajectoryone fixed 2D canvas draws the 2023→now line from your scroll position — chapters stay ordinary DOM, the canvas only ever draws the connective tissue

React Three Fiber + dreithe hero book: four instanced meshes (dark bodies + neon caps) and a 1,200-particle GPU pool — a handful of draw calls total

custom GLSLorder flights animate entirely in the vertex shader — the CPU only writes spawn attributes

GSAP ScrollTrigger + Lenisscroll chapters and the latency story; killed on prefers-reduced-motion

react-bits (MIT)target cursor, film grain, decrypt-reveal and spotlight cards are ported from David Haz's open-source collection — good instruments get borrowed, then credited

deterministic replay coreseeded RNG, Hawkes-style burst arrivals — same tape every visit, engineered to swap for the real PitchFork WASM build

self-hosted variable fontsClash Display 29KB + General Sans 38KB woff2 — no font CDN round-trips

no analytics, no trackersthe only thing measured here is the site itself

honesty ledger

▸ The hero replays synthetic order flow — seeded, deterministic, calibrated to look like ITCH. It says so in its HUD. Real-tape WASM replay is the declared next step, and the interface is already shaped for it.
▸ The latency histogram in chapter 0x01 is illustrative; its endpoints (2,646ns → 825ns) are the measured runs.
▸ Codeforces numbers are pulled live from the official API, cached one hour. If the API is down you get a labelled snapshot, not a silent stale number.

source-visible the honest way: view-source works, the console has a note for you, and ~ opens a terminal.