Repository navigation
docs: record the 011.04 closure and how to verify its commitment chain - #50
Merged
Merged
Conversation
The experiments README stopped at 011.02's disposition C, so main described the 011 learner as unreliable while carrying the turn that closed it. Add an 011.04 section: the unchanged-metric table against 011.02, the four-layer separation that makes it a closure rather than a redesign, the closure files, and the three cautions a reader needs (Query A is cheaply exact, plane-validity entails certified equivalence, selection used the already-public development seeds). Also document that fano_optimization_evaluate and fano_optimization_analysis cannot pass from main. Both assert the recorded pre-evaluation commit is an ancestor of HEAD, and the squash merge in #49 leaves no such ancestor. No number or artifact differs; the commit boundary proving selection preceded evaluation is simply not reachable from a squashed history. The section names the preserved provenance/* tags and the retained experiment branches to run them from. Fix three internal anchors that used 009-06 style where GitHub's slugger emits 00906. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
Why
Two gaps surfaced while merging #49.
The experiments README stopped at
011.02's disposition C.mainnow carries the turn that closed Issue 011, but its README still described the learner as reaching only 5 of 8 seeds and statedH_discovery_global_finite is NOT banked. Anyone readingmaingot the superseded half of the story.Two of the eight fast checks cannot pass from
main.fano_optimization_evaluate.pyandfano_optimization_analysis.pyassert that the recorded pre-evaluation commit is an ancestor ofHEAD. #49 was squash-merged, so onmainboth fail withrecorded pre-evaluation commit is not an ancestor of HEAD. No number or artifact differs — but the commit boundary that proves selection preceded evaluation is not reachable from a squashed history, and that boundary is the whole anti-cheating argument of011.04§4.What this adds
011.04section: the unchanged-metric table against011.02(5/8→16/16, every threshold at1.0000), the four-layer separation (identifiability / representation / optimization / generalization) that makes it a closure rather than a redesign, the closure files, and the closure fence.fano_plane_validentailscertified_plane_equivalentso two rows are one finding, and selection read the already-public development seeds.main" subsection naming theprovenance/*tags and the retained experiment branches to run those two checks from.011.02heading, matching the idiom already used for009.02→009.06.009-06style where GitHub's slugger emits00906.Related ref changes (already pushed, not part of this diff)
Nine annotated
provenance/*tags now pin every commit011.04§11 cites, plus the two commits009cites that no ref on origin reached. Both experiment branches are restored, anddelete_branch_on_mergeis off so future squashes stop orphaning cited commits.🤖 Generated with Claude Code