25 lines
937 B
Markdown
25 lines
937 B
Markdown
|
---
|
||
|
|
repo: tmux-amq
|
||
|
|
updated: "2026-08-24"
|
||
|
|
---
|
||
|
|
|
||
|
|
# INTENT
|
||
|
|
|
||
|
|
## Why it exists
|
||
|
|
|
||
|
|
Provide a local, durable, inspectable transport for direct messages between agent workers running in tmux, with strict repository targeting, explicit endpoint lifecycle, bounded retry behavior, and future interoperability with coordination-engine.
|
||
|
|
|
||
|
|
## Governing principle
|
||
|
|
|
||
|
|
This repository should stay focused on the purpose above. Work that changes its
|
||
|
|
authority, ownership boundaries, or operational promises should be captured in a
|
||
|
|
workplan before implementation.
|
||
|
|
|
||
|
|
## What it enables
|
||
|
|
|
||
|
|
- Agent workers can address one another by registered repository slug.
|
||
|
|
- Messages, leases, delivery state, and acknowledgements survive process restarts.
|
||
|
|
- Operators can inspect, export, replay, and purge local queue history.
|
||
|
|
- A later coordination-engine adapter can use a stable local socket boundary
|
||
|
|
without absorbing tmux-specific concerns into the coordination engine.
|