Performance Evidence Policy

Relevant source files

axiomos separates performance claims into method, current evidence, and history. A number counts as current release evidence only if its campaign records all of:

Requirement	Purpose
Exact source commit	Ties the number to code
Pinned toolchain	Rules out compiler drift
Exact command	Reproducibility
Host or hardware boundary	Scope of the claim
Tracked raw output	Numbers must be present in the raw log
SHA-256 of raw log and measured executable or image	Identifies the artifact that produced the result

Each campaign lives under docs/performance/evidence/COMMIT/ with a manifest.toml and the raw captures.

No QEMU, Raspberry Pi, Linux-comparison, boot-time, interrupt-latency, WCET, or comparative-speed headline is current release evidence until it is rerun under this contract. A developer-host campaign does not establish a hardware latency objective.

Provenance gate


python3 -B scripts/verify/benchmark-provenance.py

The checker (also run as benchmark-provenance-static in the audit gate) verifies the raw-log hash, confirms the Cargo-reported executable path and every declared result marker appear in the log, validates source-input hashes against the recorded Git commit, and requires a well-formed executable hash. It does not claim byte-identical binaries across different hosts or linkers.

Evidence tiers

Adding a campaign

Start from a clean, committed tree with the pinned toolchain.
Store raw output and manifest.toml under docs/performance/evidence/COMMIT/.
Record the Cargo-reported executable, its SHA-256, host/hardware controls, exact command, and hashes of benchmark source, Cargo.lock and rust-toolchain.toml at that commit.
Add only results present in the raw output. Hardware campaigns must also retain UART and logic-analyzer captures and deployed-image hashes.
Run the benchmark-provenance and documentation-link checks.