v3 was four skeletons. v4 is the same four, finished — every endpoint that had something to say, every drill path opened to the bottom, every number curled from the live source and frozen with its capture time. No invented data, no placeholder panels, no second screen that just repeats the first. Each one is now what it would be if it were the only way to see its subject.
The whole game, printed. A broadsheet you can read start to finish: the lede as filed, the scoring table, twenty-two possessions walked in order, the win-probability curve with the turning point named, and every one of 189 snaps in a drive-by-drive log. The standings and the injury report sit at the bottom like the agate page they belong on.
Why it exists — one game at a time deserves reading, not monitoring. Twelve tiles of bar charts cannot tell you when the game turned; a possession list with a marked hinge can.
Not a scoreboard — the season's paperwork for eight leagues at once. Above the fold, the live sweat ranked by swing. Below it: the closest game of the year, the longest streak, the rulebook each league actually plays by, roster shape against roster shape, the draft board and the traded picks, the playoff bracket as it stands, then every stat line, every bench point, every projection and the draft-day price of everyone you roster — with where else he's rostered and what the wire is trending.
Why it exists — the Sunday question is where does it hurt most, but the Wednesday question is why is this roster shaped like this. One app has to answer both without becoming a spreadsheet with a clock on it.
Everything you'd learn by standing at the sink and looking out, plus everything you can't see from there. The glass scrubs through the last 48 hours into the next 48; the pour verdict is stamped for tomorrow morning; the forecaster's desk carries the office's own written discussion, not a summary of it; and the instruments cross-check two models against each other so you can see where they disagree.
Why it exists — the evening question is narrow — can I pour at nine, what is the temperature doing overnight, what did I forget this week — and the answer is worthless without knowing how old it is and how sure it is.
A machine room you can walk. Seventy-three units in a to-scale cabinet, U73 down to U1, each with a category stripe, a live LED and a faceplate that pulls out into forty rows of spec. Then the other four views: the patch panel of forty-four caddy jacks, the cartridge bay of twenty-four containers, a ledger you can sort down to the worst offender, and an inspection sheet of eleven findings computed from the data itself — including the one where the registry's status field and reality disagree on every single line.
Why it exists — the fleet is a physical thing made of ports and processes, and it should be inspectable like one. Green pulses answer is everything okay before you read a single number; the inspection sheet answers the harder question, what is quietly wrong.
One evening paper for one man's day, printed once and frozen. The spine walks the day from the morning brief to the lamplight margin: a pour gate that computes the concrete window from 144 hourly points and says plainly when the cure lands in Monday's rain; eleven open loops read off the tracker with the four living on apps the overhaul retires named out loud; a wire that prints each feed's age instead of hiding the stale ones; three votes, six moods, and a margin line for the study rung. Every weekday claim was recomputed against the frozen harvest before it printed.
Why it exists — the fleet-overhaul vision asked what the whole fleet would look like as one daily companion instead of nine dashboards. This is the answer for a single Sunday — built to be judged before anything in the real overhaul is touched.
Fantasy and football in one surface, and every click-through kept: tap any of 807 players for the full dossier — advanced averages against his position, the week-by-week game log, the multi-season arc, trend with deltas, injuries, and the where-else-rostered map across all 100 rosters; tap any of 32 teams for schedule, season arc and roster shape; tap a game for the full board — the animated field walking every drive in order, win probability, the scoring table, team stats. The week's 14 games rank by bench swing, with pins that persist, and eight leagues sit behind it all, standings to transactions.
Why it exists — the fleet-overhaul vision asked what fantasy-platform, sports-station and draft-hub look like as one condensed app with nothing lost. This is that proof — the census ledger's single biggest slice under one roof, click-through to click-through.
The concrete-and-pool half of the overhaul: a pour board that hands every one of 72 hours its verdict — GO, CAUTION, STOP — each cell cross-checked against a second source with the FAIL printed when they disagree; the best window computed, not guessed (Mon 11–4, cure score 97, soil 65°); radar with 8 frames and 11 layers, 7 of them honestly disabled with their reasons; and the trade math live in the browser — concrete takeoff to the cubic yard, rebar to the stick, pool dose-to-target — beside an ACI-grounded pour-day checklist. Frozen from Open-Meteo, NWS, RainViewer and the weather-station pour engine.
Why it exists — the vision asked what weather-station and work-hub look like as one jobsite companion. The pour question — can we pour? — answered with receipts, cross-checks and honest blanks instead of a bare percentage.
One wire for news, the way data-hub and news-hub already see it: every one of 78 stories carries its source, its bias rating and its age — 14 minutes to 4 days, printed instead of hidden. Eight topic desks from tech (38) to security (2); five sections deduplicated 92 slots to 78 unique; a watch list across exactly four teams — Broncos, Celtics, Cardinals, Illini — aged per item; market quotes with GICS breadth; a saved shelf and source mutes frozen honestly. And the household gate is deny-by-default: nine private markers scanned on every render, personal shelves withheld from the shared view.
Why it exists — news-hub, data-hub and the household-privacy law condensed into one wire. The gate is not decoration — it is the feature, proven by flipping it: watch list and saved shelf render on MY DESK, withheld in HOUSEHOLD.
The plow-route map for David's other trade: 8 properties across Decatur, each pinned to a real OpenStreetMap street anchor, each with a state chip — queued, enroute, serviced — and a pull-card carrying driveway, walks and lot surfaces. The basemap is not a picture of a map: MapLibre 5.13.0 and PMTiles 4.5.0 are vendored and served same-origin, the PMTiles archive was built by planetiler from the Illinois OSM extract, and the style was generated from that archive's own 15-layer metadata — so the streets, the lake and the building footprints are real geometry. Radar is live MRMS from the fleet's own /radar/ service, animating the newest 8 frames. And now the route is real. OSRM 5.26.0 solved the 9-waypoint round trip through its own /trip service and the page embeds that exact response: 21.43 mi, 41.0 min, 9 legs, 970 vertices. A bold amber line is that polyline; the rig drives it on a 24-second replay; pins flip queued → enroute → serviced as it passes; every ETA is 08:00 plus the captured leg durations. The capture is stamped on screen — engine, graph, bbox, solve time, waypoint count, distance — because a frozen solve without a stamp is a lie. Under prefers-reduced-motion there is no animation loop at all: the finished route is drawn once, all stops at their end state.
Why it exists — P0 asked whether this looks like David's service area; P0b asks whether the order of stops is a real answer. So the solver runs once, at build time, and the page carries its output and its receipt instead of pretending to compute live: leg-sum vs route distance agrees to 0.000%, the polyline closes back on the depot, and two loads produce identical ETAs because the roll-out clock is a constant. The honest states stay the feature — a missing archive, a dead radar or a failed capture each get their own labelled panel instead of a blank canvas — and every business name on the map is invented: no customer data anywhere.
Cut: v1/v2's other seven directions — foreman, matchday, mission, quiet, sports, terminal, ticker — stayed deleted. Foreman came back Nov 2 as press 9: not the old mood-board cut, but a working surface on the real stack — vendored MapLibre, a PMTiles archive built from the Illinois OSM extract, live MRMS radar from the fleet's own /radar/ service, and (P0b, same day) a route actually solved by OSRM and embedded with its capture stamp. Matchday, mission, quiet, sports, terminal, ticker stay deleted. And v4 cut nothing new: the brief was to go deeper, not wider, so every addition above is another floor of the same building rather than a fifth building. The annex below arrived a day later, from the fleet-overhaul vision work — four demos now, each labelled a vision demo, none a fifth flagship.
Design Lab v4 · standalone single-file HTML, inline everything, no build step, no CDN, no chart library — every chart, rack and sky is hand-drawn SVG or canvas.
Built for 412px hands and 1746px desks alike · honors prefers-reduced-motion · keyboard-navigable, press 1–9 to open a wing.
Every figure on this page is a count taken from frozen live data, curl-verified Nov 1–2, 2026 · fantasy league names and scores appear only inside Sunday and Season, never here · teams are DEN, BOS, STL, ILL, always.