In software engineering, a compiler translates human-readable source code into machine-executable instructions. The same concept applies to the enterprise itself.
From Natural Language to Policy Execution
Companies already write extensive source material: handbooks, control lists, role maps, and workflow diagrams. Most of this material is still read by humans manually. That makes enforcement slow and uneven. The Machine-Readable Organizational Compiler is a research direction for converting company intent into reviewed policy artifacts.
1. Ingestion of Intent
The compiler starts from plain policy text or a structured table of limits. It captures what the organization wants to enforce.
2. The Compilation Phase
The compiler drafts a policy,
then schema checks make the draft strict.
For example, the human intent
“Only seniors can approve large refunds”
compiles into a rule like:
if action == "ISSUE_REFUND" and amount > 500 then require_role("SENIOR_SUPPORT").
3. Deploying the Policy
After human review, the policy moves into the runtime. It can then guide human and agent actions through the same governance boundary.
Continuous Organizational Integration
The long-term goal is a CI loop for company rules. When a policy changes, the company updates the source, reviews the new policy, and promotes it through the runtime. The goal is to shrink the gap between what the company says and what the company does.