Verification & Handover
What must be proven, documented and transferred before an engagement is considered done.
Principle
Nothing ships unverified.
A change is not complete when it works on screen; it is complete when the check that proves it works is written down and repeatable by someone else.
Structure
Prove
Test runEvidence log
Document
RunbookArchitecture record
Transfer
PairingOwnership sign-off
Handover artefacts produced during delivery, not after it.
Procedure
- 01
Define the checks with the spec
Verification steps are written when the work is specified. Placeholder body copy to be completed.
- 02
Run and record
Each check is executed and the result retained. Placeholder body copy to be completed.
- 03
Write the runbook
Operational procedures are documented in the repository. Placeholder body copy to be completed.
- 04
Transfer ownership
Pairing sessions until the internal team runs the release unaided. Placeholder body copy to be completed.
Verification
- Every specification has a completed check log.
- The runbook lives in the repository alongside the code.
- An internal engineer has run a full promotion unaided.
- Ownership is signed off in writing.