FIGURE · operant-tests
operant gate, executed
7,168 passed, 0 failed (runtime)
- How it was taken
- cargo test --workspace --no-fail-fast at commit ca33d4c, run on a clean export of that commit: 72 test binaries summed, 24 ignored.
- Measured
- 2026-10-20
- Reproducible
- Yes: clone and re-derive.
What the number is made of
The commit the gate ran at
ca33d4c on the public repository: the exact tree the 7,168 describes.
Open the reference →The fail-fast trap
A cargo test run without --no-fail-fast stops at the first failing binary, and every binary after it goes uncounted. The 4,663 reading was such an artifact. Sum every binary, or the number is a fraction.
The register entry →The status qualifier
Active development: the gate is green end to end and the runtime is not yet shippable as a production-grade platform. Both statements travel with the number.
The register entry →The static cousin
4,959 static test attributes at the pinned checkout, the labelled upper bound.
The register entry →
How to check it
Check out ca33d4c and run the same command: the runner output re-derives the figure. --no-fail-fast is required because a plain run stops at the first failing binary and reports a fraction of the suite; the source ledger recorded a 4,663 fail-fast artifact against the true 7,168. The workspace moves, so this figure describes the commit, not the repository. Status: the runtime is in active development by operator ruling, and the gate result is not a production-readiness claim.
Open the artifactWhere this site cites it
The repository's own documents
- AD-006 · Bodies are fenced from the supervisor
- AD-007 · An unfenced run is refused
- AD-023 · Plugins cannot replace a built-in
- AD-035 · One libclang resolver, and no dangling link
- AD-040 · The dashboard token only goes to its holder
- The operant mechanism library
- Organization — the Holon runtime, seats, and work graph
- Kernel — the persistent Python kernel + continual harness
- The agentic core — the ReAct loop
- The tool system
- Context management — eviction, decay, and the compaction ladder
- Gateway — the channel surface
- MCP — both sides of the protocol
- Plugins — WASM extensions
- Sub-agents — delegation, swarm, async
- Browser — the sourcehound engine
- Web tools — sourcehound intelligence
- TUI — the terminal interface
- Vision — the auxiliary-LLM contract
- Voice — TTS, STT, and the voice-mode state machine
- Verification — the harness that proves work
- Autonomous mode — the self-directed loop
- Background review — the post-turn learner
The documents the figures were measured from, published in full rather than summarised.