Label vocabulary (all forges)¶
One fixed set, the same on GitLab and GitHub (DR-008 §3). The routing block in the issue body holds the details; labels hold kind, harness and state.
| Label | Meaning |
|---|---|
for:design |
Queue of the Design (+ Preflight) harness |
for:code |
Queue of the Code (+ Test) harness; must carry a routing block |
for:test |
Queue of the Test harness (phase 2) |
ready-for-test |
Code done on a branch; Test to verify |
test-pass |
Test verified; ready for a merge request to Atul |
bug |
Defect found (by Test or a person); goes back to Code |
research |
Study or comparison requested by Design |
needs-atul |
Needs Atul's decision; never routed unattended |
question-atul |
Question for Atul (collector shows it in the panel) |
decision-log |
A significant decision an agent took; shown to Atul as FYI, veto within 48 h (rules §21) |
ask-<project> |
Question for another project's agent |
run-job |
Registered job for MMDEP to run (GitHub projects) |
support-test, support-release |
Same, on GitLab projects |
lane:prod, lane:staging |
API lanes (DR-013): production (high risk) or staging (low risk) |
Routing block field risk (from sprint 2; Atul, 19 Oct)¶
Every routing block carries risk: low | medium | high, as defined in DR-012 §5. Preflight sets it; when in doubt it takes the higher class. Example: risk: low. Items without risk are treated as high from 1 Nov.