FIGURE · holon-tests
holon gate, executed
509 OK at ec6f5ba (374 at 475127c)
- How it was taken
- ./scripts/gate.sh: the full suite plus a strict lint that must report zero errors and zero warnings. Both pinned commits ran on clean exports.
- Measured
- 2026-10-21
- Reproducible
- Yes: clone and re-derive.
What the number is made of
The first pinned commit
475127c: 374 tests OK, 0 errors, 0 warnings.
Open the reference →The second pinned commit
ec6f5ba: 509 tests OK after 38 commits, 25 touching tests/. Both figures are kept because both are true of their commits.
Open the reference →The flagship framing
A governed kernel over a measured runtime: holon is the kernel, operant is the runtime, and the two gates are one sentence.
The register entry →The governance tooling beside it
project-genome, the self-checking repository governance skill: 35 of 35 cases ok.
The register entry →
How to check it
Green at both pinned commits with no caveat: 374 tests OK at 475127c, 509 at ec6f5ba, lint clean both times. The repository was published public on 2026-10-25 at commit 4d682ea, where the full suite runs 704 tests with one failure: a self-validating assertion inside the in-flight isolation workstream, recorded by the source ledger and deliberately not cited. Clone the repository and run the gate to see the current state; the pinned figures describe their commits.
Open the artifactWhere this site cites it
- case study holon
The repository's own documents
The documents the figures were measured from, published in full rather than summarised.