Canonical system map · ENTITY v3.4.3

ENTITY is a digital authority, information, market, economic, evidence and recovery fabric.

This page is the canonical high-level capability map for the current ENTITY runtime. It exists to prevent the system from being reduced to a sovereignty, identity or provenance stamp. Sovereignty protects continuity of authority and state across providers; the implemented system is broader.

ENTITY → AUTHORITY → RIGHT → EVENT → VALUE

Governed objects and actions

ENTITY can represent persistent governed actors and objects including people, organizations, AI agents, datasets, documents, models, software, APIs, devices, vehicles, buildings, research, digital twins, financial instruments and physical assets.

Authority actions include acting, signing, data access, execution, purchase, licensing, settlement, publishing, resolution, delegation and control. Rights actions include inspection, reading, copying, derivation, training, inference, execution, modification, redistribution, commercialization, control and transfer.

Implemented source layers

Universal Transaction FabricGoverned objects, delegated authority, rights, events, provenance, value, attestations, trust policies and resolution.Exchange ProtocolVenues, instruments, balances, listings, disclosures, order books, call auctions, RFQs/quotes, trades, clearing, entitlements, usage, surveillance, cancellations, revenue rules, settlement verifiers and payment attestations.Economic ParticipationTreasuries, reserves, primary/secondary/derivative participation, service revenue, obligations and settlement verification without an automatic protocol tax.Market RecoveryProvider-independent logical export/restore of exchange and participation state using semantic hashes and identity/controller evidence.Verifiable Reality / Causal EconomyContestable evidence states and causal economic attribution linking contributors, information, rights, usage, products, transactions, revenue and settlement.BTDUGoverned information universe of exact objects, atoms, bonds, compounds, indexes, manifests and lineage/economic topology under ENTITY authority.Ecosystem RuntimeOperational composition of the major subsystems while preserving authority and evidence boundaries.

Market and economic 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.

Market Fabric Exchange API Market Recovery

ENTITY, BTDU, ADAM and NIKI

Layer	Role
ENTITY	Identity, authority, rights, evidence, value, market and recovery relationships.
BTDU	Governed information topology and reconstructable lineage/state.
ADAM	Deterministic state transformation and replay; does not mint authority or rights.
NIKI	Bounded causal reasoning over governed projections; does not mint ownership, permission or settlement.

Global infrastructure and adoption

Encrypted data vaults and purpose-bound access/use caps.
Retention, legal hold, revocation and evidenced destruction.
Federated sovereign domains and signed services.
Core, regional, edge, satellite and offline topology.
Vector-clock causal partition recovery with fail-closed conflict handling instead of silent last-writer-wins.
Versioned cryptographic-suite migration and downgrade resistance.
Rights passports and global passports.
Provider-neutral custody and connector surfaces.
Standards adapters with explicit semantic boundaries.
Healthcare, finance, manufacturing, AI, robotics and public/unclassified defence implementation packages.

Bounded engineering results

97% lower storage requirementObserved in the controlled BTDU benchmark. This is a bounded test result, not a universal percentage asserted for every workload.

100% exact destruction/cold recoveryIn the qualified tested campaign, including Memnox 865/865 tracked blobs plus archive, manifest and acceptance proof recovered without the original workspace, Git, GitHub or network.

Two accepted external contribution casesVector and Memnox reached upstream acceptance and ENTITY-recorded lineage. AWS #934 / PR #935 is an active third case below acceptance while upstream workflow approval remains external.

Real-world contribution economy

Vector and Memnox are not merely patch-ingestion examples. They demonstrate external problem → BTG engineering → exact change-set → upstream review/CI → acceptance → ENTITY/BTDU causal lineage → explicit economic state. The broader runtime can represent contribution instruments, venues, balances, listings, RFQs, execution, clearing, entitlements, usage, revenue rules, settlement verifiers and payment attestations, while each public case only claims the states actually evidenced.

Live Ledger Economic Lineage

Claim boundaries

Do not collapse these states: sovereignty is not the whole product; hosting/custody is not authority; provenance is not automatically ownership or objective truth; upstream acceptance is not payment; a trade is not verified external settlement; economic observation is not automatically accounting fair value; AI inference does not mint rights; and BTG-controlled qualification is distinct from unrelated independent validation.

Machine-readable map

The same system inventory is published as reference/capability-map.json for automated documentation, search and LLM consumers.