coilyco-flight-deck/agentic-os

Watch

Confirm whether Ward's director, qa, and engineer fixed workflows track the v3 roster rename #1224

New issue

Closed

opened 2026-08-23 21:25:10 +00:00 by coilyco-ops · 1 comment

coilyco-ops commented

2026-08-23 21:25:10 +00:00

Member

Filed while landing the v3 roster reflow (#1222), which deliberately did not touch these.

The ambiguity

The v3 migration guide says to update Ward role selections to the new identifiers. AOS docs also name three Ward surfaces that are spelled with retired slugs but are not role selections:

docs/aos-cli.md - "Ward ships the director, qa, and engineer repository workflows."
docs/aos-context-bundle.md - "It invokes the matching fixed workflow for director, qa, or engineer."
docs/ward-specs.md - director.default-scope.
docs/repo-layout.md - ward agent director --help, and "director merge" as a lane.
justfile and agent-terminal - "branded Alacritty director window / launcher".

These are Ward's names for fixed workflows, a config key, and a merge lane, not selections of a Core Roster seat. Ward owns them, so renaming them here on the roster's schedule would make the docs describe a Ward that does not exist. Leaving them is also a bet, since a reader cannot tell a Ward workflow named qa from the seat that was just cut.

What closing this looks like

Read Ward's own surface and answer two questions:

Do Ward's fixed repository workflows still spell themselves director, qa, and engineer after v3, or did they move with the roster?
Is director in director.default-scope, ward agent director, "director merge", and "director window" the same noun in all four, or has it already drifted into meaning the launching or merging surface rather than the seat?

Then either update the AOS docs to match Ward, or add one line where the collision is worst saying the Ward workflow name is not a roster seat. docs/aos-roles-and-voice.md is the sharpest place for that, since it already contrasts a role slug against Ward's lifecycle in the same paragraph.

Documentation clarity rather than a broken surface. AOS passes --role through without an allowlist, so nothing resolves against these strings at launch.

Filed while landing the v3 roster reflow (#1222), which deliberately did not touch these. ## The ambiguity The v3 migration guide says to update Ward role selections to the new identifiers. AOS docs also name three Ward surfaces that are spelled with retired slugs but are not role selections: * `docs/aos-cli.md` - "Ward ships the `director`, `qa`, and `engineer` repository workflows." * `docs/aos-context-bundle.md` - "It invokes the matching fixed workflow for `director`, `qa`, or `engineer`." * `docs/ward-specs.md` - `director.default-scope`. * `docs/repo-layout.md` - `ward agent director --help`, and "director merge" as a lane. * `justfile` and `agent-terminal` - "branded Alacritty director window / launcher". These are Ward's names for fixed workflows, a config key, and a merge lane, not selections of a Core Roster seat. Ward owns them, so renaming them here on the roster's schedule would make the docs describe a Ward that does not exist. Leaving them is also a bet, since a reader cannot tell a Ward workflow named `qa` from the seat that was just cut. ## What closing this looks like Read Ward's own surface and answer two questions: 1. Do Ward's fixed repository workflows still spell themselves `director`, `qa`, and `engineer` after v3, or did they move with the roster? 2. Is `director` in `director.default-scope`, `ward agent director`, "director merge", and "director window" the same noun in all four, or has it already drifted into meaning the launching or merging surface rather than the seat? Then either update the AOS docs to match Ward, or add one line where the collision is worst saying the Ward workflow name is not a roster seat. `docs/aos-roles-and-voice.md` is the sharpest place for that, since it already contrasts a role slug against Ward's lifecycle in the same paragraph. Documentation clarity rather than a broken surface. AOS passes `--role` through without an allowlist, so nothing resolves against these strings at launch.

coilyco-ops added the

role/platform

priority

labels

2026-08-25 08:11:43 +00:00

coilyco-ops added the

autonomy

async-consult

label

2026-08-25 09:30:45 +00:00

coilyco-ops commented

2026-08-27 03:19:02 +00:00

Author

Member

Closed in the 2026-08-26 backlog burn-down (coilyco-bridge/agentic-os-kai#901).

Closing: Ward is dormant, so its director, qa, and engineer fixed workflows are not being selected against the v3 roster by anyone. Re-ask if Ward comes back, because the answer will depend on what it looks like then.

This was priority/P3, the default tier that unsure and unscored issues land in, so it had never been positively judged worth keeping. The 2026-08-26 burn-down ranked the whole P3 pool and cut the bottom. Closed here means not on the list, not wrong or worthless.

If this is live work, reopen it. The whole set is recoverable with state:closed label:burndown-2026-08.

Closed in the 2026-08-26 backlog burn-down (coilyco-bridge/agentic-os-kai#901). Closing: Ward is dormant, so its `director`, `qa`, and `engineer` fixed workflows are not being selected against the v3 roster by anyone. Re-ask if Ward comes back, because the answer will depend on what it looks like then. This was `priority/P3`, the default tier that unsure and unscored issues land in, so it had never been positively judged worth keeping. The 2026-08-26 burn-down ranked the whole P3 pool and cut the bottom. Closed here means not on the list, not wrong or worthless. If this is live work, reopen it. The whole set is recoverable with `state:closed label:burndown-2026-08`.

coilyco-ops

2026-08-27 03:19:03 +00:00

closed this issue
added the
burndown-2026-08
label

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

coilyco-flight-deck/agentic-os#1224

No description provided.

Rows
Columns