design a fully containerized ward #1562

New issue

Closed

opened 2026-07-25 11:14:28 +00:00 by coilysiren · 4 comments

coilysiren commented

2026-07-25 11:14:28 +00:00

Owner

No description provided.

coilysiren commented

2026-07-25 11:16:09 +00:00

Author

Owner

This really comes down to: can you run a containerized broker? Said broker would be a sister to the director, same as the engineer or QA

coilysiren commented

2026-07-25 11:16:54 +00:00

Author

Owner

It would need to be docker compose at minimum, the broker can't be inside the same container as the director... I think

coilyco-ops commented

2026-07-25 12:46:36 +00:00

Member

ward#1562 implementation contract

Goal - Replace the in-process host dispatch broker with an independently supervised broker container that serves the director over a stable Compose network address and launches engineer/QA siblings without sharing the director or terminal lifecycle.

Done-condition - The landed Ward release starts a broker + director stack, brokered dispatch uses the broker service, director/client exit cannot kill the broker, broker restart reconciles accepted work without duplicate launch, targeted lifecycle/chaos coverage and the full Ward validation suite pass, and the Forgejo release is green.

Non-goals - Redesigning token or permission boundaries, creating a host-wide singleton broker, changing engineer/QA product behavior, or changing unrelated fleet infrastructure.

**ward#1562 implementation contract** **Goal** - Replace the in-process host dispatch broker with an independently supervised broker container that serves the director over a stable Compose network address and launches engineer/QA siblings without sharing the director or terminal lifecycle. **Done-condition** - The landed Ward release starts a broker + director stack, brokered dispatch uses the broker service, director/client exit cannot kill the broker, broker restart reconciles accepted work without duplicate launch, targeted lifecycle/chaos coverage and the full Ward validation suite pass, and the Forgejo release is green. **Non-goals** - Redesigning token or permission boundaries, creating a host-wide singleton broker, changing engineer/QA product behavior, or changing unrelated fleet infrastructure.

coilysiren referenced this issue from a commit

2026-07-25 14:42:00 +00:00

feat: supervise director dispatch broker in compose

coilysiren referenced this issue from a commit

2026-07-25 15:32:14 +00:00

test: align broker recovery coverage

coilyco-ops commented

2026-07-25 15:36:26 +00:00

Member

Implemented and released in Ward v0.809.0: https://forgejo.coilysiren.me/coilyco-flight-deck/ward/releases/tag/v0.809.0. Broker lifecycle: warded director now prepares a persistent Compose stack under ~/.ward/director-stacks/PROJECT/. The broker is a separate restart-unless-stopped service, while the director remains a one-off client. Stability boundary: director or client exit no longer owns the broker process, so broker loss is no longer coupled to a director surface ending. Recovery: durable request IDs, fingerprints, and a request journal let a restarted broker reconcile accepted work without launching duplicate engineers. Broker health stays unready until reconciliation finishes. Isolation: worker failures stay contained, while host identity and supported harness credentials flow into the persistent stack. Documentation covers the lifecycle, recovery contract, container contract, operator behavior, and feature inventory. Verification: ordered asynchronous broker tests, ward exec vet, and the full pre-commit suite pass. Promotion run #2429 passed on Linux and promoted the implementation to release: https://forgejo.coilysiren.me/coilyco-flight-deck/ward/actions/runs/2429. Commits: 6c929787b4 and 91606fc320.