# Coordination Engine

Framework for digital coordination as goal-driven communication.

## TAMQ worker-session adapter

Coordination-engine owns trigger observation, actionability and safety policy,
coordination leases, checkpoints, and State Hub receipts. TAMQ separately owns
local repository sessions, durable messages, terminal delivery attempts, and
acknowledgement state.

The implemented async boundary is provided by `tamq.client`:

```python
from tamq.client import CoordinationEngineAdapter, WakeRequest

receipt = await CoordinationEngineAdapter().wake(
    WakeRequest(
        lease_id="lease-123",
        trigger_id="task-456:r7",
        target_repo="audit-core",
        prompt="Resume the actionable task and publish a checkpoint.",
    )
)
```

The coordination lease ID makes wake admission idempotent. An exact live TAMQ
endpoint is required; the adapter will not choose between multiple sessions or
start an agent implicitly. Transport states (`pending`, `awaiting_ack`,
`injected`, `acknowledged`, `failed`) are receipts, not workflow completion.
See `spec/worker-coordination-service-v0.1.md` and the canonical
`tmux-amq/spec/coordination-engine-adapter-v0.1.md` contract.