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.
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
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
| 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
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
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.