Skip to content

Feature/Fix: Contain ambiguous lineage families#32

Open
iam-brain wants to merge 1 commit into
iam-brain/lineage-residual-classificationfrom
iam-brain/lineage-conservative-evidence
Open

Feature/Fix: Contain ambiguous lineage families#32
iam-brain wants to merge 1 commit into
iam-brain/lineage-residual-classificationfrom
iam-brain/lineage-conservative-evidence

Conversation

@iam-brain

Copy link
Copy Markdown
Owner

Summary

  • scope lineage identities and exceptional parent discovery to one normalized Codex home
  • preserve incomplete, truncated, and malformed evidence instead of silently dropping it
  • route every family exclusively through primary accounting or conservative containment
  • retain deterministic descendant usage when ancestry is missing and expose privacy-safe diagnostics

This is another isolated component of the planned Codex scanner rearchitecture. It keeps the production legacy total authoritative while making shadow accounting safer around malformed and ambiguous rollout histories.

Closes #22

Validation

  • swift test --filter 'CodexLineage(Shadow|Ledger|Discovery)Tests' (28 passed)\n- make check\n- env SDKROOT=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX26.5.sdk make test (642 selections, 54 groups, no failures or retries)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant