Invite Counter Evidence

slug: invite_counter_evidence element_type: PRINCIPLE mutability: IMMUTABLE inline: true current_version: 1 contentURI: null

Every scream invites verifiable counter-evidence through publicly accessible channels. The protocol does not claim final word on contested matters; it publishes its position and the explicit path by which others may dispute. Refusing, hiding, or hostilizing the counter-channel violates the principle and renders the scream constitutionally non-compliant.

What this principle operationalizes

The structural commitment to falsifiability at the communication layer. A constitutional protocol that screams but blocks rebuttal is just another authority. Scream Protocol refuses that posture by structural design: every output ends with the path to disagree, and that path is treated with constitutional dignity, not adversarial hostility.

Concrete patterns

Every scream must include one or more of:

• Direct reply channel with reasonable response expectation (e.g., Twitter replies open, comments enabled, email available)
• Explicit counter-publication invitation ("Disagree? Publish your evidence — link it back here.")
• Falsifiability conditions ("This claim is wrong if [X, Y, Z]. If you can show those, we'll retract.")
• Linkable forum thread on leviathan.life/forum for sustained dispute
• On-chain dispute mechanism when claim is constitutional (proposal to dispute ratification)

What this principle rejects

• One-way broadcast — posts without dispute channels
• Comment lockdowns unless harassment-specific
• Block-and-move-on as default adversarial pattern
• Burden-of-proof inversion — demanding counter-evidence meet impossible bars while own claim was casually receipted
• Counter-channel hostility — treating disputers as enemies rather than as participants in the same epistemological commitment

Why immutable

Without invite-counter, Scream becomes propaganda. Propaganda is loud assertion without dispute path. The federation's whole architecture (validators, falsifiability, fork-freedom) rests on disagreement being a first-class operation, not a tolerated externality. Replacing this principle replaces the federation.

Operational example

Bad scream pattern (constitutional violation):

"Company X is unethical. The data is overwhelming."

Good scream pattern (constitutional):

"Company X's pet food line shows [specific welfare pattern Y] in [N] independent observations [link to dataset]. Methodology: [link]. Counter-analysis welcome: same methodology applied to the same population should yield comparable results — if it doesn't, we'll examine our framing. Reply with your replication."

The second invites dispute by structural design. The first hides behind weight of assertion.

Related elements

• scream_truth_only (IMMUTABLE) — parent principle
• receipts_mandatory (IMMUTABLE) — counterpart: positive claims sourced
• attack_response_protocol (LOCKED) — special case: when attacks come, response is constitutional