the kernel · under development · Wave 7
The governance kernel.
Backlog in. Verified, deployable code out. Machines do the work, and the system stays accountable.
every decision, replayable
01the loop
One governed loop, end to end.
A backlog becomes verified code through six governed steps. Every step writes to the ledger, and every decision is replayable from frozen inputs.
Atoms
Work is broken into atoms: the smallest reviewable, traceable, estimable unit, each carrying its own proof obligations.
To the fleet
Each atom is assigned to a machine or a person on purpose, dispatched to isolated git worktrees under pooled accounts.
Family-diverse panels
A mixture-of-agents panel from different model families reviews the change, and adversarially verifies each finding.
Warn, route, block
A deterministic gate admits, routes for human judgment, or blocks, on evidence and calibrated policy. Never on a vibe.
Only what passes
Verified changes merge; a named human overrides in proportion to the risk, and the reason is first-class data.
On the record
Every decision, verdict, block, and override is written to an append-only, hash-chained log that replays end to end.
02what makes it a kernel
Not a review bot. A governance substrate.
Four properties competitors do not have, because copying them means having measured, and having built for accountability from the first commit.
Heterogeneous agents, Claude Code, Codex, Cursor, Gemini, run the backlog in parallel under isolated worktrees, account pooling, and containment validation. Tool-agnostic by design.
PARALLEL · governed end to endReviewers from different model families check each other adversarially before anything merges. Diversity catches the failure modes a single family shares and cannot see.
ADVERSARIAL · family-diverseNo stochastic output gates a state change. Verdicts recompute from frozen inputs with zero new model calls, hash-chained and replayable. Stochastic in, deterministic out.
REPLAYABLE · evidence, not vibesA tamper-evident, hash-chained governance record: length-prefixed SHA-256, anti-fork concurrency control, multi-tenant isolation via row-level security, fail-closed.
HASH-CHAINED · tenant-isolated03under development
What we hold, and what we are building.
All of it is under active development, implemented and refined against the kernel's own construction. This is the high-level shape: the decisions and the guarantees, not the mechanism.
- No stochastic output gates a merge. Verdicts recompute from frozen inputs.
- Every state change lands on an append-only, hash-chained ledger. No exceptions.
- Reviewers span model families. The failure one family shares, another one catches.
- The math layer is arithmetic-only. No hidden model sits inside the scoring.
named at a high level. the mechanism stays in the repo.
04the kernel, running
One command surface. Governed underneath.
The same governed loop drives a CLI, a REST API, and a TUI. Dispatch a backlog, request a family-diverse review, verify by replay, tail the ledger.
05the proof
Built by the method it embodies.
We did not learn governed delivery on a customer codebase. We built the governance kernel this way, on the hardest and most measurable domain in software: its own construction. It is in build, and the receipt is public.
It rests on a formal foundation, The Fractal Org, a general theory of the autonomous enterprise, with formal verification on the multi-agent coordination path. Its sibling instrument, CodeSentinel, audits the code it produces. The method is the product, and the product is the proof.
Read the full receipt →Autonomy you can audit.
See the kernel end to end, ledger included, under NDA. Or start with a governed audit of your own codebase.
Machines do the work. A named human stays accountable.