Summary
- Separate changed code from usable outcomes.
- Verify the final surface closest to the user.
- Include failures and limitations in the handoff.
Implementation Is Not Delivery
A changed file is only part of the process. The work reaches a user when the new route opens, the interaction behaves as expected, and the relevant data is current.
Completion is a state that can be seen.
Choose the Right Proof
Different tasks require different evidence. A site needs a real page, a service needs a healthy endpoint, and configuration needs current runtime state. Proof becomes stronger as it moves closer to the user experience.
Describe the Boundary Honestly
If something remains unverified, depends on external state, or still needs a human action, say so directly. A clear limitation is more dependable than vague completion.