Runtime architecture primitive 1/5 · non-normative to Protocol 1.0
ENTITY
Layer boundary: this page explains later/current runtime architecture. Independent Protocol 1.0 implementation uses the separately sealed Protocol 1.0 Conformance Kit.
ENTITY is the persistent identity root used by the runtime architecture to relate authority, rights, events, evidence and economic state to a durable identity.
Runtime role
- Provide a stable identifier and verifiable identity manifest.
- Carry explicit verification methods and key lifecycle state.
- Support recovery continuity while preserving the same identity root under the applicable rules.
- Make authority explicit/delegated rather than inferred from infrastructure possession.
- Support portable interpretation across the applicable qualified implementations.
Boundary
An ENTITY identity is distinct from an account, device, host, provider or application. Registration does not establish ownership; possession does not establish authority; hosting does not establish sovereignty.
Current runtime and canonical origin
The current supported runtime is ENTITY v3.4.3; the Blackmore Technology Data Universe (BTDU) component remains 3.4.2 unchanged. Canonical ENTITY origin preserves the Shawn Blackmore → Blackmore Technology Group → ENTITY lineage for ENTITY itself. That protocol/project origin is separate from the provenance and ownership of unrelated assets.
ENTITY protocol origin
≠
downstream asset provenance
≠
upstream asset ownership