ENTITY v3.4.3 runtime architecture · non-normative to Protocol 1.0
Runtime Architecture & Semantics
The current runtime is a governed digital-economic fabric built from five primitives and composed into authority, rights, evidence, information, market execution, participation, causal lineage and recovery. Sovereignty is one of its invariants, not a synonym for the system.
Protocol boundary: this section explains the current ENTITY runtime family. Independent Protocol 1.0 clean-room work still uses the separately sealed conformance material. ENTITY v3.4.3 is the current runtime; BTDU remains component 3.4.2 unchanged.
Core runtime semantics
ENTITY → AUTHORITY → RIGHT → EVENT → VALUE
ENTITY PrimitivePersistent governed subjects and objectsAUTHORITY PrimitiveWho may act and under what scopeRIGHT PrimitiveMachine-readable actions, constraints and entitlementsEVENT PrimitiveEvidence-bearing state transitions, including market and usage eventsVALUE PrimitivePotential through realized economic consequence
Economic runtime semantics
DCO → INSTRUMENT → LISTING → DISCLOSURE → ORDER / RFQ / AUCTION → PRICE DISCOVERY → TRADE → CLEARING → SETTLEMENT → ENTITLEMENT → USAGE → DERIVED OUTPUT → ECONOMIC CONSEQUENCE
Market LifecycleThe complete runtime data-rights/economic lifecycleMarket FabricVenues, instruments, balances, listings, orders, trades, clearing, entitlements, surveillance and settlement evidenceMarket RecoveryPortable logical recovery of exchange and participation stateExternal Economic LineageReal outside events connected to causal/economic history
Evidence and reality
ProvenanceOrigin, derivation and contribution without automatic ownershipReality & EvidenceObserved/asserted/attested/verified/disputed states without automatic objective-truth claimsGlobal PassportPortable binding of existing rights, evidence, profiles and economic context
Information and recovery
BTDUGoverned atomic/bonded information topology under ENTITY authorityPortability & RecoveryAuthority/economic continuity across providers and runtimesSovereignty DoctrineWhy storage, hosting, routing and venue operation never become authority merely through possession
Reader boundaries
Protocol 1.0 sealed conformance target
≠
current ENTITY v3.4.3 runtime
≠
BTDU 3.4.2 information component
≠
exchange / economic participation state
≠
external case-specific evidenceThe layers interoperate, but their claim boundaries remain separate. A platform can implement a market capability that one particular external evidence case has not yet exercised; a merged contribution can prove acceptance without proving payment; and a valid signature can prove attribution without proving external-world truth.