storage-load-bypasses-propagation

IN premise

`load()` constructs nodes directly into `network.nodes` rather than calling `add_node`, so truth maintenance propagation does not fire during deserialization.

Summary

When the database is loaded from disk, nodes are placed directly into memory without triggering the normal dependency-tracking logic. This means the system trusts the stored state as-is during startup rather than re-deriving every conclusion from scratch, which is faster but assumes the saved state was consistent when it was written.

Dependents

These beliefs depend on this one:

bootstrap-bypasses-incremental-propagation — 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.
persistence-is-snapshot-not-incremental — The storage layer operates as a full snapshot: save replaces all rows, load trusts stored values without re-propagation, and the dependents index is rebuilt from scratch

Details

Source

entries/2026/04/23/reasons_lib-storage.md