Research / Long horizon

Machine-Readable Organizational Compiler

The strategic path from human intent and company sources to governed rules.

LONG HORIZON Advanced Researcher

Long-horizon thesis, not current product scope. This page separates current product relevance from thesis material.

Strategic

Diagram interlude

Generated specs become contracts only after review.

Specs can route work when they are source-backed, reviewed, and passed through the execution boundary instead of treated as authority by themselves.

OrgDNA → OrgGenome → OrgPhenotypeGOVERNANCECOMPILATION
Raw input becomes draft rules, review makes them law, runtime enforces them.
OrgDNA → OrgGenome → OrgPhenotypeOrganization Compiler Pipeline: raw inputs flow through compiler, review, to become signed governance rules.PROOFGRAPH — Every stage leaves verifiable evidence
Show:
Text description
  1. OrgDNA — Raw source material. Not authoritative.
  2. OrgGenome Compiler — Transforms input into draft rules.
  3. VGL Review — Review, simulate, approve, sign.
  4. OrgGenome → OrgPhenotype — Signed rules → runtime state.
  5. HELM Execution — Uses approved rules only.

Compiling the Enterprise

In software engineering, a compiler translates human-readable source code into machine-executable instructions. The HELM architecture applies this concept to the enterprise itself, introducing the Machine-Readable Organizational Compiler (MROC).

Companies already write a lot of source material. Examples include handbooks, control lists, role maps, and workflow diagrams. Humans still read most of it by hand. That can make work slow and uneven.

From Natural Language to Deterministic Execution

The MROC is a research idea. It would read company intent and turn it into clear execution policies.

1. Ingestion of Intent

The compiler can start from plain policy text or a simple table of limits.

2. The Compilation Phase

The compiler first drafts a policy. Then schema checks make the draft strict.

  • Human Intent: “Only seniors can approve large refunds.”
  • Compiled Policy: if action == "ISSUE_REFUND" and amount > 500 then require_role("SENIOR_SUPPORT")

3. Deploying the Binary

After review, the policy can move into the HELM runtime. It can then guide human and agent actions through the same 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 HELM.

The goal is to shrink the gap between what the company says and what the company does.

← Back to Research