dedup-keeps-most-connected-node
IN premise
In auto-dedup mode, the node with the most dependents survives each cluster; ties break by lexicographic ID, and losers are retracted after dependents are rewired.
Summary
When duplicate beliefs are detected and automatically merged, the system preserves the one that other beliefs depend on most, rewiring any connections from the duplicates before removing them. This ensures deduplication causes minimal disruption to the existing reasoning chain.
Dependents
These beliefs depend on this one:
- dedup-is-topology-preserving-and-auditable — Deduplication preserves network topology (rewrites both antecedent and outlist references to survivors), selects structurally-optimal survivors (most dependents with lexicographic tiebreak), and supports human oversight (KEEP/RETRACT markers in a user-editable plan format).
- dedup-survivor-selection-is-topology-reliable — Deduplication reliably selects the structurally-optimal survivor in each duplicate cluster by choosing the node with the most dependents, and this selection is correct because the dependents index accurately reflects the justification graph.
Details
| Source | entries/2026/04/24/reasons_lib-api.md |