CASE STUDY · PUBLIC

operant

The Rust agent runtime under the flagship kernel: typed tools, memory, scheduling, and a plugin surface in one consolidated workspace, with the portfolio's strongest executed gate.

Status ruling active development

Problem

Agent runtimes drift into bloat and mystery: untyped tool surfaces, memory bolted on, no kernel discipline. operant is the intended realization of the harness as a typed, layered substrate.

Build

  • Seven workspace crates: core, os, config, harness, plugins, CLI, and the API surface.
  • Memory infrastructure whose MCP server is the leanest in the fleet (7 tools, about 121 tokens per tool).
  • Web access integration and cron automations with hooks for sub-agents.

Outcome

  • The gate ran 7,168 tests with zero failures across 72 binaries at commit ca33d4c, measured on a clean export of that commit. The --no-fail-fast flag is part of the method: a plain run stops at the first failing binary and reports a fraction of the suite.
  • Honest status, per the operator's ruling: the runtime is in active development. The green gate is not a production-readiness claim, and the study does not dress it up as one. The October consolidation that reshaped the workspace is recorded in reconciliations R9, R10 and R21.

Provenance

Gate, executed7,168 passed, 0 failed, 24 ignoredcargo test --workspace --no-fail-fast at ca33d4c, 2026-10-20
Crates7workspace manifest, 2026-10-26
LOC390,981 under crates/ (+4,381 vendored)recorded line-count pipeline at 5a116305
Test attributes, static4,959 (upper bound)static attribute count at 5a116305; the executed figure is the row above

Reproduce

Apache-2.0. Clone the repo and run `cargo test --workspace --no-fail-fast` at the pinned commit: the runner output re-derives the headline. The static count is an upper bound and is labelled as one.

Published documents

From the documentation

  • A 7-crate Rust workspace is the whole reduction from the 18-crate predecessor state, and the operational story is the consolidation itself: fewer crates, one workspace gate, one release train.

    cargo workspace and release history, described-not-linked

  • The runtime gate is a workspace test plus a strict lint that reports zero errors and zero warnings, so a green run is a build claim rather than a suite claim.

    repository gate scripts, described-not-linked

  • The consolidation kept the agentic harness surface intact while the org layer retired to the kernel, which is why operant is the runtime and holon is the kernel rather than two kernels.

    disposition records, described-not-linked

  • Static counts are labelled as upper bounds and runtime figures are labelled with their commit, so the published numbers state which class they are instead of blending the two.

    measurement captions, described-not-linked