Prompt
Help us with our idempotent design work based on the goals and materials below. [input] Goals and usage situations: In an idempotent design, you want to resolve a blockage and decide the next course of action. Resources to review: Write API and retry conditions Conditions and Constraints: Please proceed based on the provided data, and mark any missing facts as requiring confirmation. Previous attempts and records: This is my first attempt. Please proceed from the parts that can be confirmed in the current data. [Key points to check in this topic] Check for duplicate side effects from re-executing the same request, loss of response, and simultaneous calls. [Results to be created this time] Document the design intent, usage, exceptions, constraints, and verification methods identified in the current code. Do not create an intent that is not provided and leave any unconfirmed parts as questions. Please include a minimal call example and any contracts to be aware of when changing. [Working Principle] Give priority to facts confirmed in the current environment and provided code. Don't create APIs/files/tests that don't exist. Treat sensitive values as hidden examples and leave unexecuted tasks as unexecuted. If there is no input that will change the results, ask only the necessary questions first and proceed with the parts that can be confirmed with data. [Completion criteria] Make sure the interface and examples in the documentation match the actual code. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.