Two-Layer Architecture

Definition

The EFIList position is architecturally two-layered:

1. a structural antinatalist argument grounded on consent-impossibility, asymmetry, and suffering-as-deterrence;
2. a downstream eliminationist / NU superstructure that licenses urgency, duty, and red-button-style advocacy.

The two layers are derivationally distinct: concessions to the diagnostic layer do not entail commitment to the prescriptive layer. Many critiques target Layer 2 and treat the success of that attack as a refutation of Layer 1; this conflates two arguments that share a diagnostic premise but diverge on what the diagnosis licenses.

Operative function: the registered_move serves as the canonical disambiguator when an interlocutor cites Layer-2 commitments (often via a Peterson/Musk-style crypto-violent reading) as evidence against the Layer-1 substrate. The framework’s defenders can concede Layer-2 criticisms without yielding Layer 1.

Etymology & register

Coined construction. Two-Layer — the diagnostic substrate and the prescriptive superstructure are distinct strata, not one continuous position. Architecture — the relation is structural rather than thematic. Register: formal-apparatus, deployed across multiple objection entries as the canonical category-distinction move.

See also

• Framework-vs-Actor Distinction — companion registered_move
• Cascade-Math Safeguard — companion registered_move, Layer-2 self-application rebuttal
• Labor Sine Fructu — Layer-1 characterization anchor
• the Proxy Gamble — one of Layer 1’s nine foundational premises

Appears in

• Library substrate — primary deployment in objections/violence-as-reductio and objections/negative-util-aggregation; touched by nearly every T3+ objection
• Frame — the “How these compose” composition block on /frame/ cites this registered_move as its structural backbone