What is AxiomCore?

AxiomCore makes software contracts executable enough to guide tooling and precise enough to review. A contract can describe types and operations, but it can also carry bounded behavior, policy, domain meaning, UI packages, target support, and release metadata.

The goal is not to replace every framework. It is to give separately owned parts of a system a deterministic, versioned boundary that humans and agents can inspect before a change reaches users.

The platform in four layers

1. Authoring and extraction. Write .acore source, reuse trusted modules, or extract supported information from existing backend projects.
2. Contracts and packages. Build canonical .axiom artifacts, resolve versions into committed locks, and classify semantic changes.
3. Execution and development. Consume contracts through runtimes and framework bindings, author Acore UI, run mocks, and execute contract tests.
4. Coordination. Publish and pull releases through implemented cloud workflows. Richer visual building, collaboration, and discovery products are clearly marked as coming soon.

┌──────────────── authoring ────────────────┐
│ Acore source │ FastAPI │ Go │ bounded imports │
└────────────────────┬──────────────────────┘
                     ▼
          canonical contract packages
             (.axiom + committed lock)
                     │
        ┌────────────┼─────────────┐
        ▼            ▼             ▼
     runtime      test/mock     UI/app build
        │                          (.axiomapp)
        └────────────┬─────────────┘
                     ▼
              application behavior

Acore is the language, not the whole platform

Acore is an independent declarative language. AxiomCore is the larger ecosystem that compiles, packages, resolves, executes, tests, distributes, and audits the contracts Acore can express.

Contracts are incremental

• Keep an existing FastAPI or Go backend and extract its supported surface.
• Keep a Flutter, web, React, or Swift client and consume a contract through the target's current integration path.
• Author UI in Acore when the alpha Acore UI profile fits the application.
• Publish typed themes or component libraries without giving packages authority to execute package-author code.

The support matrix is the source of truth for which of these paths is available, alpha, experimental, or coming soon.

Continue reading

• What is Acore?
• Product landscape
• Contracts and artifacts
• Installation