Build a useful investigation brief
Gather adjacent records
Collect deployments before and after the target, repository references, build or release identifiers, branch metadata, runtime version markers, and any recorded diff summaries. Preserve source timestamps and avoid silently collapsing similar records.
Match stable attributes
Compare environment, service, branch, artifact, version, and provider reference across records. Use multiple matching fields before linking a candidate commit. Record contradictions such as a version that appears in two environments.
Test the candidate
Look for behavior or runtime evidence that the candidate code could have served the affected path. A plausible candidate remains a hypothesis until an independent record confirms it; capture what would provide that confirmation.
What to carry forward
The investigation brief should contain the strongest candidate or an explicit unresolved gap, with every join labeled exact or inferred. It should say which release comparisons are now valid and which remain unsafe because commit identity is not proven.
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