Version 1.0 is the current specification, replacing the v0.1 preview. Documents declare schema_version: "1.0"; the schemas' $id URLs move to /schema/v1/. Section 12.1 of SPECIFICATION.md is the complete migration record for v0.1 implementers.
Changes from 0.1
content_displayedbecomescontent_presented, withpresentation_kinddistinguishing presented content from source references (#14)- Output identity: event
id,output_id,citation_idandpresentation_idbind citations, presentations and engagements to exact occurrences (#14, #28) - Click context:
ctx_tokenissuance, carriage, resolver discovery (ctx_iss) and gated resolution, with owner-scoped delivery of the agent-authored engagement (#23, #28, #30) terms_refon events, occurrence boundaries per event type, and explicit coverage declarations -complete,sampled,aggregated,selected(#3, #42)- Portable counts:
chars_ingestedandexcerpt_charsprimary, token counts supplementary (#6) - Grounding
provenance(agent_fetched/agent_cached/third_party_sourced) and detection-onlycontent_fingerprint(#5, #10) purposeopen enum replacesbot_category(training,inference,search,advertising); vendor signal mappings move to informative Annex C (#7, #9)- Manifest
identifier_schemesblock and co-primary URL /content_idowner resolution with defined conflict and failure behaviour (#17, #31) - Generic evidence reference slot on content events, admitting detached
ref+digestreferences (#8) - Session
datacontainer withaccess_contextinstitutional identifiers (#43),content_depthon retrievals (#44),parent_session_idfor delegated sessions with a worked example (#1) ip_hashwithdrawn from the edge and origin profiles (#2); the manifest identifies a domain, not a legal person (#46)- The pre-release draft's
content_reproducedevent is not part of v1 (section 12.1, #25)
Conformance
171 fixtures, 15 validated worked examples, and 59 mutation checks run in CI on every pull request (tests/).
Consultation
The public comment period ran 12 June - 24 July 2026 and produced 29 specification threads, three profile threads and five pull requests; every thread carries a recorded outcome on the issue tracker, which remains the public decision record.