Skip to content

Releases: SPUR-Coalition/telemetry

Content Telemetry 1.0

Choose a tag to compare

@jalexspringer jalexspringer released this 02 Sep 13:47
7106115

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_displayed becomes content_presented, with presentation_kind distinguishing presented content from source references (#14)
  • Output identity: event id, output_id, citation_id and presentation_id bind citations, presentations and engagements to exact occurrences (#14, #28)
  • Click context: ctx_token issuance, carriage, resolver discovery (ctx_iss) and gated resolution, with owner-scoped delivery of the agent-authored engagement (#23, #28, #30)
  • terms_ref on events, occurrence boundaries per event type, and explicit coverage declarations - complete, sampled, aggregated, selected (#3, #42)
  • Portable counts: chars_ingested and excerpt_chars primary, token counts supplementary (#6)
  • Grounding provenance (agent_fetched / agent_cached / third_party_sourced) and detection-only content_fingerprint (#5, #10)
  • purpose open enum replaces bot_category (training, inference, search, advertising); vendor signal mappings move to informative Annex C (#7, #9)
  • Manifest identifier_schemes block and co-primary URL / content_id owner resolution with defined conflict and failure behaviour (#17, #31)
  • Generic evidence reference slot on content events, admitting detached ref + digest references (#8)
  • Session data container with access_context institutional identifiers (#43), content_depth on retrievals (#44), parent_session_id for delegated sessions with a worked example (#1)
  • ip_hash withdrawn from the edge and origin profiles (#2); the manifest identifies a domain, not a legal person (#46)
  • The pre-release draft's content_reproduced event 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.

Content Telemetry v0.1 (preview)

Choose a tag to compare

@jalexspringer jalexspringer released this 10 Jun 12:24

The first public version of the standard: the five-stage event model (retrieved, grounded, cited, displayed, engaged), session and standalone delivery, privacy levels, conformance levels, manifest discovery, and the conformance test suite.

Open for public comment 11 June to 10 July 2026 - see the README for how to take part. Schemas resolve at https://contenttelemetry.org/schema/v0.1/.