dangling-ids-excluded-from-changed
IN premise
The `changed` set returned by `retract()` and `assert_node()` never contains IDs that don't correspond to real nodes in the network.
Summary
When the system reports which nodes changed status after a retraction or assertion, every ID in that list points to an actual existing node. You won't get phantom or stale IDs back, so callers can safely look up any returned ID without checking whether it exists first.
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/24/tests-test_dangling_dependents.md |