VERA-K — EXECUTION VERIFICATION KERNEL
Every decision, chained.
Before an agent acts, VERA-K rewrites its plan as a formal contract and checks it against policy and state. Only a verified plan receives a one-time execution token. Every decision — admitted or denied — is written to a ledger that hides nothing.
Measured — kernel audit, 2026-07-19
HOW IT DECIDES
An action that cannot be verified does not run.
Every planned action is rewritten as a formal contract — preconditions, postconditions, forbidden states, resource limits, a recovery path. The contract is checked against live policy and state before anything runs.
A passed check mints a single-use execution token bound to the policy epoch and the state hash. Tokens expire in 60 seconds. A policy change revokes every open token at once.
A failed check returns a minimal counterexample — the smallest set of constraints that cannot hold together — so the plan comes back corrected, not merely refused.
Proofs are cached as a dependency graph. When policy or state changes, only the affected nodes are re-checked — measured 12.7 times faster than full re-verification.
THE LEDGER, OPEN
Every VERA-K decision is appended to a hash-chained ledger. This is a build-time snapshot of that chain — counts, timestamps, and integrity only. Raw paths, reasons, and plan identifiers never leave the kernel host.
Concurrent-writer forks detected
2 — #1,107 · two appends 3 ms apart
A fork is the signature of two kernel processes appending at the same moment. The ledger detects it — and publishes it. Hiding nothing includes its own anomalies.
Static snapshot, regenerated at build time. Numbers above describe this window only.
VERA-K is the kernel beneath AGEIUM's agent work — the same discipline we bring to every system we design.