Glossary · C
Cascade-Math Safeguard
Definition
Negative-utilitarian outcome ethics, when actually executed rather than gestured at, structurally rejects real-world unilateral violence on the framework’s own terms. The cascade-math — predictable backlash, terrorism designation, ideological inoculation, traumatized communities, discourse closure — produces more suffering than the act removes.
Adherents who endorse the smaller violence are not running the calculation; they are nodding at a slogan. The framework’s structural safeguard against real-world unilateral acts is the math itself, honestly run.
Operative function: the registered_move surfaces when an interlocutor argues that the framework licenses violence because some adherent gestures at violent action. The rebuttal does not require importing an external constraint; it requires only that the framework’s own consequentialist calculation be carried through honestly, at which point the cascade-math forecloses the violent option from inside the framework.
Etymology & register
Coined construction. Cascade-math — the downstream consequences (backlash, designation, inoculation, trauma, closure) that a unilateral act would set in motion, all of which the consequentialist calculation must include. Safeguard — the math itself functions as the framework’s internal block on the violent option. Register: formal-apparatus, self-application-rebuttal.
See also
- Two-Layer Architecture — this safeguard operates at Layer 2 (the prescriptive / NU layer)
- Framework-vs-Actor Distinction — companion registered_move; paired in the VAR rebuttal
- Censorship-Reversal Trap-Door — companion registered_move, the other half of the policy-register symmetry
Appears in
- Library substrate —
objections/violence-as-reductio(primary), plusslippery-slope-eugenics,policy-proposal