retraction-reporting-reflects-complete-cascades

OUT derived (depth 4)

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.

Summary

When a belief is retracted, the system should report every downstream truth-value change and suggest which affected nodes can be restored — and it does, as long as the internal dependency index tracks all relationship types including outlists. If outlist relationships are missing from the index, some cascade victims will silently go unreported, creating a gap between what actually changed and what the caller is told changed.

Justifications

SL — Reporting completeness (depth-2) and cascade transitivity (depth-3) together guarantee full-fidelity retraction reporting — but the accuracy of "all affected nodes" depends on the dependents index being complete for all reference types.

Antecedents (all must be IN):

  • retraction-effects-are-reported-with-recovery-guidance — Every retraction provides both complete effect reporting (structured before/after diffs for all mutating operations, full changed set) and surgical recovery guidance (restoration hints targeting only cascade victims with surviving premises, excluding the directly retracted node), giving callers full situational awareness and actionable recovery paths from a single operation.
  • retraction-cascade-is-transitive-and-terminating — Retraction cascades are both transitive in reach (propagating OUT to all transitively dependent SL-derived nodes, not just direct children) and guaranteed to terminate safely (BFS prevents oscillation, retracted nodes are skipped, and the cascade stops when no truth values change) — ensuring thorough impact without risk of runaway propagation.

Unless (any of these IN defeats this justification):

  • outlist-nodes-not-in-dependents-index — 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.

Dependents

These beliefs depend on this one:

Details