Establish what is happening
Capture role and state
Record event, resource, role, ownership, target state, action label, destination, response, and fallback for representative users. Include owner, reviewer, and read-only contexts. Keep visible action and server response separate. Record whether each action remains safe and useful.
Compare safe outcomes
Ask what each role needs to review, acknowledge, or change and whether the action promises that outcome. Compare an unavailable action with an action that should be hidden. Do not infer authority from a notification’s presence. Record whether a denied action still leaves a useful destination.
Set the scope boundary
State which roles see each action, what state changes remove it, and how the destination explains a boundary. Preserve a read-only control. Stop when another reviewer can predict action visibility and response from role and state.
What to carry forward
The triage output is a role-and-state action matrix with labels, destinations, and fallback. Stop when visibility and allowed outcome are distinguishable. If role or target state is unknown, keep the action conservative and route the missing context.
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