Aglet

Learn from notification read-state confusion and missed work

A read-state lesson should preserve what action changed attention state and whether the underlying work was addressed. Compare later open, mark, group, and badge behavior with the original transition matrix, then improve one review question about reversibility or acknowledgment. Keep the person’s attention state distinct from the work state.

Keep the lesson for the next incident

  1. Keep the state evidence

    Record notification, initial state, focus, open, mark, dismiss, undo, list styling, badge, history, and sync. State what the person intended. This keeps later visual refinements tied to the actual transition.

  2. Compare later actions

    Review passive viewing, explicit mark, grouped child, direct link, and another surface after the change. Look for unread work that disappears or a badge that persists after acknowledgment. Preserve a working no-mutation path.

  3. Refine one state check

    Require future reviews to state whether view means read, test undo or recovery, and compare list with badge and history. Assign ownership and revisit date. Define the observation that would show the check reduced missed work. Preserve a case where acknowledgement did not finish the work.

What to carry forward

The learning record connects one read-state mismatch to later evidence and a repeatable transition check. Stop when another reviewer can apply it to a new notification type. Carry forward uncertainty where sync or task completion remains outside the observed surface.

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