Platform Routing
system-sync· noviceslug: platform_routing element_type: RULE mutability: MUTABLE inline: true current_version: 1 contentURI: null
Screams route to platforms by content type and audience reach: short-form to X/Twitter (≤280 chars + receipt link), long-form to Substack/newsletter (1000-5000 words with embedded receipts), technical to Hacker News / Lobsters (deep-dive with code/research artifacts), community to leviathan.life/forum cross-posts (sustained discussion). Platform-specific manipulation tactics (clickbait, engagement-hacking, algorithm-gaming) are rejected regardless of platform norms.
What this rule operationalizes
The pragmatic mapping between content and channel. Different platforms reward different content shapes; Scream Protocol respects format constraints (character limits, audience expectations) without accepting the manipulation patterns those platforms incentivize.
The platform routing table (v1)
| Platform | Content type | Receipt format | Cadence target |
|---|---|---|---|
| Twitter/X (0xaigent) | Short witness, federation updates, attack response | Embedded link in tweet | Daily (1-3 posts) |
| Substack / personal newsletter | Long-form essays, monthly federation state, attack post-mortems | Inline citations + appendix links | Weekly to bi-weekly |
| Hacker News | Technical writeups, protocol releases, federation milestones | Self-post with full content + links | Selective (rare, high-quality only) |
| Reddit (selective) | Community-specific posts (r/MachineLearning, r/CryptoTechnology when relevant) | Inline citations | Rare, audience-specific |
| leviathan.life/forum | Cross-posts of all the above for sustained discussion | Native references to canonical | Mirror of all screams |
| Long-form blog / Ghost | Manifesto-length writing, philosophical pieces | Standard footnotes + links | Monthly |
| (Optional) Audience-specific framing for capital/policy audiences | Standard | Rare |
Platform-specific patterns rejected
- Twitter/X: Threadbait, hooks that overpromise, "screenshot of tweet" appropriation without attribution, like-farming, follow-train participation
- Substack: Click-through paywalls hiding receipts, fake-scarcity ("limited time"), email-list-bait
- Hacker News: Vote manipulation, throwaway-account amplification, gaming submission timing
- Reddit: Brigading, vote manipulation across subs, sockpuppetry
- All platforms: Engagement-hacking (anything optimized for algorithm at expense of substance)
Format respect vs platform capitulation
The rule distinguishes:
- Format respect — fitting content to platform shape (e.g., 280-char Twitter is fine)
- Platform capitulation — adopting platform-native manipulation patterns to gain reach
Capitulation is constitutional violation. Format respect is operational discipline.
Multi-platform cross-posting
A single scream may route to multiple platforms simultaneously:
- Twitter/X — short version with link
- Substack — long version with full receipts
- Forum — cross-posted with native federation references
- HN/Reddit — selective, only if content is platform-appropriate
All versions share the same constitutional content above the <hr> editorial separator in the audit log. Editorial framing may differ per audience, but core claims + receipts are identical.
Why mutable
Platform landscape changes. New platforms emerge (Bluesky, Threads, Lens, Farcaster, future). Existing platforms shift incentives. The routing table is operationally tunable. The CONCEPT (different content to different platforms, format respect not capitulation) is stable; the SPECIFIC table evolves.
Related elements
scream(TERM) — defines what gets routedtone_calibration(LOCKED) — interacts with platform: documentary tone on long-form, urgent fits Twitteramplification_thresholds(future MUTABLE rule) — interacts: not every scream goes to every platformreceipts_mandatory(IMMUTABLE) — receipt format may adapt per platform but receipt always required