ENTITY Documentation
Problem-focused entry point

Digital economic infrastructure

Use this path when your problem is not merely identity or provenance, but how digital rights become instruments, market positions, transactions, entitlements, usage and evidence-bound economic consequences that remain portable across providers.

RIGHT → INSTRUMENT → VENUE → LISTING → ORDER / RFQ / AUCTION → TRADE → CLEARING → SETTLEMENT → ENTITLEMENT → USAGE → ECONOMIC CONSEQUENCE

What ENTITY implements

Market formation

Venues, rights-based instrument classes, balances, listings and disclosures.

Execution

Order books, call auctions, RFQs, quotes, acceptances and cancellations.

Post-trade

Trades, clearing, entitlements, usage, settlement verifier authorization and payment attestations.

Participation

Treasuries, reserves, primary/secondary/derivative terms, service revenue and obligations.

Integrity

Evidence, provenance, surveillance, revenue-rule sets and deterministic signed state.

Recovery

Logical export/restore of the complete exchange and participation state rather than treating database bytes as authority.

Why rights instead of tokenized bytes?

Data can be copied. ENTITY therefore models economically meaningful scarcity in explicit rights and entitlements—access, training, derivation, execution, commercialization, capacity, duration, quantity, jurisdiction and transferability—rather than claiming the underlying bytes become inherently scarce.

Real-world lineage already recorded

Vector #26501 / PR #26504 and Memnox #46 / PR #86 are upstream-merged contribution cases recorded as UPSTREAM_ACCEPTED_RECORDED. They demonstrate durable external contribution/economic lineage while remaining correctly pro bono with USD 0 realized cash.

Boundary: those two cases prove accepted external contribution lineage, not a paid market settlement. ENTITY's full market fabric is implemented separately and can be exercised when valid commercial terms and settlement evidence exist.