FIGURE · operant-crates
operant crates
7
- How it was taken
- Member count in the Cargo.toml [workspace] members list.
- Measured
- 2026-10-25
- Reproducible
- Yes: clone and re-derive.
What the number is made of
The manifest, openable
The [workspace] members array at the repository root is the method itself.
Open the reference →operant-core
The kernel layer: typed tool dispatch and the runtime primitives.
Open the reference →operant-harness
The agent harness layer: the loop, context allocation, permission surfaces.
Open the reference →operant-plugins
The plugin surface: web access integration and the cron automations with sub-agent hooks.
Open the reference →operant-os / config / cli / api
The platform, configuration, CLI and API crates completing the seven.
Open the reference →
How to check it
The manifest lists them. The September count said 18. See reconciliation R9.
Open the artifactThis figure's history
- R9
18 → 7
The workspace consolidated during the October tooling-surface execution (the checkout this register measured is 5a116305, 2026-10-25). The manifest is the method for both readings; the September count and this one describe different trees.
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.