ENTITY Documentation Portal
Runtime data-rights economics · non-normative to Protocol 1.0

Market Lifecycle

Layer boundary: this is later ENTITY runtime/economic architecture. It is not part of the frozen Protocol 1.0 clean-room implementation obligation unless a normative Protocol 1.0 source explicitly says otherwise.
DCO → Instrument → Listing → Disclosure → Order / RFQ / Auction → Price Discovery → Trade → Clearing → Settlement → Entitlement → Usage → Derived Output → Economic Consequence

Digital Commodity Object (DCO)

A Digital Commodity Object (DCO) is a governed runtime representation that can carry identity, origin, controller, provenance, rights, restrictions, licences, evidence, usage/derivative lineage and explicit economic-participation terms.

Trading principle

ENTITY's data-economic architecture models tradable/licensable rights concerning data rather than pretending copied byte sequences become scarce physical objects.

Integrity

A market transition requires the applicable actor authority, right/instrument state and transition evidence. Clearing/settlement logic should prevent duplicate execution or duplicate obligation for the same authoritative occurrence and preserve the lineage of what right changed under what terms.

Usage and derivatives

Post-trade usage can generate downstream evidence. A derivative can create a new object/relationship. An economic consequence for a contributor/originator occurs only where explicit rights/terms and the required evidence establish it.

Boundary

Registration, provenance, ingestion, repository custody or protocol origin do not automatically create a market right, royalty, settlement, fair value or legal title.