Repository navigation
Phase 5: complete lineage and ancestry dev4 milestone - #2
Merged
Merged
Conversation
DavidWallstructurallaw
changed the base branch from
phase4-reports-cli
to
main
October 2, 2026 06:58
DavidWallstructurallaw
marked this pull request as ready for review
October 2, 2026 06:58
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.
Direct provenance metrics do not resolve multi-step ancestry. Phase 5 adds explicitly requested canonical graphs, cycles and depth, strict external roots, root concentration, lineage closure intervals and descriptive shared-root evidence. Schema 1.1 and local CLI context inputs preserve primary denominators, privacy boundaries and incomplete evidence.
The development milestone is complete at
0.1.0.dev4. This draft PR is stacked on the accepted, unmerged Phase 4 branch so its diff contains Phase 5 work.All 13 required jobs passed on candidate
53802fb0e99ea867a27bb82210cc9fa32d8e02d1, tree5f235a4e008f65d0cb76d0af2e5b7d929271f018:Candidate CI and delivery passed on its first attempt. Every executed test passed without skips or errors. The unselected focused job was intentionally skipped.
Actual hosted 100k reverse-chain input/ancestry execution took 66.23 seconds and 1.72 GiB peak RSS, excluding ordinary metrics and full audit serialization. The separate complete 100k metadata report took 780.73 seconds and 7.15 GiB. All three lineage Hero observations were below 0.684 seconds. A pre-CLI RSS floor in two bounded hosted measurements received a narrow local recheck and is explicitly explained in the completion report; no code change or matrix rerun was needed.
Repeated wheel bytes were identical and all sdist file payloads matched; compressed sdist bytes differed within the documented timestamp allowance. Delivery artifact and performance evidence were retrieved and checked against their artifact digests.
Final administrative head
f09521907558a193e6438d9acb316adb9e191195changes only PHASE_5_COMPLETION.md. The other 272 tracked entries retain identical mode, type and blob identities. Existing document/source/specification/traceability checks passed. Its[skip ci]commit reuses the verified candidate under the approved governance policy and does not claim a second matrix run.Final completion and limitations records all scopes and boundaries. Root identity remains topological and the shared-root proxy descriptive. This PR remains a draft and unmerged; no merge-ready branch-protection claim, tag, publication or Phase 6 implementation is implied.