bootstrap-bypasses-incremental-propagation
IN derived (depth 1)
Both persistence loading and import construct the full node graph before truth maintenance — load trusts stored truth values and skips propagation entirely, while import adds all nodes then propagates via recompute_all — sharing a bulk-construction pattern that avoids per-node incremental propagation.
Summary
When the system starts up from a saved state or imports data, it doesn't process nodes one at a time the way normal operation does. Instead, it builds the entire network first and then either trusts the previously stored truth values or recalculates everything in one pass. This avoids errors that would occur if truth maintenance ran while the network was only half-built.
Justifications
SL — Both subsystems separate graph construction from truth maintenance for efficiency and correctness during bulk operations
Antecedents (all must be IN):
- storage-load-bypasses-propagation — `load()` constructs nodes directly into `network.nodes` rather than calling `add_node`, so truth maintenance propagation does not fire during deserialization.
- 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:
- initialization-is-path-independent — Whether beliefs enter through stored-state bootstrap (load trusts stored truth values, import builds nodes before recompute_all) or through the deterministic reasoning engine (uniform pure evaluation with guaranteed termination), the system reaches correct truth states — bootstrap trusts values that were originally computed by the same deterministic engine, and import re-derives them via recompute_all, establishing path independence of initialization.