FIGURE · operant-loc
operant LOC
390,981 under crates/ (+4,381 under vendor/)
- How it was taken
- Raw line count over .rs files at checkout 5a116305. Reproduce with: git archive 5a116305 crates/ | tar -x -C /tmp && find /tmp/crates -name "*.rs" | xargs wc -l; the vendored tree is the same pipeline over vendor/. No other exclusion is applied: target/ is not tracked, so the archive cannot contain it.
- Measured
- 2026-10-26
- Reproducible
- Yes: clone and re-derive.
What the number is made of
The counted tree, openable
Every .rs file under crates/ at the pinned commit, the same files the visitor can open one by one.
Open the reference →Why vendored is separate
vendor/ carries 4,381 lines of dependency source, counted by the same pipeline and printed as its own number, never summed into the headline.
The register entry →The executed figure this code carries
The gate ran 7,168 tests with zero failures at commit ca33d4c.
The register entry →
How to check it
Run the pipeline in the method line: it returns 390,981 for crates/ and 4,381 for vendor/. The prior first-party figure (388,828) did not re-derive from its own description and is corrected in R21; the vendored figure was exact and stands.
Open the artifactThis figure's history
- R11
581,190 (539,435 Rust), raw including vendored files → 388,828 first-party Rust, plus 4,381 vendored printed separately
The method improved rather than the code shrinking gracefully: the new count separates first-party from vendored source instead of summing them. The September figure described the pre-consolidation tree with both summed.
- R21
388,828 first-party Rust, plus 4,381 vendored printed separately → 390,981 lines under crates/, plus 4,381 under vendor/, both counted by one recorded pipeline
The prior first-party figure did not re-derive from its own description: the method under-specified the pipeline, and no recorded command returns 388,828. The vendored figure was exact and stands. The row now names the find pipeline, and the figure is what the pipeline returns.
Where this site cites it
- case study operant
- essay Ideal tooling infrastructure: choosing and building tools
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.