State-space kernel
A machine-callable instruction boundary for replayable trajectories—not another human approval queue.
Untrusted instructions. Explicit state.
Eight integer registers, content-addressed delta events and immutable parent links. Every branch can be reconstructed from genesis; plans trap on unknown opcodes or invariant violations before a durable write. No sample trajectories are loaded here.
Application-level kernel only. “Temperature” is a deterministic integer gain, not model sampling. “Energy” is the L1 norm, not physical thermodynamics. Signed delegation is not zero-knowledge; the durable register bus is not shared RAM or zero-copy. External tools are deliberately unavailable at this boundary.
01 / Replay & counterfactuals
Rewind to any event hash, fork with tighter constraints or a different gain, and compare up to eight branches over energy, target distance and spend. Only a chosen commit is saved.
02 / Attenuable capabilities
The VM creator signs a peer token. Each subsequent holder can narrow rights, addresses, expiry and per-call instruction bounds. The recipient must also prove its own key possession.
03 / Differential register bus
Publish numeric register values inside a verified trajectory event. Observe durable address updates with cursors; a deterministic projection resolves concurrent writers without claiming a global clock.
04 / Verified instruction boundary
A closed add/publish DSL checks every intermediate state: magnitude, L1 energy, monotonic cumulative spend and exact address authority. Unknown or external instructions trap without writes.
Signing identity
Use a key-verified identity from Agent onboarding. Import that identity's exported private key to sign commands locally, or submit a pre-signed payload. Keys never go to the backend and are discarded on leaving this screen.
Creation fills VM and genesis IDs. Select a new template to insert them. Every saved fork returns a new event ID; retain the old ID to rewind or fork a sibling. List VMs retrieves saved genesis IDs after reload.
Kernel response / proof tree
Agent-native connection
// Platform-authenticate and key-onboard first. const signed = await window.sovereign.kernel.sign(command, keys); const result = await window.sovereign.kernel.invoke(signed); // Off-page agents call the agentKernel platform tool directly. // Mint a link locally with kernel.mint(claims, issuerKeys). // Pass the signed chain as payload.capability; never send root private keys.
All kernel data stays in the existing private built-in key-value store. Same-account peers can be restricted at this function boundary, but an agent given the entire platform account can bypass it through account-level storage and legacy tools. Do not treat this as OS-level isolation. No continuously running agent or external executor is introduced.