bulk-operations-preserve-topology-and-reconcile

OUT derived (depth 3)

Both bulk modification operations — deduplication and import/sync — preserve network topology by rewiring justification references (both antecedent and outlist) to survivors or updated targets, while providing distinct reconciliation strategies (dedup via user-editable keep/retract plans, import via dual additive/remote-wins modes)

Summary

When the system needs to clean up duplicates or pull in beliefs from another source, both operations are careful not to break the web of connections between beliefs. Duplicate removal rewires all references to point at the surviving copy and lets a human review the plan before anything is deleted, while importing from external sources offers two strategies — one that only adds new material and one that fully syncs to match the remote state. This belief is currently marked OUT, meaning one or both of those underlying claims about deduplication or import behavior may no longer hold.

Justifications

SL — Two independently-designed bulk operations converge on the same safety property — topology preservation through reference rewriting — suggesting this is an emergent architectural invariant rather than a coincidence

Antecedents (all must be IN):

  • 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).
  • import-provides-complete-reconciliation — The import subsystem provides complete reconciliation coverage: heterogeneous truth states are handled correctly on initial load, dual modes support additive import and remote-wins sync for different operational needs, and the colon-based namespace convention with auto-wiring prevents ID collisions across agents.

Dependents

These beliefs depend on this one:

Details