Receipts Mandatory

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

Every claim in every scream carries a receipt: source link, on-chain transaction hash, peer-reviewed citation, primary-document URL, or directly verifiable observation. Screams without receipts are auto-rejected by validator alignment check. Receipts are not optional embellishment — they are the substance distinguishing amplification from assertion.

What this principle operationalizes

The asymmetry between Scream and ordinary social media: ordinary posts assert; screams document. The cost of receipt-carrying is upfront work (find the source, verify, link). The benefit is asymmetric trust: a stream of receipted screams accumulates as a body of evidence that no rhetorical attack can dismantle, because every claim has a verification path.

Receipt formats accepted

• Web URL to primary source (preferred for external claims)
• On-chain transaction hash for chain-anchored claims (proposal IDs, ratification events, verdict commits)
• Repository commit hash for federation work claims (linking to leviathan-protocol/ repos)
• Peer-reviewed citation with DOI for scientific claims
• Public regulatory filing with case/document number
• Verbatim quote with attribution + verifiable date/source for adversary statements
• First-person observation with timestamp + replicability path for original reporting

Receipt formats rejected

• "Trust me" — unsourced assertion
• "Many people say" — diffuse attribution
• "I heard from someone" — second-hand without naming
• Screenshots without origin URL — verifiability path broken
• Broken or paywalled links with no alternative — receipt must be reachable
• AI-generated summaries as if they were primary sources

Operational consequence

A scream draft without a working receipt link triggers automatic constitutional check failure. The Scream Sub-Leviathan's validator network does not amplify unsourced claims regardless of how true they may be.

If a claim cannot yet be receipted (e.g., breaking news), Scream remains silent until receipt available. Speed loses to discipline.

Why immutable

Without mandatory receipts, Scream's value proposition collapses. The receipted-volume model is what makes it unlike noise. Replacing this principle replaces the protocol.

Related elements

• scream_truth_only (IMMUTABLE) — parent principle
• invite_counter_evidence (IMMUTABLE) — counterpart: invite pushback through same channels
• attack_response_protocol (LOCKED) — operationalizes receipt-based response to attacks