Skip to main content

​
Role dates and validity

A person’s recorded employment start/end dates can describe that role’s history at the source’s precision. They are distinct from a capture, observation or verification timestamp. Generic relationship valid_from / valid_to fields are not part of this public contract. A database history field or page modification date must not become a customer-visible validity claim.

​
Date semantics

The descriptive evidence JSON uses published_at, captured_at, observed_at and verified_at for the same meanings. Every field does not have every date. Date-only evidence stays in its source note; never invent a timestamp.

​
Provenance availability

Supporting source references and notes belong beside permitted facts in a bounded result. Subscription views do not expose a citation URL or every date for every field, including all commitments. Missing provenance cannot be repaired by treating record modification time as source publication or verification. Public records carry source-specific dates where available. No population-wide measured refresh cadence or universal verification deadline is established here. Page modified, source captured, fact observed, entity verified and aggregate measured describe different events. Check the date attached to the relevant claim; a missing verification date means unknown. Stored source history does not establish a customer-facing historical-analysis interface.