Specify prj- drivers and cross-owner wait mode.
Some checks failed
CI Smoke / host-smoke (push) Waiting to run
CI Smoke / container-smoke (push) Waiting to run
check / test (push) Has been cancelled

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
This commit is contained in:
tegwick 2026-09-14 16:46:45 +02:00
parent b69839b5ef
commit d2802fc55d
9 changed files with 582 additions and 6 deletions

View file

@ -2,7 +2,7 @@
## Repo Identity
**Purpose:** Coordination Engine - (fill in purpose)
**Purpose:** Goal-driven digital coordination; project-repository workplans as cross-repo drivers; worker leases/receipts (not live unless the operator started the service).
**Domain:** communication
**Repo slug:** coordination-engine
@ -27,6 +27,18 @@ Queueable writes return an explicit queued receipt if the central hub is
unreachable. Treat that as pending local evidence, then ask the operator to run
statehub outbox status/replay after connectivity returns.
### Cross-repo waits (COORDINATION-WP-0005)
Do not mint a stranded `wait` when another repo/owner is the blocker.
1. Look for a `prj-` workplan that lists both repos (`spec/coordination-model-v0.2.md`). That plan is the **driver**; product repos **implement**.
2. Observe the foreign record on State Hub. Do not copy or PATCH the other owner's tasks.
3. `flavor: residual` is not a driver and not implementation demand unless promoted.
4. Lease/wakeup only via the v0.1 worker service for selected gita repos. This session does **not** enable live worker injection.
5. Do not message `ops-warden` for secrets (SSH certs only).
Mode: `spec/cross-owner-wait-mode-v0.1.md`.
### Orient at session start
```bash