Repository navigation
Deduplicate recording proofs and clarify the memoryless invocation law - #64
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.
The probabilistic-automaton and program-attachment proofs repeated the recording invariant's support argument, and
replyLawnamed both an automaton step and a program invocation. Both proofs now reuserecording_reachabledirectly and sharerecording_init_reachable. The program's law explicitly names its memoryless inside replies; its definition and the public attachment statements keep their existing mathematical meaning.Program.replyLawProgram.memorylessReplyLawProgram.replyLaw_inlProgram.memorylessReplyLaw_inlProgram.replyLaw_succ_inrProgram.memorylessReplyLaw_succ_inrAll repository consumers and documentation links are updated. The recursive reply law and the recording invariant are explained beside their definitions/proofs. Claude reviewed the comments with only file-reading/editing tools, with no shell, Git, external tools or hooks. The coordinator checked the resulting diff.
Validation: focused builds through PRG length extension and the systems axiom checks, standard Mathlib lint on every changed Lean file, the affected-module axiom audit, source checks and
git diff --check. Classical openings in the ideal-system definitions were narrowed to their definitions to satisfy the standard linter.Fixes #31.