Automate direct finite-symbol stability tactic - #333
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.
Summary
rr_finite_symbol_stable_or_zero_autofor goal-directed operator/input inference and local certificate discoveryfiniteSymbol_preserves_stabilitydeclaration at one siteAPI boundary
This is only the direct multiaffine stable-or-zero theorem surface. It does not discharge the false legacy homogeneous finite-symbol statement, the conjectural Jensen-pencil implication, the degree-d PF-bidiagonal backend, or an affine-bidiagonal application bridge.
Verification
RealRooted.Tactic.Examples.FiniteSymbolRealRooted(8,951 jobs; only pre-existing warnings)python3 scripts/check_root_imports.pygit diff --checkand touched-file line/placeholder scans