staleness-information-survives-binary-truth-model
IN derived (depth 1)
Despite the TMS using binary IN/OUT truth values with no distinct STALE state, staleness information is preserved end-to-end: stale beliefs are mapped to OUT on import with stale_reason metadata, and the compact output surfaces this metadata for OUT nodes — so downstream consumers can distinguish intentional retractions from staleness-driven ones.
Summary
Even though the system only tracks beliefs as either active or inactive with no special "stale" category, staleness information still makes it through the whole pipeline without being lost. When stale items come in they get marked inactive with a note explaining why, and when results go out that note is included, so anything reading the output can tell the difference between something that was deliberately removed and something that just went stale.
Justifications
SL — Metadata carries staleness semantics that the binary truth model cannot express, from import through output
Antecedents (all must be IN):
- stale-maps-to-out-on-import — Nodes marked `[STALE]` in beliefs.md are stored with truth value OUT during both initial import and subsequent syncs
- compact-surfaces-stale-reason-metadata — OUT nodes with `stale_reason` in their metadata include the reason string in the compact output.
Dependents
These beliefs depend on this one:
- staleness-is-surfaced-despite-binary-truth-model — Staleness information not only survives the binary IN/OUT truth model (via metadata-based preservation through import and compact surfacing) but also emerges as deterministic, uniformly-structured, machine-parseable CI output with conservative non-mutating semantics — no information is lost between the TMS representation and the external consumer.