external

22 beliefs (5 IN, 17 OUT)

• OUT external-belief-ingestion-is-defensively-layered
  External beliefs enter the system through defensively-layered pipelines regardless of source: LLM derivation applies fail-soft validation, Jaccard retraction guards, and environment isolation, while agent import provides dual reconciliation modes with heterogeneous truth state handling — both converge on the same underlying mutation infrastructure.
• OUT external-beliefs-achieve-integration-parity
  External beliefs achieve full parity with internal beliefs: they are managed across their complete lifecycle with no gap between any management phase AND participate in the same deterministic revision engine as all other belief origins — external provenance is a property of ingestion, not of ongoing maintenance.
• OUT external-beliefs-achieve-total-integration
  External beliefs achieve total integration along all quality axes simultaneously: grounded across every invariant dimension (origin, time, structure), participating in all correction mechanisms with full auditability, and fully equivalent to internal beliefs — no property distinguishes external from internal.
• OUT external-beliefs-are-correctable-and-invariant-equivalent
  External beliefs achieve full parity along two independent quality axes: invariant equivalence ensures they participate in the same consistency guarantees as internal beliefs, while origin-spanning auditability ensures they are fully correctable with complete traceable history.
• OUT external-beliefs-are-fully-invariant-grounded
  External beliefs achieve complete invariant equivalence with internal beliefs, and those invariants are anchored along all three dimensions — origin, temporal, and structural — meaning external integration participates in the system's deepest invariant guarantees, not merely surface-level safety.
• OUT external-beliefs-are-invariant-equivalent
  External beliefs achieve complete equivalence with internal beliefs at every system level: they participate in identical invariant-preserving revision systems and achieve full behavioral integration parity — the system provides no mechanism to distinguish external from internal beliefs in terms of protection or management.
• OUT external-beliefs-defensively-contained
  External beliefs pass through two independent safety layers: defensive ingestion pipelines (fail-soft validation, Jaccard guards, dual import/sync reconciliation modes) filter and validate beliefs on entry, while the self-contained agent subsystem (namespace isolation, relay-pair kill-switches, reversible lifecycle management) constrains their operational footprint after ingestion.
• IN external-deps-become-premises
  A claim whose `depends_on` references are all absent from the beliefs file gets no justifications and is added as a premise (IN by default).
• OUT external-ingestion-is-format-resilient-and-defensively-layered
  External belief ingestion achieves both defensive containment (fail-soft validation, Jaccard retraction guards, dual import/sync reconciliation, namespace isolation) AND format resilience (parser version fallback, forward-compatible metadata parsing, prose-tolerant JSON extraction), ensuring robust integration even as external source formats evolve unpredictably.
• OUT external-ingestion-is-resilient-and-convergent
  External belief ingestion achieves end-to-end reliability through two complementary properties: format resilience absorbs syntactic variation at the parsing boundary (dual parser versions, schema migration tolerance, prose-tolerant JSON extraction with defensive layering), while deterministic convergence ensures consistent final state through fixpoint reconciliation regardless of input ordering or repeated application.
• OUT 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.
• OUT external-integration-is-hardened-and-boundary-controlled
  LLM integration achieves production-grade robustness (bounded execution, fail-soft error handling, process isolation, fault tolerance) while information boundaries are controlled at every level (authorization gating, budget constraints, defensive ingestion) — the system neither leaks sensitive information outward nor admits unvalidated beliefs inward.
• OUT external-interface-is-bidirectionally-bounded
  The system's interaction with external systems is bounded in both directions: output is budget-limited through accurate token estimation ensuring context windows are respected, and input drift is comprehensively detected through staleness checking — no unbounded data flows cross the system boundary.
• OUT external-surface-is-fully-controlled
  The system's external surface is fully controlled along independent axes: bidirectional bounds constrain output size (token budgets) and input quality (staleness detection), while defensive containment layers (validation pipelines, namespace isolation) prevent external beliefs from violating internal invariants.
• OUT external-surface-is-verified-and-trust-bounded
  The complete external-facing surface achieves both structural verification (pure delegation with hermetic tests and fault tolerance across all information paths) and comprehensive trust enforcement (architectural self-containment with information flow control at every boundary) — no external interaction bypasses either the verification chain or trust controls.
• OUT external-surface-is-verified-trust-bounded-and-bidirectionally-controlled
  The system's complete external perimeter achieves defense-in-depth through three independently-established properties: structural verification (pure delegation with hermetic tests), trust boundaries (self-containment and defensive ingestion), and bidirectional flow control (token budgets constraining output, hardened LLM integration constraining input) — no external interaction bypasses all three layers.
• OUT internal-and-external-integrity-are-unified
  Every operation — internal mutations (atomic transactions, deterministic propagation) and external belief ingestion (defensive validation, environment isolation, agent containment) — maintains end-to-end integrity through complementary safety mechanisms.
• IN migrated-retraction-external-belief-ingestion-is-defensively-layered-j0
  review-beliefs: The claim that both paths "converge on the same underlying mutation infrastructure" is not stated in or derivable from either antecedent — each antecedent describes its own defense mechanisms without addressing shared infrastructure. (defeats external-belief-ingestion-is-defensively-layered justification 0)
• IN network-has-zero-external-dependencies
  The Network class imports only stdlib (`collections.deque`, `datetime`) plus package data types (`Node`, `Justification`, `Nogood`); it has zero external dependencies.
• IN network-no-external-deps
  `network.py` depends only on stdlib (`deque`, `datetime`) and project dataclasses; it has zero external package dependencies.
• OUT origin-agnostic-loop-grounds-external-invariants
  External beliefs achieve complete invariant grounding along all three dimensions (origin, time, structure) precisely because the closed maintenance loop operates origin-agnostically — the loop's indifference to belief provenance is the mechanism that delivers invariant parity to external beliefs.
• IN project-has-zero-external-coupling
  The project enforces zero external coupling at both the packaging level (empty `dependencies` list in pyproject.toml) and the implementation level (core Network class uses only stdlib imports), eliminating supply-chain risk and simplifying deployment.