Refusal explorer

The framework records, for each refusable claim, what refusing it costs and what remains standing. This page lets you select the ones you reject and read the result together. Registers of Claim explains why refusal restores a gap rather than silently preserving the same verdict, and why refusal is not the same as defeat.

Two limits worth stating before you use it. Refusal records describe dependency, not truth: nothing here certifies a premise. And the typed relation graph that produces the “also falls” results is opt-in: of the 77 claims you can select below, 32 currently have any recorded downstream consequence, so for the remaining 45 this page can show you the author’s written cost and no computed result. An absent consequence means nothing was recorded, not that nothing follows.

The corpus’s 25 worked cases give a second, more concrete answer: refusing a premise a case names either removes that case’s verdict, leaves it undetermined, or leaves it standing on the case’s other machinery. 74 of 87 case–principle pairs now declare which; the remaining 13 sit on claims that are not refusable, so no effect could ever fire for them.

What this cannot tell you. A case responds only to the machinery its own entry names. It does not trace the full chain a verdict rests on, because that chain is not recorded anywhere. So a case shown as unaffected is unrecorded, not defended: refuse the party floor and exactly one case moves, though very little in the framework in fact survives without it. Read the counts as this corpus’s bookkeeping about itself, which is what they are, and not as a survival result.

Loading the refusal records…