outlist-relationships-survive-persistence

IN premise

Outlists are stored as `outlist_json` in the SQLite `justifications` table; on load, the dependent index is rebuilt for both antecedents and outlist nodes, preserving propagation behavior across save/load cycles

Summary

When the system saves its state to disk, the outlist relationships (which track what a justification says should be disbelieved) are preserved in the database alongside normal justification data. On reload, the system reconstructs all the dependency tracking needed for belief propagation to work correctly, so restarting the system does not lose any reasoning relationships or cause beliefs to silently change status.

Dependents

These beliefs depend on this one:

outlist-semantics-are-fully-specified — The outlist primitive has complete, well-defined semantics: multiple entries form a conjunction (all must be OUT), absent nodes are treated as OUT (permissive default), and outlist relationships survive persistence through JSON serialization with rebuilt dependent indexes.
persistence-round-trip-is-lossless — The save/load round trip preserves all network state faithfully: snapshot persistence captures the full graph, stored truth values are trusted without re-propagation, justification insertion order is preserved via rowid, and outlist relationships survive serialization.

Details

Source

entries/2026/04/23/topic-outlist-semantics.md