Archive finished workplans WP-0001, 0002, 0003 and 0005.
Some checks failed
CI Smoke / container-smoke (push) Waiting to run
CI Smoke / host-smoke (push) Waiting to run
check / test (push) Has been cancelled

Moved to workplans/archived/ with completion-date prefixes per the
workplan convention; frontmatter ids are unchanged.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 61492@bnt-lap001
Assistant-Session: 8e8b440c-c018-4275-aadc-b5b721c5b979
This commit is contained in:
tegwick 2026-09-22 12:00:42 +02:00
parent dc18dfa41c
commit 21a80c3948
4 changed files with 0 additions and 0 deletions

View file

@ -0,0 +1,67 @@
---
id: COORDINATION-WP-0001
type: workplan
title: "Bootstrap State Hub integration"
domain: communication
repo: coordination-engine
status: finished
owner: codex
topic_slug: communication
created: "2026-06-22"
updated: "2026-06-22"
state_hub_workstream_id: "656d4245-63a0-4022-98a3-e446b133a8d6"
---
# Bootstrap State Hub integration
Coordination engine for inter-repo workflows.
## Review Generated Integration Files
```task
id: COORDINATION-WP-0001-T01
status: done
priority: high
state_hub_task_id: "95769b93-99ce-4cbd-be90-a41dbb87fda0"
```
Result 2026-06-22: Filled SCOPE.md from INTENT.
Review `INTENT.md`, `SCOPE.md`, `AGENTS.md`, and `.custodian-brief.md`.
Replace generated placeholders with repo-specific facts where needed.
## Verify Local Developer Workflow
```task
id: COORDINATION-WP-0001-T02
status: done
priority: high
state_hub_task_id: "1c1930c6-8bd7-4979-b0a6-cfa476674129"
```
Result 2026-06-22: Registry-oriented dev workflow documented.
Identify the repo's install, test, lint, build, and run commands. Add or refine
those commands in the agent instructions so future coding sessions can verify
changes confidently.
## Seed First Real Workplan
```task
id: COORDINATION-WP-0001-T03
status: done
priority: medium
state_hub_task_id: "f74ef97e-8f0a-4d54-b17c-12dcb68ac3f1"
```
Result 2026-06-22: Created COORDINATION-WP-0002.
Create the first implementation workplan for the repository's most important
next change. After workplan file updates, run from `~/state-hub`:
```bash
make fix-consistency REPO=coordination-engine
```

View file

@ -0,0 +1,29 @@
---
id: COORDINATION-WP-0002
type: workplan
title: "Coordination model specification baseline"
domain: communication
repo: coordination-engine
status: finished
owner: codex
topic_slug: communication
created: "2026-06-22"
updated: "2026-06-24"
state_hub_workstream_id: "2b62c9df-577d-45ce-81a7-cf343e2fb6b0"
---
# Coordination model specification baseline
Draft the first coordination ontology and message lifecycle spec for the engine.
## Author coordination spec v0.1
```task
id: COORDINATION-WP-0002-T01
status: done
priority: high
state_hub_task_id: "0ece010b-4597-4ae9-b77d-26a3ff8c906f"
```
Result 2026-06-24: Authored `spec/coordination-model-v0.1.md` with actors, goals,
commitments, observation loops, and communication-act lifecycle baseline.

View file

@ -0,0 +1,119 @@
---
id: COORDINATION-WP-0003
type: workplan
title: "Worker coordination service contract"
domain: communication
repo: coordination-engine
status: finished
owner: codex
topic_slug: communication
created: "2026-08-23"
updated: "2026-09-07"
state_hub_workstream_id: "78a91239-ae31-5e03-98c9-54f3cbe90cb5"
---
# Worker coordination service contract
Implement cross-repository worker wake-up and dependency coordination requested
by net-kingdom. Coordination-engine owns observation, policy, coordination leases,
checkpoints and receipts. State Hub and standalone tmux-amq are adapters. Only
explicitly selected, gita-registered repos are valid worker targets.
2026-09-07: finished. The operator approved the documented deployment defaults
and transfer of canon review/registration to COORDINATION-WP-0004. Implementation
and local verification are complete. The service has not been enabled or used
to inject a live worker wake.
## Publish the v0.1 contract
```task
id: COORDINATION-WP-0003-T01
status: done
priority: high
state_hub_task_id: "a9e407aa-ac92-50b2-8aed-afb74e17e84f"
```
Authored `spec/worker-coordination-service-v0.1.md`. Reconciled on 2026-09-07 with
TAMQ's implemented adapter and the local-alpha runtime. The original speculative
proposal is preserved under `history/260907-worker-coordination-service-v0.1-proposal.md`.
The separate `coordination-engine` executable avoids replacing TAMQ's own `tamq`
CLI. TAMQ owns endpoint registration, transport profiles, queue/history/export/
replay, session lifecycle and unsafe local diagnostics. See ADR-002.
## Agree adapter and deployment decisions
```task
id: COORDINATION-WP-0003-T02
status: done
priority: high
state_hub_task_id: "1a428ed2-01d4-5af7-9341-db83712da9d9"
```
Implemented boundary: consume the published TAMQ v0.1 socket protocol, negotiate
required capabilities, preserve endpoint/message identity, refresh gita and
require exact configured targets. TAMQ remains responsible for slug/path
registration and local delivery. Coordination-engine does not introduce a second
inbound TAMQ attach handshake.
Approved deployment defaults are in `docs/worker-runtime.md` and
`docs/adr/002-worker-runtime-boundary.md`: same approved Unix user, mode-0600
sockets, explicit TAMQ socket, private XDG coordination state, retained history,
SQLite snapshots before migrations, 15-second polling, 30-second lease,
10-second renewal, four attempts, 5/15/60/300-second delays, zero safety retries,
and a conservative default policy. Repository selection is mandatory and empty
by default. No credentials are stored in configuration.
2026-09-07: operator explicitly approved these defaults in response to the
closure request. This records configuration decisions; live service activation
remains a separate operational action requiring selected repository targets.
## Establish OrwellLoggingDiagnostics practice pattern
```task
id: COORDINATION-WP-0003-T04
status: done
priority: medium
state_hub_task_id: "4ba98e37-cd98-5fb6-9065-4d241dfbabd2"
```
Prepared `docs/orwell-logging-diagnostics-candidate.md` for
`practice-pattern/orwell-logging-diagnostics`, with TAMQ as the known consumer.
Coordination-engine emits sanitized receipts and has no unsafe logging mode.
No matching canonical artifact was found in the current info-tech-canon checkout.
Its `infospace/assimilation/intake-and-assimilation-practice.md` requires explicit
owner disposition before registration. Owner review/registration remains pending.
2026-09-07: operator explicitly approved moving canon review/registration to
`workplans/COORDINATION-WP-0004-orwell-canon-review.md`. T04 closes with the
prepared candidate and approved scope transfer; canonical acceptance is not
claimed. The follow-up preserves owner disposition and registration criteria.
## Implement the coordination runtime
```task
id: COORDINATION-WP-0003-T03
status: done
priority: high
state_hub_task_id: "074e42ed-2049-5379-aac8-bb3b88672f60"
```
Implemented Python 3.11+ standard-library runtime with uv packaging and a
`coordination-engine` entry point. Includes:
- State Hub observation, task/workplan dependencies, explicit actionable inbox
markers, complete-snapshot gating and outage backoff.
- Same-user TAMQ socket client, version/capability negotiation, exact endpoint
selection, fresh gita validation and idempotent admission.
- Transactional SQLite leases/receipts, per-repo exclusion, bounded retries,
restart recovery, schema guard, snapshots and private local storage.
- Worker ack/renew/checkpoint/complete control socket; checkpoint continuation
receives a new linked trigger while transport recovery preserves lease identity.
- Conservative safety stops, sanitized durable projection outbox, safe diagnostics,
CLI help/version/completion, foreground lifecycle and a deployment/recovery runbook.
Validation on 2026-09-07: `make check` passes (54 tests passed, one opt-in live
smoke skipped; diff whitespace, compileall and help/version pass). `uv build`
produces wheel and source distribution. Tests use fake HTTP/gita/TAMQ peers,
actual temporary Unix sockets and foreground service stop/restart. No production
credentials, live worker injection, or deployment were required. The synchronous
local-alpha observer's small-worker-set limitation is documented in the runbook.

View file

@ -0,0 +1,133 @@
---
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 owner’s 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 owner’s 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; T01–T02 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: T01–T04 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.