# Bound a deployment freeze exception

Illustrative planning brief; no automatic product import.

Illustrative planning case: A planned stability freeze overlaps a fix for one confirmed severe calculation error.

## Decision

Review the evidenced fix as a bounded freeze exception.

## Owned work

- Document affected behavior
  - Owner role: Release investigator
  - Acceptance evidence: One reproducible calculation defect defines the exception scope.
- Separate incidental changes
  - Owner role: Migration engineer
  - Acceptance evidence: Refactoring and unrelated fixes stay outside the package.
- Review emergency evidence
  - Owner role: Release reviewer
  - Acceptance evidence: The calculation and adjacent invariants pass focused checks.

## Workflow

1. Preserve the reproducible calculation defect and identify affected outputs.
2. Prepare only the correction and necessary adjacent changes, listing unrelated work excluded from the exception.
3. Review the calculation and adjacent invariants, then record the authorized exception or unresolved evidence.

## Judgment

Do not treat urgency as blanket permission to deploy.


## Filled illustrative release coordination record

The illustrative exception includes a one-line rounding correction plus its focused regression fixture. A nearby query cleanup is removed from the package. The release reviewer accepts the calculation risk against the freeze purpose and records an observation window. The exception does not convert the freeze into permission for ordinary backlog work.
Decision: Review the evidenced fix as a bounded freeze exception.
Review boundary: Do not treat urgency as blanket permission to deploy.
This example uses synthetic conditions. Replace its observations with project evidence and record any changed assumptions before adopting the plan.


## Workflow questions

### Can unrelated low-risk cleanup join the exception?

Keep the reviewed emergency scope narrow unless the extra change is necessary to make the fix correct.

### What should the exception record retain?

The specific freeze rule, defect evidence, permitted change and release decision owner.

## 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.