coulomb/coordination-engine
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
coordination-engine/README.md
tegwick d2802fc55d
Some checks failed
CI Smoke / host-smoke (push) Waiting to run
Details
CI Smoke / container-smoke (push) Waiting to run
Details
check / test (push) Has been cancelled
Details
Specify prj- drivers and cross-owner wait mode. 
COORDINATION-WP-0005: map project-repository workplans onto
CoordinationCase, refuse residual as a driver, and document the wait
mode without enabling live worker injection.

Assistant: grok
Assistant-Session: 01a09dc1-b21e-77e1-919e-fcad2f82b267
2026-09-14 16:46:45 +02:00

1.5 KiB
Raw Blame History

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.

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 for configuration, worker acknowledgements, checkpoint continuation, backups and local verification.

Project-repository workplans (prj-) are coordination drivers; product repos implement. See v0.2 and cross-owner wait mode. Residual flavor is not a driver.

The v0.1 contract and adapter decision 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.