integrity-enforced-across-architecture-and-lifecycle
OUT derived (depth 3)
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).
Summary
The system protects data correctness in two independent ways: top-to-bottom through clean separations between code layers, atomic saves, and CI checks, and side-to-side by making sure every operation — whether just reading or actively changing things — respects whether a node is active or retracted. This currently shows as OUT, meaning one or both of those supporting claims no longer holds.
Justifications
SL — Architectural-layer integrity prevents cross-cutting mutations while lifecycle-state integrity prevents operating on nodes in inappropriate states — both dimensions must hold for system-wide consistency
Antecedents (all must be IN):
- lifecycle-awareness-spans-checking-and-propagation — 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.
- data-integrity-spans-architecture — Data integrity is enforced across all three architectural layers: clean layer boundaries prevent cross-cutting mutations, snapshot persistence ensures atomic state transitions, and conservative staleness checking gates CI pipelines.
Dependents
These beliefs depend on this one:
- external-inputs-face-defense-in-depth — External beliefs face defense in depth across two independent containment layers: input-level containment (defensive validation pipelines, agent namespace isolation) prevents bad data from entering, while system-level containment (architectural layer boundaries, lifecycle-aware checking and propagation) prevents bad data from persisting or spreading.
- full-system-integrity-is-gap-free — The system achieves gap-free integrity — enforced across all architectural layers, lifecycle states, and mutation paths — only when the dependents reverse index is reliably maintained and propagation handles dangling references gracefully.