Skip to content

Phase 5: complete lineage and ancestry dev4 milestone - #2

Merged
DavidWallstructurallaw merged 12 commits into
mainfrom
phase5-lineage
Oct 2, 2026
Merged

DavidWallstructurallaw merged 12 commits into
mainfrom
phase5-lineage

Conversation

@DavidWallstructurallaw

@DavidWallstructurallaw DavidWallstructurallaw commented Sep 26, 2026 •

Copy link
Copy Markdown
Owner

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, tree 5f235a4e008f65d0cb76d0af2e5b7d929271f018:

  • Eight Ubuntu/Windows, Python 3.11/3.12, current/minimum profiles: 2,960 tests each, with PyArrow actually absent.
  • Real Parquet: 2,965 tests, including all five optional cases.
  • Hero/mathematics: 279 tests; security: 1,992 tests; reference performance: 13 tests.
  • Dependent delivery: strict wheel/sdist metadata, complete same-candidate JUnit identities, 40 source modules and canonical resources, clean installed ordinary/lineage Hero, repeated builds and the exact 273-file source archive.

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 f09521907558a193e6438d9acb316adb9e191195 changes 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.

@DavidWallstructurallaw DavidWallstructurallaw changed the title Phase 5: lineage and ancestry dev4 candidate Phase 5: complete lineage and ancestry dev4 milestone Sep 26, 2026
@DavidWallstructurallaw
DavidWallstructurallaw changed the base branch from phase4-reports-cli to main October 2, 2026 06:58
@DavidWallstructurallaw
DavidWallstructurallaw marked this pull request as ready for review October 2, 2026 06:58
@DavidWallstructurallaw
DavidWallstructurallaw merged commit debfdfb into main Oct 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant