docs(triage): rename the label taxonomy to scoped priority/autonomy/role #1067

Merged

coilysiren merged 1 commit from aos/claude/ym96-label-taxonomy into main

2026-08-15 20:56:40 +00:00

coilyco-ops commented

2026-08-15 20:26:19 +00:00

Member

Updates the tooling-issue-prioritization skill for the label taxonomy Kai moved to scoped, exclusive labels on 2026-08-15.

The rename

P0..P4       ->  priority/P0..priority/P4
consult      ->  autonomy/async-consult
headless     ->  autonomy/headless
interactive  ->  autonomy/live-collab
IRL          ->  role/human
                 autonomy/epic                          new
                 role/{ai,creator,design,engineer,qa}   new

Two entries are semantic rather than spelling. live-collab means a human has to be present, where interactive described a mid-flight checkpoint - the pair now splits on scheduled time versus queue latency. And autonomy/epic is not a ceiling at all: it earns its place in the autonomy group precisely because the group is exclusive, which is what stops an epic being dispatched as a single task.

The new role/* axis answers the question async-consult kept swallowing. It said a human was needed but never which one, so a director's decision queue and an operator's action queue arrived as one undifferentiated pile.

Recorded as a breaking change, because it is one

umbra's resolveDispatchIssue matches these label strings and is not updated here. I have no umbra checkout and could not verify it, so the docs name the failure mode rather than assert a fix: nothing errors, every issue stops matching, everything falls to the fail-closed default, and the burndown queue silently empties while looking healthy. Tracked separately.

Also recorded: the surface names and the label names were deliberately one vocabulary and are not any more. A matcher can no longer treat them as interchangeable.

Structure

The 4000-char documentation cap rejected the first pass, so four references were split out rather than the content cut:

label-taxonomy.md - the three axes, the rename table, why role and epic exist
target-shape.md - the P0 net-then-confirm rules and the percentile bands
dispatch-gate.md - the enforcing half and the rename hazard
the thread-reading lesson moved into assignment-method.md, where it belongs

One test asserted on the old spelling in doc content and is updated in the same commit. pre-commit run and the contract tests pass.

Not in this PR

The org-label sync to coilyco-bridge and coilyco-flight-deck. The coilyco-ops token is an org member rather than an owner, so every org-label write returns 403 on all three orgs. That needs Kai's own credentials or an admin token.

🤖 Generated with Claude Code

Updates the `tooling-issue-prioritization` skill for the label taxonomy Kai moved to scoped, exclusive labels on 2026-08-15. ## The rename ``` P0..P4 -> priority/P0..priority/P4 consult -> autonomy/async-consult headless -> autonomy/headless interactive -> autonomy/live-collab IRL -> role/human autonomy/epic new role/{ai,creator,design,engineer,qa} new ``` Two entries are semantic rather than spelling. `live-collab` means a human has to be **present**, where `interactive` described a mid-flight checkpoint - the pair now splits on scheduled time versus queue latency. And `autonomy/epic` is not a ceiling at all: it earns its place in the autonomy group precisely because the group is exclusive, which is what stops an epic being dispatched as a single task. The new `role/*` axis answers the question `async-consult` kept swallowing. It said a human was needed but never which one, so a director's decision queue and an operator's action queue arrived as one undifferentiated pile. ## Recorded as a breaking change, because it is one `umbra`'s `resolveDispatchIssue` matches these label strings and is **not** updated here. I have no umbra checkout and could not verify it, so the docs name the failure mode rather than assert a fix: nothing errors, every issue stops matching, everything falls to the fail-closed default, and the burndown queue silently empties while looking healthy. Tracked separately. Also recorded: the **surface** names and the **label** names were deliberately one vocabulary and are not any more. A matcher can no longer treat them as interchangeable. ## Structure The 4000-char documentation cap rejected the first pass, so four references were split out rather than the content cut: - `label-taxonomy.md` - the three axes, the rename table, why role and epic exist - `target-shape.md` - the P0 net-then-confirm rules and the percentile bands - `dispatch-gate.md` - the enforcing half and the rename hazard - the thread-reading lesson moved into `assignment-method.md`, where it belongs One test asserted on the old spelling in doc content and is updated in the same commit. `pre-commit run` and the contract tests pass. ## Not in this PR The org-label sync to `coilyco-bridge` and `coilyco-flight-deck`. The `coilyco-ops` token is an org member rather than an owner, so every `org-label` write returns 403 on all three orgs. That needs Kai's own credentials or an admin token. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

coilyco-ops added 1 commit

2026-08-15 20:26:19 +00:00

docs(triage): rename the label taxonomy to scoped priority/autonomy/role

ci / ward-doctor (pull_request) Successful in 13s

Details

ci / aos-cli-tests (pull_request) Successful in 17s

Details

ci / gate (pull_request) Successful in 50s

Details

c152d0e250

The coilyco-gaming org label set moved to scoped, exclusive labels on
2026-08-15. This updates the skill that encodes the old names and meanings.

- P0-P4 -> priority/P0-P4
- consult -> autonomy/async-consult, headless -> autonomy/headless,
  interactive -> autonomy/live-collab
- IRL -> role/human, plus a new role/{ai,creator,design,engineer,qa} axis
- new autonomy/epic

Two entries are semantic rather than spelling. live-collab means a human has
to be present, where interactive described a mid-flight checkpoint. And epic
is not a ceiling at all: it earns its place in the autonomy group because the
group is exclusive, which is what stops an epic being dispatched as one task.

The gate in umbra's resolveDispatchIssue matches these strings and is not
updated here, so the rename is recorded as a breaking change with the failure
mode named: nothing errors, every issue stops matching, everything falls to
the fail-closed default, and the burndown queue silently empties.

Split four references out to stay under the 4000-char documentation cap:
label-taxonomy, target-shape, dispatch-gate, and the thread-reading lesson
moved into assignment-method where it belongs.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-authored-by: Kai Siren <coilysiren@gmail.com>
Co-authored-by: Claude <noreply@anthropic.com>

coilyco-ops requested review from coilysiren

2026-08-15 20:26:19 +00:00

coilyco-ops referenced this pull request

2026-08-15 20:40:35 +00:00

Batch: the Forgejo operations that need an attended admin token without being unsafe, and which of them a guardfile change can actually fix #1068