Aglet

Investigate notification read-state transitions across surfaces

An investigation should show which action changes read state and whether every surface reflects it. Replay keyboard, pointer, grouped, and direct paths, compare item and badge state, and inspect undo or return behavior. Keep viewed content separate from completed work.

Build a useful investigation brief

  1. Build the transition matrix

    List initial state, action, focus, open result, mark control, list style, badge, history, sync, and return path. Include a grouped item and a direct detail link. Record expected acknowledgment before each action.

  2. Trace one item

    Open, focus, dismiss, mark, undo, and revisit the same notification where supported. Compare list, badge, history, and other surface after each step. Record a change that occurs on load or focus without explicit intent.

  3. Write the read brief

    State first divergence, affected action, surfaces, and competing explanations such as automatic read, delayed sync, or unclear copy. Recommend one bounded transition experiment with a pass condition. Do not label viewing as acknowledgment without product evidence.

What to carry forward

The investigation is complete when read transitions and surface updates are reproducible, or the first unknown is explicit. Stop with one bounded state or recovery experiment. Preserve the distinction between viewed, acknowledged, and completed work in the brief.

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