Keep the lesson for the next incident
Record environment rules
Document endpoint and environment pairing, verification context, trusted source, resource marker, ambiguous-event disposition, retry behavior, and owner. State which metadata is evidence and which can be missing or spoofed for every receiver revision.
Keep crossed fixtures
Retain matching, crossed, missing-marker, rejected, and retry cases with expected route and effect. Include the original mix-up and a review of retained identifiers. Do not store credential values or unnecessary payload content in the lesson.
Review separation signals
Watch crossed endpoint attempts, environment mismatches, missing markers, rejected verification, and resource changes from test traffic. Assign thresholds and an owner. Re-run the matrix after configuration, endpoint, or fixture changes.
What to carry forward
Close learning with environment rules, crossed fixtures, ownership, recurrence signals, and explicit origin limits. The useful outcome is safer routing evidence, not a payload label treated as authority. Keep resource and credential uncertainty attached to later reviews. Review during each release review.
Technical background: OpenAI documentation.
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