Build a useful investigation brief
Freeze the version matrix
Capture component, environment, commit or artifact, exposure, and timestamp in a matrix that can be repeated. Include the known compatible pair and the suspected skew pair when available.
Trace one failing interaction
Follow a representative request, event, or job across the boundary and record payload shape, response, retries, and downstream effects. Compare it with an equivalent successful interaction under a matched version pair.
Test contract alternatives
Check whether configuration, data shape, routing, or timing could explain the behavior without version skew. Seek examples that violate the leading explanation and record which compatibility assumptions remain untested.
What to carry forward
The investigation brief should show the version matrix, first divergent boundary, representative evidence, and competing explanations. Conclude with supported incompatibility, compatible coexistence, or unresolved attribution, and state the exact evidence that would change it. Follow one representative request or event across both versions and compare serialization, validation, and response behavior; a version matrix alone cannot prove the boundary is exercised.
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