R-05 · 8 min

From Regulation to Execution

Abstract

The compilation pipeline: how a published instrument becomes an artifact a runtime can evaluate — without losing its provenance.

Learning objectives

01Walk a regulation through decomposition, compilation, and verification.
02Identify which clauses are executable and which require human judgement.
03Explain what a verification runtime proves and what it does not.

Concept

Machine-readable policy is often imagined as a translation problem. It is closer to a compilation problem: a source text is parsed into structure, the structure is checked, and the checked structure is emitted as an artifact with a stable interface. Provenance must survive every stage.

The stages

1  source        published instrument, clause-addressed
2  decomposition definitions · rules · exceptions · conditions
3  resolution    ambiguities named, owners assigned
4  compilation   typed, executable decision logic
5  validation    test cases, conflict + reachability checks
6  artifact      versioned, signed, content-addressed
7  runtime       deterministic evaluation + decision records

Provenance is the hard requirement

Every compiled rule must trace back to the clause it came from, and every decision must trace forward to the rule that produced it. Without that chain, the artifact is an opinion about the regulation rather than a representation of it — and no regulator will accept it as the latter.

What compilation refuses to hide

The most valuable output of this pipeline is often not the artifact but the list of things that could not be compiled: clauses that contradict each other, conditions that can never be satisfied, terms with no definition, thresholds with no unit. Prose absorbs these defects. Structure exposes them.

Framework

The compilation pipeline

01Source instrument
02Decomposition into definitions, rules, conditions, exceptions
03Structured representation
04Compiled, versioned artifact
05Verification runtime
06Governed execution

Case study

One article of the EU AI Act

A single article combines a general obligation, three exemptions, and a cross-reference to an annex. Read as prose it is one paragraph. Decomposed it is eleven conditions, four defined terms, and two decision branches.

Compiled, it becomes an artifact that answers a question in milliseconds and can be re-executed by a party who never saw the operator's systems.

Exercise

Decompose one clause of any regulation into its structural parts.

01Separate the operative rule from its conditions.
02List the exceptions and what activates each.
03Name every term the clause depends on.
04Write the decision logic as a branching structure.

Artifact

compiled.rule

rule: obligation.conformity_assessment
applies_if:
  system.risk_class == HIGH
  and not exemption.article_6_3
requires:
  - technical_documentation
  - post_market_monitoring_plan
outcome: OBLIGATED | EXEMPT