Aglet

Verify document links remain usable through expected waiting

Verification should test the waiting behavior readers actually use rather than clicking every link immediately. Compare the document shown, link context, response, and recovery after an idle interval. Confirm a renewed link is understandable and remains tied to the intended document revision.

Check whether the outcome improved

  1. Exercise waiting paths

    Open a document page and download immediately, after a known wait, from a copied link, and after a delayed request start. Record document identity, expiry context, response, and expected recovery before each attempt.

  2. Check renewal behavior

    When a link expires, follow the provided renewal or return action. Verify the new link opens the same intended revision, keeps the reader's context, and does not create an unexplained loop between an old page and a new document.

  3. Inspect error clarity

    Review expired, malformed, unavailable, and transport-failure outcomes for distinct wording and next actions. Confirm a reader can tell whether waiting caused expiration and whether retrying the same link can succeed.

What to carry forward

Accept link behavior when expected waits either succeed or produce a clear same-document recovery, with revision identity preserved. Fail when a reader receives an unexplained failure, renewal changes the intended file, or a valid link expires during its documented use path.

Technical background: RFC Editor reference.

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