54 lines
1.4 KiB
Markdown
54 lines
1.4 KiB
Markdown
|
---
|
||
|
|
id: TAMQ-WP-0002
|
||
|
|
type: workplan
|
||
|
|
title: "Coordination-engine adapter boundary"
|
||
|
|
domain: communication
|
||
|
|
repo: tmux-amq
|
||
|
|
status: backlog
|
||
|
|
owner: codex
|
||
|
|
topic_slug: coulomb-social
|
||
|
|
created: "2026-08-24"
|
||
|
|
updated: "2026-08-24"
|
||
|
|
---
|
||
|
|
|
||
|
|
# Coordination-engine adapter boundary
|
||
|
|
|
||
|
|
Connect coordination-engine to tmux-amq through the existing local Unix-socket
|
||
|
|
boundary while preserving tmux-amq's local transport authority and keeping
|
||
|
|
workflow/orchestration policy in coordination-engine.
|
||
|
|
|
||
|
|
## Specify the adapter contract
|
||
|
|
|
||
|
|
```task
|
||
|
|
id: TAMQ-WP-0002-T01
|
||
|
|
status: todo
|
||
|
|
priority: high
|
||
|
|
```
|
||
|
|
|
||
|
|
Define request, response, identity, delivery, acknowledgement, retry, and
|
||
|
|
failure semantics for a coordination-engine client. Resolve protocol-version
|
||
|
|
negotiation and document which system owns each state transition.
|
||
|
|
|
||
|
|
## Implement the coordination-engine client adapter
|
||
|
|
|
||
|
|
```task
|
||
|
|
id: TAMQ-WP-0002-T02
|
||
|
|
status: wait
|
||
|
|
priority: high
|
||
|
|
```
|
||
|
|
|
||
|
|
Implement the adapter against the stable socket contract without importing
|
||
|
|
tmux/control-mode concerns into coordination-engine. This task waits for T01.
|
||
|
|
|
||
|
|
## Prove interoperability and recovery
|
||
|
|
|
||
|
|
```task
|
||
|
|
id: TAMQ-WP-0002-T03
|
||
|
|
status: wait
|
||
|
|
priority: high
|
||
|
|
```
|
||
|
|
|
||
|
|
Add end-to-end coverage for delivery, acknowledgement, reconnect, replay,
|
||
|
|
deduplication, incompatible protocol versions, and endpoint disappearance.
|
||
|
|
Update both repositories' operator documentation with the verified workflow.
|