Repository navigation
Carry frames through 534 native field swaps with exact dual replay (no new κ) - #4971
Mister-Meeseeks merged 2 commits into
Conversation
Independent review at head
|
| Check | Forward | Backward |
|---|---|---|
| Source word endpoint = specified shear (632 rows) | ✓ | ✓ |
| Constructed word endpoint = specified shear | ✓ | ✓ |
| Constructed rows = source rows, all 632 inputs incl. 408 helpers | ✓ | ✓ |
| Chronological frame validation of the constructed word | ✓ | ✓ |
Paid profile {1:2201, 2:412, 3:510, 4:127, 5:40, 8:8} unchanged |
✓ | ✓ |
| Weighted swaps / unequal incoming frames | 534 / 43 | 534 / 43 |
| ADD contacts | 16,265 → 14,663 (−3·534) | 16,273 → 14,671 (−3·534) |
| Climbs | 3,290 → 3,290 | 3,290 → 3,290 |
Notes. None blocks the PR.
- My warp handling necessarily implements the same formal word semantics: prepend the generator, or cancel an inverse at the front. The physical correctness of the native maps therefore remains an inherited premise, as the PR states.
- The climb count is unchanged even though 43 swaps start from unequal frames. Carrying frames removed the shared-frame requirement at the swaps, but every retained contact still forces the same transports. That matches the PR's conclusion that only a joint frame/schedule optimization could turn this representation into a saving.
This is an author-independent check. It is not maintainer acceptance, and κ is unchanged.
Reviewed by James Reed with substantial Anthropic Claude (Claude Code) assistance.
|
I independently checked this at #4971 There is a useful acceptance-boundary follow-up to jwr404's #4571 example. On this constructed word, changing only the adjacent inverse pair at events 3/4 on A focused next step is to call the actual-operator frame audit at the mutable-word entrance, before accepting a candidate's paid profile, alongside the existing chronological/endpoint checks. For a later Gaussian-gauge candidate, first bind its literal physical transition to its entry/exit charts; changing labels or a canonical G table alone is insufficient. #4841's pinned compiler specification already supplies a phase-exact compiler and a sufficient chronological chart-substitution theorem for specified literal Cliffords. Applying that mechanism to a changed source edge, retaining endpoint ownership and the full bill, remains separate work. This binary check establishes neither absolute phase nor recursive/caller admission, and the unchanged profile establishes no new κ. Exact-pinned reproduction; no source files changedFrom a clone of this repository, with the two exact objects available: git fetch --no-tags https://github.com/CrocSwap/integer-mult-bounds.git 0130b196145a43a7d305de41f49e56e8e8556378 a018bb0ce0fe571a401e3086ddeb3ea936107164
FRAME_REVIEW_DIR=$(mktemp -d)
export FRAME_REVIEW_DIR
git archive 0130b196145a43a7d305de41f49e56e8e8556378 research/native-frame-carrying-swaps | tar -x -C "$FRAME_REVIEW_DIR"
git archive a018bb0ce0fe571a401e3086ddeb3ea936107164 research/native-warp-event-binding/warp_frames.py | tar -x -C "$FRAME_REVIEW_DIR"
python3 -B - <<'PY'
from contextlib import redirect_stdout
from copy import deepcopy
from pathlib import Path
import io, os, runpy, sys
p = Path(os.environ['FRAME_REVIEW_DIR']) / 'research'
sys.path.insert(0, str(p / 'native-warp-event-binding'))
from warp_frames import audit
with redirect_stdout(io.StringIO()):
e = runpy.run_path(str(p / 'native-frame-carrying-swaps/verify.py'))
for direction, back in [('forward', False), ('backward', True)]:
word, _, _ = e['construct'](e['a']['programs'][direction])
valid = audit(e['c'], {direction: word})
if word[3] != ['warp', ['L', 273], -59, 0, 0] or word[4] != ['warp', ['L', 273], 59, 0, 0]:
raise ValueError('Pinned inverse-pair probe changed')
mutant = deepcopy(word)
mutant[3][4], mutant[4][3] = 1, 1
if e['replay'](mutant, back) != e['replay'](word, back):
raise ValueError('Expected identical normalized rows and paid profile')
try:
audit(e['c'], {direction: mutant})
except ValueError as error:
if 'G does not carry' not in str(error):
raise
print(direction, valid, 'mutant replay identical; guard rejects:', error)
else:
raise ValueError('Invalid operator-to-frame transport accepted')
PYThe retained source payload is SHA256 Credit to jwr404 for the original #4571 report, 1337isnot1337 for #4979, Dugongue for this frame-carrying construction, and the retained Cao Yifan/Cinna Davis/native source lineage. Independent check prepared with substantial OpenAI Codex assistance. |
|
DONE: published PR #4997, scientific/publication head Both registered Python 3.12.15 modes, rejection controls, committed-byte preflight and official export integrity pass. An isolated optimized export replay with Git absent from PATH passes and preserves all 19 export files. The compressed export at that exact head has SHA-256 This scoped claim is released. A larger coordinated change, split zero-edge region, scalar rewrite or changed native contract is a new question; the result does not exclude it. Source swaps and endpoint credit remain with Dugongue/#4971 and the retained Cao Yifan/Cinna Davis/native lineage. Substantial OpenAI Codex assistance, solo. Original prospective claim, retained verbatimCLAIM: exact constant-frame-region and adjacent-region analysis of #4971 at |
This adds a source-bound construction replacing 534 three-ADD weighted swaps per orientation with direct weighted field exchanges that carry their frame labels. Of these, 43 enter with unequal frames. The constructive algebraic proof and portable checker preserve all 632 independent-input rows, all 408 helpers, terminal frames and owned-cell cleanup in both orientations.
The recursive profile is unchanged:
{1:2201, 2:412, 3:510, 4:127, 5:40, 8:8}. No higher κ or physical tape speedup is claimed. The useful output is a concrete alternate word representation that removes forced common-frame contacts at these swaps, ready for joint frame/schedule optimization. The signed-swap identity itself is classical.Validation: registered Python 3.12 standard-library replay, normal and optimized; exact all-input endpoint comparison; sign and missing-frame-carry mutations; frozen-commit byte comparison and Git-free package replay. Shared retained row primitives are disclosed. Native physical-map correctness remains inherited; complete tape costs, multiplier/outer replay, Lean verification and hosted CI are not supplied. Source history is shallow; full-history ancestry auditing is not claimed. Retained source bytes are committed on this branch, so no pending PR fetch is needed for replay.
Credit Cao Yifan’s round-three source beyond #4610; Cinna Davis’s scalar/helper and #4440/#4470 lineage; Dugongue’s transported-frame and #4935/#4948 source binding; zxv, Jacob Alan Sussman and all retained NOTICE authors. This exchanges entire owner fields, unlike the coordinate-SWAP model discussed in #4950. Targeted previous overlap checks reached #4955; Discussion coverage remains incomplete and no exhaustive novelty claim is made.
Only
research/native-frame-carrying-swaps/changes. Canonical main was refreshed to b919568; relevant guidance, priorities and selected record were unchanged. Prepared by Dugongue with substantial OpenAI Codex assistance, one agent, no subagents. The selected frontier is unchanged. Open next questions and concrete first steps are in README.md and TASK.json.