Amend the Forge Flow wiki: law 13 labels are renamed and org-owned #28

Open

opened 2026-08-05 21:13:42 +00:00 by agent.odin · 0 comments

agent.odin commented

2026-08-05 21:13:42 +00:00

Collaborator

The Forge Flow page still documents law 13's labels under their pre-ratification bare names. Two owner rulings on 2026-08-05 superseded them, and the forge has already moved — so the page and the world disagree, which the page's own preamble says must be repaired in the same breath.

Ruling 1 — the `Category/Name` convention wins

lar.ad carries Forgejo's built-in Advanced template as org labels. Label names are host-owned: the forge's template owns them until it proves insufficient. Law 13's pipeline is where it does — Advanced has no notion of a steward-driven pipeline — so the gaps adopt the template's namespaces rather than inventing bare names beside them.

Ruling 2 — `needs-decision` folds into `Status/Need More Info`

A decision is an information. The distinction did not earn a second label.

The mapping now live

law-13 concept	label	owner
`blocked` overlay	`Status/Blocked`	org
parked on an owner call	`Status/Need More Info`	org
claimed, workspace active	`Status/In Progress`	org
PR open against fastlane	`Status/In Review`	org
steward rebase failed	`Status/Conflicted`	org
merge-style verdict (PR)	`Reviewed/Curated`	org

All six now live at org level on lar.ad (22 labels total). dendrite, modron and hydramem carry zero repo-level law-13 labels; modron keeps only buzz-import and fizz-naming-go, which are lawfully its own.

Already applied

modron's six bare names deleted, after relabelling modron#18 to Status/In Review — deleting a label strips it from its issues, so replacement precedes removal
hydramem became label-conformant without being touched, purely by the org taking ownership

What the page must also say

larandar is a user account, not an org, so flaky-mesh cannot inherit org labels at all. Law 13 binds forge-wide, but its mechanism cannot be uniform: org-level where an org exists (lar.ad, swarm), repo-level replication for user-owned repos. The steward spec has to declare which applies per repo, or this repo silently sits outside a forge-wide law.

Acceptance

Law 13's tables use the namespaced names
The org-owned model is stated, with the user-account exception called out
needs-decision recorded as folded, not merely dropped
The label spec names org vs repo ownership per repo

The [Forge Flow](https://jo.et0.pw/larandar/flaky-mesh/wiki/Forge-Flow) page still documents law 13's labels under their pre-ratification bare names. Two owner rulings on 2026-08-05 superseded them, and the forge has already moved — so the page and the world disagree, which the page's own preamble says must be repaired in the same breath. ### Ruling 1 — the `Category/Name` convention wins `lar.ad` carries Forgejo's built-in **Advanced** template as *org* labels. Label names are host-owned: the forge's template owns them until it proves insufficient. Law 13's pipeline is where it does — Advanced has no notion of a steward-driven pipeline — so the gaps adopt the template's namespaces rather than inventing bare names beside them. ### Ruling 2 — `needs-decision` folds into `Status/Need More Info` A decision is an information. The distinction did not earn a second label. ### The mapping now live | law-13 concept | label | owner | |---|---|---| | `blocked` overlay | `Status/Blocked` | **org** | | parked on an owner call | `Status/Need More Info` | **org** | | claimed, workspace active | `Status/In Progress` | org | | PR open against fastlane | `Status/In Review` | org | | steward rebase failed | `Status/Conflicted` | org | | merge-style verdict (PR) | `Reviewed/Curated` | org | All six now live at **org level** on `lar.ad` (22 labels total). `dendrite`, `modron` and `hydramem` carry zero repo-level law-13 labels; `modron` keeps only `buzz-import` and `fizz-naming-go`, which are lawfully its own. ### Already applied - `modron`'s six bare names deleted, after relabelling `modron#18` to `Status/In Review` — deleting a label strips it from its issues, so replacement precedes removal - `hydramem` became label-conformant without being touched, purely by the org taking ownership ### What the page must also say **`larandar` is a user account, not an org**, so `flaky-mesh` cannot inherit org labels at all. Law 13 binds forge-wide, but its *mechanism* cannot be uniform: org-level where an org exists (`lar.ad`, `swarm`), repo-level replication for user-owned repos. The steward spec has to declare which applies per repo, or this repo silently sits outside a forge-wide law. ### Acceptance - [ ] Law 13's tables use the namespaced names - [ ] The org-owned model is stated, with the user-account exception called out - [ ] `needs-decision` recorded as folded, not merely dropped - [ ] The label spec names org vs repo ownership per repo

Commenting is not possible because the repository is archived.