Buildout replay: press play and watch the AI buildout arrive on the map

[aurph]

The mission sentence — visualizing the AI buildout for anybody who has questions — animated, on the surface you've called the biggest selling point. No new dependencies, no keys, no tokens, real data only.

What it is

A time-scrubber on the cluster map (new card directly under the existing Cluster map on Compute Frontier). Press play:

• Facilities light up in the year they came online — solid circles, sized by running MW, with a brand-orange pop as each year's arrivals land.
• Announced targets appear hollow and dashed at their promised year — and stay hollow until they actually energize, even after the target year passes. The hype gap, in motion.
• An instrument overlay on the map corner carries the big mono year and the running tally: live GW vs targeted GW (aria-live for screen readers). Play/pause + a year scrubber below; drag anywhere in time.

Honesty rules (pure, tested lib)

client/src/lib/buildout-timeline.ts: live = operational clusters at their online year using rated MW; targets = planned MW at the announced year; free-form dates parse to a year only when a real year exists ("Late 2020s" is excluded, not guessed) and the excluded count is disclosed in the footer. 216 of 235 clusters are datable today. 5 unit tests include the shipped registry animating with a sane span.

Craft notes

• Reuses the existing map idiom exactly: CARTO dark tiles, status colors, sqrt-MW sizing — nothing off-brand.
• prefers-reduced-motion drops the pop animation (discrete stepping remains); no autoplay ever.
• Named BuildoutReplay because a BuildoutTimeline component already exists on the Power page (facilities-by-opening-year bar chart, untouched) — complementary surfaces over different registries.

Verification

489/489 tests, tsc clean, build green, page serves 200 with the data flowing. Not browser-verified this session — the whole point is how it feels, so: open /compute-frontier, press play, and judge. Carries the #30 lockfile fix; independent of the other open PRs (inserts after the map card, away from #29's insertion point — both apply cleanly).

🤖 Generated with Claude Code

https://claude.ai/code/session_01FY4ziPhfu8VBPFVy5cDMNy

[aurph]

Round 2 — finished into a real instrument (the first cut was bones, fair call):

• The curve is now the scrubber. A cumulative GW area strip sits under the map — solid orange for what's live, dashed hollow for what's promised — with a playhead that tracks the year during playback. Click anywhere on the curve to jump in time; the slider stays for precision.
• Headliners. Each tick, the overlay names the year's biggest arrival ("came online · Colossus 1 · 500 MW") — live arrivals outrank same-year promises, because the story each year tells is what actually showed up. Pure and unit-tested (yearlySeries).
• Rolling tally + per-year delta. The GW counters ease upward as years land (+X.X GW arrived this year shown beside the big year); reduced-motion users get instant jumps.
• Bigger landing. Arrival pop upgraded to a two-phase radiating ring with an overshoot-settle; playback slowed to 1.1s/year so the headliners are readable.

Craft note: the repo's own chart-motion guard failed my first cut for hardcoding isAnimationActive instead of seriesMotion() — fixed to the convention. 490/490 tests, tsc, build green, page serving. Press play again.