Oklahoma City won the NBA title (Game 7, June 22nd — the depth-architecture thesis’s proof at last: the youngest champion core in decades, built on drafted patience and defensive redundancy) but the file’s lasting image is the tragedy inside the triumph: Tyrese Haliburton, whose dagger-strewn playoff run made the Finals a classic, ruptured his Achilles in Game 7’s first quarter, playing through a calf strain everyone knew about, and the old file’s grimmest doctrine (return-to-load risk, the availability pressure that eats tendons) claims its most heartbreaking specimen yet: the sport’s incentive structure (Game 7, legacy stakes, the availability-debt ledger) remains unpriced at the exact moment it matters, and the player’s own “no regrets” testimony is the problem’s shape — some invoices are paid in careers. The group chat’s neutral joy closed in silence; the file logs both halves, per thirteen years of practice.

The infrastructure fortnight delivered its own Game 7: Google Cloud went down globally (June 12th, a new Service Control policy feature deployed with a null-pointer path, no feature flag, and instant worldwide config replication; the crash-loop took API management down across regions for hours, and the blast radius included Cloudflare’s Workers KV, meaning the outage’s most instructive finding is that the internet’s redundancy diagram is a fiction of vendor logos: two “independent” providers, one hidden dependency edge, the chokepoint theorem drawing itself again at planetary scale). The postmortem’s action items (flag-gate everything, stagger global config propagation, exponential backoff) read, the file says this with thirteen years of documented affection, like this archive’s greatest-hits album (the emergency lane, the content channel, the constants file: the same lesson, now at the policy layer of the planet’s second-largest cloud), and our own dependency-tiering review added the fortnight’s real homework: mapping transitive vendor dependencies (who do our vendors’ vendors crash into?), which no procurement questionnaire on Earth currently asks.

The talent ledger went fully feral: Meta’s Superintelligence Labs raids (the transfer window at full volume), reported nine-figure packages for individual researchers, OpenAI’s leadership describing the poaching in siege vocabulary, and the file’s structural note: the compute-scarcity trade has met its human corollary (frontier-capable researchers are the scarcer input, and the market just marked them to model, the positional-leverage doctrine at its terminal price point; every equity structure and mission statement in the industry is being stress-tested by a term sheet). Fifteen days will presumably escalate; the file’s popcorn is pre-positioned.

TIL: transitive-dependency cartography at the vendor layer. The GCP-Cloudflare edge existed in no public architecture diagram and every status page’s post-hoc timeline; the real-topology doctrine’s final boss is that the map requires incidents to draw itself, and the file’s modest proposal (vendors disclosing their own critical-path vendors, the SBOM concept promoted to services) now has a lobby of one archive and, after June 12th, several thousand postmortem readers. The plumbing, the whole plumbing, and nothing but the plumbing; year thirteen’s second half loads.