staleness-is-surfaced-despite-binary-truth-model
IN derived (depth 3)
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.
Summary
When a belief goes stale, that fact travels cleanly from the internal reasoning engine all the way out to external tools like CI pipelines, with zero information loss along the way. The system achieves this even though it only tracks simple in-or-out states internally, by carrying staleness details as metadata and emitting them as structured, deterministic output that machines can parse directly without any glue code.
Justifications
SL — The binary truth model threatens to erase staleness nuance, but metadata preservation at the representation layer and deterministic output at the interface layer jointly ensure full-fidelity staleness surfacing.
Antecedents (all must be IN):
- staleness-information-survives-binary-truth-model — 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.
- staleness-output-is-ci-pipeline-ready — Staleness checking produces deterministic, uniformly-structured, machine-parseable output with conservative non-mutating semantics and nonzero exit codes, making it directly consumable by automated CI pipelines without wrapper scripts
Dependents
These beliefs depend on this one:
- metadata-enables-lifecycle-governance-beyond-binary-truth — Node metadata enables lifecycle governance capabilities that transcend the binary IN/OUT truth model: extensible metadata provides structured lifecycle state (retraction flags, stale reasons, access tags, supersession markers) that actively governs both read and write paths, while staleness information is preserved and surfaced in compact output despite having no dedicated truth state in the TMS data model.