← The register

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

  1. The commit the gate ran at

    ca33d4c on the public repository: the exact tree the 7,168 describes.

    Open the reference →
  2. 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 →
  3. 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 →
  4. 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 artifact

Where this site cites it

The repository's own documents

The documents the figures were measured from, published in full rather than summarised.