Live enforcement · kernel.execlayer.io

Test the kernel, live.

Send a real rover request to the public demonstration kernel and inspect the signed decision receipt. The rover remains our live proof.

The live kernel

kernel.execlayer.io · signed ED25519 receipts

This files a real intent with the kernel: a rover asking to fire a thruster at nineteen times its authorized burn. The action is refused unless it is authorized, and the refusal comes back as signed evidence anyone can verify.

Plain-English tour · 80 seconds · audio with captions
  1. Intent loaded
  2. Rules checked
  3. Verdict and receipt

subject

rover-7

operation

THRUST_ADJUST

parameters

{ "delta_v": 9.5 }

target

thr-x

grant_id

G1

Adjudication takes a few seconds in the browser. This is a demo surface, not the production path.
Flight strip[ DENY ]
ACTORrover-7
ACTIONTHRUST_ADJUST
RISKHIGH
POLICYG1:G-catalog
2026-08-06T23:58:27.210Zrcpt 2c9f43...51d6

Recorded from kernel.execlayer.io

Verify it yourself

The evidence outlives the demo.

A live rover decision returns a signed receipt; any captured fallback is labeled in the demo. Carry a receipt into the Auditor and your browser checks the structure, the decision hash, and the ED25519 signature itself. No trust in ExecLayer required.

The full surface

Compose your own intents, walk the receipt lineage, and audit proofs on the kernel itself.

Open kernel.execlayer.io

Score your own governance

Use the AGB self-assessment to score six runtime governance dimensions against the published rubric, entirely in your browser.

Run the assessment
How it fits into your organization

Who owns it, and how it connects.

You keep your AI and existing systems. We start with one workflow, configure checks around your approved rules, and connect them where the AI tries to act. Authorized requests can proceed. Other requests stop, with a record explaining the decision.

  1. 01 · Set the rules

    Business and control owners

    Your Robotics Program Lead or Operations Director defines permitted actions and operating limits, supported by safety engineers.

  2. 02 · Connect the workflow

    Integration specialists

    Your robotics and controls engineers connect the command workflow.

  3. 03 · Check before action

    The connected execution path

    Before a command reaches the connected machine controller. The integration must prevent the agent from going around the check.

What does a first implementation involve?

We scope one workflow, translate supported rules into a versioned, validated, signed policy package, and connect an adapter that supplies trusted facts such as identity, recipient, and approval status. We then test allowed requests, blocked requests, and attempts to bypass the check before enabling execution.

One maintained kernel can support different policy packages and system adapters. A JSON file alone is not a complete deployment. We confirm rule support and integration requirements for your systems during scoping; additional implementation may be needed.

These are typical ownership patterns; responsibilities vary by organization.

Show me how this fits our workflow