Sovereign Authority Doctrine
Sovereign authority is authority rooted in the applicable Entity identity/control relationship rather than inferred from infrastructure possession.
Runtime consequences
- A cloud provider that stores state is not automatically the Entity or its sovereign authority.
- A DNS/resolver service that helps discovery is not general authority.
- A device holding a local copy does not automatically gain ownership or delegation.
- An application acts only under applicable explicit scoped authority.
- Provider replacement must not by itself destroy identity continuity.
- Recovery authority is explicit and distinct from ordinary operational/signing authority where the applicable rules make that distinction.
BTG stewardship
Blackmore Technology Group Limited (BTG) stewards the canonical ENTITY project/release lineage and official repositories. That stewardship is intentionally separate from user sovereignty. A conforming deployment is not intended to require BTG hosting, BTG DNS or a mandatory BTG cloud service to make a user's identity authoritative.
Canonical origin versus downstream assets
Canonical ENTITY status preserves ENTITY's own origin lineage. A fork may operate independently; replacing/removing that canonical origin can make it a non-canonical derivative of ENTITY. That classification does not transfer ownership of user or upstream assets to BTG.
canonical ENTITY origin
≠
user/upstream asset provenance
≠
user/upstream asset ownership
≠
automatic economic rightsVersion boundary
ENTITY v3.4.3 is the current supported runtime. The Blackmore Technology Data Universe (BTDU) component remains 3.4.2 unchanged. Historical v3.4.2 origin evidence remains historical evidence; it is not rewritten to appear current.