Decide where the work belongs
Rank exposure
Identify environments, services, customer segments, and jobs using the drifted configuration. Higher priority follows broad or expanding exposure, sensitive behavior, or inability to identify the served setting.
Rank reproducibility loss
Ask which release or verification conclusions cannot be repeated because configuration identity is unknown. A stable but unexplained difference may deserve priority even when no error spike is visible.
Set a safe review point
Choose a checkpoint before the next release comparison, scheduled task, or customer-impact decision. State which redacted identifier, behavior comparison, or owner confirmation would change the queue position.
What to carry forward
The queue result should include affected exposure, blocked decision, owner, and a redacted evidence checkpoint. Keep priority high when drift can change behavior or conceal a regression; lower it only when runtime identity and behavior align. Prioritize drift that changes customer paths, data handling, or recovery choices, while keeping harmless formatting or an unverified comparison separate from an observed behavior change.
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