Public operator, developer, protocol, market, economic, security, recovery, evidence, domain, version and generated-reference documentation for ENTITY.
ENTITY v3.4.3 is a provider-independent digital authority, information, evidence, market, economic and recovery operating fabric from Blackmore Technology Group Limited.
Sovereignty is an important system invariant: hosting, custody, routing, storage or venue operation do not automatically become authority. But sovereignty is not the whole product.
The runtime is organized around five primitives:
ENTITY → AUTHORITY → RIGHT → EVENT → VALUE
From those primitives, the implementation composes persistent identities/objects, delegated authority, machine-readable rights, governed information, causal provenance, evidence states, market execution, economic participation, settlement evidence and provider-independent recovery.
ENTITY includes first-class support for:
- venues;
- rights-based instruments;
- balances and positions;
- listings and disclosures;
- order books;
- call auctions;
- RFQs, quotes and acceptances;
- trades and clearing;
- entitlements and usage;
- surveillance and cancellations;
- revenue rules and versioned rule sets;
- authorized settlement verifiers;
- payment attestations;
- treasuries, reserves and participation policies;
- market-state recovery.
Market lifecycle:
DCO → INSTRUMENT → LISTING → DISCLOSURE → ORDER / RFQ / AUCTION
→ PRICE DISCOVERY → TRADE → CLEARING → SETTLEMENT → ENTITLEMENT
→ USAGE → DERIVED OUTPUT → ECONOMIC CONSEQUENCE
Execution models include ORDER_BOOK, CALL_AUCTION and RFQ.
Instrument classes include SPOT_LICENSE, SUBSCRIPTION, COMPUTE_TO_DATA, PROCUREMENT, CONTRIBUTION and SECONDARY_LICENSE.
ENTITY does not require artificial scarcity of information bytes. Economic scarcity can exist in bounded rights, entitlement, capacity, duration, jurisdiction, usage quantity, derivation, participation and transferability.
- ENTITY — identity, authority, rights, evidence, value, market and recovery relationships.
- BTDU 3.4.2 — governed information topology using exact objects, atoms, bonds, compounds, indexes, manifests and lineage/economic relationships under ENTITY authorization.
- ADAM — deterministic state transformation and replay; it does not independently mint authority or rights.
- NIKI — bounded causal reasoning over approved governed projections; it does not mint ownership, permission or settlement.
The current codebase also contains support for encrypted vaults, purpose-bound access, retention/destruction controls, federated sovereign domains, core/regional/edge/satellite/offline topology, causal partition recovery, cryptographic-suite migration, rights/global passports, provider-neutral custody/connectors, standards adapters and industry implementation packages for healthcare, finance, manufacturing, AI, robotics and public/unclassified defence.
Two BTDU results are important enough to state explicitly, with their scope preserved:
- 97% lower storage requirement in the controlled BTDU benchmark. This is a bounded tested result, not a universal percentage asserted for every workload.
- 100% exact reconstruction in the qualified destruction/cold-recovery campaign. In the Memnox qualification, all 865/865 tracked Git blobs, the archive, manifest and upstream-acceptance proof were recovered without the original workspace, Git, GitHub or network.
ENTITY currently has two accepted external software contribution cases:
- Vector #26501 / PR #26504 — upstream merged and recorded as
UPSTREAM_ACCEPTED_RECORDED;PRO_BONO; realized cash0 USD. - Memnox #46 / PR #86 — maintainer-reviewed, CI/security green, upstream merged and recorded as
UPSTREAM_ACCEPTED_RECORDED;PRO_BONO; realized cash0 USD.
A third case is active:
- AWS #934 / PR #935 — submitted and locally validated, currently below upstream acceptance while AWS workflow execution remains maintainer-controlled.
These are not merely patch-ingestion demonstrations. They show real external problem → BTG engineering → exact change-set → review/CI → upstream consequence → ENTITY/BTDU lineage → explicit economic state.
Upstream acceptance is not automatically payment. Provenance is not ownership. A market capability does not mean every public case exercised every market subsystem.
ENTITY v3.4.3 is the current supported runtime.
The BTDU component remains 3.4.2 unchanged.
Published v3.4.3 qualification includes:
- Issue #28 remediation module: 76/76 PASS;
- full repository source suite: 279/279 PASS;
- full source-suite exit code: 0;
- compiled Rust qualification: PASS — inherited unchanged scope;
- real-world BTDU training qualification: PASS — inherited unchanged scope.
Release merge commit: 528b70aabd05b1e930b77e4933f157731e47274f
Immutable predecessor commit: 6dfa3d6cc738d9369cf092d2782676bf4f2a46e4
The active 30-day wall-clock qualification was not modified by v3.4.3.
- Independent Node Program: https://github.com/blackmore-technology-group/ENTITY/tree/main/independent-node
- Documentation portal: https://blackmore-technology-group.github.io/ENTITY-DOCS/
- Canonical capability map: https://blackmore-technology-group.github.io/ENTITY-DOCS/reference/capability-map.html
- Machine-readable capability map: https://blackmore-technology-group.github.io/ENTITY-DOCS/reference/capability-map.json
- Technology: https://blackmore-technology-group.github.io/ENTITY-DOCS/technology/
- Economy / Market Fabric: https://blackmore-technology-group.github.io/ENTITY-DOCS/economy/
- Exchange API: https://blackmore-technology-group.github.io/ENTITY-DOCS/developer/exchange-api.html
- Developer Manual: https://blackmore-technology-group.github.io/ENTITY-DOCS/developer/
- Evidence: https://blackmore-technology-group.github.io/ENTITY-DOCS/evidence/
- Live contribution ledger: https://blackmore-technology-group.github.io/ENTITY-DOCS/evidence/real-world.html
- Source: https://github.com/blackmore-technology-group/ENTITY
- Current release: https://github.com/blackmore-technology-group/ENTITY/releases/tag/v3.4.3
v3.4.2 remains immutable historical evidence and is superseded for current deployment. Historical BTDU release documentation remains available at:
https://blackmore-technology-group.github.io/ENTITY-DOCS/v342/
Some clean-room, audit and qualification material deliberately retains v3.4.2 in its title because that is the exact sealed artifact being reproduced or reviewed. Those labels should not be interpreted as current-release status.
Canonical ENTITY origin remains Shawn Blackmore → Blackmore Technology Group → ENTITY.
Protocol origin, repository custody, provenance, upstream ownership and automatic economic entitlement remain distinct concepts.
The portal is documentation. Exact released code, signed records, manifests, schemas, hashes, upstream evidence and settlement attestations remain controlling for their respective claims. A valid protocol record does not by itself establish external-world truth, legal title, regulatory compliance or accounting fair value.