dangling-ids-excluded-from-visited
IN premise
The propagation visited set does not include dangling IDs, so a formerly-dangling ID that becomes a real node will propagate correctly on subsequent operations.
Summary
When the system tracks which nodes it has already processed during propagation, it deliberately ignores references to nodes that don't exist yet. This means if you later create a node that was previously just a dangling reference, it won't be incorrectly skipped — propagation will process it fresh, ensuring the network stays consistent as new nodes appear.
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 |