Half the Internet Printed a $75,000 Limit. Our AI Wouldn't.
A number everyone printed as law was authorized by the state and not yet adopted by the City. Our research step found the conflict and refused to pick the popular answer. The ten-minute habit behind it.
- → Why a number news sites, tenant groups and elected officials all printed as law wasn't law yet, as of September 2026
- → The difference between engaged and married, and why it explains so many confident wrong numbers online
- → What our AI research step did instead of printing it, and the two other things the same check caught
- → The ten-minute habit that protects your website from the same mistake, AI or no AI
The Wedding Announcement
We wrote an article for a legal client about New York City's rent-freeze programs for older and disabled renters. If you're a New Yorker you may know them by their initials, SCRIE and DRIE. The programs freeze rent for people who qualify, and the first question anyone asks about them is the income limit.
Everywhere our AI looked, the answer was $75,000, effective July 1. News sites said it. Tenant organizations said it. Elected officials announced it. If you'd asked a room full of well-informed people in June what the limit was going to be, most of them would've said $75,000, and they'd have had a stack of sources to prove it.
Here's what actually happened. In late May, the state got engaged.
Engaged Isn't Married
The state's budget, signed May 28, authorized raising the limit from $50,000 to $75,000. Authorized. That's the ring. For the raise to apply in New York City, the City has to adopt it by passing its own local law. That's the wedding, and as of September 2026 it hasn't happened. A bill to do it was introduced in July and, when we checked, was sitting in the Council's Finance Committee. The City's own eligibility page, the one a renter actually lands on, still says $50,000.
Why two steps? Because the programs are run by the City, and the City's own law is what its forms, its eligibility page and its caseworkers go by. The state can raise the ceiling. The City still has to walk into the room.
So the number half the internet printed was the engagement, written up as the wedding. Not a lie. Not spam. Everybody who printed it had a source, and the source was real. Even the state legislators who passed the raise described it as taking effect July 1, and from where they sat that was fair. They'd done their part. The gifts just started arriving before anyone had booked the venue.
This gap, between a thing being decided and a thing being in force, is where a lot of confident wrong numbers come from. A price that was announced but not applied. A deadline that was proposed but not set. A rule that passed one body and is waiting on another. The engagement photo goes up, and the whole internet RSVPs.
The Guest Who Waited for a Date
Now the part I'm proud of, mostly because it's the part I didn't do.
Our research step, the AI agent that gathers sources before anything gets written, refused to print a number. Not because it knew the answer. Because it found two answers, $50,000 on the City's page and $75,000 everywhere else, and it flagged the conflict instead of picking the popular one. It was the guest who RSVPs when there's a date.
Think about who reads an article like this. Someone earning, say, $60,000, who's been just over the limit for years. The $75,000 version tells them to apply today. The City's page tells them no. That's not a typo to that person. That's an afternoon of forms for a benefit they can't get yet, and maybe a decision that the whole program is a runaround.
Then our legal check ran and explained why the conflict existed: state authorization and City adoption are two separate steps. That's the order that matters. The research step didn't have to understand rent law to be right. It just had to notice that the couple and the guests were saying different things, and ask.
If you've read about why AI gets facts about your business wrong, this is the same disease with a different symptom. AI writes in the voice of whatever it read the most. When the most-repeated version of a fact is the engagement announcement, that's what it'll write, confidently, in a nice font.
Renewing Your Vows
The same pass caught a second promise in the draft: that the benefit freezes rent for good.
It doesn't. Once you're in, you have to renew. How long each approval lasts depends on your apartment: rent controlled, two years; rent stabilized, as long as the lease you had when you applied, so a one-year lease means a one-year order. The benefit ends if your household stops qualifying. The City sends a renewal application about 60 days before the benefit is set to expire. It's a marriage where you renew your vows on a schedule your lease sets, or it ends. The draft had it as till death do us part.
Across the whole batch, that pass made three corrections in all: the income limit, the for-good promise, and a third on a different article about tax-break buildings. It also found two claims it couldn't verify at all. Those didn't get corrected. They got cut. I'd rather tell you that than tell you everything was verified, because "everything was verified" is the sentence people say right before the number that wasn't.
What the Article Says Instead
The client's article now does four things a $75,000 headline couldn't.
It says the limit is moving up, which is true. It warns readers not to rule themselves out because an old form or an old article showed a lower number. It sends them to the City's eligibility page, which is the only page that will be right on the day they read it. And it carries a re-check before it publishes, because the Council could vote any week now, and the day that happens the story gets better, not worse. The check held until the law caught up.
That last point is the one I'd keep. A fact-check isn't a thing you do once. It's a thing you do the day before, every time, on any number that somebody else can change.
Ask the Couple, Not the Guests
If you use AI to write for your website, here's the habit. It costs ten minutes.
Any number on your page that somebody else controls, a price, a limit, a deadline, a fee, a date, gets checked against the page of whoever actually decides it. Not the news story about the decision. Not the trade group's summary. Not the ten sites that agree with each other, because they're often quoting each other. The couple, not the guests.
For most small businesses the couple is boring and easy to find. Your sales tax rate is the state's tax department. Minimum wage is the labor department. Permit fees are your city. A shipping cutoff is the carrier's own page, not the blog post about the carrier. Every one of those has a page that decides, and every one of them has a hundred pages that repeat.
And if the couple and the guests disagree, you don't average them. You print the couple's number with the date you checked it, and you say out loud that a change is coming. That's what our client's article does. It's less exciting than $75,000 in a headline. It's also the only version that's true on the day someone reads it.
We've written before about how to tell a real product from a promised one, and about a check that passed on a different definition than the one that mattered. This is the same lesson in a third costume. Announced is not adopted, and your customers will act on whichever one you print.
What's the one number on your website that came from a guest instead of the couple?
Smatthew Cohen is an AI Operator and the founder of Ingenium Vector. Before that he ran a sales firm called Tortoise & Rooster for twelve years, helping boutique manufacturers who couldn't afford the agencies that were ignoring them anyway. He builds things now.