Module 4 · Executable Authority

Lecture 4.1

Policy Compilation

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 4Authority Must Precede Automation.

Learning objectives

After this lesson, the reader should understand:

  • 01Describe the inputs and outputs of a compilation.
  • 02Identify what must be signed off before issuance.
  • 03Explain why compilation is repeatable and auditable.

Concept framework

The compilation pipeline

  1. 01Decomposed policy
  2. 02Resolved ambiguity register
  3. 03Structured artifact
  4. 04Review by the authority holder
  5. 05Versioned issuance

Case study

Compiling a sanctions screening rule

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

  • Who is competent to sign a compiled artifact?
  • Should compilation be reproducible from source by a third party?
  • What is the status of an artifact whose source instrument changed?

Exercise

Write the issuance checklist for one artifact.

  1. 01List the inputs required for compilation.
  2. 02Define the review steps and who performs them.
  3. 03State the sign-off record.
  4. 04Define what invalidates the artifact.

Research notes

  • Compiler theory — source, target, and semantic preservation.
  • Software supply chain and signed releases.
  • Administrative process design for instrument issuance.