Keep the lesson for the next incident
Compare link contracts
Align source page, route, record identifier, project or tenant scope, filters, tabs, pagination, session, and final result across episodes. Separate stale resources from producer omissions.
Preserve the minimum context
Document which path and query fields are required for a meaningful review and which can be dropped safely. Keep unavailable records explicit rather than inventing fallback destinations.
Define a link recurrence rule
Set a review trigger for route, identifier, navigation, or filter changes that touch shared links. Name the producer and consumer checks required before a new URL contract is trusted.
What to carry forward
The lesson should preserve one explicit deep-link contract and a recurrence rule for producers and consumers. Treat the contract as provisional until later navigation changes keep context intact across fresh, returning, and unavailable states. Document the URL contract and a small set of producer and consumer checks, including query preservation and safe failure, so navigation changes expose broken links early.
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