import-handles-heterogeneous-truth-states
IN derived (depth 1)
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
Summary
The import pipeline is robust to messy real-world data: it can bring in beliefs that have been retracted or gone stale without accidentally reviving them, it won't crash if the dependency graph has circular references, and it processes everything in a careful two-phase order to avoid incorrect cascading effects from half-built networks. This means you can safely merge belief networks from different sources without worrying about corrupted truth states.
Justifications
SL — Three independent robustness mechanisms ensure import succeeds regardless of source network state
Antecedents (all must be IN):
- out-beliefs-imported-without-justifications — Beliefs that are OUT or STALE in the source are imported with an empty justification list, preventing `recompute_all` from resurrecting them to IN
- import-topo-sort-tolerates-cycles — `_topo_sort_claims` attempts topological ordering but appends remaining nodes when progress stalls, gracefully handling dependency cycles instead of erroring
- import-two-phase-truth-maintenance — Import/sync adds all nodes first, then runs `recompute_all()` to propagate truth values, then performs explicit retractions — this ordering prevents incorrect cascades from partially-constructed networks
Dependents
These beliefs depend on this one:
- agent-subsystem-is-self-contained — The agent subsystem provides complete lifecycle management: import handles mixed truth states and topological cycles, namespace/relay pairs provide isolation and kill-switches, and all defeat operations are reversible for agent reactivation.
- 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.