This might be the most beautiful thing I've read in my life. What a privilege to be alive in 2026.
ordinaryabundance.com
Minor bombshell re: Polymarket / MicroStrategy drama.
Will post full article a bit later, but quick teaser that afaik is original and v. additive to debate.
I was digging into the reality of whether PM really had strong "precedents" re: reporting data that falls outside an event window being inadmissible.
Basically the answer across multiple case reviews seemed no. Or at least v. inconsistent.
But then in looking at the most quoted example I found something that afaik no one else has pointed out.
Team No argues that PM's clarification on a similarly ambiguous Sep '25 MS market is binding on the current disputed one.
Weirdly, and contra to popular opinion, PM actually got a lot better after that clarification at explicitly tying new MS markets to announcement dates (vs. just "buy/sell by x date" where announcements may follow later). This was good! Ambiguity gone! It also made the '25 clarification itself more a historical footnote.
So why was this May '26 market an exception?
Because its rules were written in Dec '24!
The May '26 market is a child in an older parent event page originally created 1.5 years ago, and its key resolution terms are verbatim copy from that older parent! While the May '26 market was only created a month ago, presumably the UI lets you clone existing in-family markets and then it's up to admins to edit them. Someone may have just forgotten to update that part!
I spot-checked 10 similar MS markets that PM created after Sep '25 and 0 had this ambiguity. It appears this was just a truly unfortunate legacy exception.
As a point for Team Yes: if all the other MS markets post Sep '25 are consistent in using "announce" vs. buy/sell, why would one not take buy/sell wording at face value? How is one supposed to intuit that the wording is just a legacy holdover and that it can't be interpreted in distinction to other current contracts?
Counterpoint: Politico premised their story on a *single* water pressure complaint from a house that wasn’t even on the same water system!
A story likely to be repeated in other places where data centers are located. An Atlanta data center was siphoning 30M gallons of water unnoticed until residents complained about low water pressure. Officials discovered unauthorized pipes feeding center politico.com/news/2026/05/08…
A local reporter dug in and found that the data centre (QTS) was a victim of bad national journalism.
- The house with the water pressure issue was drawing from an unconnected well. The county put in pressure readers across its own system and found zero issues.
- The rogue use was a county issue. A usage meter hadn’t been properly integrated into its new digital billing system and was tracking manually. When discovered, the county billed QTS ~$100k in missed charges, which QTS paid without issue.
- QTS is paying 2x the price of local residents for the same water.
- The whole QTS complex uses ~1% of the county’s water output (mostly for construction), and thanks to closed-loop cooling will drop down to the consumption of about four individual homes upon completion.
- Quoting the county admin: “What can we do to get the facts out and to normalize this so people understand what happened?”
Good q for Politico!
link: thecitizen.com/2026/05/11/be…
New from me, in partnership w/ @hntrbrkmedia.
This one pained me. I love startups and newsletters. But these cases are unusually bad and a stain on both industries.
I hope thoughtful reform follows.
Also did a companion piece on what reform could look like—were Congress / the SEC to make it a priority.
Note that I don't speak for Hunterbrook in this one. My commentary and proposals are my own.
savingjournalism.substack.co…
Jeremy Arnold retweeted
This is the single most massive factual error in a major book I've ever personally noticed on my own, and I think I'm the first person to notice it? Empire of AI asserts that a data center is using 1000x as much water as a city. In reality, it's 22% of the city's water.
As a fun bit of trivia, the modern idea of “catfishing” someone actually came from the same urban legend about the catfish effect. The term just rapidly outgrew its original reference point.
There’s this metaphor in Chinese business strategy that you see all the time, even though you never really hear it in Western business schools (at least I haven't). It’s called the “catfish effect,” and it supposedly comes from a Norwegian fishing practice.
Apparently, when fishermen would transport sardines in tanks, a lot of them would die along the way because they’d stop moving and run out of oxygen. But if you put a single live catfish into the tank, the sardines would stay active, swimming constantly to avoid getting eaten, and more of them would survive the journey. The catfish made the environment slightly hostile, which weirdly made it more survivable.
This story kind of floated around in Western motivational books for a while, but it never really stuck in business theory the way things like disruptive innovation or lean operations did. In China though, the idea of the catfish effect, or 鲶鱼效应, became pretty popular in corporate training settings and state-aligned business commentary, and it's pretty obvious that a main reason for that is cultural. There’s just more acceptance of discomfort as a developmental tool, and less hesitation to design pressure into the system from the top down. It’s not “disruption” as a natural market phenomenon, it’s more like managed agitation. Like, let’s introduce a little stress on purpose, because stagnation is the bigger risk here.
And yeah, I'm sure some will disagree with this example, but in China, Tesla's arrival is considered a clear-cut case of the catfish effect in policy. At the time, the government was pretty frustrated with its domestic EV scene. The subsidy program, although improved from the decade prior, had still led to all kinds of abuse and fraud, with a bunch of half-baked companies just trying to cash in on government money without building anything truly innovative. It was getting embarrassing.
So the government said, okay, fine. Let’s put a catfish in the water. They gave Tesla this rare set of approvals -- full ownership of their China operations, fast-tracked factory deals, land, logistics support -- the works. It was a provocation. Like, hey all of y'all Chinese companies, you guys need to be way faster cuz here comes the catfish. Swim! And sure, it wasn't all because of Tesla, but the pace of innovation has indeed picked up since then, in operations, design, user experience, everything.
This is where it really differs from how Western business theory tends to approach competition. In the US, you see a lot more disruptive innovation. In China, competition can be curated, introduced, even welcomed -- not to destroy the domestic players, but to get them moving again.
Of course, it doesn’t always work. Sometimes the catfish is too strong, or the sardines were already too weak. And sometimes you get eaten, LOL. But it's an interesting question -- is that tank you're in the best environment for you? Are you swimming because you want to, or because you finally have to?
If you like interesting architecture in various states of intactness, the country of Georgia is a bit of a dream.
But you of course wouldn’t expect those bad numbers to be that predictive of how things will actually go over a year. You’d need way more data for that, over several months.
But if the survey wasn’t that pessimistic, why did the gdp forecast fall? Because the Fed model intentionally only factors the worst-case scenario numbers!
See the red text on page 4 here: atlantafed.org/-/media/docum…
You can read the highlights from the latest ISM survey here. They’re a mixed bag, in the way you’d expect, but actually more optimistic on balance than the prior month’s.
prnewswire.com/news-releases…

























