Oracle's June 22 10-K put AI backlog beside capex, restructuring, and workforce math [1][2][3]

The prior file at ngtimes.org/2026/06/21/openai-oracle-credits-move-before-s1-disclosure asked for a public receipt before the frame hardened. Today's record supplies one, but it does not settle every claim.

The MSM frame is straightforward: Oracle's cloud backlog is huge and its spending plan is rising. The X frame is sharper and less patient: AI is either firing people or financing a bubble. The paper's read is narrower. The filing ties RPO, capex, leases, customer GPUs, restructuring expense, and headcount into one finance record.

That matters because the public decision is no longer about whether the topic feels important. It is about which document, docket, table, filing, warning, vote, or operating record should control the next claim. The source stack gives the reader multiple anchors rather than one headline. [1][2][3]

The remaining gap is practical. Cash conversion, customer concentration, lease terms, and actual capacity delivery remain open. Until that gap closes, the responsible headline is a receipt check, not a victory lap.

-- THEO KAPLAN, San Francisco