Aglet

How to verify first-use help and recovery links

Verification should prove that a new person can answer the immediate question and return to the action they need. Test help from the real blank, pending, and failure states rather than only from a central page. Keep every destination grounded in an existing route and capability.

Check whether the outcome improved

  1. Verify task entry points

    Open synthetic workspace, project, verification, and setup states and assert each exposes a specific help or next-action link when needed. Confirm the link label names the destination, the route preserves workspace context, and the page explains the expected result without overpromising.

  2. Verify recovery states

    Exercise empty project, invalid setup form, failed built-in check, pending verification, stale invitation, and unavailable workspace fixtures where supported. Assert each has a safe back, retry, or relevant existing destination. Ensure unauthorized roles do not receive actions they cannot use.

  3. Verify access and layout

    Navigate with keyboard focus and at a narrow viewport. Assert links are reachable, labels remain readable, deep links do not overflow, and browser back returns to the originating task. Mark unsupported role, device, or external-mail branches partial with their gaps recorded.

What to carry forward

Accept when each tested first-use state offers one accurate path to explanation or recovery, preserves context, and respects role boundaries. Mark unsupported capabilities and external timing partial; a centralized help page cannot compensate for a dead action link.

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