Axiom
The truth layer — validation, simulation, guidance, and policy lens for Converge.
Axiom validates business specifications written in Gherkin-style .truths files using LLMs, generates Rust invariant code, and provides policy analysis tooling.
┌─────────────────────────────────────────────┐
│ Helm Decision frameworks │
├─────────────────────────────────────────────┤
│ Axiom Truth validation & codegen │ ← you are here
├─────────────────────────────────────────────┤
│ Organism Reasoning, planning, debate │
├─────────────────────────────────────────────┤
│ Converge Engine, governance, commit │
├─────────────────────────────────────────────┤
│ Providers LLMs, tools, storage │
└─────────────────────────────────────────────┘
What it does
| Module | Purpose |
|---|---|
gherkin |
Validate .truths specs for business sense, compilability, and conventions |
codegen |
Generate Rust invariant code from validated specs |
compile |
Compile and verify generated invariants |
simulation |
Simulate outcomes against specs |
guidance |
Contextual guidance for spec authors |
policy_lens |
Policy analysis and compliance checking |
jtbd |
Jobs-to-be-done framework integration |
predicate |
Predicate logic for truth evaluation |
CLI
Axiom ships cz, a workspace orchestrator:
Quick Start
Library Usage
use ;
let validator = new;
let result = validator.validate_file.await?;
Converge Boundary
Axiom uses the narrow Converge provider surface for live validation help:
converge-provider-apifor chat contracts and selection vocabularyconverge-providerfor concrete backend implementations and selection helpers
Axiom does not depend on the Converge engine crate as part of its public integration contract.
Architecture
See architecture/ for ADRs and API surface documentation.
License
MIT — Copyright 2024–2026 Reflective Group AB