{
  "kind": "original-bounded-choice-workflow",
  "version": 1,
  "scope": "Check whether supplied success feedback names the operation it reports as completed.",
  "question": "Inspect message role, text and supplied heading. Need role context: role or relevant context is missing or ambiguous. Not success feedback: a control label, named state or quoted example. Operation named: success feedback identifies the completed operation in text or heading. Generic success: a confirmed standalone success notification names no operation. Do not infer notification role from Done alone, or verify that the operation actually succeeded.",
  "choices": [
    "Operation named",
    "Generic success",
    "Not success feedback",
    "Need role context"
  ],
  "actions": {
    "Operation named": {
      "action": "preview_jev_success_message_operation",
      "payload": {
        "decision": "Operation named"
      },
      "pending": true
    },
    "Generic success": {
      "action": "preview_jev_success_message_operation",
      "payload": {
        "decision": "Generic success"
      },
      "pending": true
    },
    "Not success feedback": {
      "action": "preview_jev_success_message_operation",
      "payload": {
        "decision": "Not success feedback"
      },
      "pending": true
    },
    "Need role context": {
      "action": "preview_jev_success_message_operation",
      "payload": {
        "decision": "Need role context"
      },
      "pending": true
    }
  },
  "samples": [
    {
      "id": "case-1",
      "label": "Address save message",
      "expected": "Operation named",
      "request": {
        "context": "{\n  \"task\": \"Check whether supplied success feedback names the operation it reports as completed.\",\n  \"evidence\": {\n    \"role\": \"Success notification after saving an address\",\n    \"heading\": null,\n    \"text\": \"Shipping address saved.\"\n  }\n}",
        "question": "Inspect message role, text and supplied heading. Need role context: role or relevant context is missing or ambiguous. Not success feedback: a control label, named state or quoted example. Operation named: success feedback identifies the completed operation in text or heading. Generic success: a confirmed standalone success notification names no operation. Do not infer notification role from Done alone, or verify that the operation actually succeeded.",
        "choices": [
          "Operation named",
          "Generic success",
          "Not success feedback",
          "Need role context"
        ]
      }
    },
    {
      "id": "case-2",
      "label": "Heading supplies operation",
      "expected": "Operation named",
      "request": {
        "context": "{\n  \"task\": \"Check whether supplied success feedback names the operation it reports as completed.\",\n  \"evidence\": {\n    \"role\": \"Success notification\",\n    \"heading\": \"Password updated\",\n    \"text\": \"Success\"\n  }\n}",
        "question": "Inspect message role, text and supplied heading. Need role context: role or relevant context is missing or ambiguous. Not success feedback: a control label, named state or quoted example. Operation named: success feedback identifies the completed operation in text or heading. Generic success: a confirmed standalone success notification names no operation. Do not infer notification role from Done alone, or verify that the operation actually succeeded.",
        "choices": [
          "Operation named",
          "Generic success",
          "Not success feedback",
          "Need role context"
        ]
      }
    },
    {
      "id": "case-3",
      "label": "Generic standalone toast",
      "expected": "Generic success",
      "request": {
        "context": "{\n  \"task\": \"Check whether supplied success feedback names the operation it reports as completed.\",\n  \"evidence\": {\n    \"role\": \"Standalone success toast with no heading or surrounding operation text\",\n    \"heading\": null,\n    \"text\": \"Operation completed successfully!\"\n  }\n}",
        "question": "Inspect message role, text and supplied heading. Need role context: role or relevant context is missing or ambiguous. Not success feedback: a control label, named state or quoted example. Operation named: success feedback identifies the completed operation in text or heading. Generic success: a confirmed standalone success notification names no operation. Do not infer notification role from Done alone, or verify that the operation actually succeeded.",
        "choices": [
          "Operation named",
          "Generic success",
          "Not success feedback",
          "Need role context"
        ]
      }
    },
    {
      "id": "case-4",
      "label": "Done control",
      "expected": "Not success feedback",
      "request": {
        "context": "{\n  \"task\": \"Check whether supplied success feedback names the operation it reports as completed.\",\n  \"evidence\": {\n    \"role\": \"Button that exits editing\",\n    \"heading\": \"Edit address\",\n    \"text\": \"Done\"\n  }\n}",
        "question": "Inspect message role, text and supplied heading. Need role context: role or relevant context is missing or ambiguous. Not success feedback: a control label, named state or quoted example. Operation named: success feedback identifies the completed operation in text or heading. Generic success: a confirmed standalone success notification names no operation. Do not infer notification role from Done alone, or verify that the operation actually succeeded.",
        "choices": [
          "Operation named",
          "Generic success",
          "Not success feedback",
          "Need role context"
        ]
      }
    },
    {
      "id": "case-5",
      "label": "Quoted guide example",
      "expected": "Not success feedback",
      "request": {
        "context": "{\n  \"task\": \"Check whether supplied success feedback names the operation it reports as completed.\",\n  \"evidence\": {\n    \"role\": \"Style guide example\",\n    \"heading\": \"Avoid vague messages\",\n    \"text\": \"“Success!” is an example of wording to review.\"\n  }\n}",
        "question": "Inspect message role, text and supplied heading. Need role context: role or relevant context is missing or ambiguous. Not success feedback: a control label, named state or quoted example. Operation named: success feedback identifies the completed operation in text or heading. Generic success: a confirmed standalone success notification names no operation. Do not infer notification role from Done alone, or verify that the operation actually succeeded.",
        "choices": [
          "Operation named",
          "Generic success",
          "Not success feedback",
          "Need role context"
        ]
      }
    },
    {
      "id": "case-6",
      "label": "Done without context",
      "expected": "Need role context",
      "request": {
        "context": "{\n  \"task\": \"Check whether supplied success feedback names the operation it reports as completed.\",\n  \"evidence\": {\n    \"role\": null,\n    \"heading\": null,\n    \"text\": \"Done\"\n  }\n}",
        "question": "Inspect message role, text and supplied heading. Need role context: role or relevant context is missing or ambiguous. Not success feedback: a control label, named state or quoted example. Operation named: success feedback identifies the completed operation in text or heading. Generic success: a confirmed standalone success notification names no operation. Do not infer notification role from Done alone, or verify that the operation actually succeeded.",
        "choices": [
          "Operation named",
          "Generic success",
          "Not success feedback",
          "Need role context"
        ]
      }
    }
  ],
  "consumer": "preview_choice_workflow.py"
}
