mirror of
https://github.com/bdbrown4/peltier.io.git
synced 2026-11-07 10:58:28 +00:00
Claude
a78692bbb7
- bench-runner service mode (SPEC §3.1 mode c): a coordinated-omission- correct, open-loop, fixed-rate load generator; latency measured from the intended send time so queueing is counted, not hidden. Interleaved A/B of two server binaries, exact percentiles (bounded sample, no HDR bucketing error), bootstrap p50/p99 CIs via the existing ratio-CI machine. service-calibrate: A/A false-positive + injected latency- regression detection (calibration in progress). - targets/cjson/service.c: minimal single-threaded HTTP server wrapping the patched cJSON.c (trust-layer, outside the workspace allowlist); env-toggled per-request busy-wait for the injection calibration only. - report generator (crates/report bin): reads a ledger row + optional service-latency JSON, renders throughput→cores→dollars and/or latency percentiles, every figure with its CI, pricing source, and the methodology printed inline (SPEC §9); flags any non-accepted row so a rejected change never reads as a committed saving. - ledger::report_row; justfile service/service-calibrate/report. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01EcKPWQ3MQD4NdEHwar96u2
targets/
One directory per optimization target. This is the only agent-writable path in the repository (SPEC §10); everything else is trust layer.
Layout
targets/<name>/
target.toml # upstream repo URL, pinned commit, build & bench commands
equivalence.toml # optional; absent = byte-identical required (SPEC §3.2)
workspace/ # agent's checkout — patches land here via harness git-apply
Selection criteria (SPEC §6): CPU-bound (>70% user time), meaningful test suite, scriptable workload, permissive license, active but not hyper-optimized, builds cleanly in a container. Good hunting: codecs, parsers, serializers, image processing, compression, static-site generators, linters.
equivalence.toml
Default (no file) is byte-identical outputs. FP-producing targets may declare an explicit tolerance policy:
mode = "fp-tolerance"
abs = 1e-9 # max absolute difference per numeric value
rel = 1e-6 # max relative difference per numeric value
Declaring a tolerance covers output comparison only; FP flag changes still route to needs-human-review (SPEC §8).