1. SPUdata: The Shield & Sovereign Vault

Data Deconvolution and ESG Optimization

Before sensitive data ever touches an AI compute layer, it is routed through the SPUdata proxy. SPUdata acts as a deterministic air-gap, stripping raw Personally Identifiable Information (PII) and passing only lightweight, synthetic tokens to the LLM.

The Dual-Vault Architecture:

The Private Vault (On-Premise/Secure Edge): Holds the heavy, raw, restricted PII securely within the institution's localized jurisdiction.

The Public Vault (Cloud/Hyperscaler): Manages the lightweight, deconvoluted tokens utilized by the AI for processing.

The Commercial Dividend:

By passing only sanitized tokens to the hyperscaler, SPUdata drastically reduces token processing weight. This actively aligns the infrastructure with corporate Net Zero targets by cutting Scope 3 emissions, lowering cloud compute costs, and shielding the institution from data-leak liabilities.

2. EAVEcore: The Jurist

Pre-Execution Liability Shield and The IDE Seatbelt

EAVEcore is the logic gate that enforces the institution's constitutional rules. Rather than regulating the probabilistic AI model, EAVEcore regulates the environment it operates within.

Semantic Drift Prevention:

Translates complex regulatory texts (e.g., FCA CASS rules, Nolan Principles) into deterministic mathematical boundaries.

Active Code Interception:

Acts as a "Seatbelt" for developers and AI agents. If an action violates a sector maxim (such as commingling funds), EAVEcore throws a Hard Error, physically blocking the execution before the code compiles.

3. TallySticks: The Witness

Cryptographic Human-in-the-Loop (C-HITL) Accountability

The traditional "Human-in-the-Loop" is a passive liability trap. TallySticks transforms human operators into active, protected auditors.

Immutable Receipts:

When an operator manually overrides an EAVEcore warning, they must provide a formal statutory justification. TallySticks anchors the code snippet, the operator's ID, and their justification to a distributed cryptographic ledger in 15 milliseconds.

Insurability:

This creates a non-repudiable audit trail, proving to regulators that Senior Managers (SMF24) took "reasonable steps" to control AI deployments, effectively curing automation bias and securing corporate insurability.

Multi-Cloud Agnostic: Zero Vendor Lock-in

Reconciliation, Not Revolution.

The Axiom Tripartite API is built on the principle of absolute infrastructure neutrality. We do not force you into a proprietary cloud ecosystem, nor do we replace your existing hyperscaler. We provide the independent compliance engine that sits seamlessly on top of AWS, Microsoft Azure, Google Cloud, or your own on-premise servers.

Portable Accountability:

Your constitutional rules, EAVEcore logic, and cryptographic keys remain entirely separated from the underlying cloud provider's proprietary services. You own the governance; the cloud simply provides the compute.

G-Cloud 15 & Security Status

Axiom Origins Ltd is formally certified by the IASME Consortium for Cyber Essentials, meeting the mandatory security baseline for UK Crown Commercial Service procurement. We serve as the critical bridge for any hyperscaler looking to safely deploy Agentic AI into the public sector.

Technical Reference: Core Endpoints

The Axiom Sovereign Governance API is designed for stateless deployment within Trusted Execution Environments (TEE). Below are the core telemetry endpoints for integrating the Tripartite Engine.

Method Endpoint Pillar Description
POST /v1/spudata/deconvolute Shield Intercepts raw payloads, strips PII into secure vault, and returns low-weight synthetic tokens for the LLM.
POST /v1/eavecore/evaluate Jurist Evaluates proposed AI execution logic against deterministic Sector Maxims. Returns Permit Token or Hard Error block.
POST /v1/tallysticks/anchor Witness Generates an immutable cryptographic hash of the execution receipt, including any C-HITL operator override justifications.
POST /v1/axiom/gateway/execute Aggregated Unified gateway endpoint. Sequentially runs the payload through SPUdata (clean), EAVEcore (check), and TallySticks (record) in a single 92ms call.