Lead Ward agent launches with a compact operator state summary #1600

New issue

Closed

opened 2026-07-28 09:21:46 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-07-28 09:21:46 +00:00

Member

Observation from the recorded dress rehearsal

The first visible launch output was dominated by bootstrap paths, context composition, credentials, role metadata, preflight checks, and other implementation detail. The operator had to narrate that the output was noisy before the audience could see the important state.

For an asynchronous dispatch, the operator needs to establish only a few facts at launch: Ward accepted the issue, Ward selected the intended role and workflow, the engineer is running, and the operator can leave.

Desired behavior

Ward should print a compact operator-facing launch summary before verbose bootstrap output.

The summary should make these facts immediately visible:

issue reference
selected role and harness
resolved workflow
accepted or running state
the command or issue link for later inspection
an explicit indication that the operator can leave the execution loop

Ward can keep detailed bootstrap evidence available in verbose output or clearly separated logs. Warnings and failures must remain prominent.

Acceptance criteria

A default launch shows the compact state summary before implementation detail.
A viewer can identify the issue, actor, workflow, and current state without reading raw bootstrap lines.
The default output gives a clear later-inspection path.
Verbose mode retains the diagnostic information needed for debugging.
Focused output tests cover accepted, running, rejected, and bootstrap-failed states.

Harness-specific bootstrap noise: #1569
Recorded demo review: coilysiren/inbox#286

## Observation from the recorded dress rehearsal The first visible launch output was dominated by bootstrap paths, context composition, credentials, role metadata, preflight checks, and other implementation detail. The operator had to narrate that the output was noisy before the audience could see the important state. For an asynchronous dispatch, the operator needs to establish only a few facts at launch: Ward accepted the issue, Ward selected the intended role and workflow, the engineer is running, and the operator can leave. ## Desired behavior Ward should print a compact operator-facing launch summary before verbose bootstrap output. The summary should make these facts immediately visible: * issue reference * selected role and harness * resolved workflow * accepted or running state * the command or issue link for later inspection * an explicit indication that the operator can leave the execution loop Ward can keep detailed bootstrap evidence available in verbose output or clearly separated logs. Warnings and failures must remain prominent. ## Acceptance criteria * A default launch shows the compact state summary before implementation detail. * A viewer can identify the issue, actor, workflow, and current state without reading raw bootstrap lines. * The default output gives a clear later-inspection path. * Verbose mode retains the diagnostic information needed for debugging. * Focused output tests cover accepted, running, rejected, and bootstrap-failed states. ## Related evidence * Harness-specific bootstrap noise: #1569 * Recorded demo review: https://forgejo.coilysiren.me/coilysiren/inbox/issues/286

coilyco-ops added the

autonomy

async-consult

priority

labels

2026-07-29 03:47:41 +00:00

coilyco-ops closed this issue

2026-07-29 05:59:16 +00:00