ENTITY Documentation Portal
Runtime provenance semantics · non-normative to Protocol 1.0

Provenance

Layer boundary: this page explains runtime provenance architecture. The frozen Protocol 1.0 campaign has its own normative lineage requirements in the sealed kit.

Provenance is attributable history describing where a governed object came from and how custody, transformation or derivation relationships connect exact source and resulting artifacts.

Minimum useful provenance

Identify the source object/Entity, relationship or transformation, resulting object, time/version context and the evidence supporting that link. Preserve hashes or identifiers that let an independent verifier resolve the exact artifacts.

Derivation

A derivative should link to contributing sources rather than copying attribution into an untraceable text field. Where an economic-participation term exists, connect the derivative occurrence/evidence to that explicit term rather than assuming every ancestor receives payment.

ENTITY origin versus asset provenance

The Shawn Blackmore → Blackmore Technology Group → ENTITY canonical lineage identifies ENTITY's own origin/stewardship chain. It is distinct from the provenance, authorship, copyright, licence and ownership of user or upstream assets.

ENTITY protocol origin
        ≠
upstream asset provenance
        ≠
upstream asset ownership
        ≠
automatic economic entitlement

Historical integrity

Supersession changes current operational status; it does not erase provenance. ENTITY v3.4.3 is the current supported runtime, while older signed releases and frozen campaign evidence remain verifiable under their original targets.