retraction-cascade-is-transitive-and-terminating

IN derived (depth 3)

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.

Summary

When a belief is retracted, the effects ripple out through every downstream conclusion that depended on it, no matter how far removed — not just the immediate neighbors. This cascade is also engineered to always finish cleanly, using breadth-first traversal and short-circuiting on unchanged values, so it can never loop forever or spiral out of control.

Justifications

SL — Transitive reach ensures thoroughness; safe termination ensures bounded execution — together the cascade is both complete and safe

Antecedents (all must be IN):

  • api-retract-cascade-is-transitive — `api.retract_node()` propagates OUT to all transitively dependent SL-derived nodes, not just direct children — retracting a root premise retracts the entire downstream chain.
  • propagation-is-safe-and-terminating — Truth propagation is both lifecycle-safe and guaranteed to terminate: retracted nodes are skipped, trigger nodes are never recomputed, BFS prevents stack overflow, and stop-on-unchanged prevents oscillation — propagation respects every node state it encounters.

Dependents

These beliefs depend on this one:

Details