ENTITY Documentation Portal
Runtime architecture primitive 3/5 · non-normative to Protocol 1.0

RIGHT

Layer boundary: this page explains the later/current runtime rights model. It does not add requirements to the frozen Protocol 1.0 clean-room target.

RIGHT is a machine-represented permission, entitlement, restriction or retained interest associated with an object or activity under explicit terms.

Runtime dimensions

Depending on the applicable instrument/profile, rights can describe access, inspection, query, training, derivation, redistribution, sublicensing, commercialization, exclusion, duration, jurisdiction, quantity/capacity, revenue participation or constrained transfer/delegation.

Lifecycle

issue → verify → delegate/transfer if permitted → exercise → record EVENT → settle obligations where applicable

Non-rival data

Identical data bytes can exist in more than one place. ENTITY's data-economic architecture therefore models scarcity and economic consequence through explicit rights, entitlements, constraints and evidence rather than assuming byte possession creates exclusive ownership.

Boundary

Possession of bytes does not itself create a RIGHT. A BTDU relationship, provenance edge, repository fork, ingest or registration does not create a right merely because two records are connected. Economic participation requires explicit terms and applicable evidence.