Module 5 · Days 29–34
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.
6 lectures
Lecture 5.1
Compilation converts a decomposed policy into an executable authority artifact. This lecture treats compilation as a governed act with inputs, review, and issuance — not a file conversion — and places it within the full authority lifecycle, from source through seal, publication, and assignment.
Read lecture →
Lecture 5.2
A language model, a compiler, a policy team — any of them may help turn a source into an authority artifact. That is compilation, and it is a governed act. Execution is separate: a deterministic evaluator checks a proposed action against an already-approved artifact. This lecture defends the boundary between them and the rule that a probabilistic system may build authority but must not be the runtime that enforces it.
Read lecture →
Lecture 5.3
Determinism is what makes an outcome auditable: the same artifact and the same facts must produce the same outcome on any conforming runtime, today and years from now.
Read lecture →
Lecture 5.4
Verification is confirmation by a party who did not execute the decision. This lecture examines what must be recorded for verification to be possible without access to the executing system.
Read lecture →
Lecture 5.5
Every decision was made under some version of the rules. This lecture covers immutable issuance, effective dates, and replaying past decisions against past authority.
Read lecture →
Lecture 5.6
If authority is executable, it must be callable. This lecture covers the interface through which systems request an authority evaluation and receive a bound, traceable outcome.
Read lecture →