The Problem

Your job does not fit in one app.

Five tabs. Three logins. Two spreadsheets. One frustrated person trying to close a deal, approve an expense, or onboard a hire. Those tools reflect the way software was built, not the work you are trying to complete.

Before: five systems, one frustrated person

● CRM Update deal stage
◆ Billing Generate invoice
❆ Slack Notify delivery team
■ Sheets Update forecast
✉ Email Send confirmation
0 context switches

After: one intent, one surface

▶ Close deal with Acme Corp
○ Update deal stage CRM
○ Generate invoice Billing
○ Notify delivery team Slack
○ Update forecast Sheets
○ Send confirmation Email
The Daily Journey

Your day, shaped around the work at hand.

Helm starts from your intent and proposes a surface around what you are trying to accomplish. Describe what should be true, then inspect proposals, evidence, and open questions. The right to bind the organization must be explicit, whether exercised by a person or delegated.

08:00
☼
Arrive
09:30
✎
Close
11:00
✓
Approve
14:00
⚙
Plan
16:30
★
Review
▶ Your day starts when you express your first intent.
Intent-Driven

State the outcome and constraints. See the route.

A Business Truth describes a desired outcome and its constraints, not a prescribed workflow. Several attempts may explore it. You can compare acceptable results, request another attempt, or authorize a commitment within your mandate. A commitment binds the organization to a specific version.

1
Intent You express what you need
"Approve March expenses, flag anything over €500"
2
Decode System decomposes your intent
3 receipts to review, 1 policy check, 1 approval gate
3
Plan Formation plans the work
OCR receipts → match policies → flag exceptions → route approval
4
Validate Axiom validates the specs
Check the expense specification; validity is not approval
5
Authorize Explicit mandate required
Converge enforces the promotion and authority boundary
6
Surface Helm shows you what matters
€2,340 approved. 1 exception: hotel receipt needs justification.
▶ Helm
▶ Helm
◉ Formation
◆ Axiom
▶ Converge
▶ Helm

An accepted uncertainty remains uncertainty. If requirements allow an exception, record the mandate and what is still unknown. Learning may change future plans, but an existing commitment requires an explicit change because others may already rely on it.

The Stack

Four layers. Each does one thing well.

Layer 4

Helm

Control surface

Where work happens: intent capture, adaptive surfaces, approvals, and the daily journey.

helms.zone
Layer 3

Axiom

Specification layer

Validates specifications before execution. Six-stage pipeline from truth document to compiled WASM invariant.

axioms.zone
Layer 2

Formation

Intelligence layer

Organizes Competition, Huddle, and alternative attempts. Zero or several results may meet the requirements.

formation.zone
Layer 1

Converge

Convergence kernel

The low-level contract for shared context, facts, authority boundaries, promotions, and bounded convergence.

converge.zone

Runtime-Runway supplies messaging and storage around these components. The operating-system model describes their composition, not Converge alone.

Keep the job in view, even when it crosses systems.

From intent to commitment: how the parts fit together