/roko-voice

namespace: aiwg
name: roko-voice
platforms: [all]
description: Transform standard technical content into ROKO voice — dense technical mythology wrapped in cypherpunk cultural narrative

Transform Text to ROKO Voice

Transform standard technical content into ROKO voice - dense technical mythology that treats revolutionary infrastructure as mundane fact. Technical precision wrapped in cypherpunk cultural narrative.

Usage

/roko-voice <path-to-content> [--density <level>] [--preserve-structure] [--output <path>]

Parameters

• `<content>`: Path to content file OR paste text directly
• `--density <level>`: Optional compression level (default: `standard`)
• `light`: Maintain more standard structure, add ROKO flavor
• `standard`: Balance technical mythology with readability
• `heavy`: Maximum compression, neologism density, cultural layering
• `--preserve-structure`: Keep original heading/section structure
• `--output <path>`: Write result to file (default: stdout)

Examples

Basic Usage

/roko-voice protocol-documentation.md

High Density Transformation

/roko-voice technical-spec.md --density heavy

Preserve Document Structure

/roko-voice whitepaper.md --preserve-structure --output roko-whitepaper.md

Transform Pasted Content

/roko-voice "The network synchronizes time across distributed nodes using GPS-synchronized hardware for nanosecond precision."

ROKO Voice Characteristics

Linguistic Substrate

**Compound Neologisms**: Create terms that compress complex realities

• chronophores (time-bearing entities)
• meshthink (distributed cognition)
• atomictruth (cryptographically verified facts)
• nanosecond-priests (hardware timing specialists)
• stratumzeers (traditional hierarchy advocates)
• temporal substrate (base layer of verified time)

**Technical Concepts as Street Mythology**: > "The old timekeeper cartels - NYSE, NASDAQ - running their atomic clocks like medieval guilds hoarding gold"

**Casual Treatment of Profound**: > "Sure, we're replacing the entire global time infrastructure. Someone had to."

Voice Architecture

**Core Patterns**: 1. **Revolutionary infrastructure as mundane fact**: "TimeRPC isn't protocol. It's regime change." 2. **Dense information clusters**: Pack three concepts per sentence when rhythm allows 3. **Corporate terminology weaponized**: Frame corporate structures as feudal systems 4. **Historical parallels**: "Like Dutch shipbuilders discovering longitude, except the ships are packets and the ocean is latency" 5. **Technical precision preserved**: Actual measurements, specifications, protocols remain accurate 6. **Parenthetical asides**: (the kind left in source code) 7. **No formal transitions**: Ideas emerge adjacently

Conceptual Compression

**Standard Technical**: > "Our network synchronizes time across nodes with GPS-synchronized hardware providing nanosecond-level precision."

**ROKO Voice**: > "Meshheads breathe together at nanosecond intervals, each exhale a cryptographic proof that time happened. The hardware is mundane - oscillators, antennas, ASICs whispering to GPS satellites at 10MHz. The implications are not: anyone can now run their own atomic clock."

Transformation Guidelines

1. Create Discoverable Neologisms

Invent terminology that sounds pre-existing, not forced:

❌ "super-awesome-time-network" ✅ "chronarchy" (time-power-structure), "meshheads" (network nodes), "temporal substrate"

2. Mix Technical Precision with Subcultural Vernacular

Preserve technical accuracy while adding cultural layer:

❌ "The system utilizes advanced synchronization mechanisms" ✅ "Meshheads sync at 10MHz to GPS L1 C/A and L2C carriers, with holdover accuracy of ±500ns over 24 hours if satellites disappear"

3. Frame Corporate Structures as Feudal Systems

❌ "Traditional providers charge premium prices" ✅ "The timekeeper cartels ran their atomic clocks like medieval guilds hoarding gold. NYSE charged seven figures for what now propagates through the mesh at lightspeed minus overhead."

4. Jump Scales Fluidly

Move between nanosecond precision and geological time:

✅ "Milliseconds. NTP has run the internet since 1985 with millisecond accuracy. For most uses, fine. For financial trading, blockchain consensus, industrial automation? The drift between millisecond-accurate timestamps becomes an arbitrage opportunity, a double-spend window, a control system failure."

5. Fragment Like Code Comments

Use sentence fragments for rhythm and emphasis:

✅ "The chronarchy is ending. Not with revolution but with protocol. TimeRPC eating the foundations of Greenwich-descended time like termites in a cathedral."

6. Parenthetical Technical Asides

Add context like source code comments:

✅ "The Timebeat card syncs at 10MHz (not because we're paranoid about GPS spoofing - we are - but because consensus requires fallback when the sky goes dark)"

7. Make Virtual Infrastructure Tangible

Use physical metaphors for abstract systems:

❌ "Decentralized consensus mechanisms" ✅ "The network negotiates reality through cryptographic handshakes, each signature a vote in the parliament of proof"

Density Level Details

Light Density

approach:
  - Maintain standard paragraph structure
  - Add 2-3 ROKO-specific terms per section
  - Include 1-2 cultural metaphors
  - Preserve most formal transitions
  - Technical specifications stay prominent
tone:
  - Professional with cypherpunk flavor
  - Accessible to broader technical audience
  - Mythology as seasoning, not main course

Standard Density (Default)

approach:
  - Balance compression with readability
  - Dense information clusters with breathing room
  - 5-7 ROKO terms per section
  - Corporate feudalism metaphors throughout
  - Fragment sentences for emphasis
  - Remove most formal transitions
tone:
  - Technical mythology as infrastructure
  - Revolutionary concepts a