Aglet

Verify commit identity attached to a deployment

Verification should establish identity rather than simply populate a field. Compare the deployment record with a second source such as a build artifact, runtime version, release note, or adjacent repository record. Keep the result qualified if only one inferred clue exists.

Check whether the outcome improved

  1. Check repository and branch

    Confirm repository, service, environment, and branch values match the release under review. A matching branch is useful context but does not replace the commit proof; record that distinction explicitly.

  2. Confirm the commit independently

    Match the commit or immutable artifact reference across a deployment or build record and an observed runtime or release record. Note timing gaps and any transformation that could make identifiers appear equivalent.

  3. Revisit the blocked comparison

    Use the verified identity to reassess the original regression or rollout question. If identity remains ambiguous, preserve the candidate list and explain why the release cannot yet support a causal comparison.

What to carry forward

Verification should say confirmed, candidate only, or unresolved and cite the independent records behind that status. Close the context gap only when repository and immutable release identity agree; a newly populated label without proof is not enough.

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