staleness-output-is-ci-pipeline-ready
IN derived (depth 2)
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
Summary
The staleness checker is ready to drop straight into a CI pipeline with no glue code needed. Its output is sorted, consistently structured, and machine-parseable, it never changes any data, and it returns nonzero exit codes on failure — so a simple pipeline step can run it and trust the result without wrappers or post-processing.
Justifications
SL — Deterministic structured output combined with CI-gate semantics yields pipeline-ready staleness checking
Antecedents (all must be IN):
- check-stale-output-is-deterministic-and-structured — Staleness checking produces deterministic (sorted by node ID), uniformly structured (consistent 6-key schema across all result types), and exception-free (returns structured dicts for missing files rather than raising) output suitable for programmatic consumption and diffing.
- 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
Dependents
These beliefs depend on this one:
- all-read-paths-are-deterministic-and-resilient — Every read-path operation produces deterministic output resilient to environmental variation: search handles missing FTS5 indexes via self-healing derived indexes and substring fallback, staleness checking produces sorted uniformly-structured CI-pipeline-ready results, and compact generates predictable bounded output from a pure function with fixed priority ordering.
- 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.
- system-output-is-complete-bounded-and-ci-ready — The system's two primary output mechanisms — compact belief summaries and staleness reports — both meet production standards: structurally complete with priority ordering, predictably bounded by token budgets, and CI-pipeline ready with deterministic sorted output, nonzero exit codes, and machine-parseable schemas.