coordination-engine/workplans/COORDINATION-WP-0005-prj-cross-repo-and-agent-mode.md
tegwick d2802fc55d
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
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

133 lines
4.7 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

---
id: COORDINATION-WP-0005
type: workplan
title: "prj- awareness, cross-owner waits, and agent coordination mode"
domain: communication
repo: coordination-engine
status: finished
owner: grok
topic_slug: communication
flavor: extension
created: "2026-09-14"
updated: "2026-09-14"
related:
- COORDINATION-WP-0002
- COORDINATION-WP-0003
- STATE-WP-0092
- CUST-WP-0072
- CUST-ADR-005
origin: residual-policy
origin_ref: the-custodian/history/20260914-open-workplan-chokepoints.md
state_hub_workstream_id: "abb4bdaf-4100-5c93-9773-4213b1a4edf5"
---
# prj- awareness, cross-owner waits, and agent coordination mode
Founder direction 2026-09-14: cross-owner coordination is the top theme
holding the open-workplan count up. Tackle it with coordination-engine,
not more inbox `wait` notes. The engine must understand **`prj-`
workplans** as drivers of cross-repository work (`ADR-005`,
`project-repository-flavor_v0.1.md`). Agent instructions for Codex,
Claude, Grok and others change **after** that mode exists, so they
coordinate instead of stranding.
This repo owns observation, leases, wake-up, checkpoints, safety gates
and receipts (`COORDINATION-WP-0003`). State Hub remains the work-record
read model. Product implementation stays in participating repos.
Do not enable live worker injection as a side effect of this plan.
Do not invent credential vending.
## Model prj- workplans as cross-repo drivers
```task
id: COORDINATION-WP-0005-T01
status: done
priority: high
state_hub_task_id: "de21e1da-e66d-51d4-8689-6017346199bd"
```
Extend `spec/coordination-model-v0.1.md` (or a v0.2 successor) so a
`CoordinationCase` can be driven by a project-repository workplan:
`repo_flavor: project` / `prj-*` identity, child workplans in
participating repos, and `depends_on` edges as commitments rather than
prose. Distinguish driver (the `prj-` plan) from implementers (product
repos). Record what is out of scope: the engine does not author
workplans and does not replace State Hub.
Done when the spec names the driver/implementer split, maps `prj-`
workplans onto cases/commitments, and has a worked example from an
existing project repo.
## Cross-owner wait handling mode
```task
id: COORDINATION-WP-0005-T02
status: done
priority: high
depends_on: [COORDINATION-WP-0005-T01]
state_hub_task_id: "9e99e12b-b4a2-569a-bce2-dbdc645d75a1"
```
Define the handling mode that replaces “set status wait and hope”:
observe the foreign owners record, open or attach a coordination case,
lease/wakeup only for selected gita-registered worker targets, checkpoint
progress, fail closed on missing authorization, and emit a receipt the
hub can project. Cover the common estate pattern: repo A blocked on repo
B owner return (security subsystems included). No silent re-assignment
of another owners tasks.
Done when the mode is specified with entry/exit conditions, safety
gates, and a receipt shape, reconciled with the v0.1 worker-coordination
service rather than forked.
## State Hub adapter for workplans, flavor, and prj-
```task
id: COORDINATION-WP-0005-T03
status: done
priority: medium
depends_on: [COORDINATION-WP-0005-T01, STATE-WP-0092]
state_hub_task_id: "2c5d91a5-2e77-5778-ac52-f95ea5c2ed63"
```
Read workplans, `depends_on`, flavor, and repo classification
(including `prj-`) from State Hub. Residual flavor is not a coordination
driver unless promoted. Until `STATE-WP-0092` is indexed, stay `wait` on
that dependency; T01T02 may proceed on files and classification
standards.
Done when a local test can build a case from hub JSON for a `prj-`
workplan and refuse to treat a residual as actionable demand.
## Agent instruction pack
```task
id: COORDINATION-WP-0005-T04
status: done
priority: high
depends_on: [COORDINATION-WP-0005-T02]
state_hub_task_id: "967e709e-1fe8-5ee0-a544-41e7cfe13f4b"
```
After the mode exists, update agent instructions so Codex, Claude, Grok
and other workers can tackle or coordinate cross-repo work:
- `the-custodian/AGENTS.md` and session protocol
- coordination-engine `AGENTS.md`
- repo-seed / fleet template snippets used by other repos
Instructions must say: follow the coordination-engine mode; do not mint
a stranded `wait` when a `prj-` driver exists; do not implement
residuals; do not message `ops-warden` for secrets. Keep the pack short.
Done when the named files describe the mode with a pointer to the spec,
and a new session can choose “coordinate via engine” without inventing a
parallel process.
2026-09-14: T01T04 landed. Specs:
`spec/coordination-model-v0.2.md`, `spec/cross-owner-wait-mode-v0.1.md`.
Adapter: `coordination_engine.project_driver.build_driver_case` (HFACT
fixture; residual refused). Agent pack in this `AGENTS.md`,
`the-custodian` session protocol, and repo-manager scaffold/rapp
templates. Live worker injection was not enabled.