# Verification Plan

> Define this before implementing, so "done" is fixed in advance and cannot be
> quietly downgraded later.

## Declared verification target
<!-- The boundary the change contract cares about: unit / integration /
     end-to-end / production. -->

## Checks, layered
<!-- From focused to broad. Map each check to the boundary it actually covers. -->
| Check | Command / method | Boundary it covers |
|---|---|---|
|  |  |  |

## Non-negotiables to confirm
<!-- Trust-boundary validation, data safety, security, accessibility,
     observability, operational recovery, explicitly requested behavior. List the
     ones relevant here and how each is confirmed. -->
- 

## Rollback / recovery evidence
<!-- How the change is undone if it fails in the target environment. -->

## Gaps
<!-- Any declared-target boundary that cannot be exercised, and the weaker check
     that stands in for it (if any). -->
- 

## Verdict
<!-- pass / conditional / blocked — with the evidence. Use the
     verification-methodology skill's verdict format when available. -->