Decide where the work belongs
Map exposure and effect
For each case, list endpoint, credential label, resource, operation, environment evidence, and resulting state. Separate a rejected read from a successful write or a record that cannot be classified. Keep test and live identifiers out of shared examples.
Choose containment
Compare pausing the integration, correcting one environment variable, isolating a fixture, or reviewing a record. Record who controls each change and what evidence proves it worked. Do not use a live credential to test a configuration hypothesis.
Set environment priority
Queue successful wrong-environment writes and unclassified records first, then shared configuration drift and isolated failed reads. Set owner, review time, safe action, and proof. If endpoint origin is unknown, prioritize labeling before cleanup.
What to carry forward
Return a queue with environment evidence, operation effect, resource scope, containment, owner, and reconciliation proof. Escalate successful cross-environment mutations. Keep rank provisional when configuration or record markers are incomplete. Preserve endpoint labels during any recovery 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