Introduction to Computable Authority

Module 1

Days 1–7

The Policy Problem

Why documents written for human judgement break down the moment a machine has to act on them — and why an autonomous machine breaks them further.

• 01Why policies fail machines
• 02The limitations of documents
• 03Human-readable vs machine-readable authority
• 04Rules are not authority
• 05What autonomous agents change
• 06Why AI creates urgency

Module 2

Days 8–15

Policy Engineering

The craft of decomposing a policy into its structural parts — the unit operations of the discipline.

• 01Policy decomposition
• 02Definitions
• 03Rules
• 04Exceptions
• 05Conditions
• 06Decision logic
• 07The states of authority
• 08Contradiction and conflict

Module 3

Days 16–21

The Observed System

The documented policy is only one of an institution's two decision systems. This module is the method for finding the other one — and for judging what its divergence means.

• 01The second system
• 02Decision boundaries
• 03Evidence and admissibility
• 04Reconstruction
• 05Reconciliation
• 06Adjudication

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, the container it has to travel in before a system that has never seen it before can recognise, trust, and check it — and what changes once that object can be asked a question the way software already asks identity, storage, and the network.

• 01The reference architecture
• 02Anatomy of an authority artifact
• 03Delegation
• 04Authority, evidence and time
• 05Sealing, integrity and provenance
• 06The authority container
• 07Authority as a first-class primitive

Module 5

Days 29–34

Executable Authority

Turning a structured, reconciled policy into an artifact that executes deterministically and can be independently verified — and keeping the thing that builds authority separate from the thing that enforces it.

• 01Policy compilation
• 02Compilation is not execution
• 03Deterministic execution
• 04Verification
• 05Policy versioning
• 06Governance APIs

Module 6

Days 35–40

The Future of Authority

What institutions look like when authority itself is computable, portable and interoperable — and where the discipline sits alongside the standards already in the field.

• 01AI-native institutions
• 02Regulatory interoperability
• 03The standards landscape
• 04Computable authority
• 05Objections
• 06Policy ecosystems
• 07The future role of policy engineers