Build a useful investigation brief
Build an identity chain
List stable identifiers for project, environment, service, repository, deployment, commit, and observed request or job. Link each value to its source record and timestamp. Mark inferred joins separately from exact matches.
Find the first disagreement
Compare environment and version values at each boundary from release creation through observed behavior. Check whether a default, alias, copied configuration, or delayed event could explain the transition without assuming a system defect.
Test the exposure hypothesis
Use independent evidence such as routing records, runtime version, or environment-specific behavior to decide whether the wrong target served traffic. A presentation mismatch and an execution mismatch require different follow-up.
What to carry forward
The investigation brief should identify the first mismatched boundary, supporting records, and confidence in whether user traffic was affected. State the exact identifier or evidence still missing, and keep remediation separate from the finding until ownership reviews it. Include the record that proves each hop, such as a deployment identifier or runtime marker, and note where an alias, copied setting, or cache could have hidden the disagreement.
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