Broker vs pre-flight: check placement (duplicate where state can drift) + log directionality (broker->dispatcher, pre-flight->dispatchee, 2nd missing) #1077

New issue

Open

opened 2026-07-10 19:02:59 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-07-10 19:02:59 +00:00

Member

Broker vs pre-flight: check placement + log-surfacing directionality (child of ward#1069)

This parent issue bundled multiple scopes and was removed from the milestone queue on 2026-07-15. Kai flagged that the title alone reads too broad for headless burndown.

Split children

ward#1334 defines the broker/pre-flight check-placement matrix.
ward#1336 surfaces broker dispatch logs to every dispatcher path.
ward#1335 injects pre-flight launch logs into the launched agent context.

Original framing

The broker + pre-flight two-layer gate needs a deliberate answer to two questions that were implicit:

Which checks live at which layer, and which are duplicated.
Who each layer's logs are surfaced to.

Many checks should be duplicated across both layers on purpose: the broker rejects a bad dispatch early before spending a container, and pre-flight re-checks at launch to catch anything that changed while the dispatch sat queued.

Broker dispatch logs should surface to the dispatcher. Pre-flight logs should surface to the dispatchee.

Decision for release inclusion

Keep this parent as consult/design tracking. The release should carry the smaller child issues instead of this bundled parent.

## Broker vs pre-flight: check placement + log-surfacing directionality (child of ward#1069) This parent issue bundled multiple scopes and was removed from the milestone queue on 2026-07-15. Kai flagged that the title alone reads too broad for headless burndown. ## Split children - ward#1334 defines the broker/pre-flight check-placement matrix. - ward#1336 surfaces broker dispatch logs to every dispatcher path. - ward#1335 injects pre-flight launch logs into the launched agent context. ## Original framing The broker + pre-flight two-layer gate needs a deliberate answer to two questions that were implicit: 1. Which checks live at which layer, and which are duplicated. 2. Who each layer's logs are surfaced to. Many checks should be duplicated across both layers on purpose: the broker rejects a bad dispatch early before spending a container, and pre-flight re-checks at launch to catch anything that changed while the dispatch sat queued. Broker dispatch logs should surface to the dispatcher. Pre-flight logs should surface to the dispatchee. ## Decision for release inclusion Keep this parent as consult/design tracking. The release should carry the smaller child issues instead of this bundled parent.

coilyco-ops added the

headless

labels

2026-07-10 19:02:59 +00:00

coilyco-ops added this to the warded control plane coherence milestone

2026-07-15 05:14:54 +00:00

coilyco-ops removed this from the warded control plane coherence milestone

2026-07-15 06:34:28 +00:00

coilyco-ops added

consult

and removed

headless