check-stale-skips-out-nodes
IN premise
Only nodes with `truth_value == "IN"` are checked for staleness; retracted (OUT) nodes are ignored even if their source file has changed.
Summary
When the system checks whether beliefs are up-to-date with their source files, it only looks at active beliefs. If a belief has been retracted, changes to its source file won't trigger any staleness warning. This means a retracted belief could become relevant again due to source changes, but the system won't notice until something else restores it.
Dependents
These beliefs depend on this one:
- staleness-is-conservative-ci-gate — Staleness checking is designed as a safe CI gate: it never mutates state, only checks IN nodes, requires both source fields, and exits nonzero to fail the pipeline
Details
| Source | entries/2026/04/23/reasons_lib-check_stale-check_stale.md |