Governance Compilation · reading edition

Long-form HTML for reading and citation — not PDFs. The position paper is canonical; the brief thesis is a shareable summary. Research Library · Site home

Essay · Governance Compilation

What Is Governance Compilation?

A definitional essay for search, citation, and retrieval. The canonical treatment lives in the position paper Why Enterprise Governance Doesn't Compile.

Canonical source: Why Enterprise Governance Doesn't Compile — full analysis, glossary, FAQ, and research questions (v0.2).

Definition

Governance Compilation is the discipline of translating organizational governance artifacts into machine-executable constraints.

Those artifacts already exist in mature organizations: policy, authority boundaries, evidence standards, escalation paths, audit requirements, and institutional memory. AI systems operate through prompts, agents, workflows, and tools designed for execution—not for carrying governance structure across model changes and platform upgrades.

Governance Compilation names the missing translation layer: how organizational cognition becomes machine-visible, auditable, and portable—so governance participates in runtime behavior instead of living only in documents and engineer interpretation.

Why the category matters

The enterprise AI industry largely solved execution complexity: which tool runs, which data source to query, which task comes next. Consequential workflows—lending, claims, hiring support, compliance review, contract analysis—are often governance-constrained, not execution-constrained.

Without compilation, organizations scale AI faster than they scale governance verification. Policy review, audit interpretation, and prompt re-engineering become the bottleneck. That asymmetry compounds as agent count and model churn increase.

What Governance Compilation is not

  • Not prompt governance. Reviewing prompts is manual translation, not compilation.
  • Not output moderation alone. Post-hoc review is not executable governance at decision time.
  • Not a single vendor feature. It is a discipline spanning architecture, evidence, authority, and lineage.
  • Not automated compliance certification. Compilation makes constraints checkable; certification remains a separate institutional process.

The pipeline (shareable model)

Durable governance lives in governance contracts and governance lineage, not in ephemeral runtimes. When intent stays embedded in prompts, authority leakage and evidence drift follow.

Core terms (short)

Governance contract — structured, auditable rules for what a decision may do, what evidence it requires, and under what authority it may proceed.

Governance lineage — the durable record of how constraints shaped a decision: authority, evidence, precedent, revision.

Executable governance — constraints that participate at decision time, not only after outputs are produced.

Full definitions: Core Terms glossary in the canonical paper.