Keep the lesson for the next incident
Document error meanings
Record status, media type, machine-readable code or type, safe detail, local action, and retry policy for each supported operation class. Define an unknown-response fallback and its correlation requirements. State which meanings depend on external documentation or version.
Keep response fixtures
Retain structured, empty, malformed, proxy-like, and operation-specific errors with redacted content. Include a read and a write where retry meaning differs. Store expected local state and attempt count so a decoder change cannot quietly alter recovery.
Set drift reviews
Review new codes, media types, status changes, decoder updates, and rising unknown branches. Assign an owner and threshold for investigation. Close the follow-up only when error fixtures and retry checks cover the client versions and environments actually in use.
What to carry forward
Close learning with error meanings, fixtures, decoder and retry owners, and drift signals. Keep unknown remote or intermediary behavior visible. The durable outcome is an intentional safe fallback and a reproducible response comparison, not a claim that future errors will match today’s shape.
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