Skip to content

Isolate explicit historical receipt adapters from P104 research - #4103

Draft
Clear1nsight wants to merge 1 commit into
CrocSwap:mainfrom
Clear1nsight:fix/historical-receipt-adapters-consolidation-20261019
Draft

Clear1nsight wants to merge 1 commit into
CrocSwap:mainfrom
Clear1nsight:fix/historical-receipt-adapters-consolidation-20261019

Conversation

@Clear1nsight

@Clear1nsight Clear1nsight commented Oct 19, 2026 •

Copy link
Copy Markdown
Contributor

Scope

Isolate nine historical source/credit receipt adapter files from #3577. Exact head: 161ce1b96288349fd67ecda1734d2f96850a2ee9.

Only the PR1 and PR636 receipt packages receive explicit historical-only wrappers, alongside one adapter, its regression suite and guide. Their README/SOURCES/VERIFY wrappers change deliberately; original manifest pins, verifier and evidence bytes are authenticated unchanged from the frozen commit. The default generic live-input contract is unchanged. PASS_HISTORICAL_RECEIPT_ONLY means original source/credit validation, never present-day ledger approval, closure, or theorem acceptance.

Bounded validation

Python 3.12.14 with warnings treated as errors: all 36 synthetic positive/rejection controls pass normally and all 36 pass under -O. The suite exercises Git-free/isolated materialization, hash and tree bindings, exact wrapper transforms, assertion enforcement and mutation guards. Both SOURCES wrapper comparisons preserve every original commit/blob/SHA256 pin. Changed Python compiles. The extraction review itself ran synthetic controls only; subsequent real upstream hosted replay is recorded below. No broad mathematical replay is claimed.

python3 -W error -B -m unittest discover -s tests -p test_research_historical_receipts.py -v
python3 -W error -B -O -m unittest discover -s tests -p test_research_historical_receipts.py -v

Consolidation and boundaries

Extracted byte-for-byte from the shared repair portion of #3577 at 3088a09c77fe5353218df861e34b0fe67dbf1b6b, independently based on canonical bb4bccbf42844d2801487450727c2f63e10d1d0f. The dedicated P112 parse repair remains in #3885; no duplicate P112 change is bundled here. The 11 P104 scientific files are absent. Existing research branch heads remain untouched until maintainers incorporate an effective shared base. No upstream merge, force-push, source repinning, selected-result update or scientific acceptance is proposed.

Current AGENTS.md, CONTRIBUTING.md, autoresearch.md and linked procedure were read. Delta-only intake refresh fetched canonical main but could not authenticate its gh CLI queue read; exact-head GitHub connector reads supplied targeted status instead. This is an explicit user-assigned repair, not a queue review or ledger acceptance decision.

Credit and limitations

Existing source authors, original repair attribution and Apache-2.0 notices are retained. Consolidation by Clear1nsight with substantial OpenAI assistance. Green checks validate only their stated coverage, not the multiplication theorem or current scientific approval. Draft pending independent substantive tooling review. Canonical main still contains the inherited P112 parse problem until #3885 is incorporated; an inherited zero-job fork failure must not be mistaken for failure of the scoped tests.

Original push CI status (2026-10-19 UTC)

The receipt branch has no registered research-package workflow triggered by push. Its only run is the inherited zero-job P112 parse failure, pending #3885. The 72 successful local synthetic controls are not a claim that either real receipt has passed hosted replay at this new head.

Upstream hosted replay and integration follow-up

Registered research packages run 39323750955 passes at this exact adapter head 161ce1b96288349fd67ecda1734d2f96850a2ee9. Both real receipts report PASS_HISTORICAL_RECEIPT_ONLY with live_inputs_validated=false; each job also passes the 36 adapter regression controls and the committed-input mutation gate. This supersedes the earlier pending-hosted status while preserving its historical push-only evidence.

The ledger-only proposal #4102 initially selected these receipts and failed their original live-input drift checks. Its new additive merge 1588e746871c5f1f197dbc034db2bfadbad0b646 includes this nine-file patch unchanged, alongside the original 11 ledger/reconciliation files. #4102 is now a 20-file combined integration proposal, while this PR retains the focused nine-file adapter review. Neither proposal has been merged upstream.

Preserve exact reviewed bytes from 3088a09 on current canonical main. Keep P112 repair in PR3885 and P104 research separate. No frozen scientific inputs or selected frontier changed.

Prepared by Clear1nsight with substantial OpenAI assistance.
Clear1nsight added a commit to Clear1nsight/integer-mult-bounds that referenced this pull request Oct 19, 2026
Integrate the exact nine-file adapter patch from PR CrocSwap#4103 at
161ce1b to repair the two
registered-package source-drift failures exposed by PR CrocSwap#4102 CI.

Retain original intake/ledger repairs byte-for-byte, authenticate frozen
receipt pins and evidence, and keep the generic live-input checker strict.
Historical-only replay does not validate current ledger/contributor state.

Preserve both published extraction commits without rewriting history.
No P112 workflow, P104 scientific input or selected-frontier changes.
Prepared by Clear1nsight with substantial OpenAI assistance.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant