lifecycle-awareness-spans-checking-and-propagation
IN derived (depth 2)
Both read-only inspection and mutation-driven propagation respect node lifecycle consistently: staleness checking skips OUT nodes and never mutates state, while propagation skips retracted nodes and preserves trigger identity — lifecycle state is honored across the system regardless of whether the operation is read or write.
Summary
The system treats node lifecycle status as a hard boundary in every operation, whether reading or writing. Staleness checks silently skip over OUT nodes without touching anything, and propagation skips retracted nodes without recomputing them — so no operation, regardless of its purpose, will accidentally resurrect or process a node that has been marked inactive.
Justifications
SL — depth-2 — read path (staleness) and write path (propagation) independently enforce lifecycle awareness, suggesting a system-wide invariant
Antecedents (all must be IN):
- 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
- propagation-respects-node-lifecycle — Truth propagation respects node lifecycle states: retracted nodes are skipped during BFS traversal, and the trigger node itself is never recomputed — callers must set its truth value before invoking propagation.
Dependents
These beliefs depend on this one:
- integrity-enforced-across-architecture-and-lifecycle — Integrity is enforced along two orthogonal dimensions: vertically across architectural layers (clean data-model/TMS/persistence boundaries with snapshot persistence and CI gating) and horizontally across node lifecycle states (staleness checking skips OUT nodes without mutating, propagation skips retracted nodes while preserving them for restoration).
- lifecycle-management-is-gapless — The system manages belief lifecycle without gaps across all operation types: staleness checking detects all forms of source drift, propagation respects node lifecycle states, and both read and write paths enforce consistent lifecycle semantics — no operation ignores or corrupts lifecycle state.
- metadata-governs-lifecycle-across-read-and-write-paths — Node lifecycle state carried in metadata actively governs both mutation behavior (retracted nodes skipped during truth propagation, sticky retraction surviving recompute) and inspection behavior (staleness checking skips OUT nodes, compact surfaces stale reasons) — a single metadata mechanism controls the system's complete operational surface.