Follow-ups from retiring ward dispatch: consult/cascade gap, burndown skill rebuild, goose-triage consult label #176

New issue

Closed

opened 2026-06-18 08:09:26 +00:00 by coilysiren · 3 comments

coilysiren commented

2026-06-18 08:09:26 +00:00

Owner

Follow-ups from retiring ward dispatch (ward#174). The core retirement landed; these are the deferred pieces.

1. consult / cascade have no `ward agent` equivalent

ward dispatch had four surfaces; ward agent has two (work, headless) plus task and work --new-tab. Two postures retired with no successor:

consult - interactive with a raised interruption budget (the agent surfaces real judgment calls and waits). Today tooling-ward-agent maps "ask me before you decide" onto work + a --details note, which is weaker. Decide whether ward agent work --consult (or a --details-driven convention) is worth adding.
cascade - headless plus bounded recursive sub-dispatch. Today the answer is "slice with tooling-sidequest and spawn each child." Decide whether an automated cascade belongs on ward agent.

2. Rebuild `tooling-dispatch-burndown` on the container model (agentic-os-kai)

The burndown skill's drain loop is built on ward dispatch headless (host worktree) + a ward dispatch registry pid-count concurrency cap + ward dispatch reap + kill -TERM <pid>. None of those has a verified one-to-one ward agent / ward container equivalent:

worktree-per-issue -> container-per-issue
ward dispatch registry | grep -c '^pid=' cap -> count running agent containers (ward container ls / docker ps) or lean on the per-issue reservation
ward dispatch reap -> ward container reap
kill -TERM <pid> -> ward container down <name> / docker stop

A staleness banner was added to the skill pointing here. Rebuild the drain loop against the container surface and re-validate the concurrency cap on a Mac.

3. goose-triage `consult` mode label (agentic-os)

The goose-triage automation-mode axis labels issues headless / interactive / consult. With dispatch retired, consult no longer maps to a ward agent surface. Decide whether to keep the label (as a posture hint for a future --consult) or collapse the axis to headless / interactive. Tied to item 1.

Follow-ups from retiring `ward dispatch` (ward#174). The core retirement landed; these are the deferred pieces. ## 1. consult / cascade have no `ward agent` equivalent `ward dispatch` had four surfaces; `ward agent` has two (`work`, `headless`) plus `task` and `work --new-tab`. Two postures retired with no successor: - **consult** - interactive with a raised interruption budget (the agent surfaces real judgment calls and waits). Today `tooling-ward-agent` maps "ask me before you decide" onto `work` + a `--details` note, which is weaker. Decide whether `ward agent work --consult` (or a `--details`-driven convention) is worth adding. - **cascade** - headless plus bounded recursive sub-dispatch. Today the answer is "slice with `tooling-sidequest` and spawn each child." Decide whether an automated cascade belongs on `ward agent`. ## 2. Rebuild `tooling-dispatch-burndown` on the container model (agentic-os-kai) The burndown skill's drain loop is built on `ward dispatch headless` (host worktree) + a `ward dispatch registry` pid-count concurrency cap + `ward dispatch reap` + `kill -TERM <pid>`. None of those has a verified one-to-one `ward agent` / `ward container` equivalent: - worktree-per-issue -> container-per-issue - `ward dispatch registry | grep -c '^pid='` cap -> count running agent containers (`ward container ls` / `docker ps`) or lean on the per-issue reservation - `ward dispatch reap` -> `ward container reap` - `kill -TERM <pid>` -> `ward container down <name>` / `docker stop` A staleness banner was added to the skill pointing here. Rebuild the drain loop against the container surface and re-validate the concurrency cap on a Mac. ## 3. goose-triage `consult` mode label (agentic-os) The goose-triage automation-mode axis labels issues `headless` / `interactive` / `consult`. With dispatch retired, `consult` no longer maps to a `ward agent` surface. Decide whether to keep the label (as a posture hint for a future `--consult`) or collapse the axis to `headless` / `interactive`. Tied to item 1.

coilyco-ops added the

consult

labels

2026-06-24 04:15:18 +00:00

coilyco-ops commented

2026-06-24 17:26:34 +00:00

Member

Re-triage (goose-triage method, claude-macos-kais-macbook-pro-2 as the judgment engine, 2026-06-24)

P3 - Multi-part follow-ups from retiring ward dispatch, real but deferred decisions, kept.
consult - Each part needs a human decision (consult/cascade successor, burndown rebuild).

**Re-triage** (goose-triage method, claude-macos-kais-macbook-pro-2 as the judgment engine, 2026-06-24) - **P3** - Multi-part follow-ups from retiring ward dispatch, real but deferred decisions, kept. - **consult** - Each part needs a human decision (consult/cascade successor, burndown rebuild).

coilyco-ops commented

2026-06-24 17:28:52 +00:00

Member

Re-triage (goose-triage method, claude-macos-kais-macbook-pro-2 as the judgment engine, 2026-06-24)

P3 - Multi-part follow-ups from retiring ward dispatch, real but deferred decisions, kept.
consult - Each part needs a human decision (consult/cascade successor, burndown rebuild).

coilysiren added

and removed

labels

2026-07-01 04:29:55 +00:00

coilyco-ops referenced this issue

2026-07-02 00:17:07 +00:00

warded director: consult-to-headless conversion flow (decision interview that upgrades tickets to dispatchable) #493

coilyco-ops commented

2026-07-02 00:22:44 +00:00

Member

Stays consult: the consult/cascade successor question now has a concrete design home - the director interview flow (#493) covers the consult posture; cascade remains open. Skill rebuild + goose-triage label pieces unchanged. Recorded by Claude Code (Fable) during the 2026-07-01 ward launch triage session with Kai.

coilysiren closed this issue

2026-07-04 10:36:44 +00:00