Keep the lesson for the next incident
Cluster mismatch cases
Group findings by wrong revision, similar document, format drift, retry identity, stale selection, partial assembly, and missing comparison evidence. Record the user decision and the first identity signal that failed.
Document binding semantics
State which identity and revision are selected, how requested formats relate to that source, what response evidence is preserved, and how completion is verified. Include lookalike documents and distinct revision markers.
Add an identity trigger
Require the fixtures when changing selection, revision resolution, caching, redirects, retries, conversion, or download completion. Assign an owner for binding and record the content comparison that proves a result is the selected artifact.
What to carry forward
The learning record is useful when selection identity, revision, representation, and content evidence have explicit relationships with lookalike fixtures. If a client cannot verify bytes directly, document the strongest available identity evidence and its boundary.
Technical background: RFC Editor reference.
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