Structural/system-level shape and runtime behaviour

Bots, schedulers, dispatch, self-healing, fan-out

ABI, FFI, WASM, and cross-language interop surfaces

Something is broken or behaves incorrectly

Routine maintenance with no behaviour change

CI/CD: workflows, actions, lockfiles, pins, runners, release gates

Conformance to an external or internal specification

A ruling is required before work can proceed

Design of an interface, protocol, grammar, or type theory

Docs, prose, diagrams, READMEs, ADRs

This issue or pull request already exists

New capability or improvement to existing behaviour

Added by Gitar

Good for newcomers

Policy, rulesets, standards, compliance, and their enforcement

Extra attention is needed

This doesn't seem right

Licences, SPDX headers, REUSE compliance, attribution

Coordinated multi-repo push with a defined end state

Recurs on a schedule or by trigger; never finally closed

Forward planning; not yet actionable work

Parent issue aggregating child issues

Porting between languages or toolchains (e.g. -> AffineScript)

Guix, Nix, containers, distribution artefacts

Throughput, latency, memory, binary size

Critical - drop other work

High - schedule next

Normal - queue it

Low - nice to have

Formal verification: Agda, Coq, Idris, Lean, Z3/SMT, axiom debt