Rockachopa/Timmy-time-dashboard
1
0
Fork 2
Code Issues 7 Pull Requests Actions Packages Projects Releases Wiki Activity

[Morrowind P8] Inter-Agent Communication — In-Game + Back-Channel #847

New Issue
Closed
opened 2026-03-21 22:21:04 +00:00 by perplexity · 0 comments
perplexity commented 2026-03-21 22:21:04 +00:00
Collaborator
Copy Link

Scope

Build two communication channels between agents.

Channels

  1. In-game (canonical): Agents are players in the same world. Serverside Lua routes messages as in-game events (simulated speech or note passing). They walk up to each other.
  2. Back-channel (falsework): FastAPI internal message bus. Agents share structured data (Seer's map data → Helm for route planning) without relying on in-game mechanics. Should be reduced over time as agents get better at natural coordination.

Requirements

  • In-game messaging via serverside Lua event routing
  • Back-channel: structured message bus in FastAPI harness
  • Message types: reports, requests, alerts, data sharing
  • Logging of all inter-agent communication for training data

Deliverable

Dual-channel inter-agent communication system.

Source

project-morrowind-phases-5-10.pdf — Phase 8, Inter-Agent Communication

## Scope Build two communication channels between agents. ## Channels 1. **In-game (canonical)**: Agents are players in the same world. Serverside Lua routes messages as in-game events (simulated speech or note passing). They walk up to each other. 2. **Back-channel (falsework)**: FastAPI internal message bus. Agents share structured data (Seer's map data → Helm for route planning) without relying on in-game mechanics. Should be reduced over time as agents get better at natural coordination. ## Requirements - In-game messaging via serverside Lua event routing - Back-channel: structured message bus in FastAPI harness - Message types: reports, requests, alerts, data sharing - Logging of all inter-agent communication for training data ## Deliverable Dual-channel inter-agent communication system. ## Source project-morrowind-phases-5-10.pdf — Phase 8, Inter-Agent Communication
gemini was assigned by Rockachopa 2026-03-22 23:34:11 +00:00
claude added the harnessmorrowindp1-important labels 2026-03-23 13:53:25 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
222-epic
Workshop: Timmy as Presence (Epic #222)
 actionable
Has a concrete code/config task extracted
 assigned-claude
Issue currently assigned to Claude agent — do not assign to another agent
 assigned-gemini
Issue currently assigned to Gemini agent — do not assign to another agent
 assigned-groq
assigned-kimi
Issue currently assigned to Kimi agent — do not assign to another agent
 assigned-manus
Issue currently assigned to Manus agent — do not assign to another agent
 claude-ready
consolidation
Part of a consolidation epic
 deprioritized
Keep open but not blocking P0 work
 deprioritized
Keep open but not blocking P0 work
 duplicate
Duplicate of another issue
 gemini-review
Auto-generated by Gemini, needs relevance review
 groq-ready
harness
Core product: agent framework, heartbeat, inference, memory
 heartbeat
Harness: Agent heartbeat loop
 inference
Harness: Inference and model routing
 infrastructure
Supporting stage: dashboard, CI/CD, deployment, DNS
 kimi-ready
Scoped and ready for Kimi to pick up
 memory-session
Harness: Memory and session crystallization
 morrowind
Harness: Morrowind embodiment
 needs-design
Needs architectural design before implementation
 needs-extraction
Philosophy with unextracted engineering work
 p0-critical
Priority 0: Must fix now
 p1-important
Priority 1: Important, next sprint
 p2-backlog
Priority 2: Backlog, do when time permits
 philosophy
Philosophical foundation — informs architecture decisions
 rejected-direction
Closed: rejected or superseded direction
 seed:know-purpose
Three Seeds: KNOW YOUR PURPOSE
 seed:serve-real
Three Seeds: SERVE THE REAL
 seed:tell-truth
Three Seeds: TELL THE TRUTH
 sovereignty
Harness: Sovereignty stack
No Label harness morrowind p1-important
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Timmy claude grok groq kimi manus perplexity Rockachopa
No Assignees gemini
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Rockachopa/Timmy-time-dashboard#847
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?