Aglet

Verify a vague bug fix against the original outcome

Verification must return to the original report while using the clearer observation produced during investigation. Test the confirmed path, nearby conditions, and any safety boundary introduced by the fix. Keep unverified interpretations visible so closure does not overstate the result.

Check whether the outcome improved

  1. Restate the confirmed behavior

    Convert the investigation result into a before-and-after check with actor, state, action, and expected result. Include the original customer wording only as context. If the mechanism remains uncertain, verify the outcome without claiming a specific internal repair.

  2. Exercise adjacent paths

    Run a nearby role, input, and recovery path that could regress when the fix changes validation, permissions, or timing. Record both success and expected rejection behavior. Keep the matrix small and tied to the observed boundary.

  3. Check the closure language

    Compare the evidence with the proposed resolution statement. Ensure it says what was verified, which contexts were tested, and what remains unknown. Link the original report and investigation references so a reviewer can audit the claim.

What to carry forward

Verification passes when the confirmed customer outcome is restored, adjacent behavior remains intentional, and the closure text matches tested scope. If the original report cannot be reproduced, close only the investigated symptom or keep the item open with a stated evidence gap.

Keep the decision with the work.

Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.

Create an account See the product workflow