Decide where the work belongs
Describe operation impact
List each rejected operation, affected account or workflow, and whether the request is read, write, or retry work. Attach representative field errors and observed frequency. A high rejection count from an optional path should not outrank a smaller failure that changes a record.
Choose the smallest correction
Compare fixing domain validation, serializer mapping, content type, request contract, or error decoding. Note dependencies and rollback. Do not drop unknown fields or coerce every value just to increase acceptance; that can hide a contract disagreement.
Set the schema queue
Select the first correction, owner, test evidence, and review date. Prioritize durable writes and shared serializers before isolated form copy. If the server contract is ambiguous, queue a documented clarification or captured response rather than a speculative compatibility rule.
What to carry forward
Return a ranked schema queue with blocked operation, field or encoding evidence, data consequence, narrow remedy, owner, and acceptance proof. Escalate requests that could write incorrect values. Mark the order provisional when server validation detail or consumer reach is unknown.
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