Who is AxiomCore for?
Adoption paths for application, platform, backend, quality, and security teams.
AxiomCore is for teams that need separately owned software parts to evolve without relying on undocumented integration assumptions.
Application developers
Consume locked service contracts from an existing web, React, Flutter, or Swift codebase, or use the alpha Acore UI path to author a declarative interface. Target support differs, so validate against the support matrix.
Backend developers
Extract a supported FastAPI or Go service, then use Acore to add contract-level behavior, validation, variants, domain semantics, and reviewable security declarations. Backend application code remains responsible for trusted runtime authorization and business effects.
Platform and architecture teams
Define package boundaries, lock dependencies, review semantic diffs, and keep service, theme, component, database-schema, extension, and policy artifacts versioned independently.
QA and reliability teams
Use contract-driven mocks, tests, fault definitions, inspection, and benchmark workflows to create repeatable evidence around an integration boundary.
Security and governance teams
Review declared authentication, authorization relations, sensitive-data classification, effects, integrity metadata, and release approvals. AxiomCore surfaces these decisions; it does not replace runtime enforcement or a security assessment.
Humans and agents
The same readable source, canonical packages, locks, diagnostics, and semantic diffs can give both human contributors and software agents a narrower, auditable change surface. Planned collaborative products are described in the product landscape, with their current status made explicit.