coilyco-flight-deck/agent-compose
coilyco-flight-deck/agent-compose
Watch
2
0
Code Issues 41 Pull requests Projects Releases 187 Packages Wiki Activity Actions

Make the label taxonomy declarative, then rename role/* onto the current roster #342

New issue
Open
opened 2026-08-25 17:14:23 +00:00 by coilyco-ops · 5 comments
coilyco-ops commented 2026-08-25 17:14:23 +00:00
Member
Copy link

Outcome

The role/* label axis names the roster Core Roster v2 replaced. Fix it, and fix the arrangement that let it drift silently.

Body rewritten after the decisions landed. The investigation and the original framing are in the comments, which are worth reading for the evidence rather than just the plan.

Root cause

infrastructure/scripts/forgejo-label-taxonomy-sync.py names the authority in its docstring: "coilyco-gaming is the source of truth. Run after changing labels there." The authoritative taxonomy is live Forgejo org state, with no committed file declaring it. A label change is an API call with no diff, no review, and no commit.

agentic-os/.agents/composed/tooling-issue-prioritization/references/label-taxonomy.md describes the taxonomy without defining it, which is how it sits listing nine role/* values while the roster moved to seven different ones and nothing noticed.

This is the same failure #329 is fixing in agent-compose: configuration living inside a running system rather than in reviewable data. The drift is what the arrangement produces, not an oversight.

What makes this cheap

  • Nothing matches role/* strings. Across every checkout on this host, outside the prioritization skill docs, zero matches. No dispatch gate, no test, no script. The label-taxonomy.md warning that renaming is a breaking change is accurate for autonomy/* and priority/* and does not apply here.
  • In-place edit carries the issues. The sync script edits rather than deletes and recreates, specifically so every issue keeps its label through a rename. Five clean renames move 717 issues with zero per-issue work.

The mapping

Counts via issues/search, approximate given known indexer lag.

  • role/engineer 414 to role/platform. Clean rename.
  • role/ops 194 to role/sysadmin. Clean rename.
  • role/ai 76 to role/eval. Clean rename.
  • role/director 53 to role/tpm. Clean rename.
  • role/creator 22 to role/devrel. Clean rename.
  • role/design 11 to role/frontend. Clean rename.
  • role/exec 4. Collides with director on tpm. Migrate its 4 issues onto role/tpm, then delete.
  • role/qa 16. Retired. Redistribute its issues, then delete.
  • role/gamedev. New seat, no predecessor. Pure create.
  • role/human 4. Unchanged. Never a seat, and stays the value meaning a person and specifically not an agent seat.

Decisions

  1. Declarative first. Land a committed taxonomy file, point the sync script at it instead of the gaming org, and prove the first run is a no-op. The rename then lands as a reviewable diff rather than as undocumented org state.
  2. role/qa is retired, its 16 issues redistributed, and the label deleted. See the open question below.
  3. role/director becomes role/tpm, carrying its 53 issues. role/exec's 4 move onto role/tpm by hand, then role/exec is deleted.
  4. Scope is the three orgs: coilyco-gaming, coilyco-bridge, coilyco-flight-deck. coilysiren repo-level labels and coilysiren/inbox are out of scope and tracked separately.

Sequence

  1. Author the taxonomy file and make the sync script read it. Verify a run is a no-op against current state. Nothing changes in Forgejo.
  2. Change the file to the new mapping, review the diff, run the sync. This performs the six clean renames and creates role/gamedev.
  3. Migrate role/exec's 4 issues onto role/tpm, then delete role/exec.
  4. Redistribute role/qa's 16 issues, then delete role/qa.
  5. Update label-taxonomy.md and the tooling-issue-prioritization skill so the described taxonomy matches the defined one.
  6. Apply role labels to #329 through #342, which are waiting on this.

Steps 2 through 4 are irreversible in the delete cases and need an org owner token. Per the sync script's docstring the coilyco-ops bot is a member rather than an owner and answers 403, so Kai runs these.

Open, needs a rule before step 4

Where do role/qa's 16 issues go? Core Roster v2 has no QA seat, so each needs a destination. Proposal: read them and assign by content, with agent-behavior measurement going to role/eval and everything else defaulting to role/platform. Confirm before deleting, since the delete cannot be undone.

Acceptance criteria

  • A committed file defines the taxonomy, and the sync script reads it rather than an org's live state.
  • The first sync run against unchanged state performs no writes.
  • Every current roster seat has a role/* label across all three orgs.
  • No retired seat name remains as a label.
  • Every issue that carried a renamed label still carries its successor.
  • role/exec and role/qa issues are rehomed before their labels are deleted.
  • label-taxonomy.md and the prioritization skill describe the current set.
  • #329 through #342 carry role labels.
  • A check exists, or is filed, that reports divergence between the label set and the roster.

Boundaries

  • Do not delete a label before its issues are rehomed. Delete strips the label from every issue holding it and is the only irreversible move here.
  • Do not rename autonomy/* or priority/* in this work. Those are matched by string in a test, two AGENTS files, a worklog, and two migration scripts, and the silent-failure warning applies to them.
  • coilysiren/inbox uses an unprefixed taxonomy and is not converted here.
## Outcome The `role/*` label axis names the roster Core Roster v2 replaced. Fix it, and fix the arrangement that let it drift silently. **Body rewritten after the decisions landed.** The investigation and the original framing are in the comments, which are worth reading for the evidence rather than just the plan. ## Root cause `infrastructure/scripts/forgejo-label-taxonomy-sync.py` names the authority in its docstring: "coilyco-gaming is the source of truth. Run after changing labels there." The authoritative taxonomy is **live Forgejo org state**, with no committed file declaring it. A label change is an API call with no diff, no review, and no commit. `agentic-os/.agents/composed/tooling-issue-prioritization/references/label-taxonomy.md` describes the taxonomy without defining it, which is how it sits listing nine `role/*` values while the roster moved to seven different ones and nothing noticed. This is the same failure #329 is fixing in agent-compose: configuration living inside a running system rather than in reviewable data. The drift is what the arrangement produces, not an oversight. ## What makes this cheap * **Nothing matches `role/*` strings.** Across every checkout on this host, outside the prioritization skill docs, zero matches. No dispatch gate, no test, no script. The `label-taxonomy.md` warning that renaming is a breaking change is accurate for `autonomy/*` and `priority/*` and does not apply here. * **In-place edit carries the issues.** The sync script edits rather than deletes and recreates, specifically so every issue keeps its label through a rename. Five clean renames move 717 issues with zero per-issue work. ## The mapping Counts via `issues/search`, approximate given known indexer lag. * `role/engineer` 414 to `role/platform`. Clean rename. * `role/ops` 194 to `role/sysadmin`. Clean rename. * `role/ai` 76 to `role/eval`. Clean rename. * `role/director` 53 to `role/tpm`. Clean rename. * `role/creator` 22 to `role/devrel`. Clean rename. * `role/design` 11 to `role/frontend`. Clean rename. * `role/exec` 4. Collides with `director` on `tpm`. Migrate its 4 issues onto `role/tpm`, then delete. * `role/qa` 16. Retired. Redistribute its issues, then delete. * `role/gamedev`. New seat, no predecessor. Pure create. * `role/human` 4. Unchanged. Never a seat, and stays the value meaning a person and specifically not an agent seat. ## Decisions 1. **Declarative first.** Land a committed taxonomy file, point the sync script at it instead of the gaming org, and prove the first run is a no-op. The rename then lands as a reviewable diff rather than as undocumented org state. 2. **`role/qa` is retired**, its 16 issues redistributed, and the label deleted. See the open question below. 3. **`role/director` becomes `role/tpm`**, carrying its 53 issues. `role/exec`'s 4 move onto `role/tpm` by hand, then `role/exec` is deleted. 4. **Scope is the three orgs**: `coilyco-gaming`, `coilyco-bridge`, `coilyco-flight-deck`. `coilysiren` repo-level labels and `coilysiren/inbox` are out of scope and tracked separately. ## Sequence 1. Author the taxonomy file and make the sync script read it. Verify a run is a no-op against current state. Nothing changes in Forgejo. 2. Change the file to the new mapping, review the diff, run the sync. This performs the six clean renames and creates `role/gamedev`. 3. Migrate `role/exec`'s 4 issues onto `role/tpm`, then delete `role/exec`. 4. Redistribute `role/qa`'s 16 issues, then delete `role/qa`. 5. Update `label-taxonomy.md` and the `tooling-issue-prioritization` skill so the described taxonomy matches the defined one. 6. Apply role labels to #329 through #342, which are waiting on this. Steps 2 through 4 are irreversible in the delete cases and need an **org owner token**. Per the sync script's docstring the `coilyco-ops` bot is a member rather than an owner and answers 403, so Kai runs these. ## Open, needs a rule before step 4 Where do `role/qa`'s 16 issues go? Core Roster v2 has no QA seat, so each needs a destination. Proposal: read them and assign by content, with agent-behavior measurement going to `role/eval` and everything else defaulting to `role/platform`. Confirm before deleting, since the delete cannot be undone. ## Acceptance criteria - [ ] A committed file defines the taxonomy, and the sync script reads it rather than an org's live state. - [ ] The first sync run against unchanged state performs no writes. - [ ] Every current roster seat has a `role/*` label across all three orgs. - [ ] No retired seat name remains as a label. - [ ] Every issue that carried a renamed label still carries its successor. - [ ] `role/exec` and `role/qa` issues are rehomed before their labels are deleted. - [ ] `label-taxonomy.md` and the prioritization skill describe the current set. - [ ] #329 through #342 carry role labels. - [ ] A check exists, or is filed, that reports divergence between the label set and the roster. ## Boundaries * Do not delete a label before its issues are rehomed. Delete strips the label from every issue holding it and is the only irreversible move here. * Do not rename `autonomy/*` or `priority/*` in this work. Those are matched by string in a test, two AGENTS files, a worklog, and two migration scripts, and the silent-failure warning applies to them. * `coilysiren/inbox` uses an unprefixed taxonomy and is not converted here.
coilyco-ops commented 2026-08-25 17:29:42 +00:00
Author
Member
Copy link

Investigation: where the canon lives, what breaks, and what it costs

Read on 2026-08-25. Three findings change the plan in the body, one of them substantially.

1. The canon has no tracked home, and that is the root cause

coilyco-flight-deck/infrastructure/scripts/forgejo-label-taxonomy-sync.py is the rollout, and its docstring names the authority: "coilyco-gaming is the source of truth. Run after changing labels there, so the three orgs keep one vocabulary."

The authoritative taxonomy is live Forgejo org state. There is no committed file declaring it. A label change is an API call or a UI click with no diff, no review, and no commit. references/label-taxonomy.md in agentic-os describes the taxonomy but does not define it, which is why it can sit there listing nine role/* values while the roster it mirrors moved to seven different ones and nothing noticed.

This is the same disease #329 is curing in agent-compose: configuration living inside a running system instead of in reviewable data, with the tool that reads it treated as the authority. The label drift is not an oversight, it is what this arrangement produces.

2. Renaming role/* is not the breaking change the docs warn about

label-taxonomy.md says "Renaming these labels is a breaking change" and warns of silent failure. That warning is accurate for autonomy/* and priority/*, and substantially overstated for role/*.

Grepped across every checkout on this host. Outside the tooling-issue-prioritization skill docs, role/* values are matched in zero places. No dispatch gate, no test, no script.

For contrast, autonomy/* is matched in agentic-os/tests/test_blocked_on_dependency_contract.py:45, in sirens-echo/AGENTS.md, in its worklog, in the sync script's RENAME map, and in agentic-os-kai/scripts/backfill-personal-labels.sh.

So the axis that needs renaming is the one axis that is safe to rename.

3. In-place edit means a rename carries its issues automatically

From the sync script: "Existing labels are EDITED in place rather than deleted and recreated, so every issue keeps the label it already carries through the rename. Only genuinely new labels are created, and nothing is deleted - a delete would strip the label from every issue holding it, which is the one irreversible move here."

This supersedes step 3 in the body, which called for relabeling issues across the org. For any 1:1 rename, no issue is touched at all.

Counts, and where the mapping is not 1:1

Per-label totals via issues/search, so approximate rather than exact given known indexer lag.

  • role/engineer 414, to platform. Clean rename.
  • role/ops 194, to sysadmin. Clean rename.
  • role/ai 76, to eval. Clean rename.
  • role/director 53, to tpm. Clean rename, but collides with exec.
  • role/creator 22, to devrel. Clean rename.
  • role/qa 16, no successor seat. Decision needed.
  • role/design 11, to frontend. Clean rename.
  • role/exec 4, also to tpm. Collision with director.
  • role/human 4, unchanged. Not a seat by design.
  • gamedev, new seat with no predecessor. Pure create.

Roughly 794 labeled issues total. Five clean renames carry 717 of them with zero per-issue work. The hand-migration is about twenty issues: move exec's 4 onto tpm, and decide qa's 16.

role/qa may not be an orphan

The body called qa a value with no successor. #273 is open and titled "role-qa: evaluate bounded reconfiguration authority for the QA seat", which suggests QA is a seat under active consideration rather than a retired one. Settle #273's direction before retiring role/qa, because deleting a label is the one irreversible move in this whole operation.

Operational constraint

The sync script requires an org owner token. Per its docstring the coilyco-ops bot is a member rather than an owner on all three orgs and answers 403, so this needs Kai's credentials. That makes the rollout HITL by mechanism, not merely by policy.

Namespaces the sync script does not cover

  • coilysiren/coilysiren carries repo-level labels with the same taxonomy, ids 339 through 414. The sync script's targets are only coilyco-bridge and coilyco-flight-deck. agentic-os-kai/scripts/backfill-personal-labels.sh appears to be the separate path for these.
  • coilysiren/inbox uses an entirely different scheme. Per deploy/services/forgejo-mcp/docs/tool-surface.md:29, it "uses an unprefixed taxonomy that a prefixed rule would lock out entirely."
  • coilysiren/inbox and coilysiren/lore are private and could not be enumerated unauthenticated, so their label state is unverified here.
## Investigation: where the canon lives, what breaks, and what it costs Read on 2026-08-25. Three findings change the plan in the body, one of them substantially. ### 1. The canon has no tracked home, and that is the root cause `coilyco-flight-deck/infrastructure/scripts/forgejo-label-taxonomy-sync.py` is the rollout, and its docstring names the authority: **"coilyco-gaming is the source of truth. Run after changing labels there, so the three orgs keep one vocabulary."** The authoritative taxonomy is live Forgejo org state. There is no committed file declaring it. A label change is an API call or a UI click with no diff, no review, and no commit. `references/label-taxonomy.md` in agentic-os describes the taxonomy but does not define it, which is why it can sit there listing nine `role/*` values while the roster it mirrors moved to seven different ones and nothing noticed. **This is the same disease #329 is curing in agent-compose**: configuration living inside a running system instead of in reviewable data, with the tool that reads it treated as the authority. The label drift is not an oversight, it is what this arrangement produces. ### 2. Renaming `role/*` is not the breaking change the docs warn about `label-taxonomy.md` says "Renaming these labels is a breaking change" and warns of silent failure. That warning is accurate for `autonomy/*` and `priority/*`, and substantially overstated for `role/*`. Grepped across every checkout on this host. Outside the `tooling-issue-prioritization` skill docs, `role/*` values are matched in **zero** places. No dispatch gate, no test, no script. For contrast, `autonomy/*` is matched in `agentic-os/tests/test_blocked_on_dependency_contract.py:45`, in `sirens-echo/AGENTS.md`, in its worklog, in the sync script's `RENAME` map, and in `agentic-os-kai/scripts/backfill-personal-labels.sh`. So the axis that needs renaming is the one axis that is safe to rename. ### 3. In-place edit means a rename carries its issues automatically From the sync script: **"Existing labels are EDITED in place rather than deleted and recreated, so every issue keeps the label it already carries through the rename. Only genuinely new labels are created, and nothing is deleted - a delete would strip the label from every issue holding it, which is the one irreversible move here."** This supersedes step 3 in the body, which called for relabeling issues across the org. For any 1:1 rename, no issue is touched at all. ### Counts, and where the mapping is not 1:1 Per-label totals via `issues/search`, so approximate rather than exact given known indexer lag. * `role/engineer` 414, to `platform`. Clean rename. * `role/ops` 194, to `sysadmin`. Clean rename. * `role/ai` 76, to `eval`. Clean rename. * `role/director` 53, to `tpm`. Clean rename, but collides with `exec`. * `role/creator` 22, to `devrel`. Clean rename. * `role/qa` 16, no successor seat. **Decision needed.** * `role/design` 11, to `frontend`. Clean rename. * `role/exec` 4, also to `tpm`. **Collision with `director`.** * `role/human` 4, unchanged. Not a seat by design. * `gamedev`, new seat with no predecessor. Pure create. Roughly 794 labeled issues total. Five clean renames carry 717 of them with zero per-issue work. The hand-migration is about **twenty issues**: move `exec`'s 4 onto `tpm`, and decide `qa`'s 16. ### `role/qa` may not be an orphan The body called `qa` a value with no successor. #273 is open and titled "role-qa: evaluate bounded reconfiguration authority for the QA seat", which suggests QA is a seat under active consideration rather than a retired one. Settle #273's direction before retiring `role/qa`, because deleting a label is the one irreversible move in this whole operation. ### Operational constraint The sync script requires an **org owner token**. Per its docstring the `coilyco-ops` bot is a member rather than an owner on all three orgs and answers 403, so this needs Kai's credentials. That makes the rollout HITL by mechanism, not merely by policy. ### Namespaces the sync script does not cover * `coilysiren/coilysiren` carries repo-level labels with the same taxonomy, ids 339 through 414. The sync script's targets are only `coilyco-bridge` and `coilyco-flight-deck`. `agentic-os-kai/scripts/backfill-personal-labels.sh` appears to be the separate path for these. * `coilysiren/inbox` uses an entirely different scheme. Per `deploy/services/forgejo-mcp/docs/tool-surface.md:29`, it "uses an unprefixed taxonomy that a prefixed rule would lock out entirely." * `coilysiren/inbox` and `coilysiren/lore` are private and could not be enumerated unauthenticated, so their label state is unverified here.
coilyco-ops changed title from The org role labels encode the retired roster, so new work cannot be role-labeled to Make the label taxonomy declarative, then rename role/* onto the current roster 2026-08-25 17:34:32 +00:00
coilyco-ops commented 2026-08-25 18:19:17 +00:00
Author
Member
Copy link

Step 1 authored, in review

coilyco-flight-deck/infrastructure#932. Changes nothing in Forgejo.

config/forgejo-label-taxonomy.yaml declares the taxonomy, the sync script drives it, and four justfile verbs exist where there were none. The committed file is a faithful snapshot of current state.

Verified, both directions

just forgejo-label-taxonomy-check reports all three orgs converged and exits 0. A probe taxonomy carrying a rename, a colour change, and a new label plans all three correctly on every org and exits 1, so "converged" is a real reading rather than a vacuous one. 17 planner tests with no live calls. Full pre-commit suite green.

A finding that explains the drift

The rollout script had been unrunnable. It called json.loads on aosguard output without --output json, and aosguard emits YAML, so it raised on its first read. There was no test and no justfile verb, so nothing caught it.

That reframes the root cause in the body. The taxonomy did not drift only because the authority was live org state. It drifted because the one tool that could have corrected it was broken, and nothing anywhere would have said so.

Acceptance criteria this covers, pending merge

  • A committed file defines the taxonomy, and the sync script reads it rather than an org's live state.
  • The first sync run against unchanged state performs no writes.

What step 2 now looks like

A diff to the new file. Add the pairs to renames:, change the entries under labels:, dry-run, apply. From the probe:

=== coilyco-gaming
  would rename role/ai -> role/eval
  would edit   role/ops
  would create role/gamedev

Because a rename is an edit in place, role/engineer's 414 issues move with the label and cost nothing.

Where it stops

The merge is director-gated per infrastructure's own AGENTS.md, so I stopped at the pull request rather than merging. Steps 2 through 4 need an org owner token regardless, since coilyco-ops is a member rather than an owner and gets 403 on org label writes.

## Step 1 authored, in review [coilyco-flight-deck/infrastructure#932](https://forgejo.coilysiren.me/coilyco-flight-deck/infrastructure/pulls/932). Changes nothing in Forgejo. `config/forgejo-label-taxonomy.yaml` declares the taxonomy, the sync script drives it, and four justfile verbs exist where there were none. The committed file is a faithful snapshot of current state. ### Verified, both directions `just forgejo-label-taxonomy-check` reports all three orgs converged and exits 0. A probe taxonomy carrying a rename, a colour change, and a new label plans all three correctly on every org and exits 1, so "converged" is a real reading rather than a vacuous one. 17 planner tests with no live calls. Full pre-commit suite green. ### A finding that explains the drift **The rollout script had been unrunnable.** It called `json.loads` on `aosguard` output without `--output json`, and aosguard emits YAML, so it raised on its first read. There was no test and no justfile verb, so nothing caught it. That reframes the root cause in the body. The taxonomy did not drift only because the authority was live org state. It drifted because the one tool that could have corrected it was broken, and nothing anywhere would have said so. ### Acceptance criteria this covers, pending merge * A committed file defines the taxonomy, and the sync script reads it rather than an org's live state. * The first sync run against unchanged state performs no writes. ### What step 2 now looks like A diff to the new file. Add the pairs to `renames:`, change the entries under `labels:`, dry-run, apply. From the probe: ``` === coilyco-gaming would rename role/ai -> role/eval would edit role/ops would create role/gamedev ``` Because a rename is an edit in place, `role/engineer`'s 414 issues move with the label and cost nothing. ### Where it stops The merge is director-gated per infrastructure's own AGENTS.md, so I stopped at the pull request rather than merging. Steps 2 through 4 need an org owner token regardless, since `coilyco-ops` is a member rather than an owner and gets 403 on org label writes.
coilyco-ops commented 2026-08-25 18:32:05 +00:00
Author
Member
Copy link

Step 4 prepared: where role/qa's 16 issues go

Rule approved by Kai: agent-behavior measurement to role/eval, everything else defaulting to role/platform, confirmed per issue before the delete. All 16 read.

Refinement that halves the work

Eight of the sixteen already carry a second role/* label. role/* is deliberately non-exclusive, so those are already routed. Deleting role/qa strips it from every issue holding it, which is exactly the desired outcome for these eight and needs no per-issue action at all.

Applying the default to them would be wrong rather than merely redundant. sirens-echo#265 carries role/ai, which becomes role/eval, so adding role/platform would misroute it.

So the work is 8 label adds, then the delete.

Needs a label before the delete

To role/eval, because each measures how an agent or the inference path actually behaves:

  • coilyco-gaming/sirens-echo#1134 - watch the coalescing lane answer a real member, six observations no test reaches. Observing live agent behavior.
  • coilyco-gaming/sirens-echo#1082 - measure the coalescing lane once #1080 rolls, and check how a merged reply reads.
  • coilyco-flight-deck/agent-proxy#107 - concurrency burst test. Body is a measurement design: Little's law arrival-rate arithmetic, three competing explanations span data cannot separate, and one burst to decide between them. Textbook eval.

To role/platform, because each is a defect or gap in software rather than a measurement:

  • coilyco-flight-deck/agentic-os#1117 - docs/test-harness.md documents a goose harness deleted in June 2026.
  • coilyco-flight-deck/lunch-money-k8s#42, coilyco-flight-deck/bluesky-mcp#12, coilyco-flight-deck/node-stats-mcp#22 - the caveat-last ordering audit. The finding surfaced from an agent's wrong answer, but the fix is response construction in each MCP server, so the work is platform's.
  • coilyco-gaming/eco-app#270 - QA sweep collector across the 25-tool Eco MCP surface. A defect collector on a service.

Needs nothing, the delete handles them

  • coilyco-gaming/eco-mods#19, coilyco-gaming/eco-app#269, coilyco-gaming/eco-app#184, coilyco-gaming/galaxy-gen#78, coilyco-gaming/sirens-echo#577 (closed) - all carry role/engineer, which becomes role/platform.
  • coilyco-gaming/sirens-echo#265 - role/ai, which becomes role/eval.
  • coilyco-gaming/sirens-echo#179 - role/exec, which becomes role/tpm.
  • coilyco-flight-deck/agentic-os#781 - role/ops, which becomes role/sysadmin.

A consequence of the rename worth a separate look

role/engineer becomes role/platform mechanically, and that is correct as a rename. But it will route every Eco mod issue to role/platform when role/gamedev exists and starts empty. eco-mods#19 is tailoring and husbandry perks not applying at mod benches, which is gamedev work wearing an engineer label because gamedev was not a seat when it was filed.

The rename cannot fix this, because it cannot know which of role/engineer's 414 issues belong to the new seat. A sweep of the coilyco-gaming repositories after step 2 would, and it is cheap because it is additive rather than destructive. Not filed yet.

Blocked until step 2

role/eval and role/platform do not exist until the rename lands, so none of the 8 adds can be applied yet. This is a prepared plan rather than pending work.

## Step 4 prepared: where `role/qa`'s 16 issues go Rule approved by Kai: agent-behavior measurement to `role/eval`, everything else defaulting to `role/platform`, confirmed per issue before the delete. All 16 read. ### Refinement that halves the work Eight of the sixteen already carry a second `role/*` label. `role/*` is deliberately non-exclusive, so those are already routed. **Deleting `role/qa` strips it from every issue holding it, which is exactly the desired outcome for these eight** and needs no per-issue action at all. Applying the default to them would be wrong rather than merely redundant. `sirens-echo#265` carries `role/ai`, which becomes `role/eval`, so adding `role/platform` would misroute it. So the work is **8 label adds**, then the delete. ### Needs a label before the delete To `role/eval`, because each measures how an agent or the inference path actually behaves: * `coilyco-gaming/sirens-echo#1134` - watch the coalescing lane answer a real member, six observations no test reaches. Observing live agent behavior. * `coilyco-gaming/sirens-echo#1082` - measure the coalescing lane once #1080 rolls, and check how a merged reply reads. * `coilyco-flight-deck/agent-proxy#107` - concurrency burst test. Body is a measurement design: Little's law arrival-rate arithmetic, three competing explanations span data cannot separate, and one burst to decide between them. Textbook eval. To `role/platform`, because each is a defect or gap in software rather than a measurement: * `coilyco-flight-deck/agentic-os#1117` - `docs/test-harness.md` documents a goose harness deleted in June 2026. * `coilyco-flight-deck/lunch-money-k8s#42`, `coilyco-flight-deck/bluesky-mcp#12`, `coilyco-flight-deck/node-stats-mcp#22` - the caveat-last ordering audit. The finding surfaced from an agent's wrong answer, but the fix is response construction in each MCP server, so the work is platform's. * `coilyco-gaming/eco-app#270` - QA sweep collector across the 25-tool Eco MCP surface. A defect collector on a service. ### Needs nothing, the delete handles them * `coilyco-gaming/eco-mods#19`, `coilyco-gaming/eco-app#269`, `coilyco-gaming/eco-app#184`, `coilyco-gaming/galaxy-gen#78`, `coilyco-gaming/sirens-echo#577` (closed) - all carry `role/engineer`, which becomes `role/platform`. * `coilyco-gaming/sirens-echo#265` - `role/ai`, which becomes `role/eval`. * `coilyco-gaming/sirens-echo#179` - `role/exec`, which becomes `role/tpm`. * `coilyco-flight-deck/agentic-os#781` - `role/ops`, which becomes `role/sysadmin`. ### A consequence of the rename worth a separate look `role/engineer` becomes `role/platform` mechanically, and that is correct as a rename. But it will route every Eco mod issue to `role/platform` when `role/gamedev` exists and starts empty. `eco-mods#19` is tailoring and husbandry perks not applying at mod benches, which is gamedev work wearing an engineer label because gamedev was not a seat when it was filed. The rename cannot fix this, because it cannot know which of `role/engineer`'s 414 issues belong to the new seat. A sweep of the `coilyco-gaming` repositories after step 2 would, and it is cheap because it is additive rather than destructive. Not filed yet. ### Blocked until step 2 `role/eval` and `role/platform` do not exist until the rename lands, so none of the 8 adds can be applied yet. This is a prepared plan rather than pending work.
coilyco-ops commented 2026-08-25 18:45:09 +00:00
Author
Member
Copy link

Status: steps 1, 2, and 5 authored

  • Step 1 - infrastructure#932. Merged as a0caf7e. The taxonomy is declarative and the check reports all three orgs converged.
  • Step 2 - infrastructure#933. Open, CI green, mergeable. The role rename as a one-file diff.
  • Step 5 - agentic-os#1237. Open, CI green, mergeable. The docs third of the batch.

Ordering, and why step 5 is being held

agentic-os runs a merge-your-own-PR lane, and #1237 is being held against it deliberately.

label-taxonomy.md carries the rule that labels, matchers, and docs change in one batch. There are no matchers for role/*, so the batch is two parts. If the doc merges before the apply runs, it names role/platform while the orgs still carry role/engineer, and an agent following it would apply a label that does not exist. A wrong label name silently applies nothing rather than erroring, so the failure would be invisible.

The window hurts equally in the other direction, which is the point of the batch rule. Order:

  1. Merge #933.
  2. Run just forgejo-label-taxonomy with an org owner token.
  3. Merge #1237.

Expected intermediate state

Between the apply and the two deletes, just forgejo-label-taxonomy-check exits 1 and reports role/exec and role/qa as undeclared. That is the design working, not a regression. The check goes green once steps 3 and 4 finish.

What unblocks after the apply

  • Step 3 - move role/exec's 4 issues onto role/tpm, then delete role/exec.
  • Step 4 - the 8 label adds settled above, then delete role/qa. The other 8 need nothing, because the delete strips the label and each already carries a second role.
  • Step 6 - apply role labels to #329 through #345.
  • #345 - the post-rename role/gamedev sweep of the gaming repositories. Additive and repo-scoped, so it needs no owner token.

Steps 3 and 4 both end in a delete, which is the only irreversible move in this operation, so both need Kai.

## Status: steps 1, 2, and 5 authored * **Step 1** - [infrastructure#932](https://forgejo.coilysiren.me/coilyco-flight-deck/infrastructure/pulls/932). **Merged** as `a0caf7e`. The taxonomy is declarative and the check reports all three orgs converged. * **Step 2** - [infrastructure#933](https://forgejo.coilysiren.me/coilyco-flight-deck/infrastructure/pulls/933). Open, CI green, mergeable. The role rename as a one-file diff. * **Step 5** - [agentic-os#1237](https://forgejo.coilysiren.me/coilyco-flight-deck/agentic-os/pulls/1237). Open, CI green, mergeable. The docs third of the batch. ### Ordering, and why step 5 is being held agentic-os runs a merge-your-own-PR lane, and #1237 is being held against it deliberately. `label-taxonomy.md` carries the rule that labels, matchers, and docs change in one batch. There are no matchers for `role/*`, so the batch is two parts. If the doc merges before the apply runs, it names `role/platform` while the orgs still carry `role/engineer`, and an agent following it would apply a label that does not exist. A wrong label name **silently applies nothing** rather than erroring, so the failure would be invisible. The window hurts equally in the other direction, which is the point of the batch rule. Order: 1. Merge #933. 2. Run `just forgejo-label-taxonomy` with an org owner token. 3. Merge #1237. ### Expected intermediate state Between the apply and the two deletes, `just forgejo-label-taxonomy-check` exits 1 and reports `role/exec` and `role/qa` as undeclared. That is the design working, not a regression. The check goes green once steps 3 and 4 finish. ### What unblocks after the apply * **Step 3** - move `role/exec`'s 4 issues onto `role/tpm`, then delete `role/exec`. * **Step 4** - the 8 label adds settled above, then delete `role/qa`. The other 8 need nothing, because the delete strips the label and each already carries a second role. * **Step 6** - apply role labels to #329 through #345. * **#345** - the post-rename `role/gamedev` sweep of the gaming repositories. Additive and repo-scoped, so it needs no owner token. Steps 3 and 4 both end in a delete, which is the only irreversible move in this operation, so both need Kai.
coilyco-ops commented 2026-08-25 20:38:12 +00:00
Author
Member
Copy link

Step 2 applied. The role labels now name the Core Roster v2 seats.

Ran clean against all three orgs. Six renames and one create each, with role/exec and role/qa reported and left alone.

=== coilyco-gaming
  rename role/ai -> role/eval
  rename role/creator -> role/devrel
  rename role/design -> role/frontend
  rename role/director -> role/tpm
  rename role/engineer -> role/platform
  rename role/ops -> role/sysadmin
  create role/gamedev
  undeclared, left alone: role/exec, role/qa

just forgejo-label-taxonomy-check from merged main now reports all three converged, and exits 1 solely because of the two pending retirements. That is the designed intermediate state.

It took two more fixes to get there

Both were mine, and both are the same shape.

  • infrastructure#934 - writes went to aosguard ops forgejo org-label, where create and edit are flagless stubs that only redirect. The real surface is forgejo-admin. The original script had this defect too, which with the json.loads bug from #932 means it carried two independent failures and had never run.
  • infrastructure#935 - #934's patch half-applied. guard() kept hardcoding forgejo while its caller passed a surface in, so the surface landed as an argument to the wrong verb group.

The lesson is about test shape, twice over. #932 covered plan() and not the argv. #934 covered the argv builder and the constants but not the command line they combine into. Each time, the only piece that was wrong was the only piece nothing asserted. #935 now asserts the full argv end to end and was checked with a negative control: reintroducing the bug fails two tests, removing it turns all 30 green.

No issue lost its label

Verified structurally rather than by counting. Every renamed label kept its id: role/engineer 360 to role/platform 360 in gaming, 382 to 382 in flight-deck, and so on for all six across both orgs sampled. Issue-label association is by id, so a rename cannot drop one.

The apparent shortfall against my pre-rename baseline reconciles exactly against coilysiren user-owned repositories, which carry their own repo-level labels, were out of scope, and still hold the retired names. Per-label: role/design 4, role/creator 4, role/engineer 8, role/ops 1, role/ai 1. That is #343, now with a number.

Where this leaves the sequence

  • Steps 1, 2, and 5 are done. The docs in agentic-os#1237 now match live state, so the window that PR opened is closed.
  • Step 3 - move role/exec's 4 issues onto role/tpm, then delete role/exec.
  • Step 4 - the 8 role/qa adds settled earlier, then delete role/qa. The other 8 need nothing.
  • Step 6 - apply role labels to #329 through #345.
  • #345 - the role/gamedev sweep. It is now unblocked, and role/gamedev currently holds 0 issues.

Steps 3 and 4 end in deletes, the only irreversible move here.

## Step 2 applied. The role labels now name the Core Roster v2 seats. Ran clean against all three orgs. Six renames and one create each, with `role/exec` and `role/qa` reported and left alone. ``` === coilyco-gaming rename role/ai -> role/eval rename role/creator -> role/devrel rename role/design -> role/frontend rename role/director -> role/tpm rename role/engineer -> role/platform rename role/ops -> role/sysadmin create role/gamedev undeclared, left alone: role/exec, role/qa ``` `just forgejo-label-taxonomy-check` from merged main now reports all three converged, and exits 1 solely because of the two pending retirements. That is the designed intermediate state. ### It took two more fixes to get there Both were mine, and both are the same shape. * [infrastructure#934](https://forgejo.coilysiren.me/coilyco-flight-deck/infrastructure/pulls/934) - writes went to `aosguard ops forgejo org-label`, where create and edit are flagless stubs that only redirect. The real surface is `forgejo-admin`. The original script had this defect too, which with the `json.loads` bug from #932 means it carried two independent failures and had never run. * [infrastructure#935](https://forgejo.coilysiren.me/coilyco-flight-deck/infrastructure/pulls/935) - #934's patch half-applied. `guard()` kept hardcoding `forgejo` while its caller passed a surface in, so the surface landed as an argument to the wrong verb group. **The lesson is about test shape, twice over.** #932 covered `plan()` and not the argv. #934 covered the argv builder and the constants but not the command line they combine into. Each time, the only piece that was wrong was the only piece nothing asserted. #935 now asserts the full argv end to end and was checked with a negative control: reintroducing the bug fails two tests, removing it turns all 30 green. ### No issue lost its label Verified structurally rather than by counting. Every renamed label **kept its id**: `role/engineer` 360 to `role/platform` 360 in gaming, 382 to 382 in flight-deck, and so on for all six across both orgs sampled. Issue-label association is by id, so a rename cannot drop one. The apparent shortfall against my pre-rename baseline reconciles exactly against `coilysiren` user-owned repositories, which carry their own repo-level labels, were out of scope, and still hold the retired names. Per-label: `role/design` 4, `role/creator` 4, `role/engineer` 8, `role/ops` 1, `role/ai` 1. That is #343, now with a number. ### Where this leaves the sequence * Steps 1, 2, and 5 are done. The docs in agentic-os#1237 now match live state, so the window that PR opened is closed. * **Step 3** - move `role/exec`'s 4 issues onto `role/tpm`, then delete `role/exec`. * **Step 4** - the 8 `role/qa` adds settled earlier, then delete `role/qa`. The other 8 need nothing. * **Step 6** - apply role labels to #329 through #345. * **#345** - the `role/gamedev` sweep. It is now unblocked, and `role/gamedev` currently holds 0 issues. Steps 3 and 4 end in deletes, the only irreversible move here.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
aos/claude/sb46-tpm-execution-handoff
aos/claude/sb46-tpm-gate-exits
feat/gamedev-role
feat/boundary-omit
aos/claude/eval-context
aos/claude/eval-current-state
aos/claude/eval-refs-restore
aos/claude/eval-docs-one-page
aos/claude/personality-anchors
aos/claude/favorite-color-spread
aos/claude/personality-catalog-gaps
aos/claude/gh297-binding-skill-selector
aos/claude/personality-prose-distinctiveness
aos/claude/gh56-adopt-aos-eval
aos/claude/aw85-bands
aos/claude/xu59-just
aos/claude/xu59-eval-export
aos/claude/xu59-comment-caps
aos/claude/xu59-pr-ci
aos/claude/xu59-role-attribution
aos/claude/ck78-banner
aos/claude/mg96-fm
rescue/precommit-v0.18-uncommitted
evals/262-board-run
claude/agents-temp-clone-note
assets/compose-mark
adjacency/262-role-adjacents
chore/precommit-bump
prose/257-258-233-second-person
boundary/254-primitive-rename
fix/acompose-undefined-role-bindings
comms/rescope-counterpart
native-home/968-user-scope-projection
meld/248-evidence-acquisition
meld/231-shared-role-melds
evals/240-baseline
evals/240-model-arms
spike/claude-native-ui-surfaces
issue-225-compact-director-eval
issue-210
issue-218
issue-215-remove-context-levels
codex/luna-medium-ai-evaluation
issue-206-align-role-tiers
codex/luna-medium-roster-prose
issue-196-remove-legacy-role-providers
issue-197-role-provider-graph
feat/model-tiers
feat/remove-context-levels
issue-187
issue-178-content-communication-ownership
issue-163-designer-evals
codex/issue-794-preserve-canonical-projections
issue-163-ornith-direct-eval
issue-163-design-current-eval
issue-150-v2-baseline
issue-156-content-code
issue-150-v2-evidence
issue-150-v2-evaluation
issue-154-v2-main-integration
issue-148-remove-v1-integrations
issue-146-core-roster
issue-144-aos-catalogue-manifest
issue-152-release-classifier
issue-139-role-metadata-last
issue-138-designer-visual-web
issue-785-first-person
ward-salvage/agent-compose-078db83c
ward-salvage/agent-compose-74e37165
issue-130
recovery/2026-07-27-local-work
v2.66.0
v2.65.0
v2.64.0
v2.63.0
v2.62.0
v2.61.0
v2.60.0
v2.59.0
v2.58.0
v2.57.0
v2.56.0
v2.55.0
v2.54.0
v2.53.0
v2.52.0
v2.51.0
v2.50.0
v2.49.0
v2.48.0
v2.47.0
v2.46.0
v2.45.0
v2.44.0
v2.43.0
v2.42.0
v2.41.0
v2.40.0
v2.39.0
v2.38.0
v2.37.0
v2.36.0
v2.35.0
v2.34.0
v2.33.0
v2.32.0
v2.31.0
v2.30.0
v2.29.0
v2.28.0
v2.27.0
v2.26.0
v2.25.0
v2.24.0
v2.23.0
v2.22.0
v2.21.0
v2.20.0
v2.19.0
v2.18.0
v2.17.0
v2.16.0
v2.15.0
v2.14.0
v2.13.0
v2.12.0
v2.11.0
v2.10.0
v2.9.0
v2.8.0
v2.7.0
v2.6.0
v2.5.0
v2.4.0
v2.3.0
v2.2.0
v2.1.0
v2.0.0
v1.49.0
v1.48.0
v1.47.0
v1.46.0
v1.45.0
v1.44.0
v1.43.0
v1.42.0
v1.41.0
v1.40.0
v1.39.0
v1.38.0
v1.37.0
v1.36.0
v1.35.0
v1.34.0
v1.33.0
v1.32.0
v1.31.0
v1.30.0
v1.29.0
v1.28.0
v1.27.0
v1.26.0
v1.25.0
v1.24.0
v1.23.0
v1.22.0
v1.21.0
v1.20.0
v1.19.0
v1.18.0
v1.17.0
v1.16.0
v1.15.0
v1.14.0
v1.13.0
v1.12.0
v1.11.0
v1.10.0
v1.9.0
v1.8.0
v1.7.0
v1.6.0
v1.5.0
v1.4.0
v1.3.0
v1.2.0
v1.1.0
v1.0.0
v0.70.0
v0.69.0
v0.68.0
v0.67.0
v0.66.0
v0.65.0
v0.64.0
v0.63.0
v0.62.0
v0.61.0
v0.60.0
v0.59.0
v0.58.0
v0.57.0
v0.56.0
v0.55.0
v0.54.0
v0.53.0
v0.52.0
v0.51.0
v0.50.0
v0.49.0
v0.48.0
v0.47.0
v0.46.0
v0.45.0
v0.44.0
v0.43.0
v0.42.0
v0.41.0
v0.40.0
v0.39.0
v0.38.0
v0.37.0
v0.36.0
v0.35.0
v0.34.0
v0.33.0
v0.32.0
v0.31.0
v0.30.0
v0.29.0
v0.28.0
v0.27.0
v0.26.0
v0.25.0
v0.24.0
v0.23.0
v0.22.0
v0.21.0
v0.20.0
v0.19.0
v0.18.0
v0.17.0
v0.16.0
v0.15.0
v0.14.0
v0.13.0
v0.12.0
v0.11.0
v0.10.0
v0.9.0
v0.8.0
v0.7.0
v0.6.0
v0.5.0
v0.4.1
v0.4.0
v0.3.0
v0.2.1
v0.2.0
v0.1.2
v0.1.1
v0.1.0
Labels
Clear labels   
burndown-2026-08
Closed in the 2026-08-26 backlog burn-down. Reopen freely: state:closed label:burndown-2026-08 recovers the whole set.

  
autonomy
async-consult
 A human needs to consult on the issue to upgrade it to headless

  
autonomy
epic
 This issue has many units of sub work - its size makes it meaningfully exclusive with other autonomy types

  
autonomy
headless
 The agent can perform the work on its own

  
autonomy
live-collab
 The agent and the human need to work together in realtime

  
coherence-core
Core review set for the warded control plane coherence milestone. These issues form the release spine; adjacent milestone issues are stretch or supporting work.

  
priority
P0
 priority tier

  
priority
P1
 priority tier

  
priority
P2
 priority tier

  
priority
P3
 priority tier

  
priority
P4
 priority tier

  
qa-fixture
Disposable issue admitted to the bounded Ward QA verification lane.

  
role/devrel
requires work from the Developer Advocate seat

  
role/eval
requires work from the Agent Evaluation Engineer seat

  
role/exec
requires work from the exec role

  
role/frontend
requires work from the Frontend Design Engineer seat

  
role/gamedev
requires work from the Game Developer seat

  
role/human
requires a person, and specifically not an agent seat

  
role/platform
requires work from the Developer Platform Engineer seat

  
role/qa
requires work from the QA role

  
role/sysadmin
requires work from the Systems Administrator seat

  
role/tpm
requires work from the Technical Program Manager seat

No labels
burndown-2026-08
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
coherence-core
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
qa-fixture
role/devrel
role/eval
role/exec
role/frontend
role/gamedev
role/human
role/platform
role/qa
role/sysadmin
role/tpm
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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/agent-compose#342
No description provided.