Repository navigation
Derive finite-path Landauer bounds and move pure checks to Python - #227
Merged
Merged
Conversation
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.
Closes #88.
Derive the fep-050 heat/work bounds from normalized finite-path erasure laws, reverse support, local detailed balance and a reset marginal. The biased-prior bound gives the fair-bit corner; six constructive controls include a reversible equality case. The constitutive-law bridge keeps its explicit entropy-balance assumption and conditional meaning. The maturity disposition remains unchanged.
Validate the five current successor statements and exact current metadata before copied historical comparisons. Existing sealed review fixtures remain unchanged. Retain independent science, software, test-partition and native/publication observations.
Move 182 source-only cases into Python feedback. This marker-only transition preserves its 4,469 collected identities and every test function body; all 37 compiler functions in the audited files remain explicitly serial. Frozen/uncertain owners stay excluded. Use the active interpreter for the artifact-proof freshness check, and document packaging preparation before strict test collection.
Validation:
sorryand independently validated its source-bound receipt.The first local split run passed all executed tests but correctly failed its final integrity join when wheel building first created six packaging metadata files. That failed record is retained. Wheel metadata was prepared before a new collection and full execution; no source-drift waiver or relaxed acceptance was used.
Normal hosted PR and merged-main CI are still required. No release or tag is proposed. H3 export/refactor and broader Gaussian issue acceptance remain in their own scopes.
Integration update: normally merged paired main
0a3feec63b4561202d168548a14f66de70af2b8dinto this branch. The only conflict was the changelog; both entries are retained. All generated-owner freshness checks passed. Earlier local native/PDF receipts and original-head hosted artifacts remain scoped to their original checkpoints. Fresh full combined-head hosted qualification is required before main integration.Combined-head qualification completed at
4d7d1d6e00975a5c3859a814f9ab4172db3dd054: all 22 hosted contexts accepted (21 success, expected documentation skip). Independent retained-artifact audit verified all five ZIP digests, 4,001 accounted Python cases (3,982 passes and 19 permitted skips), every package coverage floor, 168 clean native topic results, the 2,060-declaration audit, and current source-bound 392-page PDF payload. This is PR-head acceptance; actual merged-main qualification remains separate.