execution
What the executor did
Control contracts for agent workflows
A completed workflow.An accountable decision.
Connect what your agents did to the evidence, authority and outcomes that make the next decision defensible.
0.1 · Executable candidate0.2 · Proposed · not released
An illustrative decision
The provider completed the action. Outcome evidence is still missing.
execution- COMPLETED
evidence- MISSING
authority- ACTIVE
promotion- HOLD
reconciliation- MATCHED
observedOutcome- UNKNOWN
Next: collect outcome evidence. The owner decides promotion.
HelmLoop / Overview
HelmLoop is a runtime-neutral control-contract protocol. It gives execution, evidence, authority, promotion, reconciliation and observed outcomes their own explicit states. Your host keeps control of execution and permission.
HelmLoop
Keep six different questions separate.
A terminal graph node answers whether execution ended. The next consequential decision also needs a current account of evidence, authority and external reality.
evidence
Whether required claims are fresh and supported
authority
Whether the exact action was authorized
promotion
What the accountable owner decided
reconciliation
What the provider and observed external state show
observedOutcome
What independent outcome evidence shows
0.1 / Executable candidate
What you can inspect today
Protocol 0.1 includes eight record schemas, a deterministic six-axis reducer, a CLI and two fixture observation adapters. These are local implementation artifacts, not a public package release or live-runtime certification.
Read the protocol ↗0.2 / Proposed · not released
A clearer contract for the next decision.
The 0.2 plan adds an assurance axis, authority lifecycle events, criterion-bound outcome observations and versioned evidence admission. These changes are proposed in r3 / sync-4.
Explore the 0.2 plan ↗HelmLoop
Start with the current source
Run from a local HelmLoop source checkout with Node.js 20 or later. This command uses fixtures; it does not call a live provider.
The standalone helmloop try command is planned for 0.2. It is not available in the current CLI.
Protocol 0.1 ↗SOURCE CHECKOUT / FIXTURE
node bin/helmloop.mjs schemas
node bin/helmloop.mjs conformance --adapter coreHelmLoop
Keep ownership where it belongs
The host owns scheduling, state, grants, effects and business truth. HelmLoop evaluates supplied contracts and observations. Better Workflows is an optional integration, not a required backend.
completed ≠ PROMOTERuntime completion cannot decide portfolio or release promotion.
intent ≠ action authorityA goal, prompt or handoff cannot mint permission for side effects.
receipt ≠ business outcomeA trace or provider receipt proves an event, not its downstream value.
instance nesting ≠ ownershipParent/child topology does not transfer resource or decision ownership.
preference ≠ authorityA preference can guide a proposal but cannot authorize an action.
FAQ
Questions, answered directly
What is HelmLoop?
HelmLoop is a runtime-neutral control-contract protocol for AI agent workflows. It separates execution, evidence, authority, promotion, provider reconciliation and observed outcomes so a host can inspect what supports a decision.
Is Protocol 0.2 available?
No. The current local implementation is the 0.1 candidate. Protocol 0.2 is a proposed r3 / sync-4 plan, including ten record types and seven decision axes. No 0.2 package, runtime conformance or production-readiness claim is made.
Does HelmLoop require Better Workflows?
No. The proposed neutral package is independent. A separate Better Workflows binding maps host-verified observations without transferring execution ownership or authority.
Do passing fixtures prove portability?
No. Fixtures check declared cases. Two mock adapters and one real binding would still not prove cross-runtime portability; that needs a qualifying pair of independent real-runtime observations.