Labels

• phase:architecture

  phase:architecture

  Structural system changes and boundary clarification.

• phase:governance

  phase:governance

  Governance rollouts, standards enforcement, process updates.

• phase:hardening

  phase:hardening

  Security/safety/robustness improvements and guardrails.

• phase:mvp

  phase:mvp

  Minimum viable functionality to establish baseline.

• phase:observability

  phase:observability

  Metrics/logging/tracing improvements.

• phase:operations

  phase:operations

  Runtime, deployment, healthchecks, and operability.

• phase:optimization

  phase:optimization

  Performance/cost improvements after correctness is stable.

• phase:release

  phase:release

  Release preparation, packaging, and deploy readiness.

• phase:research

  phase:research

  Feasibility exploration and unknown reduction.

• phase:stabilization

  phase:stabilization

  Correctness, CI confidence, and reliability improvements.

• priority:critical

  priority:critical

  Must be addressed immediately.

• priority:high

  priority:high

  High priority; should be scheduled soon.

• priority:low

  priority:low

  Low priority; do last.

• priority:medium

  priority:medium

  Normal priority.

• risk:critical

  risk:critical

  High risk to security, correctness, or stability.

• risk:high

  risk:high

  Significant technical or operational risk.

• risk:low

  risk:low

  Low risk.

• risk:medium

  risk:medium

  Moderate risk.

• status:blocked

  status:blocked

  Blocked by unresolved issues listed under `blocked-by` in the issue body.

• status:needs-adr

  status:needs-adr

  Requires an ADR before implementation.

• status:needs-clarification

  status:needs-clarification

  Cannot proceed until missing info is provided.

• status:needs-tests

  status:needs-tests

  Requires test coverage (TDD enforcement).

• status:ready

  status:ready

  No unresolved `blocked-by` dependencies; eligible to start.

• type:architecture

  type:architecture

  Structural design or boundary change affecting system architecture.

• type:bug

  type:bug

  A defect: something is not working as intended.

• type:documentation

  type:documentation

  Documentation improvements or additions.

• type:feature

  type:feature

  New capability or user-facing functionality.

• type:governance

  type:governance

  Process, standards, templates, or engineering governance changes.

• type:infra

  type:infra

  Infrastructure, CI/CD, build, or environment-related work.

• type:performance

  type:performance

  Performance/cost/latency optimization work.