# HelmLoop

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

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.

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.

## Documentation

- [Overview](https://helmloop.dev/index.md): HelmLoop — Control contracts for AI agent workflows
- [Protocol](https://helmloop.dev/engineering.md): Protocol 0.1 — Schemas, evidence and integration | HelmLoop
- [Roadmap](https://helmloop.dev/roadmap.md): Protocol 0.2 roadmap — r3 / sync-4 | HelmLoop
- [Research](https://helmloop.dev/research.md): Research, alternatives and evidence | HelmLoop
- [Protocol 0.1 specification](https://helmloop.dev/protocol/v0.1/spec.md): Current local candidate specification.

## Languages

- [English](https://helmloop.dev/index.md): Official documentation in English.
- [繁體中文](https://helmloop.dev/zh-Hant/index.md): Official documentation in 繁體中文.
- [日本語](https://helmloop.dev/ja/index.md): Official documentation in 日本語.
- [한국어](https://helmloop.dev/ko/index.md): Official documentation in 한국어.
- [ไทย](https://helmloop.dev/th/index.md): Official documentation in ไทย.

## Scope and status

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

The standalone helmloop try command is planned for 0.2. It is not available in the current CLI.

Plan: helmloop-v02-plan-20260915-r3, sync-4, 2026-09-16; PROPOSED. This website does not establish runtime attestation, action authority, package publication, or business outcome.