label-taxonomy

# Label Taxonomy

Reference for Giant Swarm's 200+ GitHub labels and labeling conventions.

## Label Categories

1. **Teams** - Required, exactly ONE per issue
2. **Kinds** - Issue types, recommended
3. **Functions** - Cross-functional domains
4. **Areas** - Product areas (kaas, platform)
5. **Providers** - Cloud providers
6. **Impact** - Severity levels
7. **Workstreams** - Long-running initiatives

## Teams (Required - Exactly ONE)

| Label | Focus Area |
|-------|------------|
| `team/atlas` | Observability, monitoring, logging |
| `team/cabbage` | Networking, service mesh, ingress |
| `team/honey-badger` | App platform, GitOps |
| `team/phoenix` | Cloud providers (AWS, Azure) |
| `team/planeteers` | Product, cross-team coordination |
| `team/rocket` | On-prem, edge (vSphere, Cloud Director) |
| `team/shield` | Security, auth, RBAC |
| `team/tenet` | Releases, testing, CAPI core |
| `team/up` | Marketing, growth, people ops |
| `team/turtles` | Platform foundations |
| `team/nifflers` | (Newer team) |

## Kinds (Recommended)

| Label | Use For |
|-------|---------|
| `kind/epic` | Strategic initiatives |
| `kind/story` | User-facing value |
| `kind/task` | Specific actions |
| `kind/bug` | Defects |
| `kind/postmortem` | Incident docs |
| `kind/discovery` | Research/spikes |
| `kind/request` | Customer asks |
| `kind/feature` | New capabilities |
| `kind/rock` | Quarterly bets |
| `kind/recurring` | Scheduled tasks |
| `kind/operational` | Platform health |
| `kind/note` | Reference docs |
| `kind/experiment` | POCs, validation |

## Providers (Optional)

- `provider/aws` or `provider/capa` - AWS/CAPA
- `provider/azure` or `provider/capz` - Azure/CAPZ
- `provider/vsphere` or `provider/capv` - vSphere/CAPV
- `provider/cloud-director` or `provider/capvcd` - Cloud Director/CAPVCD

## Impact (Optional - For Bugs)

- `impact/high` - Critical, customer-facing, outage
- `impact/medium` - Degraded, workaround exists
- `impact/low` - Minor, cosmetic, nice-to-have

## Area