# Choose a canary observation population

Illustrative planning brief; no automatic product import.

Illustrative planning case: A canary receives only internal traffic while the changed path is mostly used by external batch clients.

## Decision

Choose a canary cohort that exercises the changed behavior.

## Owned work

- Map changed-path callers
  - Owner role: Release investigator
  - Acceptance evidence: Internal and batch request shapes are separated.
- Select bounded canary
  - Owner role: Migration engineer
  - Acceptance evidence: One reviewed batch cohort exercises the new path.
- Review expansion evidence
  - Owner role: Release reviewer
  - Acceptance evidence: Errors and output parity are checked for that cohort.

## Workflow

1. Separate internal request shapes from the external batch paths affected by the change.
2. Select one approved bounded batch cohort and record the observation interval and expected outputs.
3. Review errors and output parity for that cohort before discussing expansion; keep unobserved caller types explicit.

## Judgment

Do not expand solely because aggregate traffic looks healthy.


## Filled illustrative release coordination record

The synthetic internal canary makes 100 successful requests but never invokes batch grouping. The revised cohort includes one controlled batch client with ten known input sets. Expansion waits for those outputs and their failure paths. Passing unrelated traffic remains recorded, but cannot satisfy the changed path's release gate.
Decision: Choose a canary cohort that exercises the changed behavior.
Review boundary: Do not expand solely because aggregate traffic looks healthy.
This example uses synthetic conditions. Replace its observations with project evidence and record any changed assumptions before adopting the plan.


## Workflow questions

### Does any canary traffic count as validation?

It validates only the exercised behavior; traffic must cover the contract changed by this release.

### How small can the cohort be?

Small enough to contain impact, but capable of producing the specific correctness and recovery evidence needed.

## Product connection

Use the manual work brief to discuss task ownership, review evidence and next actions in TeamBoost. Release execution remains a separate project workflow; the download performs no deployment or import.

Confirm account availability before adopting this manual outline.