docs: replace declaration provenance with semantic references - #5040
Merged
Conversation
phasetr
force-pushed
the
docs/5019-5026-remove-provenance
branch
from
August 13, 2026 00:09
d7551bc to
01d1ad7
Compare
53 tasks
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.
Closes #5019
Closes #5026
Intent
Finish the unresolved provenance portions of both errata issues. Declaration documentation should
describe the current theorem and its semantic dependencies; workflow step numbers, issue IDs and
PR numbers belong in Git history and become opaque as the implementation evolves.
Changes
PR #N, bare#N, andStep Nreferences from declaration docs inAmbientLattice/Analyticity*.lean(the live-main population after docs(errata): PR1 of 2 — false-claim corrections from #4984 campaign errata #5030).names such as
freeEnergyAlongExhaustion_le_uniform_upper_bound,freeEnergyInfinite_high_temp_h_zero_deviation_bound_exp, andlog_partitionFunction_sum.InducedUnion.leanandPerStageIncrement.leanfiles found by the required live boundary sweep. These carried the sameissue/PR-number defect class and are direct dependencies of the reported layer.
/--doc-comment defects in the AmbientLatticeSum layer (found in wave 15 of #4984) #5026 inSuperadditiveConvergence.lean: remove the embedded progress transition andreplace the obsolete future-PR roadmap with the current
of_J_zero/of_beta_zeroconstructorsplus the general direct-field route.
declaration signature, import, or dependency changed.
History and scope evidence
git log -Sand blame show the Analyticity prose was carried through file splits such as922a5b2c, while the AmbientLatticeSum prose was carried through01e6f84b/1002f3a3.docs(errata): PR1 of 2 — false-claim corrections from #4984 campaign errata #5030 had already rewritten part of that population.
AmbientLattice/Analyticity*.lean,AmbientLatticeSum/, and theAmbientLatticeSum root modules reports zero
PR #N, bare#N,Step N, orIssue #Ntokens.Verification
lake build IsingModel: PASS, 4943 jobs.audit_gate.py --full: PASS over 1921 Lean files; all 13 capstones remain limited to the standardthree axioms.
git diff --check: PASS.