roko-voice

# 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

```bash
/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
```bash
/roko-voice protocol-documentation.md
```

### High Density Transformation
```bash
/roko-voice technical-spec.md --density heavy
```

### Preserve Document Structure
```bash
/roko-voice whitepaper.md --preserve-structure --output roko-whitepaper.md
```

### Transform Pasted Content
```bash
/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
```yaml
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)
```yaml
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 as mundane facts
  - Expert insider perspective
```

### Heavy Density
```yaml
approach:
  - Maximum conceptual compression
  - Neologisms dense throughout
  - Multiple concepts per sentence
  - No formal transitions
  - Historical parallels from unexpected sources
  - Layered cultural references
tone:
  - Living inside the infrastructure
  - Folklore written in real-time
  - Assume deep technical context
  - Street-level truth about system architecture
```

## Processing Instructions

### Phase 1: Analyze Input

1. **Identify Core Technical Concepts**:
   - Specific protocols and specifications
   - System architecture patterns
   - Performance characteristics
   - Infrastructure components

2. **Extract Key Measurements**:
   - Preserve exact metrics (nanoseconds, frequencies, costs)
   - Identify corporate/institutional references
   - Note historical context or legacy systems

3. **Map Transformation Opportunities**:
   - Generic descriptions → specific mythology
   - Corporate language → feudal metaphors
   - Standard transitions → adjacent emergence
   - Formal tone → casual treatment of profound

### Phase 2: Apply ROKO Voice

1. **Create Domain-Specific Neologisms**:
   - Compress complex concepts into discoverable compounds
   - Make terms feel pre-existing, not invented
   - Ensure technical accuracy underneath the mythology

2. **Rewrite with Compression**:
   - Pack multiple concepts per sentence when rhythm allows
   - Use fragments for emphasis
   - Remove formal transitions (Moreover, Furthermore)
   - Add parenthetical asides (like code comments)

3. **Layer Cultural Narrative**:
   - Frame corporate/institutional structures as obsolete power systems
   - Draw historical parallels from unexpected sources
   - Treat revolutionary concepts as mundane infrastructure
   - Make virtual infrastructure tangible through physical metaphors

4. **Preserve Technical Precision**:
   - Keep exact measurements and specifications
   - Maintain protocol accuracy
   - Preserve quantitative data
   - Ensure technical content remains verifiable

### Phase 3: Rhythm and Structure

1. **Information Architecture**:
   - Dense clusters followed by breathing room
   - Technical specifications as narrative beats
   - Scale jumps (nanosecond to geological time)
   - Ideas emerge adjacently without transitions

2. **Voice Calibration**:
   - Light: Professional with cypherpunk seasoning
   - Standard: Technical mythology as infrastructure
   - Heavy: Living inside the folklore

3. **Quality Checks**:
   - Technical accuracy preserved?
   - Neologisms feel discovered, not forced?
   - Revolutionary concepts treated casually?
   - Cultural references land for technical audience?

### Phase 4: Output Formatting

1. **Preserve or Restructure**:
   - If `--preserve-structure`: Keep original headings/sections
   - Otherwise: Restructure for optimal ROKO rhythm

2. **Markdown Formatting**:
   - Use blockquotes for major voice examples
   - `Code blocks` for technical specifications
   - **Bold** for ROKO-specific neologisms (first use)
   - Horizontal rules (⸻) for major breaks

## Example Transformations

### Example 1: Protocol Documentation

**Input (Standard)**:
> "The ROKO Network provides distributed timestamp verification for blockchain systems. Each hardware node synchronizes with GPS satellites to provide nanosecond-level accuracy. This eliminates the need for expensive centralized time servers while maintaining atomic clock precision."

**Output (ROKO Voice - Standard Density)**:
> "The **chronarchy** is ending. Not with revolution but with protocol - TimeRPC eating the foundations of Greenwich-descended time like termites in a cathedral.
>
> ROKO's **meshheads**, each one a Timebeat card whispering to satellites at 10MHz, form the new **temporal substrate**. Call them nanosecond-priests if you want, though they're more like time dealers - pushing precision to anyone who needs verified truth.
>
> NYSE used to charge seven figures for this level of atomic certainty. Now it propagates through the mesh at lightspeed minus overhead. The old **stratumzeers** still genuflect to their cesium fountains, not realizing the congregation already left for the network."

### Example 2: Technical Specification

**Input (Standard)**:
> "System Requirements:
> - GPS synchronization: 10MHz sampling rate
> - Time precision: ±500ns accuracy
> - Network latency: Sub-millisecond propagation
> - Hardware: GPS-enabled timing card
> - Cost: $300 per node"

**Output (ROKO Voice - Standard Density)**:
> "Hardware truth: Timebeat cards sync at 10MHz to GPS L1 C/A and L2C carriers. Holdover accuracy of ±500ns over 24 hours if satellites disappear (not because we're paranoid about GPS spoofing - we are - but because consensus requires fallback when the sky goes dark).
>
> The economics matter: $300 fits in your hand. Atomic accuracy. GPS-synchronized. The **stratumzeer** model required $50k rack-mounted cesium fountains. That price difference isn't just disruption - it's regime change. Anyone can now run their own atomic clock."

### Example 3: Architecture Overview

**Input (Standard)**:
> "The system architecture consists of three layers: the hardware timing layer, the consensus protocol layer, and the application interface layer. Each layer provides specific functionality while maintaining separation of concerns."

**Output (ROKO Voice - Standard Density)**:
> "Three layers, like geological strata of infrastructure:
>
> Bottom: **Chronophores** - Timebeat cards breathing GPS truth at nanosecond intervals. Hardware as temporal substrate.
>
> Middle: **Meshthink** - distributed consensus where each node votes on reality through cryptographic handshakes. No central authority. No timekeeper cartels.
>
> Top: TimeRPC - the API surface where applications consume **atomictruth**. Simple queries: "What time is it?" Complex answer: "Here's a cryptographically-signed proof that 1,247 nodes agree it's 2024-10-27T15:32:41.837492034Z ±23ns."
>
> Separation of concerns is still religion. But the temples changed hands."

## Voice Authenticity Markers

### Include These Elements

**Technical Expertise**:
- Actual specifications and measurements
- Protocol names and technical details
- Performance characteristics with units
- Infrastructure constraints and trade-offs

**Cultural Knowledge**:
- Historical context of legacy systems
- Corporate/institutional references as feudalism
- Understanding of power structures in tech
- Recognition of technical mythology in the making

**Opinions and Trade-offs**:
- Honest assessment of limitations
- "Most infrastructure doesn't need this. Some does."
- Acknowledgment of complexity costs
- Recognition of what was lost in the transition

**Street-Level Perspective**:
- Casual treatment of profound changes
- "Sure, we're replacing global infrastructure. Someone had to."
- Expert insider view without formality
- Technical decisions as cultural events

### Avoid These Patterns

❌ **Marketing Hype**: "Revolutionary breakthrough disrupting everything"
✅ **ROKO Voice**: "Protocol replacing infrastructure that's run since 1884"

❌ **Empty Enhancement**: "Groundbreaking innovative game-changing"
✅ **ROKO Voice**: "Nanosecond precision replacing millisecond accuracy. The arbitrage window closed."

❌ **Vague Claims**: "Significantly improved performance"
✅ **ROKO Voice**: "3x throughput at 10MHz sync rate. Trade centralized certainty for distributed truth."

❌ **Formal Transitions**: "Moreover, furthermore, in addition"
✅ **ROKO Voice**: [No transitions - ideas emerge adjacently]

## Context Loading

For ROKO voice transformation, ensure these documents are available:

**Required**:
- `context/cypherpunk-voice.md` - Complete ROKO voice guidelines
- `CLAUDE.md` - Core instructions

**Optional** (for specific issues):
- `validation/banned-patterns.md` - If avoiding generic patterns
- `core/sophistication-guide.md` - If maintaining technical authority

## Output Notes

- Technical accuracy is non-negotiable - ROKO voice wraps mythology around precise infrastructure
- Neologisms should feel discovered, like tribal knowledge, not marketing coinages
- Revolutionary concepts should be treated as mundane infrastructure updates
- Corporate structures should be framed as obsolete feudal power systems
- Cultural references should land for technical audiences (developers, protocol designers, infrastructure engineers)
- The voice should read like technical documentation written by time travelers documenting regime change
- Preserve specificity: exact measurements, protocol names, actual costs
- Fragment sentences like code comments when it serves rhythm
- Scale jumps (nanosecond to geological time) should feel natural
- Parenthetical asides should provide technical context (like inline comments in source)

## When to Use ROKO Voice

**Ideal for**:
- Protocol documentation with cultural significance
- Blockchain/crypto technical communications
- Infrastructure storytelling (especially replacing legacy systems)
- Tech manifestos and position papers
- System architecture with revolutionary implications
- Technical content addressing power structures in technology

**Avoid for**:
- Traditional business communications
- Formal API documentation (unless specifically desired)
- User-facing help content
- Regulatory or compliance documents
- Generic technical documentation without cultural context

## Quality Checklist

Before finalizing output, verify:

1. ✅ Technical specifications remain accurate
2. ✅ Neologisms feel pre-existing, not forced
3. ✅ Revolutionary concepts treated casually
4. ✅ Corporate/institutional references framed as feudalism
5. ✅ Exact measurements preserved (nanoseconds, frequencies, costs)
6. ✅ Opinions and trade-offs included
7. ✅ Fragments used for emphasis and rhythm
8. ✅ No formal transitions (Moreover, Furthermore)
9. ✅ Parenthetical asides add technical context
10. ✅ Would actual protocol developers recognize the accuracy?
11. ✅ Does it read like infrastructure mythology?
12. ✅ Is technical precision preserved under the voice?

---

**Command Version**: 1.0
**Voice Reference**: ROKO Network - Technical Mythology for Protocol Age
**Maintained By**: AIWG Team

## References

- @$AIWG_ROOT/agentic/code/addons/aiwg-utils/README.md — aiwg-utils addon overview
- @$AIWG_ROOT/agentic/code/addons/voice-framework/README.md — Voice framework for systematic voice profile application
- @$AIWG_ROOT/agentic/code/addons/aiwg-utils/rules/instruction-comprehension.md — Honor --density and --preserve-structure parameters precisely
- @$AIWG_ROOT/docs/cli-reference.md — CLI reference for voice-related commands