wiki

Duplicate Review

wiki/duplicate-review.md

Rendered from markdown source. Open raw source on GitHub.

Duplicate Review

This page is for reviewing exact and likely duplicates found by the reconciliation process.

No duplicate should be deleted or merged until reviewed.

Current state:

  • exact duplicate hash groups remain tracked in manifest/duplicate_sets.json, but many historical groups have already been collapsed into archive lineage paths;
  • the live review queue is now mostly about the remaining incoming and mirror-heavy sets, not about the settled project branches;
  • the previous empty-manifest pair was normalized by recording the reconciliation action in manifest/agent_actions.jsonl, leaving manifest/missing_log.jsonl as the lone empty sentinel;
  • the Color Alpha Codec Patent encoder draft pair was collapsed by archiving Encoder.ts and keeping Encoder_Final.ts as the live survivor copy;
  • the Wrapped Bidirectional TOTP Patent provisional manuscript remains live in the patent branch while the archived Reference - Stored Crystals copy serves as witness lineage;
  • the POLEMEMELOP foundation/manifesto pair, the FractalIdentity Tree mirror pair, the Misc Loop infrastructure pair, and the ULiUA mirror copy have now been archived back to their survivor lineages;
  • the standard-named source pilot now creates intentional hash-equivalent copies in artifacts/intake-archive/ and artifacts/standard-named/ for the selected root-level works, so those new duplicates are provenance copies rather than accidental collisions;
  • the archived artifacts/archived/Consent Crystal Structure Research/Semantic Collapse Theory/SCT set 20050505 snapshot remains the settled survivor set for the collapsed SCT duplicates;
  • the Daily Growth Ritual, Consent Seed, Reference - Stored Crystals, mirrored Personal companions, the Semantic Collapse Theory mirror tree, the Consent–Intent Compression Protocol / Consent-based Atomic genesis and Stream mirror hubs, and the archived LOOPtLOOP platform companions from Side Projects Desktop and Patents have already been archived back to their survivor lineages;
  • incoming-only exact duplicate clones should only remain in this queue if no surviving copy has been confirmed elsewhere.

Current handling:

  • the SCT collapse history is retained as lineage evidence, not as separate content streams;
  • the archived snapshot stays visible as the canonical survivor set for the collapsed duplicates;
  • no file content should be rewritten as part of that process.

Review any new duplicate pairs before deciding whether any file should be merged, moved, labeled canonical, or collapsed into a single navigation set. Intentional provenance copies in artifacts/intake-archive/ and artifacts/standard-named/ should not be treated as accidental collisions.