{
  "title": "Application error recovery survey",
  "questions": [
    "What were you trying to complete?",
    "What next action did the message suggest?",
    "What recovery information was missing?"
  ],
  "question_notes": [
    "The intended task establishes what the failure interrupted and which context a recovery message must preserve. Keep private task data out of the response.",
    "The suggested action reveals whether the failure message offers an understandable recovery route instead of merely announcing a problem. Clarify actual supported steps, without inventing fixes or implying the underlying failure has been resolved.",
    "Missing recovery information identifies the uncertainty preventing an appropriate next action. Explain verified retry or assistance routes without promising that the underlying failure is resolved."
  ],
  "answer_guidance": [
    {
      "question": 1,
      "format": "Optional short text",
      "reason": "Retain the specific point or condition described; avoid replacing it with an unexplained rating."
    },
    {
      "question": 2,
      "format": "Optional written explanation",
      "reason": "Keep context that distinguishes different experiences. Do not collect stack traces containing private data."
    },
    {
      "question": 3,
      "format": "Optional improvement suggestion",
      "reason": "Keep the suggested change separate from whether it has been tested. Explain whether retrying duplicates the action."
    }
  ],
  "respondent_instruction": "If nothing was unclear or difficult, say so. Skip questions about steps you did not experience; use not applicable where appropriate.",
  "note": "Examples to adapt. Not a validated instrument."
}