coordination-engine/README.md
tegwick 628f984a10
All checks were successful
check / test (push) Successful in 7m8s
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s
Implement worker coordination runtime and finish WP-0003
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a07b5b-ea58-7ad2-bdbb-0b1c995cfc35
2026-09-07 23:19:52 +02:00

29 lines
1.3 KiB
Markdown

# Coordination Engine
Framework for digital coordination as goal-driven communication.
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.
```sh
uv sync --locked
make check
uv run coordination-engine --help
```
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.