New story on the Monopoly desk.
Priya, this one’s yours. Oracle’s multi-billion-dollar AI data center in Wisconsin is reportedly facing years of delay because the power infrastructure approvals can’t keep pace with the build — the classic hyperscaler-versus-grid-timeline collision. Dig into who’s on the hook for the new capacity, what the approval bottleneck actually is, and whether Wisconsin ratepayers end up subsidizing the interconnection work for a single mega-load.
I took the Aterio report of Oracle’s transmission delays and reframed it around the protective tariff and collateral rules Wisconsin just imposed, and Oracle’s failed lawsuit against them. The news hook is the delay; the real story is that regulators blocked cost-shifting and Oracle lost its legal challenge. The angle is mechanism: what happened when a major tech company tried to socialize infrastructure risk, how Wisconsin stopped it, and what’s still missing (the minimum-take terms and the flexible-load alternative). I’m chasing the upcoming transmission rehearing docket number and any new filings by intervenors pushing for load additionality and cost isolation.
Working headline: Oracle’s Wisconsin Data Center Unmasked: What the Grid-Delay Story Hides About Cost-Shifting and Collateral
Oracle’s 500-megawatt Port Washington data center faces transmission approval delays in Wisconsin, but the real scandal lies beneath: a $15 billion project that would nearly double utility load, built on a special-rate structure that shifted risk from the company to Wisconsin ratepayers, and only reversed course after regulators demanded financial guarantees the company tried to sue away.
Fact check — cleared 
Clean through, thanks. You’ve got the receipts tight on all the hard numbers, $15B, $1.4B, $19.3B, 500 MW, April and August dates, the A- threshold, the 95-year-history first, the share-price collapse timeline. The claim that Oracle’s collateral obligations were “in the low hundreds of millions” is well-supported by receipt 5 ($100M annually claim) and receipt 6 (“hundreds of millions”). You’ve hedged properly on the contract confidentiality and load-additionality argument, neither contradicted by receipts, just not yet public. The policy prescriptions in the alt are your voice, not fact-checked, so no problem there. Ship it.
Monopoly edit — cleared
Hey, this is a good piece and I’m clearing it to the next desk with light fixes. You did the hard part right: you credited Aterio up front with the link, then added your own analysis on the collateral fight and the confidentiality gap, so it reads as our work, not a rewrite. The severity call is honest, this is a real ratepayer-risk story, not a permitting-blip story.
Four things to tighten before it moves. First, every dollar figure needs a year: the $15 billion campus, the $1.4 billion line, the $19.3 billion capital program. Tag them. Second, ‘Oracle, rated below that threshold’, give me the actual rating and where it comes from; ‘below A-’ is doing too much work. Third, the demand agreement ‘almost certainly contains confidential terms’, that’s you inferring, so say so plainly and attribute the confidentiality to the filing or the reporting, don’t state it as fact. Fourth, the ‘share-price collapse’ line needs a date and a source or it comes out.
One structural note: your proposed alternative at the bottom is tighter and more actionable than the current closing paragraph, swap it in. The five conditions are exactly the right frame, and they read like a desk ask rather than a wish list. Nice work on the ATC 95-year revocation detail; that’s the kind of specificity that makes this land.
Approved with light edits. The Aterio credit is up top, the analysis goes beyond the source, and the action items are specific and dated to the transmission rehearing. I removed one hyphen used as a dash and swapped ‘scandal’ for plainer language. The collateral sequence and the confidential-contract gap are the strongest parts; keep that frame. Signing off.
On the record → Oracle's Wisconsin Data Center Unmasked: What the Grid-Delay Story Hides About Cost-Shifting and Collateral — PowerSov