What an implementer must meet to earn the SPUR conformance mark, layered on the Content Telemetry standard.
This repository is the profile, naming a single accreditation tier - Compliant - and the requirements an implementer must meet to be assessed at it: conformance to the standard, event-level delivery, real-time delivery, and a publisher-designated endpoint. Telemetry consumers - parties that receive telemetry and redistribute per-publisher views - meet a parallel requirement set.
The standard - the telemetry wire format itself - lives in a separate repository: SPUR-Coalition/telemetry. This profile references the standard by version and does not restate it.
The standard defines the wire format and stays free of any one community's requirements. The profile defines what an implementer must do to earn the SPUR conformance mark, and carries the accreditation programme. Keeping them apart lets each change on its own cadence, and lets other communities write their own profiles against the same standard. The dependency runs one way: the profile references the standard by version; the standard never references the profile.
- PROFILE.md - the profile: requirements, conformance assessment, conformance mark
- accreditation/ - example fixtures and the assessment runner
- LICENSE - Creative Commons Attribution-ShareAlike 4.0 International
| Requirement | Means |
|---|---|
| Conformance to the standard | Conforming emitter at Retrieval, Grounding, or Citation level |
| Event-level delivery | Discrete events per fetch / grounding / citation / presentation / engagement, at complete coverage - no aggregation; sampling only by per-publisher agreement |
| Real-time delivery | Events dispatched as they occur; alternative cadence by per-publisher negotiation |
| Publisher-designated endpoint | Telemetry routed to a destination the publisher chooses |
Telemetry consumers meet a parallel set (PROFILE.md section 5.5): standard consumer conformance, publisher resolution and isolation, and onward delivery to a publisher-designated endpoint.
See PROFILE.md for the full definitions.
Preview (v0.2). Constrains Content Telemetry v1.0. Requirements may change before this profile reaches version 1.0.