retracted-pin-survives-recompute
IN premise
A node explicitly retracted via `retract()` gets a `_retracted` metadata flag that pins it OUT — surviving both `assert_node` on its antecedents and `recompute_all()`, clearable only by `assert_node` on the pinned node itself
Summary
When you explicitly retract a node, the system marks it with a sticky flag that keeps it forced out, even if its supporting evidence changes or the entire network is recomputed. The only way to bring it back is to directly reassert that specific node — no amount of upstream changes will override the manual retraction.
Dependents
These beliefs depend on this one:
- metadata-is-universal-extension-mechanism — Node metadata is the universal extension mechanism carrying all structured lifecycle state (retraction flags, stale reasons, challenges, access tags, supersession markers), and retraction flags pinned in metadata survive recomputation to enforce sticky retraction.
Details
| Source | entries/2026/04/24/tests-test_network.md |