Developers
Everything your team needs to build on the Kernel Engine: the manifest specification, the artifact lifecycle, and the Control Plane API.
Back to Axiom-Trace PlatformStart here
Five minutes to the first 200 OK — then the live console and the recipes.
Quickstart
Session → open a lot → record a piece → close → read the projection. Copy-paste, five minutes.
API Playground
Read-only live console: sign in with a portal account, inspect your tenant's real JSON.
End-to-end examples
curl / Node / Python recipes: operator login, the production-line trigger flow, the tenant surface and the signed ingest channel.
API Reference
Every endpoint by trust boundary: sync channel, tenant portal, admin ops, Stripe webhook.
The knowledge tree
Progressive disclosure, one bounded context per node: Level 1 teaches the rules, Level 2 the failure modes.
Authoring & platform
Manifest Specification
The declarative contract: meta, five engines, expression namespaces, security rules, and practical authoring pitfalls.
Publish → Pull → Verify
The artifact lifecycle: how a manifest reaches the fleet, gets verified, and hot-swaps without downtime.
Industrial OT
Deterministic manifest-driven execution, fail-closed constraints and signed audit — the edge node on the machine.
Every action crosses the same six gates
The execution protocol is the real pipeline behind the synoptic: six checks in fixed order inside a single tenant transaction, then the audit seal and the commit. If a gate fails, the transaction rolls back — nothing is written, the attempt is still recorded.
AUTHsession or API key resolvedIDEMPidempotency key replay checkRBACrole permits the triggerFSMtransition legal from current stateCONSTRpre-commit rules holdDLINKguarded data-link writeAUDIT → COMMIThash-chained row, then finalTwo further gates run when declared: contract (before the transaction) and license (when the trigger requires a plugin). Same discipline — fail-closed, inside the same write.
You write the manifest. We run the engine.
Your application is a signed JSON manifest plus its UI assets. The kernel supplies the runtime: five deterministic engines, the offline-first store, the audit chain, and the sync channel. You never fork the engine — you publish a new manifest version.
What you build
Manifest (screens, actions, rules, roles), SQL migrations, plugin logic and UI — packaged and published through the Control Plane.
What the kernel runs
Deterministic execution, tenant isolation, audit chain, outbox sync, license enforcement — identical on every node.
What you get back
A signed, auditable, offline-proof application your customers can run anywhere — with distribution handled for you.