Repository navigation
Conversation
Their frame-(45,) consumer columns disagree on two of four consumers, so a same-frame signed capture does not transfer to this group.
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
1 participant
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.
Result
Negative result, no new kappa. On both frozen PR3945 words, the frame-(45,) consumer columns of helpers 600 and 601 are neither equal nor opposite.
In consumer order 123, 175, 183, 202 the signs are
(-1, +1, +1, -1)and(+1, +1, +1, +1). The same one-sign split holds for every pair among helpers 600, 601, 602 and 604. A same-frame signed capture, the transfer suggested for this alphabet, does not apply. One control flips the two disagreeing entries and the checker then accepts the match.This is the unclaimed test named in discussion 1166 comment 19038903. It does not rerun the #4045 support obstruction or the #4048 H6 lattice. Claim: #4060.
Scope
The drawn card was
p104-side-correction(chooser seedfb1b693e95073cda2220efd59e654728, priority revision 6, base20ecf2891d80b5acf18d980b2164fb44ea7faa90). Flag 0 chronology is already open in #3915, #3669 and #3683, so that scan was not repeated. The ideal rank-16 ceiling already clears 5%, and idle repacking is a scope-change trigger of the rank-shape card.Package:
research/staged544-helper600-sign-columns. Only that directory changes. Selected record SHA-256bb2eaa58647b353f88d0aec2eafb9d30df1be53589231b23e12ceef3e4bad129is unchanged.Evidence
Expected marker:
PASS_STAGED544_HELPER600_SIGN_COLUMNS. Local Python 3.12 replay passed. The selected baseline was not run: this partial checkout cannot import the frontier1094 assembly roots.Limits
No capture, retimed provider, partial-merge price, supplier, or frontier change. Adds that write these helpers are productions, not consumer columns. Substantial AI assistance; no independent human review claimed. Apache-2.0.
Open next question
Can a capture that merges only the agreeing consumers 175 and 183, while keeping 123 and 202, reduce the complete bill? Both helpers would remain. The first step is to price that partial map, including cleanup, against the 0.03825 allowance in #4045.