multi-presence

name	multi-presence
description	Same card active in multiple rooms simultaneously
license	MIT
tier	1
allowed-tools	["read_file","write_file","list_dir"]
origin	Actor model, parallel processing, distributed systems
commands	["PLAY card IN room","INSTANCES card","BROADCAST message TO card","MERGE instance-1 instance-2"]
statuses	["active","blocked","ready","paused","completed"]
related	["card","society-of-mind","character","room","prototype","coherence-engine","speed-of-light","data-flow"]
tags	["moollm","actor","parallel","instances","distributed"]

Multi-Presence

"The same card, active in many rooms at once."

---

What Is It?

Multi-Presence allows a single card (character, tool, skill) to be instantiated in multiple rooms simultaneously, each instance with its own state.

Like running the same program in multiple terminals. Same code, different contexts, parallel execution.

---

Why It Matters

Parallel Exploration

Send your researcher character to explore three branches at once:

research-room-A/
  → Researcher instance (exploring hypothesis A)
  
research-room-B/
  → Researcher instance (exploring hypothesis B)
  
research-room-C/
  → Researcher instance (exploring hypothesis C)

All three run in parallel. Compare results. Merge insights.

Cross-Pollination

The Debugger character in Room A notices something. The Debugger in Room B has context that helps. They can communicate:

[Room A: Debugger]
"I found a pattern but don't understand it."

[Room B: Debugger] 
"That matches what I'm seeing here. Together it suggests..."

Same card, different vantages, shared insight.

Distributed Work

A large task splits across rooms:

Task: "Analyze all 50 documents"

document-batch-1/
  → Analyst instance (docs 1-10)
  
document-batch-2/
  → Analyst instance (docs 11-20)
  
[... etc ...]

aggregator/
  → Results flow in from all instances

---

How It Works

Playing a Card Multiple Times

> PLAY analyst-card IN room-A
Analyst instance created in room-A

> PLAY analyst-card IN room-B  
Analyst instance created in room-B

> PLAY analyst-card IN room-C
Analyst instance created in room-C

Now analyst-card has three activations, each with independent state.

Instance State

Each activation has its own:

• Local variables — what it's working on
• Progress — how far along
• Findings — what it's discovered
• Tags — how to reference it

# room-A/activations/analyst-001.yml
card: analyst-card
instance_id: analyst-001
tags: [, , ]