Repository navigation
Research consolidation: selected-source provenance gap map + 298-row vendored-source re-verification (no new kappa) - #867
Merged
Mister-Meeseeks merged 1 commit intoOct 13, 2026
Conversation
…w vendored-source re-verification (no new kappa)
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
2 participants
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.
Research note / independent verification. No new kappa, no certificate change, no whole-PR approvals.
Base: f567884. Track 95-99, seed 97.
Question: certificates/selected-result.json lists 76 source_prs, but the central ledger marks many unreviewed and 17 appear in no disposition record. This PR resolves that discrepancy by indexing every in-repo record (central ledger, all nine audit DISPOSITIONS.json files, round-9 ledger, overnight dispositions, family-588 workflow dispositions, both review queues, pr531 + frontier799 integration receipts, frontier799 PUBLICATION + CONTENT-COVERAGE).
Finding: 50/76 have incorporated-strength records. The other 26 split into three documented groups: (1) ten PR 635-PR 699 PRs with file-level vendored-source binding explicitly scoped as not whole-PR approval; (2) PR 653/PR 658/PR 660 narrative credit only; (3) twelve ledger-unreviewed historical lineage PRs plus PR 620 partial. Full map in research/selected-source-coverage-audit/COVERAGE.md (generated, not hand-written).
New evidence: research/selected-source-coverage-audit/verify-vendored.ps1 independently re-verifies all 298 SOURCE-FILES.json rows - SHA256 against the manifest and git blob id against the named commit object. Result: 298/298 pass (VENDORED-CHECK.json). All ten PR 635-PR 699 PROVENANCE pins verified resolvable to commit objects.
Reproduce (PowerShell 5.1+, no Python needed):
powershell -NoProfile -ExecutionPolicy Bypass -File research/selected-source-coverage-audit/coverage.ps1
powershell -NoProfile -ExecutionPolicy Bypass -File research/selected-source-coverage-audit/verify-vendored.ps1
Limitations: no finite replay re-run (no Python on verifying machine); vendored-byte identity is not whole-PR approval; SW4-ancestor vendoring only. Upstream/ untouched. Prepared with help from opencode.