Repository navigation
Bind research verification to exact candidate identities and types - #5
Merged
Merged
Conversation
afflom
commented
Nov 4, 2026
afflom
left a comment
Owner
Author
There was a problem hiding this comment.
Maintainer self-review of 4230698 (not an independent approval): checked candidate selection, semantic/build identity binding, contextual premise closure and refutation, report ownership, stale/cancel/cleanup handling, and the generated native entry smoke evidence. The unchanged pre-commit gate accepted all 64 API modules, kernel replay, exact axiom policies and production certificates; the push hook reused that accepted tree. No merge-blocking finding remains for this change's stated scope. Source provenance, strategy construction, native research wiring and durable publication remain explicitly unfinished; this PR does not establish Problem 1. Merge remains conditional on the PR CI result.
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.
A successful verification report must prove the research request's actual contextual goal. Previously, the runner could accept an externally supplied checked answer after a successful job without comparing that goal with the audited declaration's type.
This change authors the binding and its lifecycle in LexLean. It recomputes the candidate semantic identity from canonical linked IR and lexicon data, selects a unique proof-bearing native declaration, reconstructs the selected source premise under its preceding binders, and compares exact core types. Refutation negates the premise within that context. Source origins match the request's recorded source names; they are not mistaken for artifact hashes.
ResearchProofowns verification and report reads before promotion.ResearchRunnerroutes proof jobs through that owner, refuses externally submitted checked answers, cancels stale work, and retains ownership after failed cleanup. The attention catalog includes the new modules and behavioral features. Canonical encoding rejects duplicate keys, malformed UTF-8, out-of-domain numbers, exhausted work and output limits; oversized keys and numbers are refused before costly comparison or slicing.The compiler pin follows the v0.5-based native Host driver in UOR-Foundation/lexlean#439. Compiler/target metadata and official locks are refreshed. The API certificate-part limit is 6 MiB, based on the measured 4,541,007-byte part; proof policy and the acceptance hook are unchanged. The only legacy Python edits update two target-digest constants. CI and runtime use no remote models.
Validation completed on 4230698:
PR CI passed: Main Branch Validation run 41910715189. Maintainer self-review is recorded on the unchanged head.
This completes candidate/type binding within the owned verifier. Source inspection must still establish provenance, and native strategy construction, research command integration and durable publication remain implementation work. This change does not claim a proof of Rule 30 Problem 1 or completion of the native research engine.