Repository navigation
Docs: map current P104 support and chronology work - #3314
Merged
Mister-Meeseeks merged 1 commit intoOct 17, 2026
Merged
Mister-Meeseeks merged 1 commit into
Mister-Meeseeks merged 1 commit into
Conversation
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.
Change and mathematical scope
Adds
docs/research/p104-live-support-map.mdand links it from the P104 rows inresearch-family-status.mdandcurrent-priorities.md. The map reconciles the merged #2981 static flags with the newer event-touch, support-propagation, helper-13 and fixed-cover support submissions. It records exact heads, finite counts, assumptions, evidence status and the remaining gap.This is a documentation/navigation result, not a new theorem or independent proof. In particular, #3259 remains an open, conditional fixed-cover support claim; the note does not call it accepted or generalize it beyond its stated model. The selected result and κ are unchanged.
Task and overlap
463113d675af7410ac91d53a4fed51ec6494eb9a.scope-navigation, priority revision 6, scope keyfff26335d457e528d9c4; selector seedf3d3f03fa8473d6c7626048a3e6f723a. Refined to a dated P104 fixed-cover support/chronology status map.python3 scripts/find_overlap.py --task scope-navigationcompleted pagination for 349 open PRs and 2,148 Discussions at 21:22 UTC. It reported possible matches, not a novelty certificate; its documented scope does not inspect arbitrary diffs or unpublished work. A fresh issue query found only open issue All size/compiler is retained #913, an unrelated editorial complaint.Validation
On CPython 3.14.8:
The selected-record binding baseline passes; package metadata and source pins pass; both fixed-flag verifiers pass; the behavioral suite passes all eight groups.
git diff --checkpasses, and all 28 changed-document internal links resolve against the tracked tree plus the new file.The registered #2981 package runner requires Python 3.12, which is not installed in this environment; the runner refuses Python 3.14. Its optimized direct checks above pass. I did not run the full
frontier1094-verifyreplay or the open PR package replays, and I did not independently review their proofs. Hosted CI and formal-kernel verification are not claimed.Credit
The map preserves the source links and exact heads for Nick Petalas/#2981/#3252/#3259, commdata2338/#3214/#3225, jwr404/#3242, tekuuu/#3298, dcharb78/#3182, the PR #3124 matching, and the original #1972/#1991 channel. The prior #2633 map remains credited for its distinct earlier scope. Prepared by @1337isnot1337 with substantial OpenAI Codex assistance. No independent human review is claimed.
Open next questions
Independently review #3259's source pins, support implication and exact fixed-cover assumptions before treating that route as closed. If confirmed, avoid more matching-only work inside that model; a new route must name a changed source/frame/target contract and account for exact coefficient delivery, dirty restoration, native/physical/precision costs and the complete consumer invoice. If the support proof fails, identify the precise invalid implication or reachable coefficient. No universal P104 obstruction or supplier admission follows from this PR.