Build a useful investigation brief
Build the language map
List label, description, example, event category, channel, timing, default, mute state, and resulting delivery for representative settings. Include an in-app path and an external channel where available. Record uncertainty about platform-level behavior.
Trace one choice
Change a setting and follow a later event or durable status. Compare expected and observed location, timing, and copy. Check whether a category label controls one channel or several, and record when the product cannot guarantee delivery.
Write the vocabulary brief
State the first mismatch, canonical term, affected settings, and competing explanations. Recommend one bounded copy or mapping experiment with a pass condition based on user prediction. Avoid promising exact delivery from a label alone.
What to carry forward
The investigation is complete when representative labels map to observable outcomes or the first behavior gap is explicit. Stop with one vocabulary or mapping experiment. Keep platform permission and provider delivery uncertainty visible rather than hiding it behind friendly wording.
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