This release makes the distinction explicit in the specification, but does not establish that industry reporting is already reliable.
Observed facts: SPUR labels v1.0 the current specification and says it replaces the v0.1 preview. The release introduces event, output, citation, and presentation identifiers to bind records to exact occurrences. It also defines coverage declarations as complete, sampled, aggregated, or selected, and specifies provenance categories including agent-fetched, agent-cached, and third-party-sourced. SPUR reports 171 fixtures, 15 validated worked examples, and 59 mutation checks in CI.
Mechanism: Event-level identity, declared coverage, and provenance make records more specific and their scope more legible; they do not compel disclosure or guarantee truthful reporting. The mechanism is event-level identity, declared coverage, and provenance: identifiers attach records to particular occurrences, coverage labels show the scope of a report, and provenance marks how content entered a workflow. This data contract does not compel disclosure or guarantee truthful reporting.
Why now: The release moves beyond a preview after a public comment period that SPUR says ran from 12 June to 24 July 2026 and generated recorded outcomes. A versioned schema and test suite give prospective implementers a more stable target than an experimental draft. The release moves beyond a preview after a public comment period, giving prospective implementers a versioned schema and test suite as a more stable target.
Implications: Publishers and AI providers can evaluate whether their systems can emit records against a common format. Implementers will need to map product events and content flows to the specification’s identifiers, provenance fields, and coverage declarations. For readers, the format could make claims about content use more comparable if organizations adopt it and publish sufficiently complete records.
Evidence boundary: The supplied public release documents a standard and its tests; it does not show deployment by AI labs, independent audits, or completeness of future disclosures. The test counts describe conformance assets, not proof that implementations in production meet the standard. The supplied public release documents a standard and its tests; it does not show deployment by AI labs, independent audits, or completeness of future disclosures.
What to watch: Look for named AI providers and publishers publishing compatible telemetry or documenting conformance against v1.0. Also watch whether the schema’s coverage declarations are used in public reporting, and whether independent parties can inspect or validate emitted records.