Protocol 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.

Markdown version ↗

HelmLoop

Eight executable 0.1 records

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.

RecordSchemaResponsibility
OutcomeContractV1JSON ↗Accountable outcome, risk, owner, horizon, criteria, constraints, preferences, stop conditions, and all six axes.
AuthorityGrantV1JSON ↗Owner-issued, exact, expiring, revocable, single-use authority with durable reservation and terminal lineage.
ExecutionReceiptV1JSON ↗Attempt-bound execution fact with resource owner, provider-request binding, and exact reserved authority reference.
EvidenceRecordV1JSON ↗Freshness-capped, criterion-digested conclusion with provenance, dependency fingerprints, and limitations.
AssuranceDecisionV1JSON ↗Evidence-bound L0–L3 assurance decision whose sufficiency is recomputed.
PromotionDecisionV1JSON ↗Owner decision with exact target parameters, separate promote authority, and non-regressing lineage.
ReconciliationRecordV1JSON ↗Fresh query bound to the exact execution, attempt, provider request, locator, and observed external state.
LearningSignalV1JSON ↗Bounded proposal based on outcome evidence; never self-accepting and never truth by itself.

HelmLoop

Six current decision axes

AxisResponsibilityState
executionWhat the executor didNOT_STARTED · RESERVED · RUNNING · COMPLETED · FAILED · UNKNOWN · INVALID
evidenceWhether required claims are fresh and supportedMISSING · FRESH · STALE · CONFLICTING · INVALID
authorityWhether the exact action was authorizedMISSING · ACTIVE · EXPIRED · REVOKED · WRONG_BINDING · CONSUMED · AMBIGUOUS · INVALID
promotionWhat the accountable owner decidedNOT_REQUESTED · PENDING · APPROVED · REJECTED · HOLD · AMBIGUOUS · INVALID
reconciliationWhat the provider and observed external state showNOT_REQUIRED · PENDING · MATCHED · DIVERGED · UNKNOWN · INVALID
observedOutcomeWhat independent outcome evidence showsNOT_DUE · NOT_OBSERVED · MET · NOT_MET · MIXED · UNKNOWN · INVALID

HelmLoop

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.

01

Name the inequalities

Separate completion, authority, receipt, outcome and ownership in existing logs.

02

Add one promotion gate

Use a small deterministic check and named owner for one consequential transition.

03

Bind evidence freshness

Record subject, revision, expiry and external reconciliation.

04

Plug in governed assurance

Use Better Workflows or an equivalent only where risk justifies the cost.

HelmLoop

Read the evidence at its actual scope

Current fixture results do not certify a live runtime, broad portability, production readiness or business value. The research page keeps these open questions visible.

Version boundaries matter

0.1 keeps HL-C14N-1, its original readers and six-axis semantics. Planned 0.2 uses helmloop-jcs-sha256-v1 and typed sha256: references. A matching digest checks integrity; it does not grant trust or authority.

Research ↗