coilysiren/* repos cannot carry the scoped label taxonomy #1106

New issue

Open

opened 2026-08-16 07:02:44 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-08-16 07:02:44 +00:00

Member

The scoped taxonomy (priority/*, autonomy/*, role/*) is defined at org
scope, and coilysiren is a user account rather than an organization. The API
404s on /orgs/coilysiren/repos, and there is no user-level label surface, so
its four repos - coilysiren, lore, voice-corpus, website - cannot carry
any of it.

Repo-level label create is policy-denied (ward#107) because repo labels
duplicate and shadow the org taxonomy. That denial is correct: shadowed
repo-scoped headless and interactive labels in eco-app and deploy were
a real bug earlier this month (eco-app#305). So the workaround the gap invites
is the thing the guard exists to stop, and I did not take it.

Concretely, four issues filed for the docs band migration carry no labels at
all and are invisible to every triage query that filters on them:

coilysiren/coilysiren#31
coilysiren/lore#18
coilysiren/voice-corpus#16
coilysiren/website#117
also coilysiren/website#116, filed the same day

Options:

Move the four repos into an org. They get the taxonomy for free and the
guard keeps working as designed. Costs a redirect on every clone URL.
Carve a policy exception for namespaces with no org above them, letting
repo labels exist exactly where there is nothing to shadow. Narrow, and the
guard's own reasoning supports it.
Accept it. Those four repos are triaged by hand, and queries skip them.

I would take 1. The shadowing risk in 2 returns the moment a repo moves under
an org, and 3 quietly drops four repos out of every queue.

The scoped taxonomy (`priority/*`, `autonomy/*`, `role/*`) is defined at org scope, and `coilysiren` is a user account rather than an organization. The API 404s on `/orgs/coilysiren/repos`, and there is no user-level label surface, so its four repos - `coilysiren`, `lore`, `voice-corpus`, `website` - cannot carry any of it. Repo-level `label create` is policy-denied (ward#107) because repo labels duplicate and shadow the org taxonomy. That denial is correct: shadowed repo-scoped `headless` and `interactive` labels in `eco-app` and `deploy` were a real bug earlier this month (eco-app#305). So the workaround the gap invites is the thing the guard exists to stop, and I did not take it. Concretely, four issues filed for the docs band migration carry no labels at all and are invisible to every triage query that filters on them: * coilysiren/coilysiren#31 * coilysiren/lore#18 * coilysiren/voice-corpus#16 * coilysiren/website#117 * also coilysiren/website#116, filed the same day Options: 1. **Move the four repos into an org.** They get the taxonomy for free and the guard keeps working as designed. Costs a redirect on every clone URL. 2. **Carve a policy exception** for namespaces with no org above them, letting repo labels exist exactly where there is nothing to shadow. Narrow, and the guard's own reasoning supports it. 3. **Accept it.** Those four repos are triaged by hand, and queries skip them. I would take 1. The shadowing risk in 2 returns the moment a repo moves under an org, and 3 quietly drops four repos out of every queue.

coilyco-ops added the

labels

2026-08-16 07:02:46 +00:00

coilyco-ops referenced this issue from coilysiren/coilysiren

2026-08-16 07:02:59 +00:00

docs band migration: trim 2 files #31

coilyco-ops referenced this issue from coilysiren/website

2026-08-16 07:03:06 +00:00