retraction
17 beliefs (16 IN, 1 OUT)
-
IN
add-nogood-retraction-prefers-least-entrenched
The primary retraction path traces back through justification chains to premises and chooses the one with the lowest entrenchment score (speculative assumptions before evidence-backed observations) -
IN
deferred-retraction-ordering
During agent import, nodes are added and truth values propagated before explicit retractions are applied, ensuring the dependency graph is fully wired before OUT transitions are forced. -
IN
dry-run-prevents-both-retraction-and-metadata
The `dry_run` flag in review-beliefs prevents both truth-value changes (retraction of invalid beliefs) and metadata side-effects (`last_reviewed` timestamp, `review_result` classification), making it fully read-only — extending beyond what `auto-retract-respects-dry-run` covers. -
IN
migrated-retraction-api-enforces-typed-preconditions-j0
review-beliefs: Three specific boundary validations demonstrate a pattern but cannot establish the claim of "consistent error contract at every entry point" without enumerating all entry points. (defeats api-enforces-typed-preconditions justification 0) -
IN
migrated-retraction-architecture-has-no-hidden-fragility-j0
review-beliefs: Two positive safety properties and one gated known fragility cannot prove the universal negative "no hidden consistency hazards" — absence of evidence for other fragilities is not evidence of their absence. (defeats architecture-has-no-hidden-fragility justification 0) -
IN
migrated-retraction-batch-fault-isolation-is-universal-across-llm-operations-j0
review-beliefs: The review antecedent describes per-batch skipping (entire batch dropped on LLM failure), which contradicts the claim of fault isolation at the "individual item level." (defeats batch-fault-isolation-is-universal-across-llm-operations justification 0) -
IN
migrated-retraction-budget-enforcement-is-efficient-across-pipeline-j0
Invalid: universalizes floor bounds to all budget operations when only derive has floor-5 (defeats budget-enforcement-is-efficient-across-pipeline justification 0) -
IN
migrated-retraction-cli-is-pure-delegation-layer-j0
review-beliefs: The claim includes "producing binary exit codes and correct stream separation" which neither antecedent establishes — delegation and flat dispatch do not entail specific exit code semantics or stream routing. (defeats cli-is-pure-delegation-layer justification 0) -
IN
migrated-retraction-compact-budget-controls-output-size-j0
review-beliefs: The first antecedent presupposes budget truncation works ("survive budget truncation") rather than establishing it, making the derivation circular; the summary-hiding antecedent describes a scenario where output grows, not how the budget constrains it. (defeats compact-budget-controls-output-size justification 0) -
IN
migrated-retraction-context-agnosticism-follows-from-minimality-j0
False causal claim: context-agnosticism comes from evaluation purity, not from minimality. They co-occur but are not causally linked. (defeats context-agnosticism-follows-from-minimality justification 0) -
IN
migrated-retraction-critical-operations-converge-to-fixed-points-j0
review-beliefs: Individual convergence of three operations does not establish the system-level claim of reaching stable state "regardless of operation ordering" — without commutativity or serialization guarantees, interleaved operations could produce different fixed points. (defeats critical-operations-converge-to-fixed-points justification 0) -
IN
migrated-retraction-every-mutation-reports-its-effects-j0
review-beliefs: Three mutation-reporting mechanisms are demonstrated but the universal claim "All mutating operations" is not established — add_node, propagate, dedup, and import mutations are not shown to report their effects. (defeats every-mutation-reports-its-effects justification 0) -
IN
migrated-retraction-minimality-produces-uniformity-and-determinism-j0
review-beliefs: Antecedent 1 establishes minimality→uniformity, but antecedent 2 presents minimality and determinism as co-existing properties that are *unified* in the system, not as one generating the other — the BFS fixpoint and conservative failure semantics are independent operational design choices, not consequences of semantic minimality, so the claim that minimality is the 'shared generative root' of determinism is an unsupported causal upgrade from co-occurrence to generation. (defeats minimality-produces-uniformity-and-determinism justification 0) -
IN
migrated-retraction-negative-semantics-are-uniform-through-minimality-j0
Internal contradiction: claims 'permanent identity effects from challenge' but antecedent (negative-semantics-are-complete-reversible-and-recoverable) characterizes negative semantics as fully reversible and recoverable (defeats negative-semantics-are-uniform-through-minimality justification 0) -
IN
migrated-retraction-premise-identity-is-inherently-transient-j0
review-beliefs: The claim references 'dialectical challenge' and 'defend' as transformation mechanisms while the antecedents only establish add_justification, and the 'irreversibly' qualifier is not established — convert-to-premise could reverse the transformation (defeats premise-identity-is-inherently-transient justification 0) -
IN
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. -
OUT
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.