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

AUTHORITY

Layer boundary: this page describes runtime architecture. Protocol 1.0 authority semantics for independent clean-room work come from the sealed Protocol 1.0 material.

AUTHORITY is permission recognized for an actor to perform a bounded action or operation under specified scope, purpose, time and revocation conditions.

Runtime evaluation model

  1. Identify the actor Entity, application, device or node.
  2. Verify the applicable delegation/authorization record.
  3. Confirm scope, purpose, time and object/domain restrictions.
  4. Check revocation or supersession.
  5. Reject scope escalation.

Authority is explicit and attributable to the applicable authoritative record. An application, agent, device or node does not manufacture authority merely by being installed, online or in possession of data.

BTDU runtime example

BTDU is not a Protocol 1.0 conformance requirement. BTDU means Blackmore Technology Data Universe. In ENTITY v3.4.3 the BTDU component remains version 3.4.2 unchanged.

Within the BTG runtime architecture, a BTDU mutation can require a signed authorization receipt whose scope is BTDU_WRITE. This illustrates scoped runtime authority. It is not an extra requirement imposed on an independent Protocol 1.0 implementation.

See BTDU — Blackmore Technology Data Universe.

Provider boundary

Cloud administrators, storage providers, routers, discovery services and DNS operators do not gain ENTITY authority merely because they control infrastructure.