CASE STUDY · PUBLIC
holon
The agentic-OS kernel and the portfolio's flagship: persistent AI employees organised into departments under a ratified charter, with a gate that proves the kernel green end to end.
Status ruling active development
Problem
Agent frameworks answer how agents compose, not how a self-modifying system stays trustworthy while it composes. The operation needed the layer beneath the framework: a kernel whose governance is executable, not aspirational.
Build
- A gate that runs the full suite plus a strict lint that must report zero errors and zero warnings: governance the repository enforces on itself.
- Departments and charters instead of a flat agent pool: each employee contract declares its function, lanes and state.
- project-genome governance tooling beside it, so every repository the kernel touches carries owned document roles and mutability classes.
Outcome
- The gate is green with no caveat at two pinned commits: 374 tests OK at 475127c, 509 at ec6f5ba, lint clean both times. The repository went public 2026-10-25; at the publish commit the in-flight isolation workstream carries one failing self-validation test, recorded by the ledger and deliberately not cited.
- The flagship sentence, per the operator's own ruling: a governed kernel over a measured runtime. holon is the kernel; operant, at 7,168 passing tests, is the runtime under it.
Provenance
| Gate, first pinned commit | 374 OK, 0 errors, 0 warnings | ./scripts/gate.sh at 475127c, 2026-10-20 |
|---|---|---|
| Gate, second pinned commit | 509 OK, 0 errors, 0 warnings | ./scripts/gate.sh at ec6f5ba, 2026-10-21 |
| The governance tooling beside it | 35 / 35 self-check cases | test_genome.py at 3a2873a, 2026-10-25 |
Reproduce
Clone the repository and run ./scripts/gate.sh: the pinned figures describe their commits, and the runner output re-derives them. The strict lint is part of the gate, so a passing run is suite plus lint, not suite alone.
https://github.com/ishan-parihar/holon
Published documents
- Architecture The kernel shape: the instance, its databases, and what may not touch what.
- Contract The interface the kernel guarantees, in one page.
- Decisions What a decision record on this kernel is: immutable once numbered, superseded by name rather than edited.
- Intent What the project is for, stated once so every later decision can cite it.
From the documentation
The kernel runs as an organization, not a task queue: a human Chair sets the charter, a CEO leads departments, and each employee keeps an identity, roles, a memory and a record so knowledge accumulates instead of evaporating.
INTENT.md at 1881362 (2026-10-27)
The organization diagram in the intent document is the whole governance model in nine lines, which is why the study can claim executable governance: what the kernel keeps is written once, in a document that ships with it.
INTENT.md at 1881362 (2026-10-27)
The harness contract is a numbered protocol (a run, result envelopes, drivers, leases, staleness, identity, messages, adapters, the read API, policy and refusals, usage, the supervisor protocol, event triggers), which is the opposite of an informal prompt sketch.
CONTRACT.md at 1881362 (2026-10-27)
Schemas are referenced as a published directory rather than described in prose, so the contract points at a machine-checkable artefact instead of asserting one.
CONTRACT.md at 1881362 (2026-10-27)
The architecture document covers the kernel shape and the databases it owns, so the boundary between what the kernel is responsible for and what it is not is written down.
ARCHITECTURE.md at 1881362 (2026-10-27)