role/exec and role/qa are declared in no org taxonomy but live in all three #1415

Open
opened 2026-08-29 13:11:42 +00:00 by coilyco-ops · 0 comments
Owner

Split out of agentic-os#1380, whose two halves are both complete: the state/ambient drift it cites is declared now, and the infra sync script already routes every call through aosguard (infrastructure#935).

What is left is a taxonomy question rather than a second-writer problem.

Measured 2026-08-29, declared taxonomy against all three live orgs:

coilyco-flight-deck   declared 18, live 22
  undeclared: coherence-core, qa-fixture, role/exec, role/qa
coilyco-bridge        declared 18, live 20
  undeclared: role/exec, role/qa
coilyco-gaming        declared 18, live 21
  undeclared: c#, role/exec, role/qa

Nothing declared is missing, so the sync applies everything it owns. These five sit as "undeclared, left alone", which is the sync's designed behaviour rather than a failure.

The interesting pair

role/exec and role/qa are in all three orgs and neither names a seat on the current roster: platform, sysadmin, science, frontend, gamedev, director, advocate. The declared taxonomy carries role/platform, role/sysadmin, role/director, role/human and role/gamedev, so the two vocabularies have diverged.

agentic-os#1377 recorded the same divergence from the coilysiren/inbox side, where the role list is role/ai, role/creator, role/design, role/director, role/engineer, role/exec, role/human, role/ops, role/qa.

tooling-issue-prioritization treats the role axis as one vocabulary and it is at least two.

The question

For each of the five: declare it in config/forgejo-label-taxonomy.yaml, or delete it from the orgs. Deleting strips the label from every issue carrying it, so edit org-label is the rename path if any of them is a mis-named survivor rather than a stray.

That is a call about which seats exist, which is why it is not bundled into a platform change.

Split out of agentic-os#1380, whose two halves are both complete: the `state/ambient` drift it cites is declared now, and the infra sync script already routes every call through aosguard (infrastructure#935). What is left is a taxonomy question rather than a second-writer problem. Measured 2026-08-29, declared taxonomy against all three live orgs: ``` coilyco-flight-deck declared 18, live 22 undeclared: coherence-core, qa-fixture, role/exec, role/qa coilyco-bridge declared 18, live 20 undeclared: role/exec, role/qa coilyco-gaming declared 18, live 21 undeclared: c#, role/exec, role/qa ``` Nothing declared is missing, so the sync applies everything it owns. These five sit as "undeclared, left alone", which is the sync's designed behaviour rather than a failure. ## The interesting pair `role/exec` and `role/qa` are in all three orgs and neither names a seat on the current roster: platform, sysadmin, science, frontend, gamedev, director, advocate. The declared taxonomy carries `role/platform`, `role/sysadmin`, `role/director`, `role/human` and `role/gamedev`, so the two vocabularies have diverged. agentic-os#1377 recorded the same divergence from the `coilysiren/inbox` side, where the role list is `role/ai`, `role/creator`, `role/design`, `role/director`, `role/engineer`, `role/exec`, `role/human`, `role/ops`, `role/qa`. `tooling-issue-prioritization` treats the role axis as one vocabulary and it is at least two. ## The question For each of the five: declare it in `config/forgejo-label-taxonomy.yaml`, or delete it from the orgs. Deleting strips the label from every issue carrying it, so `edit org-label` is the rename path if any of them is a mis-named survivor rather than a stray. That is a call about which seats exist, which is why it is not bundled into a platform change.
Sign in to join this conversation.
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#1415
No description provided.