interval: derive checker input from Lean goals - #9210
Merged
Conversation
kim-em
force-pushed
the
agent/interval-exp-vertical
branch
from
August 11, 2026 19:33
d684a5f to
fc34666
Compare
kim-em
force-pushed
the
agent/interval-goal-frontend
branch
from
August 11, 2026 19:34
e9e52f1 to
316034f
Compare
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
1 participant
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.
Adds the first extensible goal-reification layer for the interval engine. Operation packages own Lean-expression recognizers; the generic builder enforces unique matching, typed arity, resource bounds, SSA validation, and expression/domain CSE. A separate fact parser derives version-zero facts and the caller target while retaining complete same-node assumption provenance.
The Real.exp canary now reifies its actual goal and requires the resulting program, initial facts, and target to match the existing semantic fixture before planning and kernel proof emission. Conformance also checks CSE, assumption seeding, and rejection of overlapping syntax packages.
This remains deliberately incremental: package-compositional semantics and generic discharge of top/assumption seed recipes are the next step. No native_decide, axioms, or sorries.