Conversation
added 2 commits
August 22, 2026 10:37
Specify the copy-switch-delete migration from Grind to Sym.Arith and the downstream Hex tactic architecture.
kim-em
marked this pull request as draft
September 2, 2026 03:32
Owner
Author
|
Marked draft during repository cleanup. This is a 1,949-line architecture proposal, not a routine merge candidate; it needs a current design review against the substantial tactics/interval work merged since August before it can be considered ready. |
This was referenced Sep 10, 2026
This branch has not been deployed
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.
This PR adds two planning documents.
SPEC/lean4-sym-arith.mdproposes completingLean.Meta.Sym.Arithas Lean's shared algebraic reflection service, running inSymMrather than under a dormant Grind goal. It sequences the work as a strict copy-switch-delete migration of the reusable machinery out of Grind, and defers every generalization (the standalone interface, batch operations, and the rational, additive, noncommutative, module and symbolic-exponent views) until that migration has landed and the duplicates are deleted. It also records what parity requires, including that core tests alone do not cover the numeral-recognition boundary and the migration should be validated against https://github.com/leanprover/downstream-lean4.SPEC/Libraries/hex-tactics.mdspecifies the Hex side against that interface: a state transformer over the caller's symbolic monad owning computational providers, derived typed views, direct conversions, conditional results, proof provenance and budgets, with Lean's algebraic grammar left closed. It covers scalar and additive normalization, matrix determinant, rank and characteristic polynomial, univariate and multivariate factorization, the rational-expression transformationstogether,cancelandapart, and which pieces stay Mathlib-free versus moving to a*-mathlibcompanion.Not ready to merge. The Lean half of this depends on what Leo wants to do with
Sym.Arith, and that conversation has not happened yet. The Hex document is written against the proposed interface, so its assumptions move if his answer does. Staying a draft until that is settled.🤖 Generated with Claude Code
https://claude.ai/code/session_01CrYPRybNqBoZYzXHpGCwKZ