Where did it come from?
Source class, evidence URL or raw record reference, retrieval context, and content integrity.
Proof describes how an endpoint handles provenance, time, confidence, correction, and distribution. It does not declare that every result is perfect.
Each live service publishes a machine-readable manifest beside its API. Buyers can evaluate controls before data enters a model, workflow, or decision.
{ "schema_version": "sentient.proof.v0.1", "timestamps": { "event_ts": "...", "publish_ts": "...", "fetch_ts": "..." }, "controls": { "public_data_rungs": [1, 2], "person_level_shared_cache": false } }
Source class, evidence URL or raw record reference, retrieval context, and content integrity.
Event, publication, and retrieval timestamps remain separate so buyers can judge staleness.
Correction routes, review states, material update handling, and visibility restrictions.