outlist-nodes-not-in-dependents-index
OUT premise — entries/2026/04/24/defect-resolution-clean-network.md
Reason OUT: Fixed in PR #31 (commit 5316c1a, 2026-04-23) — _rebuild_dependents, add_node, and add_justification now track outlist nodes
Outlist nodes are not tracked in the `dependents` index, so when an outlist node is retracted (goes OUT), dependent GATE beliefs are not enqueued for re-evaluation by `_propagate` — requiring manual `reasons assert` as a workaround.
Summary
When a node is added to an outlist (meaning the gate should activate if that node goes OUT), the system does not register it in the dependency tracking index. This means retracting an outlist node does not automatically trigger re-evaluation of any gate that depends on its absence, breaking the expected propagation behavior and forcing users to manually reassert affected gates.
Dependents
These beliefs depend on this one:
- IN all-truth-effects-propagate-through-outlist-paths — All truth effects — both incremental truth changes and outlist-based defeat reversals — propagate completely through outlist-connected paths without requiring full network recomputation, ensuring outlist-based non-monotonic reasoning achieves the same incremental efficiency as antecedent-based reasoning
- IN any-mode-expansion-propagates-completely — When any_mode expands a conjunctive justification into per-premise disjunctive justifications, each resulting justification inherits the complete outlist specification (conjunction semantics, absence tolerance, persistence across save/load), and all resulting truth-value changes propagate completely to every affected dependent — but only when outlist nodes are tracked in the dependents index, ensuring outlist-mediated effects are not silently dropped.
- IN dedup-reflects-complete-dependency-graph — Deduplication survivor selection accurately reflects the complete dependency graph — the node with the most dependents survives each cluster, and that dependent count includes both antecedent-based and outlist-based dependency edges, ensuring the structurally most-connected node is always preserved.
- IN defeat-reversal-propagates-automatically — All outlist-based defeat mechanisms (challenge, kill-switch, supersession) not only reverse in principle but propagate recovery automatically through safe terminating BFS — when a defeating node is retracted, the outlist entry becomes satisfied, and propagation cascades truth-value restoration to all affected nodes without manual re-assertion
- IN defeat-reversal-with-guided-recovery — All defeat mechanisms (challenge, kill-switch, supersession) are reversible through outlist semantics, and the system provides surgical restoration hints for cascade victims with viable recovery paths — enabling guided recovery from retraction cascades where multi-premise justifications have surviving premises.
- IN dependency-tracking-is-complete-for-all-reference-types — The dependents index fully tracks all relationship types — both antecedent references and outlist references — enabling complete incremental propagation for every truth value change without requiring periodic full recompute as a fallback
- IN incremental-propagation-is-fully-complete — Incremental truth propagation reaches every node whose truth value should change — including nodes that depend via outlist entries — without requiring periodic full recomputation, because safe terminating BFS traversal operates over a dependents index that tracks both antecedent and outlist relationships.
- OUT propagation-automatically-cascades-on-all-truth-changes — Truth propagation automatically cascades to all dependent nodes whenever any node's truth value changes, including nodes that appear only in outlists — making GATE belief re-evaluation fully automatic with no manual intervention required after outlist node retraction.
- OUT retraction-reporting-reflects-complete-cascades — The retraction reporting system provides accurate effect coverage across all cascade paths — structured before/after diffs capture every truth-value change, restoration hints target only cascade victims with surviving premises, and the cascade itself transitively reaches all dependent nodes — but only when the dependents index tracks all relationship types including outlists, ensuring no outlist-mediated cascade victims produce unreported effects.