docs: sync Lean-side Priority 17 bridge provenance contract - #110
Merged
Conversation
Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Contributor
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
AkiraTamai
marked this pull request as ready for review
August 26, 2026 14:15
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
Lean-side half of canonical Priority 17 (implemented in mumei-lang/mumei#497). Documentation only — no bridge code, no vocabulary, and no existing implementation status changed.
mumei releases and Homebrew now ship per-module proof certificates plus a
std-proof-bundle.jsonwhoselean_provenanceindex carriestranslator_version,bridge_lemma_hash, andmanual_lemma_reasonper Lean-proved atom. That makes provenance checkable from a distribution alone, so this repo's consumer-facing docs need to say how:docs/ROADMAP.md— new "Priority 17 bridge surface" checkpoint, explicitly subordinate to mumeidocs/CROSS_PROJECT_ROADMAP.mdas the sole upper roadmap.docs/BRIDGE_HARNESS_SPEC.md,docs/LEAN_HARNESS_CONTRACT.md,README.md— the distributed-bundle consumer procedure: locate certificate and source viaartifact_paths, read the matchinglean_provenanceentry, requirez3_check_result == "lean_verified"with currenttranslator_version/bridge_lemma_hashand an understoodmanual_lemma_reason, then re-runmumei verify-cert <certificate> <source> --strict(adding--allow-lean-verifiedon acceptance paths that permit Lean results).The key point every added section repeats: a translator or bridge-lemma mismatch stays
stale_translatorand is not a proof.lean_verified/stale_translator/translator_version/bridge_lemma_hashare reflected as-is, never aliased.Verification
Link to Devin session: https://app.devin.ai/sessions/0f87f38914874eedbc48c92f3b941354
Requested by: @AkiraTamai