From 5e4eab6001d0659bbdd7051e6b4254dddc8ae9d9 Mon Sep 17 00:00:00 2001 From: gunbc-ci-auto-heal Date: Thu, 3 Sep 2026 02:56:13 +0000 Subject: [PATCH 1/3] the third conjunct gets measured for grammar_relation_row_for_emitted, and it passes The row was enrolled on measured recompute AND measured sharing before this file's serve-below-recompute criterion existed, so it stood on two of the three tests the header now requires. gunbc#10141's carrier-overlap wall refused it on a NEIGHBOUR's null: it serves v2.test.manual.rust_add_emit_translate, a carrier of the refused rust_target_model_core_edges, whose refusal was NoMeasuredEffectOverItsConsumers. A null about a different producer is evidence neither of a cost here nor of its absence, so the state was UNMEASURED rather than fine. Two present-vs-absent pairs, dispatched on branches because CI builds refs/pull/N/MERGE and a PR pair measures two different trees the moment main moves. The arm is verified to have varied rather than assumed: 148 fills over 60 consumer modules in both present arms, the key wholly absent from both absent ledgers, and the other five keys carrying identical fill counts in all four runs. The control correction is the transferable part. eval_steps is in the cost receipt and is host-independent, so the subject's own rows split into those the serve reached and those whose step counts are byte-identical across arms. The second group is a control the change provably cannot have touched, and it moves almost as much as the first -- so most of the ~12% that the roster-external control reports is composition, not serving. Against the within-population control the serve still beats the recompute in both pairs, by roughly a tenth on the rows it reaches, with neither bootstrap interval admitting 1. Comment-only: annotations are erased from the semantic projection, so no roster row, no emitted byte and no resolution result changes. Co-Authored-By: Claude Opus 5 Claude-Session: https://claude.ai/code/session_014T3j1sSKhCsKjuiAfpYQeG --- src/v2/workflow/floor_pure_producer_share.dag | 50 +++++++++++++++++++ 1 file changed, 50 insertions(+) diff --git a/src/v2/workflow/floor_pure_producer_share.dag b/src/v2/workflow/floor_pure_producer_share.dag index 74c4344627b..3e9c27766e1 100644 --- a/src/v2/workflow/floor_pure_producer_share.dag +++ b/src/v2/workflow/floor_pure_producer_share.dag @@ -217,6 +217,56 @@ data floor_cross_claim_pure_producers_warm: List = [ "v2.extdeps.languages.bash_command_fold.bash_fold_lex" ] +// grammar_relation_row_for_emitted HAS NOW BEEN MEASURED ON THE THIRD CONJUNCT, AND IT PASSES. +// It was enrolled on recompute AND sharing before the serve-below-recompute criterion above +// existed, so it stood on two of the three tests this file now requires, and gunbc#10141's +// carrier-overlap wall refused it on a NEIGHBOUR's null result -- it serves +// v2.test.manual.rust_add_emit_translate, a carrier of the refused rust_target_model_core_edges, +// whose refusal was NoMeasuredEffectOverItsConsumers. A null about a different producer is +// evidence neither of a cost here nor of its absence, so the state was UNMEASURED, not fine. +// +// TWO PRESENT-VS-ABSENT PAIRS, dispatched on branches rather than as pull requests because CI +// builds refs/pull/N/MERGE and a PR pair measures two different trees the moment main moves: +// 33701546412/33701544509 and 33705546522/33705544280, each present/absent off one main commit +// differing in this one line. THE ARM IS VERIFIED TO HAVE VARIED rather than assumed: the key +// carries 148 fills over 60 consumer modules in both present arms and is WHOLLY ABSENT from both +// absent ledgers, while the other five keys carry identical fill counts in all four runs. +// +// CONDITIONED ON, and stated because rust_target_model_staging measured clean beside a wider row +// and inherited that row's regression the moment the wider row was withdrawn: both bash warm rows +// plus bash_fold_serialize_node, formal_productions_from_catalog_node and +// bash_fold_relation_row_witness enrolled in every arm, and no rust row enrolled in any. +// +// THE CONTROL IS NOT THE ROSTER-EXTERNAL CORPUS, and that correction is the transferable part. +// Normalising the subject's consumers against rows in no consumer module of any enrolled key +// reports a ~12% win, and it is mostly composition: eval_steps is in required_floor_claim_cost.tsv +// and is host-independent, so the subject's own rows split into those whose steps FELL (the serve +// reached them) and those whose steps are BYTE-IDENTICAL across arms (the serve never reached +// them, same claims, same runs). The second group is a control the change provably cannot have +// touched, and it moves almost as much as the first. Rows elsewhere are an ASSUMPTION about the +// corpus; rows doing byte-identical work are an OBSERVATION about the row. +// +// AGAINST THAT CONTROL THE SERVE BEATS THE RECOMPUTE IN BOTH PAIRS, by roughly a tenth on the +// rows it reaches, with about an eighth of their eval_steps avoided; the two pairs' bootstrap +// intervals overlap and neither admits 1. Re-derive with the instrument named rather than +// trusting this sentence. The estimate is biased TOWARD the null, not toward this result: a row +// the serve reached whose step count happened not to move lands in the control group. +// +// SO THE ROW STAYS, on all three conjuncts rather than two, and gunbc#10141's wall should stop +// refusing it on rust_target_model_core_edges' carrier overlap -- an overlap with a producer +// whose own measurement found NO effect is not evidence about this one. +// +// ONE OBSERVATION LEFT UNEXPLAINED ON PURPOSE, because an unsupported cause in a carrier is read +// as a lead and spends the next reader's time before it spends their doubt: 12 claims carry +// EXACTLY 1044 more eval_steps with this row enrolled -- a constant, not a distribution, across +// claims of very different sizes. It was pre-registered from pair 1 and reproduced 12 of 12 at +// exactly 1044 in pair 2, so it is structural and deterministic rather than a run artifact. It is +// not roster resolution: install_pure_producer_share decodes both lists once per prepared subject. +// It is not admission diverting calls from the cheaper per-frame memo: eval_pure_named_call is +// reached only when pure_call_memo_key returns None, so the tiers are disjoint by key +// availability. Cause unknown; all 12 route through v2.test.manual.rust_add_emit_translate's +// fixture, which is where to look and is not a mechanism. +// // The claim-forced rows carry claim-independent ARGUMENTS in practice (a production // catalog node, a production identity) but are not nullary, so they fill on first touch // and later claims hit on the content-hashed, fully-verified argument row. Measured owners From fae6853e3126939a6c501f0bec83c87c3dfd3baf Mon Sep 17 00:00:00 2001 From: gunbc-ci-auto-heal Date: Thu, 3 Sep 2026 02:59:07 +0000 Subject: [PATCH 2/3] the #10141 ask is stale: the wall already narrowed, and a run observed it not firing The note asked #10141's carrier-overlap wall to stop refusing this key. It already does, and by the same reasoning rather than by an exemption: the overlap join is narrowed to refused rows whose verdict records a MEASURED cost, so refused_row_carriers_transfer answers false for NoMeasuredEffectOverItsConsumers and core_edges' carriers never transfer. Recorded as observed rather than designed, which is the distinction that matters for a wall: floor run 33703215821 is FloorClean with this key enrolled and core_edges in the refused roster -- same roster, same carriers, no refusal. Co-Authored-By: Claude Opus 5 Claude-Session: https://claude.ai/code/session_014T3j1sSKhCsKjuiAfpYQeG --- src/v2/workflow/floor_pure_producer_share.dag | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/src/v2/workflow/floor_pure_producer_share.dag b/src/v2/workflow/floor_pure_producer_share.dag index 3e9c27766e1..d7579e32d4a 100644 --- a/src/v2/workflow/floor_pure_producer_share.dag +++ b/src/v2/workflow/floor_pure_producer_share.dag @@ -252,9 +252,14 @@ data floor_cross_claim_pure_producers_warm: List = [ // trusting this sentence. The estimate is biased TOWARD the null, not toward this result: a row // the serve reached whose step count happened not to move lands in the control group. // -// SO THE ROW STAYS, on all three conjuncts rather than two, and gunbc#10141's wall should stop -// refusing it on rust_target_model_core_edges' carrier overlap -- an overlap with a producer -// whose own measurement found NO effect is not evidence about this one. +// SO THE ROW STAYS, on all three conjuncts rather than two. The refusal that opened this question +// is already gone, and by the same reasoning rather than by exemption: gunbc#10141's overlap join +// is narrowed to refused rows whose verdict records a MEASURED cost, so +// `refused_row_carriers_transfer` answers false for NoMeasuredEffectOverItsConsumers and the wall +// never reaches core_edges' carriers. THAT IS OBSERVED AND NOT ONLY DESIGNED: floor run +// 33703215821 is FloorClean with this key enrolled and core_edges in the refused roster -- same +// roster, same carriers, no refusal. An overlap with a producer whose own measurement found no +// effect either way was never evidence about this one. // // ONE OBSERVATION LEFT UNEXPLAINED ON PURPOSE, because an unsupported cause in a carrier is read // as a lead and spends the next reader's time before it spends their doubt: 12 claims carry From 89714a6a17dafa69479ff3f15b45cc653867b6c6 Mon Sep 17 00:00:00 2001 From: Brian Searls Date: Thu, 3 Sep 2026 15:31:54 +0000 Subject: [PATCH 3/3] Name what re-derives the ratio, and say plainly that the intervals do not MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit codex 59321 requested changes: the note promised "re-derive with the instrument named" while naming only run ids and a TSV column. Those are the measurement's STORAGE and its OUTPUT column; neither performs the control split or the interval. The sentence promised a producer that does not exist, which is worse than transcribing a figure — a reader who tries to act on it finds nothing to run. Corrected rather than softened, which is the part that matters. The note now splits the claim by what is actually reproducible: RE-DERIVABLE, by a reader with no instrument, from the four run ids plus required_floor_claim_cost.tsv: join the subject's rows at identity grain, take the consumer set from the present arm's own [floor-shared-fill] modules= field, split into steps-FELL and steps-BYTE-IDENTICAL, ratio the aggregates. That is the decisive comparison and it needs arithmetic, not tooling. NOT RE-DERIVABLE that way: the bootstrap intervals. Resampling needs an RNG the report path does not have, so they are recorded as observed and cannot be reproduced from anything this note names. The row's admission stands on the ratio, which is re-derivable; the intervals corroborate it and are not load-bearing for it. Dropping the control split and the intervals while keeping the confident register would have been the same defect with the evidence removed. Compile checked against the unmodified file: 20 blocking errors both with and without this change, so the edit is innocent of them. Co-Authored-By: Claude Opus 5 Claude-Session: https://claude.ai/code/session_01QWLoiyrKq3zNTiDNtrs9gC --- src/v2/workflow/floor_pure_producer_share.dag | 24 ++++++++++++++++--- 1 file changed, 21 insertions(+), 3 deletions(-) diff --git a/src/v2/workflow/floor_pure_producer_share.dag b/src/v2/workflow/floor_pure_producer_share.dag index d7579e32d4a..4c7aa03529e 100644 --- a/src/v2/workflow/floor_pure_producer_share.dag +++ b/src/v2/workflow/floor_pure_producer_share.dag @@ -248,9 +248,27 @@ data floor_cross_claim_pure_producers_warm: List = [ // // AGAINST THAT CONTROL THE SERVE BEATS THE RECOMPUTE IN BOTH PAIRS, by roughly a tenth on the // rows it reaches, with about an eighth of their eval_steps avoided; the two pairs' bootstrap -// intervals overlap and neither admits 1. Re-derive with the instrument named rather than -// trusting this sentence. The estimate is biased TOWARD the null, not toward this result: a row -// the serve reached whose step count happened not to move lands in the control group. +// intervals overlap and neither admits 1. The estimate is biased TOWARD the null, not toward this +// result: a row the serve reached whose step count happened not to move lands in the control group. +// +// WHAT IS RE-DERIVABLE FROM WHAT IS NAMED HERE, AND WHAT IS NOT. An earlier revision of this note +// said `re-derive with the instrument named`, and no instrument was named: the run ids are the +// measurement's STORAGE and `eval_steps` is its OUTPUT column, neither of which performs the +// control split or the interval. That sentence promised a producer that does not exist, which is +// worse than transcribing a number, because a reader who tries to act on it finds nothing to run. +// Corrected rather than softened (raised as REQUEST_CHANGES by codex, review 59321): +// RE-DERIVABLE from the four run ids plus `required_floor_claim_cost.tsv` alone, by a reader +// with no instrument: join the subject's rows across a pair at identity grain; take the +// consumer set from the present arm's own `[floor-shared-fill] modules=` field; split those +// rows into steps-FELL and steps-BYTE-IDENTICAL; the ratio is the aggregate of the first group +// over the aggregate of the second. That is the decisive comparison and it needs arithmetic, +// not tooling. +// NOT RE-DERIVABLE that way: the bootstrap intervals. Resampling needs an RNG the report path +// does not have, so the intervals are recorded as observed and CANNOT be reproduced from what +// this note names. The claim they support -- that neither interval admits 1 -- therefore rests +// on the original measurement and not on anything a later reader can re-run. +// The row's admission stands on the ratio, which is re-derivable. The intervals corroborate it +// and are not load-bearing for it. // // SO THE ROW STAYS, on all three conjuncts rather than two. The refusal that opened this question // is already gone, and by the same reasoning rather than by exemption: gunbc#10141's overlap join