chore: register repository governance baseline
Some checks failed
tamq-ci / test (push) Failing after 6s
Some checks failed
tamq-ci / test (push) Failing after 6s
Assistant: codex Assistant-Model: gpt-5.6-sol Assistant-Session: 01a03397-4d51-7fd1-8ff2-946eb22ea2bc
This commit is contained in:
parent
7c76f79463
commit
7b4a972655
18 changed files with 902 additions and 0 deletions
24
INTENT.md
Normal file
24
INTENT.md
Normal file
|
|
@ -0,0 +1,24 @@
|
|||
---
|
||||
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.
|
||||
Loading…
Add table
Add a link
Reference in a new issue