Skip to main content

Verification

Verification proves that a change works in the intended environment and did not break the public surfaces users rely on.

Operator Workflow​

  • Match verification to the affected scope.
  • Check both machine-readable status and user-visible behavior.
  • Record the exact routes or pages verified.

Verification Gates​

Verification gates: define the affected scope, run the relevant build or validation checks, perform the smallest appropriate deploy or config action, and verify the live user-facing or API behavior that changed.

For high-risk work, also prepare a rollback or follow-up plan before touching production.

Evidence To Capture​

  • Target environment and affected service, docs surface, API group, workspace, artifact, or operation.
  • Validation command or manual check performed.
  • Live route, API response, screenshot, or operation timeline proving the result.
  • Follow-up needed if verification is incomplete.

Media To Add​

  • Table: change type to required checks for docs, app shell, API, database, containers, and sample content. It helps operators pick the right checks. Source: release checklist.