Lecture 4.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.
Supports Law 4 — Authority Must Precede Automation. →Learning objectives
After this lesson, the reader should understand:
Concept framework
The compilation pipeline
Case study
What must be true before a compiled screening artifact is allowed to run?
The ambiguity register must be empty or explicitly accepted, the definitions must resolve to named sources, every condition must have a fact source, and the authority holder must have signed the artifact rather than the memo describing it. Compilation without sign-off produces working software with no authority behind it — the most dangerous artifact of all, because it looks legitimate.
Discussion questions
Exercise
Write the issuance checklist for one artifact.
Research notes