coulomb/coordination-engine
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Implement worker coordination runtime and finish WP-0003
All checks were successful
check / test (push) Successful in 7m8s
Details
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details

Browse source 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a07b5b-ea58-7ad2-bdbb-0b1c995cfc35
This commit is contained in:
tegwick 2026-09-07 23:19:52 +02:00
parent 214964ccb8
commit 628f984a10
23 changed files with 3025 additions and 544 deletions
Download patch file Download diff file Expand all files Collapse all files

47
README.md
View file

@ -2,31 +2,28 @@
Framework for digital coordination as goal-driven communication.
## TAMQ worker-session adapter
The first runtime observes State Hub work and wakes explicitly selected local
repository workers through TAMQ. It owns actionability/safety checks, durable
coordination leases, checkpoints, deduplication and sanitized audit receipts.
TAMQ independently owns terminals, its durable queue and delivery policy.
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.",
)
)
```sh
uv sync --locked
make check
uv run coordination-engine --help
```
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.
Configure selected gita repositories before starting `coordination-engine serve`.
Installation does not enable a service or start workers. See the
[runbook](docs/worker-runtime.md) for configuration, worker acknowledgements,
checkpoint continuation, backups and local verification.
The [v0.1 contract](spec/worker-coordination-service-v0.1.md) and
[adapter decision](docs/adr/002-worker-runtime-boundary.md) describe the ownership
boundary. The authoritative transport contract lives in
`tmux-amq/spec/coordination-engine-adapter-v0.1.md`. This package speaks that Unix
socket protocol directly and does not install TAMQ's executable.
Transport delivery is distinct from workflow completion. A worker must recheck
scope and authority, acknowledge/renew its coordination lease, and publish its
own task updates and completion.