Skip to content

Substrate Overview

Kairos Substrate is the Rust-native evaluation engine at the core of the Kairos on-premise stack. It provides deterministic, real-time structural risk assessment that runs entirely within your infrastructure — no cloud calls, no data exfiltration, no external dependencies at evaluation time.

Substrate sits between your autonomous system and the actions it wants to take. Every proposed action passes through the Substrate evaluation pipeline, which:

  1. Scales domain metrics (capability index, alignment score, etc.) into simulation parameters (λ\lambda, γ\gamma) using calibrated mapping functions
  2. Runs the physics engine to compute stability, reachability, and warning signals
  3. Applies policy gates — state thresholds, action preview, hazard detection — to produce a PASS or REJECT decision
  4. Returns a structured response with the decision, evaluation detail, and optional escalation directives

The entire pipeline is deterministic: same inputs always produce the same outputs, with bit-for-bit reproducible traces.

Substrate compiles from a single Rust codebase to three distribution targets:

TargetBuild outputUse case
CLI binarykairos executableTrace tooling, scenario management, policy/license operations, single-shot evaluation, live TUI dashboard
Native librarycdylib / staticlib + C headerC FFI and Python (PyO3) bindings for embedded integration
WASM modulewasm32-unknown-unknownBrowser/Node.js integration for advisory (non-authoritative) evaluation

The CLI and native library targets are authoritative — they enforce licensing, policy signatures, and cryptographic HITL override verification. The WASM target is intentionally advisory: policy signature and license checks are skipped, and HITL tokens are uniformly rejected. Authoritative enforcement must run on a licensed native build.

  • Integration engineers embedding Substrate into autonomous pipelines (LLM agents, MoE routers, robotics controllers)
  • Safety operators monitoring live systems via the kairos observe TUI and HITL override protocol
  • Platform teams deploying, configuring, and maintaining Substrate infrastructure on-premise
AreaCovers
ArchitectureCrate map, data flow, key types
Getting StartedBuild from source, licensing, first evaluation
Fly-by-WireStateful evaluation loop, action gating, hazard detection
ConfigurationCalibration artifacts, deployment policies, feature flags
CLI ReferenceAll CLI commands and flags