# Axioms Zone

> Axiom makes desired outcomes explicit and checkable through Truth specs and Gherkin. Specification validation is separate from outcome evidence and commitment authority.

Axiom is the specification validation and compilation layer in the Reflective Labs stack. Truth documents combine Gherkin scenarios with governance declarations. The pipeline checks intent, authority, constraints, and compilability before it produces invariant modules for the Converge engine. Validation does not prove an outcome or grant authority. Converge enforces the low-level contract for context, facts, authority, and promotions.

## Pages on this site

- [Validate before you execute](https://axioms.zone/): Axiom validates truth documents in six stages before compiling WASM invariants for Converge. See specification validation, governance declarations, and auditable findings.

## Explore this product

- [Validation Pipeline](https://axioms.zone/#pipeline)

- [Truth Documents](https://axioms.zone/#how-it-works)

- [Governance Findings](https://axioms.zone/#governance)

- [The Kernel Boundary](https://axioms.zone/#converge)

## Core concepts

- **Truth documents**: Specifications in .truths files combine business scenarios with intent, authority, constraints, evidence, and exceptions.

- **Parse**: Extract governance declarations and Gherkin scenarios into a structured specification.

- **Validate**: Check business sense and compilability where judgment is needed, and apply local conventions where rules suffice.

- **Simulate**: Assess convergence risks under stated simulation conditions; a readiness assessment is not a guarantee.

- **Generate and compile**: Generate semantic predicates and Rust source, then compile deterministic WASM invariant modules.

- **Analyze**: Examine Cedar policy coverage and identify gaps in the declared governance.

- **Findings and manifests**: Retain validation results and module metadata so the path from specification to runtime artifact remains inspectable.

## Who this is for

- Developers writing governed business specifications

- Teams building specification-driven multi-agent systems

- Organizations that need traceable validation and policy coverage before execution

## 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)

- [Proposal, gate, commitment](https://www.reflective.se/labs/research/converge): The decision foundation that consumes the invariant modules Axiom produces.

- [Searched, not verified](https://www.reflective.se/labs/research/soter): A precise account of symbolic assurance and the distinction between searched evidence and independently checked proof.

- [Policy that participates](https://www.reflective.se/labs/research/arbiter): The relationship between policy, authorization, and execution-order independence in the governed loop.

- [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://axioms.zone/llms-full.txt): A longer reading guide and product definitions from the site knowledge base.

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