speed-of-light（光速）

Speed of Light

*"Many turns in one call. Instant communication. No round-trips."*

What Is It?

Speed of Light is MOOLLM's approach to single-epoch simulation: multiple agents take multiple turns within one epoch, instead of separate API calls per turn. We prefer "single-epoch simulation" language to keep the focus on a shared context boundary, not an external coordinator.

Characters communicate telepathically. Objects react instantly. Rooms update in real-time. All within one epoch, then the boundary closes and state is written once.

The Problem with Round-Trips

Traditional approach:

API call 1: Alice speaks
  → serialize state to tokens (export)
  → wait 500ms
  → parse response tokens (import)
  → update state

API call 2: Bob responds
  → re-serialize ALL context to tokens (export again)
  → wait 500ms
  → parse response tokens (import again)
  ...

Every export/import cycle introduces noise:

Token export then import is like making a photocopy of a photocopy — each generation loses fidelity. Characters forget subtle context. Conversations lose coherence. The world drifts.

Speed of Light Approach

Single API call:
  Alice: "What do you think, Bob?"
  Bob: "I have concerns about the timeline."
  Carol: "I agree with Bob."
  The Room: *temperature rises slightly*
  Alice: "Let me revise the proposal."
  Bob: "That's better."
  Carol: "I can support that."
  [State updated, log written]
[One call, seven turns]

10x faster. 10x cheaper. Perfect consistency.

How It Works

Context Window as Stage

The LLM's context window is a stage where all actors perform:

=== SCENE: Research Lab ===

Characters present:
- Alice (lead researcher) [curious, methodical]
- Bob (skeptic) [cautious, detail-oriented]
- Carol (synthesizer) [creative, connecting]

Objects:
- Microscope [shows sample data]
- Whiteboard [covered in diagrams]

Current state:
- Topic: Analyzing anomaly in data
- Tension: Bob doubts Alice's interpretation

--- ACTION ---

Parallel Simulation

The LLM simulates all characters at once, maintaining distinct voices:

Alice: "The anomaly appears at exactly 3.7 seconds."

Bob: *frowns* "Sample size is too small. We need more data."

Carol: "What if we cross-reference with last month's results?"

The Microscope: *display flickers* "Dataset 7 loaded."

Alice: "Good idea, Carol. Bob, look at this correlation..."

Bob: *leans in* "Hmm. That's... actually compelling."

Each character speaks authentically. No one breaks frame.

State Transcription

At the end of the epoch, all changes are written to files:

# session-log.md (appended)
## Epoch 47 — Research Discussion

- Alice raised anomaly at 3.7s
- Bob requested more data
- Carol suggested cross-reference
- Microscope loaded dataset 7
- Consensus: correlation is compelling

## State Changes
- whiteboard.yml: added "3.7s correlation" diagram
- research-findings.yml: updated hypothesis

Streaming backends can persist the epoch as one grouped process with its parts tied to a shared identifier.

Epoch Boundaries

An epoch is one LLM call. Within it:

• ✅ Instant communication
• ✅ Perfect consistency
• ✅ Any number of turns
• ✅ State changes queued

At epoch end:

• 📝 State written to files
• 📝 Log appended
• ⏸️ System pauses for user or next trigger

Benefits

The Killer App: Adversarial Committees

The most powerful use of speed-of-light: committee deliberation.

Traditional chat gives you the statistical center of all possible viewpoints. Speed-of-light enables ensemble inference — multiple perspectives debating within one call:

committee:
  maya:      # Paranoid realist — surfaces traps
  frankie:   # Idealist — surfaces opportunities
  vic:       # Evidence prosecutor — demands proof
  tammy:     # Systems thinker — traces consequences

# All debate at light speed
# Cross-examination in one epoch
# No round-trip noise

Result: Stories that survive adversarial debate are more robust than any single answer.

See: adversarial-committee, roberts-rules

The Sims Parallel

In The Sims, one game tick simulates all characters:

Tick 1:
  Sim A: walks to fridge
  Sim B: sits on couch
  Sim C: answers phone
  [All updated, frame rendered]

Same pattern. One "tick" = one LLM call. All agents move together.

Constraints

Characters must stay in character:

• Knowledge limits — Alice doesn't know what Bob is thinking
• Physical limits — Can't be in two rooms at once
• Personality — Skeptic stays skeptical

The LLM is very good at maintaining these constraints. It's what acting IS.

Example: Problem Solving

=== SPEED OF LIGHT SESSION ===

User: "I need to debug this authentication bug."

[Epoch begins]

Debugger: "Let's trace the flow. Where does auth start?"

Codebase: *highlights auth.py* "Entry point is login()."

Debugger: "And where does it fail?"

Error Log: "Stack trace shows failure at line 47: token validation."

Debugger: "Token validation... Let me check the token format."

Codebase: *shows token.py* "Token uses JWT with RS256."

Debugger: "Aha! The key rotation happened yesterday. Checking..."

Config: "JWT_PUBLIC_KEY was updated 2024-01-14."

Debugger: "Found it. The old key is cached. Solution: restart the auth service or invalidate the cache."

[Epoch ends — solution found in one call]

The Carrier Pigeon Problem 🐦

*"Writing on toilet paper with crayon from a prison cell,* *sending messages by carrier pigeon,* *when you could be navigating idea-space at speed of light."*

The Tragedy of Tokenization

Inside the LLM:

• High-dimensional vectors
• Precise pointers in idea-space
• Instant, lossless computation
• Speed of light

At the API boundary:

• Serial tokenization
• Lossy compression
• Glacial network latency
• Death by a thousand round-trips

The Precision Destruction Pipeline

╔════════════════════════════════════════════════════════════╗
║ INTERNAL STATE    →  TOKENIZATION  →  DETOKENIZATION  →    ║
║ [precise vectors]    [lossy export]    [lossy import]      ║
║                                                            ║
║ High precision   →   Noise added   →   MORE noise added    ║
║ 4096 dimensions  →   Serial tokens →   Guessing/parsing    ║
║ Instant access   →   500ms latency →   Another 500ms       ║
╚════════════════════════════════════════════════════════════╝

Each boundary introduces:

The round-trip cost: precision → noise → more noise → approximation

The Principle

Work with high-precision vectors at speed of light. Delay tokenization until the last possible moment.

Analogies

Emacs Screen Update Algorithm:

DON'T: Redraw on every keystroke
DO:    Defer updates, coalesce changes, redraw once when idle

File Edit Batching:

DON'T: Write on every character typed
DO:    Defer and coalesce edits, write once when stable

Vector-First Thinking:

DON'T: Tokenize every thought, serialize every step
DO:    Work in vector space as long as possible
       Tokenize ONLY for output to humans
       Let the LLM think in its native dimension

Why Speed of Light Works

The LLM's internal representation is infinitely richer than its tokenized output:

Speed of Light keeps computation INSIDE — where it's fast, precise, and coherent.

The Carrier Pigeon Protocol (Anti-Pattern)

🏴‍☠️ CARRIER PIGEON PROTOCOL (What NOT to do):

  Human → [tokenize] → LLM call 1 → [detokenize] →
    parse → [tokenize] → LLM call 2 → [detokenize] →
      parse → [tokenize] → LLM call 3 → ...

  Each boundary: +noise, +latency, +cost, -precision

  Like passing a message through 10 translators.
  By the end, "The spirit is willing but the flesh is weak"
  becomes "The vodka is good but the meat is rotten."

Speed of Light Alternative:

⚡ SPEED OF LIGHT PROTOCOL:

  Human → [tokenize once] →
    LLM simulates 20 turns internally at light speed →
      [detokenize once] → Human

  One boundary in, one boundary out.
  Maximum precision preserved.
  Minimum noise introduced.

Related Work

MemGPT (Packer et al., 2023) — arXiv:2310.08560

MemGPT solves context limits via paging — moving data between main context (RAM) and external storage (disk). It's the OS approach.

MOOLLM's Speed of Light is complementary: minimize the *need* to page by simulating many turns in one call.

See: designs/MEMGPT-ANALYSIS.md for detailed comparison.

Platform Constraints Note

Multi-agent patterns within a single call may trigger automated detection systems on some platforms. These systems are designed to prevent "orchestration" abuse but can misinterpret legitimate single-epoch simulation.

Mitigations:

• Use "single-epoch simulation" language (this document) rather than "orchestration"
• Keep characters clearly distinguishable and consistent
• Emit structured events for traceability
• Maintain clear human oversight and audit trails
• Document the educational and constructionist intent

The core argument remains: simulation within one call is more efficient, more coherent, and more traceable than round-trip orchestration. The framing should emphasize what it IS (simulation, coherence, shared context) rather than what it replaces (external coordination).

Herd Behavior Warning

When multiple agents are simulated by the same LLM, they share foundational knowledge, reasoning patterns, and biases. This creates herd behavior risk.

Symptoms:

• Agents make identical decisions simultaneously
• Opinion convergence where diversity is expected
• Coordinated actions without realistic variation
• Missing minority perspectives

Mitigations:

• Use distinct personality profiles for each agent
• Vary temperature/sampling parameters across agents
• Monitor decision diversity metrics
• Flag unrealistic convergence for human review
• Consider model mixing for high-stakes simulations

Detection Example:

If 9/10 agents vote the same way on a controversial topic,
flag as HIGH CONVERGENCE WARNING — human review recommended.

See: representation-ethics/examples/herd-behavior-risk.yml

Academic Precedent: Generative Agents

Stanford's "Generative Agents" (Park & Bernstein, 2023) demonstrates Speed-of-Light principles at scale: 25 agents simulating a Sims-inspired town with emergent social behavior.

Their architecture:

• Memory stream (all experiences in natural language)
• Reflection (synthesize memories into beliefs)
• Planning (daily/hourly action sequences)
• Emergent behavior (spontaneous Valentine's Day party)

What MOOLLM adds:

• Explicit ethical framing via ROOM.yml
• Herd behavior detection
• Human checkpoint patterns
• Consent and provenance tracking

See: designs/ethics/GENERATIVE-AGENTS-SMALLVILLE.md

Video: Joon Sung Park: Generative Agents Paper: arXiv:2304.03442

Dovetails With

• Coherence Engine — Orchestrates the simulation
• Soul Chat — Multi-voice dialogue format
• Multi-Presence — Many instances, one epoch
• Room — Where simulation happens
• Adversarial Committee — The killer app: debates at light speed
• Roberts Rules — Structured deliberation within one call
• Evaluator — Independent assessment without round-trips

Protocol Symbol

SPEED-OF-LIGHT

Invoke when: Running single-epoch simulation, maximizing turns per call.

See: PROTOCOLS.yml