Gate signature

Dry-run signoff

Final record after production dry run: what passed, what failed, who saw it, who owns it, and whether live can open.

Without written signoff, launch becomes a memory that things were probably checked.

Record pass/fail

Record results for all dry-run rooms: order, email, support, refund/recreate, mobile, rollback.

  • Every room has pass/fail.
  • Every fail has owner.
  • Screenshots/log links noted privately.

Make go/no-go decision

Make an explicit decision: launch, postpone, limited beta, or test-only mode.

  • Decision written.
  • Scope written.
  • Next review date written.

Lock the launch state

After signoff, do not add new features before launch without another dry run.

  • Feature freeze set.
  • Env freeze set.
  • Rollback version noted.

checklist

What to check

  • All drills recorded.
  • Go/no-go decision written.
  • Feature freeze accepted.
  • Rollback version noted.
  • Support owner assigned.

red flags

When to stop

  • Decision is verbal only.
  • A failed payment path is accepted as minor.
  • New feature added after signoff without retest.

done when

Definition of done

  • Signoff exists and names a decision.
  • No unresolved hard blocker remains.
  • Next action is clear.

related doors