{
  "title": "Automation retry message survey",
  "questions": [
    "What did the retry notice mean?",
    "Which timing detail was unclear?",
    "What duplicate-risk explanation was missing?"
  ],
  "question_notes": [
    "Ask whether the notice means a scheduled retry, an available manual retry or a completed attempt. These interpretations lead to different next actions, so preserve the user’s explanation of the displayed state.",
    "Identify whether the unclear timing concerns when a retry starts, how long it may run or when another status update arrives. Use only timing that the actual workflow can support.",
    "Check whether the message explains what is known about the previous attempt and whether repeating the action could repeat a side effect. User feedback locates uncertainty; it does not prove idempotency."
  ],
  "answer_guidance": [
    {
      "question": 1,
      "format": "Short open text",
      "reason": "Ask whether the notice means a scheduled retry, an available manual retry or a completed attempt. These interpretations lead to different next actions, so preserve the user’s explanation of the displayed state.",
      "optional": true
    },
    {
      "question": 2,
      "format": "Short open text",
      "reason": "Identify whether the unclear timing concerns when a retry starts, how long it may run or when another status update arrives. Use only timing that the actual workflow can support.",
      "optional": true
    },
    {
      "question": 3,
      "format": "Short open text",
      "reason": "Check whether the message explains what is known about the previous attempt and whether repeating the action could repeat a side effect. User feedback locates uncertainty; it does not prove idempotency.",
      "optional": true
    }
  ],
  "respondent_instruction": "If nothing was unclear or difficult, say so. Skip questions about steps you did not experience; use not applicable where appropriate.",
  "field_protocol": {
    "send_when": "Show a synthetic failed automation attempt and its real approved retry wording after the user reads the notice, before inviting any further action. Do not test by repeating a production side effect.",
    "decision_owner": "The automation product owner together with the execution or retry-policy maintainer.",
    "followup": "Show the revised notice and ask users to explain the known prior state, the next permitted action and any uncertainty about duplicate effects. Compare those explanations with the approved workflow specification rather than treating reassuring wording as evidence of safe retries.",
    "response_handling": "Record interpretations of synthetic runs only. Exclude credentials, production payloads and real run logs."
  },
  "editorial_sections": [
    {
      "id": "guide-decision-routes",
      "kind": "decision-routes",
      "heading": "Explain the retry state before the next action",
      "intro": "Synthetic notices should reflect the approved execution specification; wording cannot prove safe retry behavior.",
      "rows": [
        [
          "Retry scheduled",
          "Explain which attempt is scheduled and what timing is actually supported.",
          "The user does not mistake scheduled for already completed."
        ],
        [
          "Manual retry available",
          "Explain the approved action and known prior-attempt state.",
          "Uncertainty about duplicate effects stays explicit."
        ],
        [
          "Prior result uncertain",
          "Use the verified status or support route before further action.",
          "Do not infer that the previous side effect failed merely because a response was missing."
        ]
      ]
    }
  ],
  "note": "Examples to adapt. Not a validated instrument; manual editorial data, not a product import payload."
}