ENTITY is a Canadian-designed digital authority and operating infrastructure created by Blackmore Technology Group Limited. Its codebase is built to govern people, organizations, AI agents, datasets, software, devices, physical assets and transactions through persistent identity, explicit authority, machine-readable rights, verifiable events, causal provenance, economic state and provider-independent recovery.
Across identity, data, AI, commerce, evidence and recovery, the implementation preserves the same five primitives so applications do not need to invent a new trust model for every domain.
The universal transaction fabric has native object classes for digital, institutional and real-world subjects.
Delegated authority can be bounded to actions such as act, sign, access data, execute, purchase, license, settle, publish, resolve, delegate or control. Delegations can expire and be revoked; implicit privilege escalation is prohibited.
Rights can cover inspect, read, copy, derive, train, infer, execute, modify, redistribute, commercialize, control or transfer, with purpose, jurisdiction, duration and economic constraints. Access is not treated as ownership.
Persistent entities, signed proofs, append-only claims, protocol graphs, typed relationships, audit history and controlled mutations.
Explicit permissions, scoped delegation, revocation, policy evaluation, purpose restrictions and fail-closed authorization.
Owner-controlled AES-256-GCM content storage with metadata-only ledger state, deletion, cryptographic erasure and retention states.
Governed atoms, bonds, exact information objects, relationships, derivations, indexes, repository manifests, economic topology and exact reconstruction.
Deterministic atomic state transformation, event replay, recovery and execution coordination underneath BTDU.
Bounded causal reasoning over approved models and governed evidence. NIKI may reason, but activation authority remains ENTITY.
Objects, authorities, rights, events, provenance, value records, attestations, trust policies, resolution and settlement bridges in one fabric.
Venues, rights instruments, listings, disclosures, order books, call auctions, RFQs, trades, clearing, entitlements, usage and payment attestations.
Treasuries, originator participation policies, reserves, contractual participation, service revenue, economic obligations and verified settlement records.
Provider-independent logical snapshots of market, entitlement and participation state with semantic hashes and controlled restore.
Evidence objects, typed claim states, external anchors and causal economic graphs that keep attribution, evidence and truth claims separate.
Purpose-bound grants, use caps, expiry, revocation, selective disclosure, retention schedules, legal holds and evidenced destruction.
Entity-owned domains, signed node authority, service manifests, provider migration, resolution, presence, recovery and revocation.
Core, regional, edge, satellite and offline topology; signed partition checkpoints, vector clocks, bounded offline envelopes and fail-closed conflicts.
Rights passports and global passports that bind existing authority, rights, evidence, jurisdiction, custody, provenance and economic context without replacing them.
Backup, migration, recovery, scale, telemetry, transaction evidence, updates, release gates, clean-room kits, conformance and qualification tooling.
Identity, authority, rights, evidence and economics. ENTITY determines the governed relationships and the evidence required to rely on them.
Deterministic transformation and replay. ADAM is the atom/bond state engine that applies and recovers governed transitions.
Governed information topology. BTDU binds exact content, atoms, bonds, derivations, indexes, repository state and economic relationships under ENTITY authority.
Causal intelligence inside explicit boundaries. NIKI receives bounded projections and approved causal models; it does not manufacture permission, ownership or settlement.
The fresh 2026-10-01 run generated 250 million bonds for 50 million entities. The compact bond-plus-index representation was 4.4 GB versus 153.6 GB for the tested 768-dimension float32 vector baseline: 97.1354167% lower. All 1,000 sampled lookups were correct and the regenerated artifact hashes matched the historical qualification.
The fresh 2026-10-01 Memnox rerun reconstructed the accepted source archive, manifest and acceptance receipt from sealed ADAM/BTDU state. All 865 of 865 tracked Git blobs matched with zero missing, extra or mismatched paths; Git, GitHub, network and the source clone were not used.
Claim boundary: 97.1354167% is the measured result of the specified Level-3 comparison against a 768-dimension float32 vector baseline, not a universal compression guarantee. 100% recovery describes the qualified 865-blob corpus and evidence path, not every conceivable damaged system.
The implementation explicitly rejects the idea that copied bytes must be artificially scarce. Economic scarcity can instead exist in bounded rights, entitlements, capacity, duration, jurisdiction, usage quantity, derivation, participation and transferability.
The Exchange Protocol supports spot licences, subscriptions, compute-to-data, procurement, contribution instruments and secondary licences.
Order-book, call-auction and RFQ execution models are implemented alongside signed listings, orders, quotes, cancellations, surveillance and entitlements.
Payment attestations and authorized settlement verifiers are separate from a trade record. Technical acceptance, an obligation and actual settlement remain distinct states.
Originator and treasury profiles can record validly established reserve units, primary participation, secondary royalty terms, derivative participation and service revenue. Terms must exist legitimately; provenance does not create them retroactively.
The participation layer recognizes listing, execution, clearing, settlement, market data, certification, managed infrastructure, API and index-licence services, with separate obligations and settlement evidence.
Evidence can include sensor observations, documents, registry records, lab results, payment records, images, API responses, certificates and court records.
Government registries, sensor networks, bank settlement, labs, supply-chain systems, corporate registries, courts and certificate authorities can be referenced without becoming automatic ENTITY authority.
Source data can be traced through rights, licences, usage, derived assets, products, transactions, revenue, settlement and contributors using an evidence-bound acyclic graph.
Controllers can issue signed grants for specific purposes and actions with expiry, use caps and revocation. Every authorized use can bind its own evidence hash.
Retention policy supports payload deletion, source redaction, external-copy destruction and legal holds while preserving evidence commitments.
ENTITY locators support AWS S3, Azure Blob, Google Cloud Storage, Snowflake, Databricks, PostgreSQL, SQL Server, local filesystems and HTTP APIs without treating custody as authority.
Versioned jurisdiction and domain profiles can allow, require or prohibit actions with precedence, effective dates, supersession, conflict detection and fail-closed evaluation. They are policy evidence, not legal determinations.
Domains bind names, authorized nodes, service manifests, scopes, access classes, revocations and provider migrations to the Entity root rather than to a hosting vendor.
Commissioned nodes publish signed domains and services and can establish encrypted direct sessions. Network participation requires owner commissioning; the network itself does not become sovereign authority.
Core, regional, edge, satellite and offline nodes can publish signed causal checkpoints. Vector clocks identify converged, dominant or conflicting state; divergent concurrent state is not silently resolved by last-writer-wins.
Crypto suites can be versioned through governed activation, deprecation and retirement, including dual-sign transition windows and explicit downgrade resistance.
Signed immutable versions bind rights, authority references, jurisdiction, semantics, custody, provenance, disclosure, privacy profiles, economic terms and legal classification around an existing ENTITY object.
A single portable envelope can compose rights passports, profile stacks, evidence, provenance, jurisdiction, standards mappings, economic state, industry context, protocol origin and BTDU bindings.
Explicit adapters cover ODRL, W3C Verifiable Credentials, DID, Gaia-X and IDS. Repository requirements also define scoped interoperability with C2PA and standard SBOM formats. Mapping is evidence—not silent semantic equivalence or certification.
Clinical datasets, documents, models and medical devices with HL7 FHIR and DICOM mappings and restricted/purpose-bound privacy defaults.
Financial instruments, trades, settlement records and market data with ISO 20022, FIX and LEI mappings.
Machines, digital twins, firmware, telemetry and maintenance records with OPC-UA and Asset Administration Shell mappings.
Training data, corpora, models, weights, evaluations, agents and outputs with SPDX, CycloneDX and NIST AI RMF mappings.
Robots, controllers, models, software, telemetry and action records with ROS 2 and Open-RMF mappings.
Public/unclassified assets, data, software and custody records with originator-control mappings; the package explicitly prohibits classified-material ingestion.
These packages configure ENTITY semantics for industry use. They do not themselves constitute regulatory compliance, legal approval or certification.
The repository carries Android, Apple, Web and Windows SDK surfaces, open/reference SDKs, ecosystem and global-passport SDKs, principal binding, schemas and reference clients. The adoption facade exposes rights passports, authorization, exchange actions, settlement, positions and market data while preserving the authority of the underlying components.
Vector and Memnox are public examples where BTG-authored fixes were reviewed and accepted by unrelated upstream projects, then captured through ENTITY lineage and recovery evidence. AWS #934 / PR #935 is a separate active case and remains below upstream acceptance until maintainer-controlled review and CI gates complete.
The v3.4.3 release manifest records 279/279 full-source tests passing and 76/76 tests passing for the issue-28 remediation module. BTDU remains component version 3.4.2 unchanged in that remediation.
The repository contains clean-room kit builders, conformance campaigns, crypto/privacy qualification, scale and soak qualification, market-scale checks, recursive-closure qualification, global-passport verification, polyglot verification and industry-package verification.
No token is required. The economic participation profile explicitly defines zero protocol tax and derives value from rights, contractual terms and services.
The architecture is about authority, rights, events, evidence and recoverable state; a particular ledger technology is not the definition of ENTITY.
NIKI and other AI agents can act only inside authority granted elsewhere. Model inference does not mint rights, ownership or settlement.
Evidence and cryptographic verification make claims attributable and testable, not automatically true.
Cloud, database, custody and topology providers do not become the owner or sovereign authority merely because they host bytes or services.
Provenance does not manufacture ownership, a licence does not imply every right, and an asserted amount does not become fair value or settled money without its own evidence.
The canonical-status layer preserves ENTITY's origin and BTG stewardship. Removing or replacing that lineage changes canonical status; it does not grant BTG ownership of third-party assets, data or source code.
The core repository is public under Apache-2.0 so developers and organizations can inspect, test, reproduce, fork and independently implement published protocol material.
ENTITY source repository →ENTITY v3.4.3 is the current public runtime line. Its bounded remediation did not change the BTDU implementation, which remains 3.4.2. Historical releases, hashes, receipts and qualification artifacts remain preserved rather than being silently rewritten.