System / responsibility / release
Write the acceptance decision before the release decision.
Discovery identifies the current behavior, desired behavior, access rights and dependencies. A proposal names the bounded change and the evidence that would demonstrate it. Ambiguous business rules return to the responsible person rather than becoming hidden code assumptions.
Implementation is reviewed with synthetic data and representative exceptions. Before release, we check the full task, backups, rollback and account ownership. The handover lists verified behavior, known limits and any untested environments. A test report does not become a certification merely because it is written down.