propagation-respects-node-lifecycle
IN derived (depth 1)
Truth propagation respects node lifecycle states: retracted nodes are skipped during BFS traversal, and the trigger node itself is never recomputed — callers must set its truth value before invoking propagation.
Summary
Propagation only flows through active nodes — if a node has been retracted, the system skips over it rather than pushing truth values through dead branches. The node that kicks off propagation is treated as already settled, so whatever called propagation is responsible for setting that node's value first; the propagation engine won't second-guess it.
Justifications
SL — Propagation treats retracted and trigger nodes as boundaries, not participants, preventing unintended reactivation and circular recomputation
Antecedents (all must be IN):
- retracted-nodes-skipped-in-propagation — Retracted nodes (marked with `_retracted` metadata) are skipped during BFS propagation but remain in the network for potential restoration.
- propagate-does-not-change-trigger — The seed node (`changed_id`) is added to `visited` immediately and never has its own truth value recomputed; callers must update it before calling `_propagate`
Dependents
These beliefs depend on this one:
- lifecycle-awareness-spans-checking-and-propagation — Both read-only inspection and mutation-driven propagation respect node lifecycle consistently: staleness checking skips OUT nodes and never mutates state, while propagation skips retracted nodes and preserves trigger identity — lifecycle state is honored across the system regardless of whether the operation is read or write.
- metadata-actively-governs-truth-propagation — Lifecycle state carried in node metadata (retraction flags, stale reasons) is not passive storage but actively governs truth propagation behavior — retracted nodes are skipped during BFS traversal and trigger nodes are never recomputed — ensuring that the universal extension mechanism directly controls truth maintenance rather than merely recording state
- propagation-is-safe-and-terminating — Truth propagation is both lifecycle-safe and guaranteed to terminate: retracted nodes are skipped, trigger nodes are never recomputed, BFS prevents stack overflow, and stop-on-unchanged prevents oscillation — propagation respects every node state it encounters.