Repository navigation
Floor: enrolment margin in same-run host-calibrated CPU ms - #13352
Merged
Merged
Conversation
The enrolment margin compared raw CPU readings to a fixed budget, so same-step claims flipped red/green with runner speed (#13168). Each run now measures the source-fixed calibration specimen, derives one host-speed factor against the pinned rate, and rescales every enrolment reading by it before the margin, dead band and roster floors are consulted. Raw ms stay reported. A missing, censored, moved or out-of-range specimen refuses the run, typed; there is no default factor. Records sharp-raven-357's narrow overturn of the per-runner ban in v2.workflow.floor_eval_step_calibration, admits the specimen to the required gate, and adds model and seed controls. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…est of three specimen replicates Review (sharp-raven-357): once readings are normalised to calibration-runner speed, the p90 cross-runner envelope double-counts host variance. Replace it with the residual same-host spread (1130 permille, worst of three measured specimen samples) applied to the two independent readings (claim and specimen): 1276 permille, so the margin is 391 ms, dead-band floor 306 ms, roster floor 391 ms, all derived. Measured specimen spread on one runner: 75 ms first touch, then 43-47 ms. A slow specimen reading loosens the gate, so the run now measures three replicates (distinct accumulator seeds, identical steps) and takes the fastest; any refusing replicate refuses the run. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
… the wildcard) Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
… envelope paragraph (review 76320) Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Contributor
Author
|
Addressed review 76320 in 4d3af90:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Node
adhoc-c9504740-637. Decision: sharp-raven-357, with the operator's go-ahead (option A of escalation msg_decc213d).Problem
The enrolment margin compared a raw CPU reading to a fixed 302 ms budget. On #13168, fifteen parse claims refused with eval steps identical to their green run, while a peer with the same step count went 240 → 426 ms on a runner ~1.75x slower. The verdict depended on which runner the run drew.
Change
test.claim.floor_eval_step_calibration_specimen_test(its work is fixed in source, 55,011 eval steps) on the same runner.factor = specimen_cpu × pinned_rate × 1000 / specimen_steps. The reference is derived from the existing pin; it adds no new figure.raw × 1000 / factorbefore the margin, dead-band floor or roster floor is consulted. The same factor applies to every claim, with no per-claim or per-tier adjustment. Raw ms are still printed (raw_cpu_ms=… host_speed_factor_permille=…).cause=HostSpeedCalibrationRefused standing=…. There is no default factor.v2.workflow.floor_eval_step_calibration, next to fierce-lark-661's ban: dated, scoped to this one consumer, and with its reasons. The step budgets are not rescaled.required_gate_authored_modules. It was outside the gate, so no run measured it.gunbc.host_speed_calibration_seed_growth.Controls
v2.test.floor_enrolment_margin: same claim gets the same verdict at two synthetic runner speeds, and the raw readings are shown to disagree; a genuinely expensive native claim still refuses at both speeds; missing, censored, withheld, moved and out-of-range specimens all refuse.the_same_claim_gets_the_same_enrolment_verdict_at_two_runner_speedsandthe_host_speed_calibration_refuses_without_an_exact_plausible_specimen_readingpass remotely (with the existing dead-band test).Receipt (PR floor run 37263410184)
[enrolment-margin] host_speed_calibration specimen=…calibration_specimen_performs_its_declared_work standing=calibrated specimen_cpu_ms=84 factor_permille=1103. The specimen's floor eval steps match the pin exactly (any difference would have refusedhost_speed_specimen_moved). This PR's own new controls were enrolled and judged through the factor (raw_cpu_ms=… host_speed_factor_permille=1103). floor / generated / emit-build / witnesses are all green.Open, for the reviewer
v2.test.floor_enrolment_marginsits outside the required gate's executed population, so its controls run when enrolled (as on this PR) or when invoked by hand; this change doesn't touch that admission.🤖 Generated with Claude Code
Note: with the margin at 391 ms, some existing dead-band and typed cost-debt rows become deletable (readings ≤ 391 ms). That doesn't break anything: those grounds are judged only when an identity is newly enrolled. Pruning them is a follow-up.