ENTITY Documentation Portal
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

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.

ENTITY, BTDU, ADAM and NIKI

LayerRole
ENTITYIdentity, authority, rights, evidence, value, market and recovery relationships.
BTDUGoverned information topology and reconstructable lineage/state.
ADAMDeterministic state transformation and replay; does not mint authority or rights.
NIKIBounded causal reasoning over governed projections; does not mint ownership, permission or settlement.

Global infrastructure and adoption

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.

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.

What is qualified and what is still developing?

The dated implementation-status matrix distinguishes the protected v3.4.3 tag from newer main-branch BTDU formula storage, wallet work, SDK requirements-only surfaces, independent qualification gates and full-storage costs. A source module or capability category is not equivalent to an independently validated deployment.

DataChip platform and native hosts (post-tag engineering)

Formula-native EDCF v0.2, the ENTITY Data Processor, portable verifiable content, typed visual Composer, signed-native-host planning and the capability-first wallet form an additive DataChip platform. A DataChip does not automatically grant ownership, export permission or executable host capability. Read the DataChip implementation and production-gate guide before interpreting current support; the protected ENTITY v3.4.3 release remains distinct.

Machine-readable map

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