Local semantic transformation for private AI reasoning.
Status: Early-access infrastructure SDK.
APIs, guarantees, behavior, and licensing details may change.
Axiom Core is an early-access execution layer for transforming sensitive local input into non-identifying semantic representations, enabling cloud models to reason over structure without access to raw data.
The SDK performs semantic transformation locally by removing identifying information while preserving the relational structure required for reasoning.
This repository is shared for transparency and early technical validation, not as a production-ready security boundary.
- Overview
- Design Intent
- Installation
- Usage
- Design Guarantees (Current Scope)
- What This SDK Is
- What This SDK Is Not
- High-Level Architecture
- Security Model (Current Scope)
- Experimental: Enclave Execution (Preview)
- Repository Structure
- Contributing
- License
- Links
Many high-value AI workflows are blocked today because sensitive data cannot move to the cloud.
Existing approaches typically:
- redact information and break reasoning
- encrypt data and block inference
- rely on local models with limited quality
Axiom Core explores an alternative approach: preserving semantic structure while removing identity, so modern models can reason without seeing raw data.
Axiom Core is built with the following intent:
- Correctness over convenience
- Deterministic behavior over heuristics
- Explicit boundaries over implicit trust
- Known failure modes over undefined behavior
The SDK is designed to fail explicitly when boundaries are violated and to make assumptions and limitations visible.
- Node.js >= 20.0.0
- npm >= 9.0.0 (or Yarn / pnpm)
npm install @axiom-infra/core
# or
yarn add @axiom-infra/coreimport { Axiom } from "@axiom-infra/core";
const axiom = new Axiom({
securityTier: "standard",
enclave: "none",
policyVersion: "v1",
});
const result = await axiom.reason({
context: localDocuments,
task: "analyze obligations and risks",
model: "gpt-5",
});
// Only result.transformedContext is intended to be sent to the cloudnpm install
npm run demoIf your shell blocks npm scripts:
node --experimental-strip-types demo/demo.jsThe following properties describe intended behavior within the current SDK-controlled execution scope. They are not contractual guarantees and may evolve as the system matures.
| Property | Description |
|---|---|
| No raw data transmission | Raw input data is not transmitted by the SDK |
| Local transformation | Semantic transformation occurs locally |
| Explicit network calls | No implicit network calls are performed |
| Fail-fast boundaries | Boundary violations fail explicitly |
| No identity mapping output | Raw ↔ transformed mappings are not exposed |
These properties apply only to SDK-controlled execution paths.
Axiom Core is infrastructure, not an application.
It is designed to be embedded in systems where:
- Sensitive data should not be transmitted externally
- Frontier models are still required for reasoning
- Trust boundaries and auditability matter
At a high level, the SDK:
- Performs semantic analysis on local input
- Transforms raw data into non-identifying representations
- Preserves entities, roles, and relationships
- Enforces a strict boundary between local context and external models
To avoid ambiguity, Axiom Core is explicitly not:
- A hosted service or proxy
- A redaction or PII-masking tool
- A compliance product or legal authority
- A cryptographic encryption system
- A local language model or inference engine
- A cloud routing, billing, or orchestration layer
These concerns are intentionally out of scope.
Axiom Core operates entirely on the local side of a strict trust boundary.
┌─────────────────────────────────────────────────────────────────┐
│ Local Environment (This SDK) │
│ │
│ • Semantic analysis and transformation │
│ • Entity and relationship abstraction │
│ • Context filtering and minimization │
└─────────────────────────────────────────────────────────────────┘
│
▼ Transformed context only
┌─────────────────────────────────────────────────────────────────┐
│ External Model Boundary │
│ │
│ • Receives non-identifying context only │
│ • Performs reasoning using external models │
│ • Never receives raw private data │
└─────────────────────────────────────────────────────────────────┘
Within SDK-controlled execution paths, the system enforces:
- No raw text serialization
- No implicit network access
- Explicit local-to-external boundary enforcement
- Zero data retention by default
The SDK assumes:
- The host operating system is honest-but-curious
- The runtime environment is not actively malicious
The SDK is not designed to be safe under fully compromised host conditions.
Enclave execution is experimental and not required to use Axiom Core.
This feature does not define the security posture of the SDK.
Notes:
enclave: "auto"may fall back to a simulatorenclave: "required"fails if a native runner is unavailable- Simulator mode provides no security guarantees and is intended for development only
axiom-core/
├── src/ # Core SDK implementation
├── demo/ # Demo script
├── artifacts/ # Example artifacts and outputs
├── docs/ # Design notes and specifications
├── tests/ # Unit and boundary tests
├── STATUS.md # Project status and maturity notes
├── README.md
├── docs/architecture.md
├── docs/security.md
├── docs/roadmap.md
└── LICENSE
At this stage, Axiom Core is not accepting external code contributions.
Feedback, issues, and discussion are welcome. Contribution guidelines will be published once the architecture and licensing model are finalized.
Axiom Core is released under the Apache 2.0 License.
This repository represents an early-access, open component of the Axiom system. Other components may be licensed differently.
- Integration Guide: docs/INTEGRATION.md
- Architecture: docs/architecture.md
- Security: docs/security.md
- Roadmap: docs/roadmap.md
- Status: STATUS.md
- Issues: https://github.com/Axiom-Infra/axiom-core/issues
- Contact: [email protected] | [email protected]
Axiom exists to preserve intelligence under constraint.