all-external-inputs-produce-correct-state
OUT derived (depth 4)
Both external input pathways (LLM derivation and multi-agent import) produce a fully correct persisted network state — bounded validation prevents invalid beliefs, namespace isolation prevents cross-contamination, and layered reconciliation handles all truth states — provided the agent count bug is fixed and missing source files are detected.
Summary
Every way that outside data enters the system — whether generated by an LLM or imported from another agent — should result in a valid, consistent knowledge graph, thanks to input validation, namespace isolation, and reconciliation logic. This claim is currently retracted because it depends on an agent count bug being fixed and missing source file detection being added, neither of which is confirmed complete.
Justifications
SL — External paths are structurally safe but the agent-count bug inflates token budgets and silent missing-file handling creates undetectable staleness — both must be resolved for full correctness
Antecedents (all must be IN):
- llm-mutations-are-bounded-end-to-end — LLM-driven belief derivation is bounded at every stage of the pipeline: input validation (fail-soft filtering, Jaccard retraction guard, environment isolation), atomic persistence (context-managed load/save), and output propagation (deterministic terminating BFS with lifecycle-aware traversal).
- multi-agent-safety-spans-all-layers — Multi-agent operation is safe across the full system: agent isolation prevents cross-contamination between namespaces with reversible lifecycle control, while data integrity is enforced across all three architectural layers through clean boundaries and snapshot persistence.
Unless (any of these IN defeats this justification):
- 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
- 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."