Establish what is happening
Describe the event
Record event type, actor, deadline, consequence of waiting, available recovery, current label, and channel. Include a routine update and a time-sensitive example. Keep the user’s ability to review the event later in the evidence.
Compare interruption needs
Ask whether the event needs immediate attention, eventual visibility, or no interruption. Compare active, passive, scheduled, and urgent paths where supported. A high-impact event can still need a quieter channel when the consequence is not immediate.
Set an urgency boundary
State the evidence for each level, the safe default, and the condition that would justify escalation. Preserve an example that should remain routine. Stop when another reviewer can explain urgency from consequence and timing rather than title alone.
What to carry forward
The triage output is an urgency matrix with event, consequence, timing, channel, and recovery. Stop when immediate need and convenient information are distinguishable. If the consequence of waiting is unknown, keep the event at a conservative level and route the evidence question.
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