Labels

Barrier affecting people with disabilities

Structure of the system

Behavior the code promises but does not deliver

Pipelines, locks, images

Results and figures must be right

Per-use spend or resource ceilings

Docs only; code unchanged

Another issue already covers this

Committed work must survive a crash or restart

Several sessions, more than one component, or a migration to watch

One session with a design decision, a deploy, or a manual step

One session, no decision; ships without a deploy or with a routine one

Several repos or a staged rollout, each stage reviewed

New behavior

Umbrella issue tracked as stories

Compose, deployment, hosting

Parked: valid, but not scheduled; never with priority/high

Logs, traces, metrics

Throughput and latency

Breaks a guarantee or blocks the core flow

Nice to have

Important, but not blocking

User data leaving the app or over-shared

Faults outside the app's control: failures, restarts, recovery

Touches auth, money or stored user data; hard to revert

Contained change, easy to revert

Touches a contract or more than one repo

Serving more people from more replicas; pairs with scaling-safety or scaling-out

Adding replicas serves more users without degrading anyone's experience

N copies of the service must behave exactly as one would