Keep the lesson for the next incident
Document the environment contract
Record endpoint origin, credential label, resource marker, configuration precedence, allowed operations, and safe outcome for a mismatch. Define who owns each environment and how a record is classified when its destination cannot be proven.
Keep crossed fixtures
Retain matching test and production cases, crossed endpoint and credential, copied identifier, missing marker, and restart examples with synthetic resources. Store expected local state and side-effect limits. Include the original mixup shape for future configuration changes.
Review boundary signals
Watch endpoint changes, unexpected markers, cross-environment rejections, successful writes, and configuration overrides by client revision. Assign an owner and threshold. Close the follow-up only when real caller paths use the documented labels and safeguards.
What to carry forward
Close learning with environment rules, crossed fixtures, configuration ownership, and review signals. Keep external resource markers and unclassified records explicit. The useful outcome is a fast destination check, not a promise that a familiar endpoint always means the right environment.
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