check-stale-requires-both-source-fields

IN premise

A node must have both `source` (non-empty) and `source_hash` (non-empty) to be eligible for staleness checking; nodes missing either field are silently skipped.

Summary

When the system checks whether a node's source material has changed, it only examines nodes that have both a source URL and a recorded hash of that source. If either piece is missing, the node is quietly ignored during staleness checks, meaning it will never be flagged as outdated — even if it should be.

Dependents

These beliefs depend on this one:

staleness-checking-is-comprehensive — Staleness checking detects all nodes whose source material has changed on disk
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