Decide where the work belongs
Set the confidence ceiling
List the strongest claim the current evidence supports and the stronger claims it cannot support. For example, repeated checkout friction may be supported while data loss is unconfirmed. Use that ceiling when comparing the report with known queue items.
Compare possible harm
Consider who might be affected, whether a workaround exists, how quickly the report could spread, and how reversible the harm would be. Keep these as questions with evidence status instead of converting them into invented counts.
Choose an evidence or fix queue
Decide whether to request details, reproduce immediately, schedule a scoped fix, or defer. Name the trigger for changing the decision, such as a second independent report or a confirmed permission boundary, and assign the next owner.
What to carry forward
The output is a queue position tied to an evidence ceiling, plausible harm, and a concrete next step. If the report may represent severe harm but lacks proof, prioritize bounded investigation rather than declaring either a critical bug or harmless noise.
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