Every claim about speed is a recorded measurement

Every externally callable operation is timed directly, over MCP and over HTTP, the denominator is generated from the registry, and a regression against the accepted baseline fails the check.

status

stable

exposed through

• ✓cli
• ✓api
• ✓mcp
• ✓cockpit
• ✓docs

area

verification

cost

What it does

majordomus bench times every operation through the real transports and reports the slowest first; bench coverage --check refuses a required target nobody covers; bench --check compares a run with this platform's baseline under the policy's thresholds; bench baseline update records a reviewable, tracked baseline and refuses a dirty tree. The executor's counters say whether an execution was answered from the cache, so a claim about work done is a count rather than a clock.

What it does not do

A baseline belongs to the machine that measured it; a value from one platform says nothing about another, and no number in prose is trusted over the file that recorded it.

The capabilities behind it

The capability modules of the executable this feature names, each with the capabilities it composes. The command line, the HTTP route, the MCP tool and the reference beside every row are projections of one declaration, not four registrations.

The commands that run it

• majordomus bench inspect

  Time every public command of the registry, cold and warm, and compare with the baseline.

What it answers

Operational moments from the Why catalogue that name one of this feature's mechanisms. Nothing here was assigned: a moment appears because it names a rule, a command, a capability or a claim this feature also names.

• →asked what the workers did last night and had only transcripts to grep
• →shipped an interface change whose contract document still described the old one
• →pasted a command from the documentation and watched it fail
• →had a green pipeline over generated files that no longer matched their sources
• →looked at the bill and could not say which of it produced anything
• →could not reproduce a result because nothing recorded the state it came from

The rules that hold it

• advisoryA performance claim carries its measurementproject.performance-evidence
• blockingNo endpoint of the Rust executable without a benchmark, and no number without evidenceproject.rust-benchmark-coverage
• advisoryEvery public command is benchmarkable from the registryproject.benchmarkable-commands
• blockingA request never rebuilds canonical state, and a cache is never trusted without an equivalence testproject.rust-hot-path
• advisoryA command reads each canonical file at most onceproject.hot-path-reads-once
• advisoryDerived state is computed once per state versionproject.derived-once

What is guaranteed

• guaranteed Every externally callable operation of the Rust executable is a benchmark target with a denominator generated from the registry, and a missing case fails the structural check
• guaranteed After startup, no MCP or HTTP request of the Rust executable scans the repository, builds the index or the registry, derives a schema or builds a projection, and perf.counters proves it
• guaranteed A cached capability of the Rust executable answers the same value uncached, cold and warm, a hit runs no handler, errors and commands are never cached, and the key carries the registry fingerprint
• guaranteed The paths of the Rust executable that scale with the repository carry criterion benchmarks that build on every push, and every executable capability declares its benchmark policy, required or waived for a typed reason
• guaranteed Every gate the Rust executable must pass is one script, scripts/rust-check, and CI runs that script on every change that can reach the crate
• guaranteed Line coverage of the Rust crate is measured on every change that can affect the crate and on every push to master, and the build fails under the floor in scripts/rust-coverage-threshold, one integer read by CI, by scripts/rust-check and by just coverage

Executable use cases

• performanceProve the tool is fast, not assume it, and refuse a regression