Build a useful investigation brief
Map route resolution
List route pattern, parameter names, query keys, resource lookup scope, authorization check, and redirect behavior. Mark where the expected record or selected view becomes unavailable.
Compare entry points
Generate the link from list, detail, notification, search, and filtered views where applicable. Compare identifiers, return parameters, and final state to find which producer emits an incomplete contract.
Test safe edge states
Check archived, missing, cross-project, signed-out, and stale links using non-sensitive fixtures. Confirm failures remain appropriately bounded and do not turn a routing repair into an access expansion.
What to carry forward
The brief should identify the first broken route or context field, producer entry point, safe failure behavior, and evidence for each. Conclude routing defect, stale resource, intentional denial, or unresolved with confidence. Trace the producer’s path and parameters into route matching, tenant scope, policy checks, lookup, and rendering, keeping an unavailable record distinct from a broken URL. Use a known-good link from the same producer to separate a route contract error from a record lifecycle 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