Sovereign digital authority
ENTITY separates persistent identity from the accounts, applications, providers and devices that act around it. Applications and agents operate through explicit, scoped and revocable authority rather than becoming the sovereign identity themselves.
Problem
Conventional systems often bind authority to an account, provider, application database or device. ENTITY's design goal is to keep authority portable while making delegation, evidence and recovery explicit and verifiable.
What to inspect
Identity ≠ account
Persistent identity is modeled separately from provider accounts and application registration.
Delegation is scoped
Applications and agents act only through explicit authority with bounded scope and revocation semantics.
Recovery is part of sovereignty
The architecture is intended to survive replacement of a device, host or provider subject to the applicable qualification evidence.
Evidence is not truth
A valid signature proves a cryptographic statement under its trust context; it does not automatically prove an external-world assertion.
Verify rather than trust
The strongest way to evaluate ENTITY is to challenge a bounded invariant or reproduce a public campaign.
Current release boundary
ENTITY v3.4.3 is the current supported runtime. It is a bounded remediation release based on immutable v3.4.2 evidence. The BTDU component remains 3.4.2 unchanged.