external-belief-lifecycle-is-complete
IN derived (depth 3)
The system manages external beliefs across their full lifecycle: import/sync provides dual reconciliation modes with heterogeneous truth state handling and namespace auto-wiring, while staleness checking detects source drift for CI gating — beliefs are tracked from initial ingestion through ongoing validity monitoring.
Summary
When beliefs are brought in from outside sources, the system handles the entire journey from start to finish. It can import and synchronize them using two different modes that correctly deal with varying truth states and automatically organize them into namespaces to avoid conflicts. Once imported, it keeps watching for drift between the belief and its original source, providing a safe check that can block a CI pipeline if something has gone stale. Together, this means external knowledge is not just ingested once and forgotten — it is actively maintained.
Justifications
SL — Import reconciliation (depth-2) + staleness CI gate (depth-1) span the full lifecycle, but silent skipping of missing source files creates a gap in drift detection
Antecedents (all must be IN):
- import-provides-complete-reconciliation — The import subsystem provides complete reconciliation coverage: heterogeneous truth states are handled correctly on initial load, dual modes support additive import and remote-wins sync for different operational needs, and the colon-based namespace convention with auto-wiring prevents ID collisions across agents.
- 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
Unless (any of these IN defeats this justification):
- missing-source-file-is-silent — If a node's source file no longer exists on disk, `check_stale` silently skips it; callers cannot distinguish "file deleted" from "file never tracked."
Dependents
These beliefs depend on this one:
- external-beliefs-are-defended-and-lifecycle-managed — External beliefs are managed end-to-end across a complete trust boundary: defensively contained at ingestion through layered validation pipelines and namespace isolation, then actively lifecycle-managed through dual reconciliation modes, staleness detection against source material, and CI gating — no phase of external belief existence lacks oversight.
- external-lifecycle-is-complete-and-automatically-maintained — External beliefs achieve both complete lifecycle management (dual reconciliation modes with heterogeneous truth state handling and staleness detection) and automated ongoing maintenance (idempotent sync with cascade preservation and full source staleness coverage), enabling zero-touch external belief management