all-exceptions-are-safely-handled
IN derived (depth 5)
The system handles both automated exceptions (contradictions triggering dependency-directed backtracking) and manual challenges (irreversible premise-to-justified transformation via dialectics) safely — exceptional conditions from any origin reach correct truth states through deterministic propagation, and no exception pathway corrupts network consistency.
Summary
Whether an error comes from an automatic contradiction detected by the system or from a manual challenge issued through the dialectical process, the system reaches a correct and consistent state. This matters because it means no exceptional situation, regardless of how it originates, can leave the truth network in a corrupted or inconsistent condition.
Justifications
SL — both automated and manual exceptions converge on deterministic propagation (depth-5 GATE from depth-3 + depth-4 GATE)
Antecedents (all must be IN):
- tms-handles-all-conditions-safely — The TMS core handles both normal operation (crash-free truth propagation via BFS with stop-on-unchanged) and exceptional conditions (deterministic contradiction resolution via backtracking with least-entrenched selection) through shared propagation infrastructure — no reachable execution state leads to undefined behavior.
- dialectical-transformation-is-fully-reliable — The irreversible premise-to-justified transformation during challenge is both semantics-preserving (the resulting node inherits complete outlist evaluation with conjunction, absence, and persistence semantics) and crash-safe (recursive dialectical chains terminate deterministically), making dialectical operations reliable despite their irreversibility.
Unless (any of these IN defeats this justification):
- propagate-assumes-dependents-exist — Every ID in `node.dependents` is accessed via `self.nodes[dep_id]` without a membership check; a dangling dependent reference will raise `KeyError` — this is intentional (broken invariant = bug)
Dependents
These beliefs depend on this one:
- exception-safety-spans-tms-and-source-lifecycle — The system handles failures safely across both domains: the TMS core resolves exceptional conditions (contradictions via backtracking, challenges via deterministic propagation) while the source integrity pipeline handles its failure modes (missing files, changed content, deleted sources) — no exception in either domain can produce inconsistent or undefined state.
- revision-is-exception-safe-and-recoverable — Every revision mechanism — whether normal (outlist defeat, dialectical challenge/defend) or exceptional (contradiction-triggered backtracking, graph inconsistency) — is simultaneously safe (handled without crashes or corruption), traceable (producing deterministic artifact trails), and recoverable (providing guided restoration hints for cascade victims) — the system never enters an unobservable or unrecoverable state regardless of failure mode.
- system-is-self-correcting-and-exception-proof — The system is both actively self-correcting (maintaining consistency through the derive pipeline for new beliefs and staleness detection for existing ones) and passively exception-proof (handling contradictions through deterministic backtracking and challenges through reliable dialectical transformation) — providing comprehensive fault tolerance that covers both anticipated maintenance and unanticipated disruptions.