Aglet

Learn from stale notification links and lost context

A stale-link lesson should preserve what the notification promised and what current context remained available. Compare later clicks with the original replay matrix, then improve one review question about identifier, state, role, fallback, or action without promising an old page forever.

Keep the lesson for the next incident

  1. Keep the stale evidence

    Record event, identifier, original and current state, age, role, action, destination, explanation, and recovery. State what changed. This prevents a later route cleanup from losing the reason the fallback mattered.

  2. Compare later clicks

    Review current, changed, and permission-limited targets after the change. Look for a state that still lands on a dead end or copy that loses resource identity. Preserve a current-link control and one known fallback.

  3. Refine one destination check

    Require future reviews to replay a current and changed target, inspect role boundary, and verify a useful parent or status path. Assign ownership and revisit date. Define the observation that would show the check reduced notification dead ends.

What to carry forward

The learning record connects one stale click to later state evidence and a reusable destination-and-recovery check. Stop when another reviewer can apply it to a new resource. Carry forward uncertainty where resource state or permission cannot be replayed safely.

Technical background: Apple developer documentation.

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