propagate-does-not-change-trigger
IN premise
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`
Summary
When propagation runs, it skips over the node that triggered it — it only ripples outward to that node's dependents. This means any code that calls propagate is responsible for updating the trigger node's status first, because propagate will not do it for them.
Dependents
These beliefs depend on this one:
- propagation-respects-node-lifecycle — 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.
Details
| Source | entries/2026/04/23/reasons_lib-network-_propagate.md |