Repository navigation
affected-set: record the fenced REAL-fix follow-on (behind resolver-B #6155) - #6170
Merged
Merged
Conversation
…solver-B #6155) #6105 (runtime provenance ingest) was closed as not-landable: a floor-repair scout measured it as work-neutral theater — pruning INCREASES resolve+typecheck (PRESENT 6/28/3885ms vs run-all 1/27/2042ms) and only saves the witness EVAL, because the node-frontier skip fires AFTER the witness-entry closure is resolved and floor_runner resolves its closure twice. Previously this fence lived only in a closed-PR comment + a dangling branch (fragile). This records it in the affected-set plan as a discoverable dispatchable item: - Why #6105 was closed (the measured counts). - Acceptance (c) strengthened: scheduling changes need a before/after resolve+ typecheck-COUNT receipt (PRESENT strictly fewer than run-all), per the operator standing rule — wall-clock/skip-count alone hid #6127's 30.9x regression. - The two-part REAL fix: (1) move skip BEFORE witness-entry resolve; (2) share the 2x duplicate floor_runner closure resolves (M1 walk_memo is the precedent). - Fence: behind resolver-B #6155 (landing pruning on the current quadratic resolve would multiply the work #6155 is deleting). Branch session/quick-carp-343 preserved as harvest. Doc-only. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
What
Durably captures the affected-set REAL fix as a discoverable, dispatchable item in
docs/plans/affected-set-precompute-pruning.md, so it survives lane wind-down instead of living only in a closed-PR comment + a dangling branch.Context
PR #6105 (
Provenance ingest at CI floor runtime) was closed as not-landable. A floor-repair scout measured its overlay path by execution on thepa_ingestsingle-witness fixture:Pruning as built is work-neutral theater — it increases resolve+typecheck and only saves the witness EVAL, because the node-frontier skip fires after the witness-entry closure is resolved and
floor_runnerresolves its closure twice. The #6127 width-1 shard trap in miniature.The recorded follow-on
session/quick-carp-343preserved as harvest.floor_runnerclosure resolves (M1walk_memois the precedent).Doc-only; no code/
.dag/gate surface. Revert-trivial.🤖 Generated with Claude Code