Labels
Labels
29 labels
- Band D follow-up work
- Pull requests that update a dependency file
- Audit rule firing incorrectly. Fix may be rule-tightening, doc-rewording, or scope adjustment.
- Pull requests that update GitHub Actions code
- Latent violation of a governance principle, pre-existing or revealed by new rules. Tracked.
- Known risk or failure mode worth tracking even when no action is taken. Named so not forgotten.
- Project organization
- Blocks a band from closing, or represents unmitigated risk. Picked ahead unless deferred.
- Low urgency; park until higher priorities clear
- Default priority. Picked at session-start based on leverage and context, not urgency.
- Pull requests that update python code
- Roadmap item
- Cannot progress until a dependency resolves. The blocking item should be named in the body.
- Named intentionally but not being worked. Available for pick at session-start.
- Work complete; waiting on runtime observation or natural triggering to confirm. Passive.
- Authoring or revising an Architectural Decision Record. Closed when the ADR is merged.
- Structural or design decision affecting system shape
- Defect in existing behaviour
- CI/CD
- Changes to the core-admin command surface or CLI handler code.
- Changes to user-facing docs (README, docs site, guides). Not ADRs or papers; those have own types.
- Multi-issue effort too large for one task. Spawns child issues. Closes when all children close.
- New capability or user-visible functionality added to CORE. Results in code, not only documentation.
- Read-only discovery or diagnostic effort. Produces a report or a decision, not code.
- Open architectural or operational question requiring governor decision. Closed when decided.
- Single executable unit of work. One session, one outcome. The default for most issues.
- Developer tooling, scripts, or local development infrastructure. Not user-facing.
- North Star or strategic direction. Rare. Keeps or updates the project's long-term orientation.