Computable·Authority
← Curriculum

Module 4 · Days 22–28

The Authority Layer

A rule is not authority. Authority is the relationship between an institution, an agent, an action, a delegation, a version, and the evidence available when the action is proposed. This module makes that relationship an object — its architecture, its anatomy, how it is delegated, timed, and sealed, and the container it has to travel in before a system that has never seen it before can recognise, trust, and check it.

6 lectures

  1. Lecture 4.1

    The Reference Architecture

    The discipline builds many parts — decomposed rules, compiled artifacts, verification records. This lecture assembles them into one named model: six layers running from the authoritative source to the institutional record, with a clear statement of what each layer is responsible for and where authority actually becomes operational.

    Read lecture →

  2. Lecture 4.2

    Anatomy of an Authority Artifact

    Module 2 took apart the definition, the rule, the exception. This lecture takes apart the authority object itself: the fields it carries — issuer, jurisdiction, scope, delegation, version, effective period, constraints, evidence requirements, lifecycle state, integrity — and what each one is for. The claim is that authority can be an object with an anatomy, not an instruction buried in an application.

    Read lecture →

  3. Lecture 4.3

    Delegation

    Authority is rarely exercised by the body that holds it. It is delegated — to an office, a person, a system, and now to an agent that may sub-delegate again. This lecture treats delegation as a first-class object with a grantor, a holder, a scope, conditions, and an expiry, and examines what breaks when a chain of delegations is implicit.

    Read lecture →

  4. Lecture 4.4

    Authority, Evidence and Time

    A runtime authorisation is not rule-in, outcome-out. It composes the authority, the agent, the proposed action, the context, the evidence available, and the moment in time. This lecture examines the two that decay — evidence and time — and why a valid credential is not a standing authority.

    Read lecture →

  5. Lecture 4.5

    Sealing, Integrity and Provenance

    If an authority artifact governs consequential action, a party must be able to establish that the artifact and the decision record have not changed since issuance. This lecture covers canonicalisation, cryptographic sealing, and the precise limit of what a seal proves — it protects a representation of authority; it does not create authority.

    Read lecture →

  6. Lecture 4.6

    The Authority Container

    The reference architecture, the anatomy of an artifact, delegation, evidence and time, the seal — every lecture in this module has described what authority must carry and how its integrity is protected. None of it says what shape the thing takes, or what lets a system that has never seen the issuer before recognise it, trust its structure, and check it. This lecture treats the container itself as the object of study: the properties a serialization format needs before an authority artifact can be exchanged between institutions with no prior relationship.

    Read lecture →

Back to the curriculumGlossary of terms