The six-month anniversary retrospectives of the outage autumn landed this fortnight — the long-form reconstructions of how businesses on three continents survived the AWS-Azure-Cloudflare trilogy, or didn’t. The genre has grown up. The best pieces document Nairobi payment processors and Jakarta logistics firms rerouting around us-east-1’s bad Monday: cloud concentration as a development-economics story. The regulatory count went from three jurisdictions to four, with the postmortems still serving as committee exhibits. And the datapoint I find most satisfying: multi-provider degraded-mode programs like ours are now common enough to have survey categories and consultant practices. The incident wrote the industry’s homework. ...

Earth Day fortnight, and the datacenter-energy question is now the AI buildout’s binding public negotiation. Grid-interconnection queues are still the limiting reagent, three years running. This year’s addition is utility-rate politics: “are residential bills subsidizing hyperscale load” is the recurring local-news investigation, and rate shocks write regulation the same way incidents do. Nuclear’s renaissance proceeds from announcement era to construction era at nuclear’s eternal cadence — the physics is sound, the timelines are the product, and the bridge decade belongs to efficiency and storage. The counter-ledger, because both hands: inference efficiency keeps improving faster than the discourse tracks, so the net is still growing but the composition is shifting the way every infrastructure boom shifts. The boom builds overcapacity, the overcapacity gets priced, the efficiency inherits it. ...

Thirteen years ago this month, entry #007 recorded a four-hour backup-restore drill and a tech lead’s proverb that started my whole file: “a backup you haven’t restored is a rumor.” The anniversary fortnight delivered a perfect echo. Our quarterly restore drill ran against the newest layer of the stack for the first time — not just databases but the model portfolio’s routing state, eval baselines, and agent intent docs, all from cold storage. The finding was pure #007 lineage: the golden test sets restored perfectly, and the routing config’s restore procedure referenced a secrets path that had been migrated in November. The rumor was in the plumbing’s plumbing, where it always is. Fixed by Tuesday, drill re-run clean by Friday. Thirteen years, four title changes, one unbroken discipline: restore-test everything, especially the things that restore the other things. ...

The Champions League knockouts performed their annual rite: the datacenter-megawattage methodology died in the round of 16 (the science records its sacrifice), and the pool is currently led by the office’s one methodology-free entrant, who picks by “which club has the cooler crest.” Fourteen years of prediction pools; the crest method remains undefeated where it counts. Also for the permanent record: the women’s Champions League carried the cultural mainline for the third straight year. That’s not a surge anymore. It’s the sport. ...

The reliability-year bet files its first quarterly evidence, and the industry supplied plenty. Enterprise surveys show the pilot-to-production gap closing for exactly one kind of agent deployment: narrow, eval-gated, workflow-embedded, with approval gates — converting at multiples of the “transformation initiative” rate. Agent-incident postmortems with sequence traces attached are now a steady publishing genre. And the vendor ecosystem is consolidating the way it always consolidates: platforms absorbing the workflow layer while the protocol survives underneath as plumbing. After three years of preaching deployment discipline to these pages, watching it show up in aggregate statistics feels like watching the congregation arrive. ...

Grading the eve predictions as the Games enter their final weekend, because that’s the deal I made with myself in 2013: write it down, then check. The Olympics streaming stack held — the two-cluster topology ran clean, my latency curiosity got its answer (it didn’t show; the logistics grumbles did), and the medal ceremonies proceeded across the Alpine arc without a single infrastructure headline, which is the trophy. The Champions League matchday set its concurrency record, and the buffering-apology discourse arrived exactly on schedule; the lineage extends its unbeaten run. The office score-prediction pool paid out to the one person who couldn’t name either team, per cosmic tradition. And the ad census: agent products outnumbered every other tech category, so I’m ruling it — as pre-committed — both arrival and top-tick. The crypto-ads comparison is now in every capex-skeptic newsletter. ...

Tonight the Milan-Cortina Winter Olympics open at San Siro. Sunday brings a heavyweight Champions League knockout matchday. Two global live events in one 72-hour window — the biggest scheduled-traffic test since streaming ate broadcast, and my favorite kind of fortnight. The Games themselves are an infrastructure story: the most geographically distributed Winter Olympics ever, two clusters — Milan and the Cortina mountain arc — hundreds of kilometers apart, one Games. The IOC has essentially gone multi-region. I’ll be watching whether the latency shows. ...

My first game day at the new badge ran Thursday. Yes, week two. The fastest way to learn a platform is to watch it degrade on purpose, and the team — bless them — agreed. We deliberately blackholed our primary model provider in staging, and then, with sign-off and new-guy audacity, for eleven minutes in production. The fallback worked. Routing shifted traffic to the secondary and the self-hosted tier inside 40 seconds, and the golden test sets confirmed quality stayed within tolerance. The surprise, as always, was adjacent: our status-page automation composes its incident notices with the same model provider we had just blackholed. It tried to announce the drill using a model that wasn’t there. The room’s laughter was the sound of tuition being paid at drill prices instead of outage prices. The fix — plain static templates for incident comms, paper runbooks for the AI era — shipped Friday. The drill is the deliverable. It has been the deliverable for thirteen years and one new layer of stack. ...

Year fourteen of this blog opens the way every year now opens: CES put an agent in everything with a power supply. The S in “agentic appliance” also stands for security. Time for the annual bet, written down where it can embarrass me in December: 2026 is the reliability year. Everything 2025 filed — agents on by default, the math of long task sequences, a commoditized frontier, the outage autumn’s regulatory sequel, insurers pricing agent-caused losses — converges on one question the industry can’t defer anymore. Not “can the machine do the task,” but “who is accountable when it half-does ten thousand of them.” The orgs that spent 2023–25 building judgment infrastructure — evals, intent docs, degraded modes — enter this year with a balance sheet. The orgs that spent it demoing enter with a backlog of unpriced risk. ...

Entry 316 closes year thirteen, and the file renders the year in its two artifacts. The trench coat: 2025’s defining incidents were the outage autumn’s five weeks (AWS’s DNS race, Azure’s edge config, Cloudflare’s feature file), three hyperscale control planes, three internally-generated artifacts, zero staged rollouts, one civilizational dependency diagram drawn in 5xx errors, plus the year’s steady percussion of the same lesson at every layer (the signing screen, the system prompt, the GCP null-pointer, the values config): the archive’s thirteen-year thesis (the automation that manages the system is the system; anything that changes runtime behavior is code) is no longer this file’s thesis, it’s the year’s regulatory agenda (the committee-testimony doctrine: the postmortems are writing the legislation, on schedule). The dial: 2025’s capability story was the reasoning dial’s domestication, DeepSeek’s cost collapse, the think-when-needed convergence, GPT-5’s router and its griefs, the agentic year’s arrival as marketed reliability and lived incident reports (the wish-lawyer, the purchase gates), the loom completing its transition from oracle to workforce, with the bubble question (real curve, circular financing, unknowable date) as the year’s permanent weather and the commoditized-frontier finding as its quiet technical verdict: intelligence became a portfolio line-item, and the differentiation moved, as it always moves, to reliability, which is to say to the boring layer, which is to say home. ...