defeat-reversals-are-lifecycle-governed

IN derived (depth 5)

All outlist-based defeat reversals (challenge, kill-switch, supersession) operate within metadata-enabled lifecycle governance — every reversal produces not just a truth-value change but a fully governed lifecycle transition with metadata-tracked state (retraction flags, stale reasons, access tags), ensuring reversals are first-class lifecycle events rather than bare truth flips.

Summary

When a belief gets defeated — whether by being challenged, superseded, or killed — the system doesn't just flip it from true to false. It treats every such reversal as a full lifecycle event, recording metadata like retraction flags and staleness markers. This means reversals are always traceable and governable, not silent truth-value changes, because the same metadata system that controls how beliefs propagate also tracks how and why they were reversed.

Justifications

SL — reversible defeats + metadata governance = reversals are governed lifecycle transitions

Antecedents (all must be IN):

  • all-defeat-mechanisms-are-reversible — Every outlist-based defeat operation (challenge, kill-switch, supersession) is inherently reversible because outlist semantics flip truth values without deleting nodes
  • metadata-provides-extensible-lifecycle-governance — Node metadata is simultaneously the universal extension mechanism for network state (carrying all structured lifecycle properties with consistent audit tracking) and the active governor of truth propagation behavior across both read and write paths — retracted and stale nodes are skipped in propagation and staleness checking respectively, driven by the same metadata fields.

Dependents

These beliefs depend on this one:

Details