claude
4ff85b94e5
Architect drift review (drift_found) resolved fix-path on all three items. [high] The sweep/walkforward/mc family builders and validate_and_register_axes read authored envelope files and put_blueprint'd them ungated — falsifying the C29 exemption's premise that the store is populated through gated intakes; all four sites now gate the root name before the family/axis build (placing the gate after the build produced a misleading unknown-axis error instead of the gate refusal — RED-verified), with an e2e pin on the synthetic sweep route. The decision was gate-the-routes, not weaken-the-prose: the exemption's premise is the invariant, not a wording choice. [medium] C24 now states the gate rule as the class it is (the op intake plus every CLI intake reading an authored envelope from a file; store read-back exempt, C29). [low] C23 reconciles names-as-debug-symbols with the render name's one operational role (trace-directory key — never compilation, identity, or execution semantics). Ratify: aura-bench cli_fixed_cost baseline re-pinned (run_line_fnv 6bb0d796f760d140 -> 9bdbc3acf7b2926a). The moved metric was caused by the #328 tidy (4474814), which switched single-run manifest defaults from wrapped to raw axis names after that cycle's bench rerun had already passed;bbac29dand this cycle's HEAD produce fingerprint-identical record lines (verified with both binaries on one scratch project), so this cycle only inherits the stale pin. All five surfaces fingerprint OK after the re-pin. refs #331, #328
aura-bench
Wall-clock benchmarks with committed baselines (issue #251, phase 1). Catches hot-path regressions the E2E suite structurally cannot see: every surface pins its inputs and asserts a determinism fingerprint, so a fast-but-wrong binary fails the bench instead of pinning a bogus baseline.
Running
cargo run --release -p aura-bench -- run # measure + compare, report-only
cargo run --release -p aura-bench -- run --surface engine_throughput
cargo run --release -p aura-bench -- pin # rewrite committed baselines
Debug builds refuse to measure (exit 2) — wall-clock numbers from a debug build measure the profile, not the code.
Surfaces
| surface | workload | metrics |
|---|---|---|
engine_throughput |
10M synthetic bars through an SMA-cross harness (library) | wall_s, bars_per_s |
ingest_throughput |
24 synthetic archive months x 20 fresh drains via the ingest window API (library) | wall_s, bars_per_s |
campaign_sweep |
8-cell sweep-only campaign, release aura binary on a scratch project |
wall_s, cpu_percent, peak_rss_mb |
campaign_heavy |
same cells; sweep → gate → walk-forward → 1000-resample bootstrap | wall_s, cpu_percent, peak_rss_mb |
cli_fixed_cost |
spawn floor (aura --help) + minimal data-only project run |
help_ms, run_ms |
Discipline
- Quiet box: the driver warns at 1-min loadavg > 2.0. Close heavy jobs first.
- 1 discarded warmup + 3 measured reps (median). Reps must agree on the fingerprint — cross-rep drift is reported as nondeterminism, not averaged.
- Baselines are per-host context (
hostblock inside each JSON): comparison on a different host prints an informational banner and stays report-only. - Timing drift NEVER fails the run (report-only phase, #251 cadence decision); a NOTICE line flags drift >= 10%. A fingerprint mismatch exits 1.
- Re-pin (
pin) deliberately, after an accepted behaviour or performance change; the baseline diff is reviewed like any other commit.
Deferred (follow-up on the tracker)
- Instruction-count backend (iai-callgrind) once valgrind is installed on the measuring host — slots in as a sibling backend without reshaping baselines.
- Native-crate project-load sub-cost (dylib SHA-256) — needs a build step in the scratch project.
- Thresholded failure, once recorded variance data justifies thresholds.