Axioms Zone · Specification Validation

Validate before
you execute.

Describe what should be true, not how to get there. Axiom makes Business Truths explicit and checkable through Truth specs and Gherkin. Its checks catch specification errors; they do not prove the desired outcome or authorize a commitment.

See the pipeline How it works

The Stack

The Pipeline

Six checks; each catches a different class of error.

Specifications pass through a layered validation pipeline before code is generated or compiled.

.truths

{ }

Parse Extract governance blocks & Gherkin

LLM

Validate Business sense & compilability

Simulate Convergence readiness check

Generate Predicates to Rust source

Compile Rust to WASM binary

Analyze Cedar policy coverage gaps

.wasm

Truth Documents

Business intent, written as a governed specification.

.truths files combine Gherkin scenarios with governance declarations for intent, authority, constraints, evidence, and exceptions. Outcome and evidence requirements belong in or alongside the versioned specification. Authorization is a separate decision.

vendor-eval.truths

1 # Intent

2 Outcome: selected vendor meets the declared cost and quality requirements

3 Goal: reduce vendor evaluation from weeks to hours

5 # Authority

6 Actor: procurement-committee

7 May: evaluate, score, recommend

8 Must Not: commit spend above €50K without human sign-off

10 @invariant @structural @id:vendor-eval-001

11 Feature: Vendor evaluation produces a governed recommendation

13 Scenario: Every vendor has a compliance score

14 Given vendors are loaded from the shortlist

15 Then each vendor must have a "compliance_score" field

16 And compliance_score must be between 0 and 1

1 |

Validation Checks

◯ Business sense

◯ Compilability

◯ Conventions

Findings

Illustrative syntax and findings. A validated specification describes what should be true; it is not evidence that this state already exists.

Governance

Each validation leaves an auditable finding.

LLM-powered checks apply where judgment is needed; local checks handle rules that can be stated directly. Both have fallback paths.

Current Stage

Ready

Press play to begin validation.

Audit Ledger

Stage	Finding
Parser	2 governance blocks, 1 scenario
LLM Validator	Business sense assessment recorded
Simulator	Verdict: Ready
Codegen	RequiredFields + ContentMust
Compiler	WASM binary 4.2KB
Policy Lens	No coverage gaps

Architecture

Axiom checks specifications; Converge enforces the kernel contract.

Axiom

Validates and compiles a specification

◆ Parse governance blocks & Gherkin scenarios

◆ LLM-powered business sense validation

◆ Simulate convergence readiness

◆ Generate & compile Rust WASM modules

◆ Cedar policy coverage analysis

WASM ABI v1

Converge

Governs shared context, facts, authority boundaries, and promotions

✓ Loads WASM invariant modules

✓ Manages context and facts

✓ Runs the convergence loop

✓ Checks invariants within bounded convergence attempts

Axiom contributes checkable specifications. Formation organizes reasoning; Helm supports operator decisions. Runtime-Runway supplies messaging and storage around the Converge kernel.

From intent to commitment

Validate beforeyou execute.