Aglet

Verify document stages provide safe and specific next actions

Verification should test the decision a reader faces at each stage, including a slow process and a recoverable failure. Compare status, capability, controls, and resulting transition. Confirm a document is preserved when waiting is safe and replaced only by an explicit choice.

Check whether the outcome improved

  1. Exercise each stage

    Use pending, partial-derivative, accepted, and failed fixtures. Record the expected next action and verify the interface offers a matching control or a clear wait state without implying that all processing stages are complete.

  2. Run recovery choices

    Follow wait, retry, replace, download, and continue actions where supported. Confirm each transition preserves or changes the document identity as documented, and that a retry does not repeat a known failure without evidence.

  3. Check revisit and handoff

    Leave and return during each state, then hand the document to its next workflow. Verify the same action guidance persists and that downstream controls appear only when their required capability is ready.

What to carry forward

Accept stage guidance when every tested state presents a safe, specific next action and transitions preserve the documented document identity. Fail when users must guess whether to wait or retry, can discard useful work accidentally, or see a control before its capability exists.

Technical background: W3C guidance.

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