# Helms Zone

> Helm is an intent-adaptive workbench that keeps the job ahead of the tools. Describe what should be true, compare proposals and evidence, and exercise explicit authority for commitments.

Helm is the control surface in the Reflective Labs stack. The unit of work is a job, such as closing a deal, hiring a person, or resolving an incident. An intent session states the desired outcome and constraints; adaptive surfaces bring evidence, alternatives, and required authority into view. Selecting a proposal is not a commitment without an explicit binding mandate. Existing CRM, ERP, and other tools remain providers behind the workbench.

## Pages on this site

- [Your daily journey, one intent at a time](https://helms.zone/): Helm brings work from business tools into an intent-adaptive workbench. See intent sessions, adaptive surfaces, governed blueprints, typed approvals, and the daily journey.

## Explore this product

- [The Coordination Problem](https://helms.zone/#problem)

- [The Daily Journey](https://helms.zone/#journey)

- [Intent-Driven Work](https://helms.zone/#intent)

- [The Zone Family](https://helms.zone/#stack)

## Core concepts

- **Intent sessions**: Declare the outcomes, deadlines, budgets, and authority that shape a work period.

- **Adaptive surfaces**: Assemble the relevant work panels around the active job and its current context.

- **Blueprints**: Structure cross-functional jobs with defined ownership, approvals, and exits.

- **Typed approvals**: Keep financial, legal, brand, and compliance decisions tied to the authority needed for each domain.

- **Providers**: Use existing business tools for data and actions while coordinating the job through the workbench.

- **Daily journey**: Open an intent session, work through active jobs and exceptions, then carry open items into the next session.

- **Honest exits**: Make the ending explicit: converged, budget exhausted, policy blocked, or escalated.

## Who this is for

- Business operators working across multiple systems

- Teams coordinating jobs across sales, legal, finance, and operations

- Founders designing intent-driven work with explicit human authority

## Shared reading at Converge Zone

The family header points to the original Converge pages. Backstage, Signals, Voices, Mechanics, and Research are hosted at converge.zone.

- [Backstage](https://converge.zone/manifesto)

- [Signals](https://converge.zone/signals)

- [Voices](https://converge.zone/podcast)

- [Mechanics](https://converge.zone/mechanics)

- [Research](https://converge.zone/research)

## Related research at Reflective Labs

Reflective Labs publishes the original technical reports, including methods, results, limitations, PDFs, and slide summaries. The Converge Research page provides a reading guide. These links identify related research rather than claiming a separate paper for every product.

- [Reflective Labs research library](https://www.reflective.se/labs/research)

- [Institutionalized disagreement](https://www.reflective.se/labs/research/formation): The planning and review stages between an operator declaring intent and a governed commitment.

- [What to learn before you train](https://www.reflective.se/labs/research/jepa): Research on learning about coordination and initiative trajectories rather than modeling individual employees.

- [No room for slop](https://www.reflective.se/labs/research/collective-intelligence): How people check proposals and contribute knowledge to shared decisions.

- [From intent to commitment](https://converge.zone/model): The current product model: outcomes, attempts, evidence, selection, authority, and learning.

Runtime-Runway supplies messaging and storage around the components. The operating-system analogy belongs to this composition, not to the Converge kernel alone.

## The Zone family

- [Converge Zone](https://converge.zone/): The kernel contract for shared context, facts, authority boundaries, and promotions. Admission and binding commitment are distinct.

- [Formation Zone](https://formation.zone/): Formations, including Competition and Huddle, explore alternative attempts. Zero or more results may meet the declared outcome and evidence requirements.

- [Axioms Zone](https://axioms.zone/): Truth specs describe what should be true. Validation and checkable artifacts do not themselves establish real-world outcomes or authorization.

- [Helms Zone](https://helms.zone/): The operator surface for expressing outcomes, inspecting evidence, and exercising explicit authority.

## Scope

This is a public product and architecture website. Its animations and governance demonstrations are illustrations of the intended mechanisms, rather than live engine telemetry. Use the original technical reports for the precise scope of research results and open questions.

## Optional

- [Extended product context](https://helms.zone/llms-full.txt): A longer reading guide and product definitions from the site knowledge base.

- [Sitemap](https://helms.zone/sitemap.xml): Canonical pages hosted on this domain.