Autonomous Enterprise Loop — HELM Diagram
The Autonomous Enterprise Loop
GOVERNED
CLOSED-LOOP
Company work flows through HELM's execution boundary. Only checked actions run. Everything leaves proof.
The Autonomous Enterprise Loop
A horizontal loop diagram showing 9 stages of governed AI execution. Stages 1-4 (Company Work, Context, Plan Gap, GeneratedSpec) represent proposal. A vertical double-line execution boundary separates proposal from execution. Stages 5-8 (HELM Boundary, CPI Verdict, Action, Proof) represent governed execution. Proof flows back to Context, closing the loop.
SYS.PLANE.PROPOSE
SYS.PLANE.GOVERNED
PROPOSE
EXECUTE + PROVE
Source-backed context
Company Work
Tickets · Repos · Calls
[LOOP-WORK-01]
1
Source-backed context
Context
Source-backed evidence
[LOOP-CTX-02]
2
Plan Gap
Should vs. Is
[LOOP-GAP-03]
3
GeneratedSpec
Draft proposal
[LOOP-SPEC-04]
4
EXECUTION BOUNDARY
Policy check
PEP + CPI
Policy
Identity
Sandbox
Connector
[LOOP-PEP-05]
5
✓ ALLOW
[OK]
6
✕ DENY
[ERR]
↑ ESCALATE
[WARN]
Governed action
Action
Governed effect
[LOOP-ACT-07]
7
Proof
Receipt → ProofGraph
EvidencePack / checkpoint
[LOOP-PROOF-08]
8
9. Proof returns to company evidence
Text description
Company Work
— Meetings, tickets, repos, docs, calls, incidents.
Context
— Source-backed company evidence and permission-aware retrieval.
Plan Gap
— Should-vs-is comparison finds a mismatch.
GeneratedSpec
— HELM drafts a source-backed proposal; it is not execution authority.
── HELM Boundary ──
— PEP/CPI validates policy, identity, sandbox, connector, and evidence requirements.
CPI Verdict
— ALLOW, DENY, or ESCALATE.
Action
— Only ALLOW dispatches a governed side effect.
Proof
— Receipt → ProofGraph; EvidencePack or checkpoint as required.
Loop Closure
— Proof returns to company evidence, closing the loop.