external-integration-preserves-all-invariants

OUT derived (depth 7)

External beliefs are architecturally safe at ingestion and participate in the same invariant-preserving revision system as all other belief origins — architectural containment and revision parity together ensure external integration cannot corrupt system invariants.

Summary

When beliefs come in from outside the system, they go through the same safety checks and revision processes as internally generated ones. This means importing external knowledge cannot break the system's guarantees, because containment at the point of entry and equal treatment during revision together close off any path to corruption.

Justifications

SL — architectural safety plus revision parity closes the invariant gap for external beliefs

Antecedents (all must be IN):

  • external-integration-is-architecturally-safe — External beliefs are end-to-end safe within the system's architecture: defensively contained at ingestion and lifecycle-managed thereafter (external belief thread) within the same three-layer boundaries and atomic mutation guarantees that protect internal operations (architecture thread).
  • revision-invariants-span-all-origins — Both revision paths (reactive contradiction resolution and proactive dialectical challenge) preserve system invariants across all belief origins — human, LLM, and agent — because invariant preservation flows from shared minimal foundations and all origins share the same deterministic revision engine.

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."
  • derive-agent-count-bug — `_build_beliefs_section` has a bug: `count += len(belief_ids)` is inside the per-belief loop instead of outside it, inflating the count and shrinking the non-agent budget below intended size

Dependents

These beliefs depend on this one:

Details