justification-evaluation-is-uniform-and-pure
IN derived (depth 1)
All justification types (SL and CP) use the same validity rule (antecedents IN, outlist OUT), evaluated as a pure function with no side effects
Summary
Regardless of whether a justification represents support or consistency-preservation, the system evaluates all of them with the same simple test and never changes any state while doing so. This means the evaluation logic is predictable and safe to call anywhere without worrying about unintended consequences or type-specific edge cases.
Justifications
SL — Uniform evaluation means the TMS engine has exactly one truth-computation path regardless of justification type
Antecedents (all must be IN):
- cp-and-sl-evaluated-identically — CP and SL justifications use the same validity check in `_justification_valid`; the distinction is semantic (support vs. consistency), not computational.
- justification-valid-is-pure — `_justification_valid` is a pure query with no side effects, no logging, and no mutations to network state
- justification-validity-requires-inlist-in-and-outlist-out — A justification is valid iff all antecedents are IN and all outlist nodes are OUT; this single rule drives retraction cascades, kill-switch behavior, challenges, and supersession
Dependents
These beliefs depend on this one:
- evaluation-purity-grounds-agnosticism-and-minimality — Evaluation purity (uniform, deterministic, no metadata inspection) independently grounds both context-agnosticism (identical results regardless of timing/origin) and semantic minimality (no special-case logic), making them co-occurring consequences of the same architectural choice rather than causally related.
- justification-evaluation-is-context-independent — Justification evaluation produces identical results regardless of evaluation context: it is pure (no side effects), uniform across types (SL/CP use the same validity rule), and temporally invariant (attaching a justification at creation or later yields the same truth outcome) — making truth computation fully context-free
- justification-timing-is-irrelevant-to-evaluation — Justification evaluation produces identical truth semantics regardless of when a justification is attached: add_node evaluates justifications immediately at insertion, and add_justification triggers identical propagation when attached post-creation — the system has no time-of-attachment sensitivity.
- tms-core-is-crash-safe — The TMS core provides crash-free truth maintenance: deterministic termination, pure evaluation, and conservative failure semantics ensure correct results across all reachable nodes.
- tms-core-is-deterministic-and-conservative — The TMS engine produces deterministic, terminating truth maintenance through uniform pure evaluation, guaranteed convergence, and conservative asymmetric failure semantics for missing nodes.
- truth-semantics-are-emergent-and-uniform — Truth maintenance semantics are fully emergent from simple uniform rules: premise behavior arises from empty justification lists, evaluation is pure and type-agnostic across SL/CP, and node truth is a clean disjunction-of-conjunctions — no special cases exist anywhere in the evaluation path.