dangling-dependent-guard-skips-missing-nodes
IN premise
`_propagate` skips dependent IDs not present in `net.nodes` rather than raising `KeyError`, and emits a structured warning log entry for each (fix for issue #22).
Summary
When propagating belief status changes through the network, the system gracefully handles cases where a dependent node no longer exists instead of crashing with an error. If a node references a dependent that has been deleted or is otherwise missing, it logs a warning and moves on. This defensive behavior prevents cascading failures during retraction or status updates in networks where nodes may have been removed.
Dependents
These beliefs depend on this one:
- dangling-dependents-are-safely-contained — Dangling dependent references are safely contained across all propagation dimensions: BFS skips missing nodes with structured warnings, the changed set never includes ghost IDs, and the visited set excludes dangling IDs so later-created nodes propagate normally.
Details
| Source | entries/2026/04/29/tests-test_dangling_dependents.md |