import-provides-complete-reconciliation

IN derived (depth 2)

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.

Summary

When data is brought in from external sources, the import system covers all the tricky edge cases. It correctly handles beliefs that arrive in different truth states, offers both a gentle merge mode and a full overwrite mode depending on what the situation calls for, and uses a naming scheme that keeps different agents' data from stepping on each other. Together, these pieces mean the system can reliably absorb outside knowledge without corruption or conflicts.

Justifications

SL — Import handles all truth states, sync handles ongoing updates, and namespacing prevents cross-agent collisions

Antecedents (all must be IN):

  • import-handles-heterogeneous-truth-states — The import pipeline handles mixed truth states: OUT/STALE beliefs arrive without justifications, topological sort tolerates cycles, and two-phase truth maintenance reconciles everything post-import
  • import-sync-has-dual-reconciliation-modes — The import/sync subsystem offers two distinct reconciliation strategies: import is additive (skips existing nodes), while sync is remote-wins (overwrites text, justifications, and truth values from the remote source).
  • namespace-is-colon-convention-with-auto-wiring — The namespace system is a colon-based convention with automatic infrastructure wiring: colon presence prevents double-prefixing, the `agent:id` format provides scoping, and node creation auto-wires a `{ns}:active` premise as an antecedent.

Dependents

These beliefs depend on this one:

Details