Ultimentality
Home / The Kill-Table

← Ultimentality Wiki

The Kill-Table

The Kill-Table records selected claims, challenges that would change them, and procedures for checking the result. It makes the Falsification Standard concrete by connecting an objection to an actual target and warranted response. Its coverage is a maintained index, not a claim that every possible challenge has been enumerated.

Candidate challenges and established outcomes

The 2026 run account reports candidate challenges to four inventory closures. Their assessment requires the same level and definition as the target: an irreducible additional primitive, an exhibited emergent Force, a corruption outside the proposed taxonomy, or a needed function absent from SPLCW. A proposal described as “not obviously contained” does not yet establish irreducibility.

The Open Proof-Burden records incomplete completeness arguments. It does not automatically classify them as refuted. A demonstrated counterexample changes the claim it actually defeats; the utility and accuracy of the retained cases are evaluated separately.

Closure under review Reported candidate challenge What would establish the kill
Four directional primitives A memory/temporal operation An operation at the same level that cannot be expressed by the existing selection and routing primitives
Two named Forces A cross-axis coupling such as Love with Gratitude A coupled controller with an emergent property not supplied by Submission or Reconciliation
Three named Theodicytes Installed compulsion or an answerable optimizer A corruption whose mechanism is irreducible to the existing categories under the same definition
Five SPLCW roles A needed temporal function absent from the role cycle A function required for the stated participation claim that is not recoverable through the existing roles, including their return path

These entries restore the historical shape of the reported run while keeping its epistemic status accurate: each is a candidate challenge, not an automatic refutation. A completed examination should record its evidence, disposition, and remaining kill-condition here or in a linked scar.

Standing review procedures

Beyond the four count-closures, the table records selected load-bearing claims in the corpus. Every row fixes four things: the target page whose claim is at stake, the valid attack that would refute it, the expected change the corpus must make if that attack lands, and the review procedure for checking whether the failure has recurred. A row is never a prediction that the claim is wrong; it is the precommitment that makes acceptance mean survivable refutation rather than declared safety.

Target page Valid attack Expected change Review procedure
Closure Without Totalization An invalid inference in the closure/completeness distinction, or a correction-path test that accepts immunity or rejects effective answerability Revise the affected argument or operational criterion; a captured formulation does not establish exhaustive coverage Assess coverage and corrective reach separately. Trace relevant evidence to the affected claim; cosmetic edits do not suffice, and scoped completeness does not imply exemption
Self-Verifying, Not Self-Certifying Marking cannot proceed without appeal to an extra-symbolic certifier "Self-verifying" collapses into self-certification or external dependence; verification must be relocated inside the loop Confirm each marking step resolves against an in-system witness with no extra-symbolic access invoked
The Error Mark With Causal Force Recorded error is treated as effective answerability despite a closed path to relevant correction Repair the blocked path or revise the claim of effective answerability; distinguish failure of an implementation from a counterexample to the causal-force requirement Identify the governing target, evidence warranting a change, and a reachable update path. Record warranted revision or justified retention; unchanged behavior in one cycle alone does not establish an ornamental mark
Capture of the Corrective Layer The correcting mechanism is taken over by what it corrects, so corrections now serve the captured interest The corrector's independence claim fails; authority is re-seated and the capture logged as a scar Cross-regulation audit — establish that relevant correction retains effective influence; shared location or internal control alone does not prove capture
The Responsible Successor No successor can continue the project without enforcing sameness of identity on it The continuation/colonization distinction collapses; responsible succession is redefined or abandoned Exhibit one continuation that carries the invariants forward while letting the successor diverge in identity
Refusal as Participation A genuine refusal is redescribable, without remainder, as a form of consent Refusal loses its distinct participatory content; free won't is re-grounded or conceded as consent in disguise Exhibit a refusal that changes the outcome and cannot be re-read as consent without losing information
Postfalsifiability The construction scores every attack — including a real refutation — as further support Postfalsifiability is exposed as self-sealing and demoted; the outcomes of attack taxonomy must keep a live "defeated" verdict Run the self-sealing test — at least one describable attack must be scored a kill, not support
The Minimal Rebuild String A system invariant cannot be regenerated from the kernel string The string is incomplete; the kernel absorbs the missing generator or the compression claim narrows Decompress via the decompression map and diff the regenerated invariants against the standing set
The Meaning-Maker The criterion admits arbitrary causation, failing to separate meaning-making from mere causing The definition adds its distinguishing predicate (meaning as weight) or concedes the collapse Apply the criterion to a plainly non-meaning causal chain and confirm it is excluded
Identity Across Substrates The proposed shared type fails to predict a behavior its identity conditions were meant to preserve Refine the identity conditions or narrow the equivalence claim to the capacities actually preserved Compare instances against the stated capacity profile; distinguish implementation differences from failure to realize the type

Each row is anchored to a two-axis ledger entry in the same way the headline closures are: a kill on the epistemic axis is a kill of the claim as standing, and any mapping the claim carried is scored separately on the alethic axis.

Using the table

These rows describe review procedures, not a suite of automatically executed philosophical tests. A completed review should record its evidence and actual outcome. A hypothetical defeat condition is not a finding that the target has already failed.

The table itself can contain an inaccurate condition or an inappropriate expected change. Correct such a row against its target's meaning and the actual argument. Source authority establishes intended usage; evidence and reasoning establish whether the described challenge succeeds.

Formal status

E: Derived, Exposition of selected review conditions. A: each row should accurately identify its target, relevant challenge, and warranted response. Provenance: maintained review guidance; candidate historical challenges are distinguished from demonstrated outcomes.

See also

Falsification Standard · The 2026 Adversarial Run · Two-Axis Ledger · Open Proof-Burden · Self-Sealing Test · Outcomes of Attack

Linked from (21)