Axiom
Axiom — Governed AI for Coherent Software Engineering
Axiom is a hierarchical, multi-agent software engineering platform designed to build, analyze, and evolve complex codebases with architectural integrity, logical correctness, and human authority.
Unlike traditional agent frameworks, Axiom does not optimize for autonomy.
It optimizes for coherence.
Why Axiom?
Modern AI coding tools struggle with:
- Large, undocumented codebases
- Architectural drift over time
- Broken business logic despite passing tests
- Context limits and token inefficiency
- Uncontrolled agent behavior
Axiom addresses these problems by enforcing:
- Architecture-first development
- Persistent sources of truth
- Hierarchical reasoning
- Deterministic execution
- Human-owned decisions
Core Principles
-
Governed, not autonomous
Humans own intent and truth. AI assists within explicit boundaries. -
Persistent knowledge, ephemeral agents
Architecture and constraints outlive agents. -
Logic over locality
System-wide reasoning matters more than file-level correctness. -
Parallel execution, centralized control
Execution scales without losing coherence. -
Token efficiency as a design constraint
Abstractions replace context bloat.
Licensing
Axiom uses a dual-license model to ensure open collaboration while protecting commercial value:
- AGPL-3.0-or-later: For non-commercial, internal, open-source, and research use.
- Commercial License: Required for any monetized use, including SaaS, paid tools, or consulting.
Commercial Use Examples
- SaaS Offerings: Hosting Axiom as part of a paid service.
- Paid Developer Tools: Embedding Axiom in a proprietary tool sold to customers.
- Consulting Platforms: Using Axiom as a core engine in a paid consulting engagement.
Non-Commercial Use Examples
- Internal Evaluation: Testing Axiom prior to adoption
- Research: Academic or non-profit research
- Open-Source Contributions: Developing and sharing improvements to Axiom
Note: For-profit companies using Axiom in production—whether internally or externally—should obtain a Commercial License.
For licensing questions, see FAQ-LICENSING.md.
For commercial licensing inquiries, please contact Ramsanjiev at ramsanjiev@gmail.com.
High-Level Architecture
┌─────────────────────────────────────────────────────────────────────┐
│ HUMAN USER │
│ Goals, Constraints, Approvals │
└─────────────────────────────────────────────────────────────────────┘
│
▼
┌─────────────────────────────────────────────────────────────────────┐
│ INTERACTION LAYER │
│ ┌─────────────┐ ┌─────────────┐ ┌─────────────────────────────┐ │
│ │ Axiom CLI │ │ IDE Surface │ │ Copilot Interaction Layer │ │
│ │ (axiom) │ │ (VS Code) │ │ (Witness, not Approver) │ │
│ └─────────────┘ └─────────────┘ └─────────────────────────────┘ │
└─────────────────────────────────────────────────────────────────────┘
│
▼
┌─────────────────────────────────────────────────────────────────────┐
│ STRATEGIC LAYER (Axiom-Archon) │
│ Long-lived, Persistent │
│ ┌─────────────────────────────────────────────────────────────┐ │
│ │ • System-wide coherence • Logical reasoning │ │
│ │ • Knowledge stewardship • Human decision handling │ │
│ │ • CPKG/BFM/UCIR management • Strategic review │ │
│ └─────────────────────────────────────────────────────────────┘ │
└─────────────────────────────────────────────────────────────────────┘
│
▼
┌─────────────────────────────────────────────────────────────────────┐
│ TACTICAL LAYER (Axiom-Strata) │
│ Ephemeral, Planning │
│ ┌─────────────────────────────────────────────────────────────┐ │
│ │ • Intent interpretation • Task graph generation │ │
│ │ • Work decomposition • Validation strategy │ │
│ │ • LLM tactical planning • Outcome summarization │ │
│ └─────────────────────────────────────────────────────────────┘ │
└─────────────────────────────────────────────────────────────────────┘
│
▼
┌─────────────────────────────────────────────────────────────────────┐
│ TASK EXECUTOR (Axiom-Conductor) │
│ Deterministic Control Plane │
│ ┌─────────────────────────────────────────────────────────────┐ │
│ │ • Task graph execution • Dependency ordering │ │
│ │ • Parallel scheduling • Retry and failure handling │ │
│ │ • NO LLM calls • Structured event emission │ │
│ └─────────────────────────────────────────────────────────────┘ │
└─────────────────────────────────────────────────────────────────────┘
│
▼
┌─────────────────────────────────────────────────────────────────────┐
│ EXECUTION LAYER (Axiom-Forge) │
│ Stateless Workers │
│ ┌─────────────────────────────────────────────────────────────┐ │
│ │ • Code generation • Refactoring │ │
│ │ • Test generation • Tool invocation │ │
│ │ • Shell execution • Playwright automation │ │
│ │ • Context-aware backends • Remote execution │ │
│ └─────────────────────────────────────────────────────────────┘ │
└─────────────────────────────────────────────────────────────────────┘
│
▼
┌─────────────────────────────────────────────────────────────────────┐
│ VALIDATION LAYER │
│ ┌──────────────────┐ ┌──────────────────┐ ┌─────────────────┐ │
│ │ Axiom-Logos │ │ Axiom-Sentinel │ │ Semantic │ │
│ │ Logical │ │ Behavioral │ │ Regression │ │
│ │ Validation │ │ Validation │ │ Detection │ │
│ └──────────────────┘ └──────────────────┘ └─────────────────┘ │
└─────────────────────────────────────────────────────────────────────┘
Core Components
| Component | Role | Persistence | Authority |
|---|---|---|---|
| Axiom-Core | Shared schemas, workflow orchestration | N/A | Workflow control |
| Axiom-Canon | Knowledge artifacts (CPKG, BFM, UCIR, TaskGraph) | Persistent | Source of truth |
| Axiom-Archon | Strategic reasoning, human decision handling | Long-lived | Coherence gate |
| Axiom-Strata | Tactical planning, task decomposition | Ephemeral | Plan generation |
| Axiom-Conductor | Deterministic task execution | Stateless | Execution control |
| Axiom-Forge | Code generation, tool invocation | Stateless | Task execution |
| Axiom-Logos | Logical validation | Stateless | Invariant checks |
| Axiom-Sentinel | Behavioral validation | Stateless | E2E testing |
| Axiom-CLI | Command-line interface | Stateless | Transport only |
CLI Commands
Axiom provides a governed command-line interface:
# Initialize or adopt a project
axiom init # New project
axiom adopt # Existing project
# Plan and execute work
axiom plan "<intent>" # Create execution plan
axiom preview # Validate and simulate
axiom approve --rationale "..." --yes # Human approval (REQUIRED)
axiom execute # Execute approved plan
# Utilities
axiom status # Show workflow status
axiom docs # Generate documentation
axiom discover # Run discovery analysis
Important: Commands must be run in order. You cannot skip steps or auto-approve.
Copilot Interaction
Key Principle: Copilot acts as a witness, not an approver. It can help you formulate decisions, but it cannot make them for you.
Approval Grammar (enforced by Axiom):
APPROVE: <rationale explaining why you approve>
REJECT: <rationale explaining why you reject>
OVERRIDE: <rationale for overriding AI recommendation>
EXECUTE (no rationale, requires prior approval)
Invalid (will be REJECTED):
- "yes", "ok", "looks good", "lgtm", "approved", "👍"
Persistent Knowledge Artifacts
Axiom avoids long prompts and fragile memory by using explicit, minimal artifacts.
Canonical Project Knowledge Graph (CPKG)
- Components, responsibilities, dependencies
- Decisions, invariants, risks
- Human-approved, token-efficient
Business Flow Map (BFM)
- End-to-end user and system flows
- Drives logical reasoning and E2E validation
User Constraint & Instruction Registry (UCIR)
- Persistent architectural, UX, and business constraints
- Enforced across all layers
- Editable at any time
These artifacts are the only long-lived memory in the system.
AI vs Human Authority
AI recommends. Human decides.
| Actor | Authority |
|---|---|
| Human | Final decision, approval, override |
| AI (Strategic) | Advise, recommend, surface risks |
| AI (Tactical) | Plan, decompose, organize |
| AI (Execution) | Execute approved tasks only |
Key principles:
- No execution without explicit human approval
- AI approval alone never authorizes action
- Override requires rationale
- Silence equals rejection (no timeout-based approval)
See: GOVERNANCE.md
Validation Beyond Tests
Axiom does not assume "tests passing = system correct".
It validates software through:
- Static logical reasoning (flows, invariants, dependencies)
- Behavioral testing (Playwright, E2E flows)
- Semantic regression detection (intent vs outcome)
All validation results are surfaced for human ratification.
GitHub Copilot Integration
Copilot is treated as a controlled execution assistant, not an architect.
- Scoped tasks only
- Explicit constraints
- Minimal context
- No architectural invention
See: .copilot/copilot-instructions.md
Supported Use Cases
- Greenfield project bootstrapping
- Large legacy codebase refactoring
- Architecture enforcement over time
- Parallel feature development
- Safer AI-assisted engineering
What Axiom Is Not
- ❌ A fully autonomous coding agent
- ❌ A prompt-heavy agent swarm
- ❌ A replacement for engineering judgment
- ❌ A "magic" AI that understands everything
Axiom is a system, not a shortcut.
Project Status
✅ v1.0.0 — Production Ready
Axiom v1.0.0 is a stable release with:
- Complete governance model
- Deterministic task execution
- Multi-layer validation framework
- Copilot integration with strict approval grammar
- Human Decision Intake API
- New project and existing project onboarding
- First-run guardrails
- CLI with workflow enforcement
Test Coverage: 716 tests passing
Getting Started
See: ONBOARDING.md
Installation
pip install axiom-engine
New Projects
# Using CLI
axiom init
axiom plan "Create a REST API for user management"
axiom preview
axiom approve --rationale "Reviewed plan, architecture looks correct" --yes
axiom execute
Existing Projects
# Using CLI
axiom adopt
axiom discover
axiom plan "Refactor authentication module"
axiom preview
axiom approve --rationale "Reviewed changes, low risk" --yes
axiom execute
Python API
from axiom_core import AxiomWorkflow
from axiom_canon import CPKG, BFM, UCIR
workflow = AxiomWorkflow()
result = workflow.run(
user_request="Add user authentication",
cpkg=cpkg,
ucir=ucir,
bfm=bfm
)
Documentation
| Document | Description |
|---|---|
| ARCHITECTURE.md | System architecture, components, and workflows |
| GOVERNANCE.md | Authority model and approval rules |
| ONBOARDING.md | Getting started guide |
| INSTALLATION.md | Installation and setup |
| SECURITY.md | Threat model and security invariants |
| SIGNING.md | Code signing and release verification |
| PUBLIC_API.md | API stability tiers |
| FAQ-LICENSING.md | Licensing questions and answers |
| CHANGELOG.md | Version history |
Philosophy
Software systems are not files.
They are structures of intent.
Axiom exists to preserve that intent — even as code changes.
License
Axiom is available under a dual-license model:
- AGPL-3.0-or-later — for non-commercial, internal, open-source, and research use
- Commercial License — required for any monetized use (SaaS, paid tools, consulting platforms)
See:
For commercial licensing inquiries, contact Ramsanjiev at ramsanjiev@gmail.com.
Metadata
Release files for axiom-engine 1.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| axiom_engine-1.0.0.tar.gz | 337.0 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| axiom_engine-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 635.0 kB
Release files / axiom_engine-1.0.0.tar.gz
| Download URL | axiom_engine-1.0.0.tar.gz |
|---|---|
| Size | 337.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1138814d5f3650c07d18c04f6ff682b1620a9700abc1a60f179ffb2c4316eaba
|
|
BLAKE2b-256 checksum How to use checksums |
06822138b342a06fee689aa342a67ccd458355c03eb713f793cfd62c0904d3b9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Dec 15, 2025.
Transparency logRelease files / axiom_engine-1.0.0-py3-none-any.whl
| Download URL | axiom_engine-1.0.0-py3-none-any.whl |
|---|---|
| Size | 297.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
03639ba51cf5f8d1fe55346bccf73ecfd84adcfc1306f32afdfeed2228c2f802
|
|
BLAKE2b-256 checksum How to use checksums |
94d603a22f7db54091b52f36a4a390fa1fb35f776e1fca810b1c73e53593d177
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Dec 15, 2025.
Transparency logSecurity for axiom-engine 1.0.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for axiom_engine-1.0.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Dec 15, 2025.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.