Build the digital-economic fabric
ENTITY is built around five primitives—ENTITY, AUTHORITY, RIGHT, EVENT and VALUE—and composes them into governed information, market execution, economic participation, causal lineage and provider-independent recovery.
Start with the core implementation surfaces
Five primitives
| Primitive | Developer question |
|---|---|
ENTITY | What persistent actor, asset, dataset, software, model, device or financial object exists? |
AUTHORITY | Who may act, sign, access, execute, purchase, license, settle, publish, resolve, delegate or control? |
RIGHT | What may the holder inspect, read, copy, derive, train, infer, execute, modify, redistribute, commercialize, control or transfer? |
EVENT | What state transition, usage, provenance, market action or evidence event occurred? |
VALUE | What potential, offered, contracted, accrued, settled or realized consequence is actually supported? |
Market & economic APIs
The exchange implementation supports ORDER_BOOK, CALL_AUCTION and RFQ, with instrument classes SPOT_LICENSE, SUBSCRIPTION, COMPUTE_TO_DATA, PROCUREMENT, CONTRIBUTION and SECONDARY_LICENSE.
Information, execution and reasoning
SDKs, standards and packages
Determinism, conformance and independent implementation
Real-world developer proof
Vector and Memnox are now upstream-merged, ENTITY-recorded external contribution cases. The developer lesson is not “ENTITY can hash a patch.” It is that an external problem, contributor, exact change-set, review/CI, acceptance and economic state can remain reconstructable lineage that can later participate in a rights instrument or settlement workflow if valid terms are established.
Independent verification
BTG-controlled Rust, TypeScript, C#, Go, Swift and Java baselines remain reproducibility evidence, not unrelated implementations. Independent reproduction, independent implementation, security review and institutional use remain separate evidence classes.