# Validation Exception Structure

A validation exception is allowed only when a planned validation command is blocked. It cannot substitute for missing runtime code changes, missing Runtime Delta targets, or documentation-only changed paths.

Each exception must record:

- Planned command: the exact validation command that was intended.
- Blocker: the concrete reason the command could not run.
- Substitute evidence: the inspection, narrower command, build step, or other evidence used instead.
- Residual risk: what remains unproven because the planned command did not run.
- Follow-up validation path: the command or environment change needed to complete validation later.

Invalid exceptions include:

- "Not run" with no blocker.
- Environment claims with no substitute evidence.
- Exceptions used to justify runtime acceptance when runtime files did not change.
- Exceptions that omit residual risk or follow-up validation.

Reconciliation may accept a validation exception only for the validation gap it describes. It must not treat the exception as proof of runtime behavior.
