Build a useful investigation brief
Reconstruct the starting state
Use available timestamps, release identifiers, role context, and workflow records to define the narrowest plausible setup. If a field is unavailable, say so. Avoid copying private payloads into notes when a stable reference can support the same check.
Run discriminating checks
Test the shortest path and one nearby alternative, changing role, input, network state, or timing only when evidence suggests it. Record exact results, including successful attempts. A failed attempt with different conditions does not confirm the original report.
Separate symptom and mechanism
Write the reproducible symptom, triggering conditions, and current mechanism hypotheses in separate sections. Rank hypotheses by observations and state what would falsify each. Recommend the smallest next experiment if the original failure remains unconfirmed.
What to carry forward
A useful investigation ends with a repeatable symptom, a bounded condition set, negative results, and ranked hypotheses or an explicit inability to reproduce. Stop when new variations no longer distinguish explanations; hand off the smallest evidence gap rather than broadening randomly.
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