---
id: TAMQ-WP-0002
type: workplan
title: "Coordination-engine adapter boundary"
domain: communication
repo: tmux-amq
status: active
owner: codex
topic_slug: coulomb-social
created: "2026-08-24"
updated: "2026-08-24"
state_hub_workstream_id: "48da5fa7-b7bf-5d13-8edc-b90f266e241c"
---

# 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
state_hub_task_id: "a222dab7-edea-58c6-9dab-d684eb65c412"
```

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
state_hub_task_id: "195db613-05a3-58d8-9e94-2db34920576f"
```

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
state_hub_task_id: "23c7f6c7-be48-5b6c-b85c-ae05d82cc277"
```

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.