Understand the architecture by problem, not product name
These guides explain the engineering problems ENTITY v3.4.2 addresses and the boundaries it deliberately preserves. They are written for architects, security engineers, data engineers, AI governance teams and developers evaluating whether the protocol fits a real system.
Data provenance protocol
How ENTITY separates source, controller, rights holder, evidence and derived outputs so provenance does not silently become truth or ownership.
Lineage vs provenance vs rights
Why a transformation chain, provenance record, ownership assertion, usage right and economic entitlement are different claims that should not silently strengthen one another.
Sovereign data rights
How identity, delegated authority, rights instruments, usage and settlement can remain explicit when data is copied, derived and reused.
AI agent authorization
Why an agent's authentication, API access, tools or infrastructure control must not silently become delegated sovereign authority.
AI governance and provenance
Why signed model output is not automatically truth, and how data/model lineage can stay rights-aware.
BTDU, knowledge graphs and vector indexes
Where the Blackmore Technology Data Universe overlaps with—and differs from—knowledge graphs, embeddings and retrieval indexes.
Portable digital authority and recovery
Why account recovery and infrastructure possession are not the same thing as sovereign authority, and how ENTITY treats export and recovery.
Standards mapping
How ENTITY concepts relate to W3C Verifiable Credentials, DID, PROV-O, ODRL and domain standards without converting architectural correspondence into a conformance claim.
Research & citation
Exact v3.4.2 release identity, CITATION.cff, CodeMeta, Zenodo-ready metadata and evidence boundaries for researchers and technical reviewers.
Architecture comparisons
ENTITY vs IAM
Conventional IAM controls accounts and access inside administrative domains. ENTITY adds portable authority, provenance, rights, governed transitions and sovereign recovery.
ENTITY vs verifiable credentials
Signed credentials prove issuer attribution and integrity; ENTITY separately models authority, rights, events, evidence and recovery.
ENTITY vs blockchain provenance
Ledgers provide ordering and replicated history; ENTITY focuses on authority, rights, provenance boundaries, recovery and explicit economic consequence.
Independent qualification
Hardware-backed key custody, physical multi-host operation, certified-device testing, independent security audit and independent assessor review are open external qualification gates. See the qualification program →
Verify instead of taking claims on trust
The released implementation, qualification record and bounded external verification tasks are public. Start with the v3.4.2 release or the external verification challenge.