Runtime architecture primitive 4/5 · non-normative to Protocol 1.0
EVENT
Layer boundary: this page explains the runtime EVENT model. The frozen Protocol 1.0 event-envelope requirements remain defined by the sealed Protocol 1.0 material.
EVENT is a governed record of an authorized state transition, observation, usage, transfer, derivation or other material occurrence represented by the runtime.
Runtime event model
A useful event identifies the actor, target/object, action, time, authorization/rights context, evidence/provenance references and resulting state. Events are append-oriented; corrections, disputes or supersession should preserve history rather than silently rewriting it.
Examples
- Authority delegation or revocation.
- Rights issuance, transfer or expiry.
- Evidence ingestion or attestation.
- Passport issuance or verification.
- Trade, clearing or settlement transition.
- Usage of a licensed asset.
- Creation of a derivative output.
- Backup, export or recovery.
From event to economic consequence
An EVENT records the occurrence/state transition represented by the applicable rules. It does not automatically create economic VALUE. A monetary obligation, entitlement, settlement or realized consequence requires the applicable rights, terms and evidence.