Aglet

Verify work against clear acceptance criteria and edge states

Verification should use the criteria as a decision contract, not as a checklist of implementation details. Exercise meaningful boundaries, record evidence and exceptions, and ensure the final status reflects the outcome rather than the number of tasks completed. Use acceptance as an outcome contract so implementation detail does not substitute for a pass decision.

Check whether the outcome improved

  1. Run representative outcomes

    Test each required actor, starting state, input, action, and expected result. Capture evidence references and compare observed behavior directly with the acceptance condition, including intentional unsupported cases. Capture evidence for the observed outcome, not just the code path that produced it.

  2. Exercise failure and recovery

    Check rejection, permission, empty, retry, partial failure, and recovery paths that could change the acceptance decision. Record whether behavior is accepted, failed, or outside scope with a reason. Include the boundary that would reopen or split the work.

  3. Review independent interpretation

    Have a reviewer who did not implement the work assess the criteria and evidence. Confirm they reach the same pass or fail decision and can identify the remaining owner or follow-up.

What to carry forward

Verification passes when representative outcomes and meaningful boundaries meet observable criteria, evidence is traceable, and an independent reviewer reaches the same decision. If criteria remain ambiguous or a required case fails, keep the item open with the exact 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