# ADR 0027. Mint aliases at link complete for listed integrations

## Status
Accepted (as listed in the decisions index).

Link exchange already returns provider aliases (spec §37.4). The remaining
choice was whether to mint every possible future integration up front, or wait
until first activity. Minting on ingest would be passive first exposure and
breaks the glossary. Minting every future integration wastes aliases and
creates consent for audiences the Player never linked.

## Decision

Mint Pairwise aliases only for audiences on the completed link intent:
operator alias when the flow is operator-led; one `pp_plr_prv_...` per
integration listed on that intent. Provider-led complete still does not mint
an operator alias.

Do not mint on Activity ingest. Do not mint for integrations that did not
exist or were not listed at link time.

When an operator enables a new provider integration later, mint through
`POST /v1/operator-players/{alias}/provider-aliases:resolve` (spec §37.5),
not as a side effect of gameplay.

## Consequences

- Normal game launch can cache aliases from the original exchange (spec §11).
- The resolve endpoint is the later-integration path; until it exists,
  operators only have aliases from the original link.
- Ingestion keeps resolving inside the authenticated integration audience
  (ADR 0014). Unknown alias stays unknown.