{
  "kind": "original-bounded-choice-workflow",
  "version": 1,
  "scope": "Interpret the continuity and customer-reported status of a support follow-up relative to one supplied prior issue. Preserve distinct new problems and missing history; propose a review step without merging, closing or writing tickets.",
  "question": "Compare priorIssue with latestMessage. Need prior context: either absent or relationship unclear. Same issue: latest continues or adds evidence for the unresolved prior problem. New issue: latest describes a different problem, even in the same product. Customer reports resolution: latest clearly says the prior problem is resolved with no new one. A distinct new problem plus prior resolution is New issue. Judge supplied reports only; never close, merge or update tickets.",
  "choices": [
    "Same issue",
    "New issue",
    "Customer reports resolution",
    "Need prior context"
  ],
  "actions": {
    "Same issue": {
      "action": "review_followup_with_prior_issue",
      "payload": {
        "continuityLabel": "Same issue",
        "ticketChanged": false
      },
      "pending": true
    },
    "New issue": {
      "action": "review_separate_issue_intake",
      "payload": {
        "continuityLabel": "New issue",
        "ticketChanged": false
      },
      "pending": true
    },
    "Customer reports resolution": {
      "action": "review_customer_resolution_report",
      "payload": {
        "continuityLabel": "Customer reports resolution",
        "ticketChanged": false
      },
      "pending": true
    },
    "Need prior context": {
      "action": "request_previous_issue_context",
      "payload": {
        "continuityLabel": "Need prior context",
        "ticketChanged": false
      },
      "pending": true
    }
  },
  "samples": [
    {
      "id": "continuing",
      "label": "The customer still sees the same problem",
      "expected": "Same issue",
      "request": {
        "context": "{\n  \"task\": \"Review how the latest support message relates to the prior issue.\",\n  \"priorIssue\": \"The customer reports that saving a renamed project seems to work, but reloading restores the old project name. No final resolution is recorded.\",\n  \"latestMessage\": \"It still changes back to the old name when I reload after saving. Can you keep investigating that rename problem?\"\n}",
        "question": "Compare priorIssue with latestMessage. Need prior context: either absent or relationship unclear. Same issue: latest continues or adds evidence for the unresolved prior problem. New issue: latest describes a different problem, even in the same product. Customer reports resolution: latest clearly says the prior problem is resolved with no new one. A distinct new problem plus prior resolution is New issue. Judge supplied reports only; never close, merge or update tickets.",
        "choices": [
          "Same issue",
          "New issue",
          "Customer reports resolution",
          "Need prior context"
        ]
      }
    },
    {
      "id": "new-evidence",
      "label": "A new reproduction for the same symptom",
      "expected": "Same issue",
      "request": {
        "context": "{\n  \"task\": \"Review how the latest support message relates to the prior issue. Different wording alone does not make a new issue.\",\n  \"priorIssue\": \"The customer reports that saving a renamed project seems to work, but reloading restores the old project name. No final resolution is recorded.\",\n  \"latestMessage\": \"I found another way to reproduce the project rename issue: rename it from the settings panel, save, then reload. The previous name returns.\"\n}",
        "question": "Compare priorIssue with latestMessage. Need prior context: either absent or relationship unclear. Same issue: latest continues or adds evidence for the unresolved prior problem. New issue: latest describes a different problem, even in the same product. Customer reports resolution: latest clearly says the prior problem is resolved with no new one. A distinct new problem plus prior resolution is New issue. Judge supplied reports only; never close, merge or update tickets.",
        "choices": [
          "Same issue",
          "New issue",
          "Customer reports resolution",
          "Need prior context"
        ]
      }
    },
    {
      "id": "unrelated-feature",
      "label": "A different product problem",
      "expected": "New issue",
      "request": {
        "context": "{\n  \"task\": \"Review how the latest support message relates to the prior issue. Account identity alone does not establish continuity.\",\n  \"priorIssue\": \"The customer reports that saving a renamed project seems to work, but reloading restores the old project name. No final resolution is recorded.\",\n  \"latestMessage\": \"A separate problem: exported billing CSV files have no currency column. This message supplies no relation to the project rename issue.\"\n}",
        "question": "Compare priorIssue with latestMessage. Need prior context: either absent or relationship unclear. Same issue: latest continues or adds evidence for the unresolved prior problem. New issue: latest describes a different problem, even in the same product. Customer reports resolution: latest clearly says the prior problem is resolved with no new one. A distinct new problem plus prior resolution is New issue. Judge supplied reports only; never close, merge or update tickets.",
        "choices": [
          "Same issue",
          "New issue",
          "Customer reports resolution",
          "Need prior context"
        ]
      }
    },
    {
      "id": "reported-fixed",
      "label": "The customer says the problem is resolved",
      "expected": "Customer reports resolution",
      "request": {
        "context": "{\n  \"task\": \"Review how the latest support message relates to the prior issue. Reported resolution is not independent verification.\",\n  \"priorIssue\": \"The customer reports that saving a renamed project seems to work, but reloading restores the old project name. No final resolution is recorded.\",\n  \"latestMessage\": \"After the fix, saving a new project name and reloading preserves it. The rename problem is now resolved for me. No other problem is reported.\"\n}",
        "question": "Compare priorIssue with latestMessage. Need prior context: either absent or relationship unclear. Same issue: latest continues or adds evidence for the unresolved prior problem. New issue: latest describes a different problem, even in the same product. Customer reports resolution: latest clearly says the prior problem is resolved with no new one. A distinct new problem plus prior resolution is New issue. Judge supplied reports only; never close, merge or update tickets.",
        "choices": [
          "Same issue",
          "New issue",
          "Customer reports resolution",
          "Need prior context"
        ]
      }
    },
    {
      "id": "history-absent",
      "label": "The earlier issue is unavailable",
      "expected": "Need prior context",
      "request": {
        "context": "{\n  \"task\": \"Review how the latest support message relates to the prior issue. Do not reconstruct missing history.\",\n  \"priorIssue\": \"\",\n  \"latestMessage\": \"The same problem happened again. The earlier support issue is not included.\"\n}",
        "question": "Compare priorIssue with latestMessage. Need prior context: either absent or relationship unclear. Same issue: latest continues or adds evidence for the unresolved prior problem. New issue: latest describes a different problem, even in the same product. Customer reports resolution: latest clearly says the prior problem is resolved with no new one. A distinct new problem plus prior resolution is New issue. Judge supplied reports only; never close, merge or update tickets.",
        "choices": [
          "Same issue",
          "New issue",
          "Customer reports resolution",
          "Need prior context"
        ]
      }
    },
    {
      "id": "fixed-then-new",
      "label": "The earlier issue is fixed but a new one appears",
      "expected": "New issue",
      "request": {
        "context": "{\n  \"task\": \"Review how the latest support message relates to the prior issue. Apply the explicit new-problem priority.\",\n  \"priorIssue\": \"The customer reports that saving a renamed project seems to work, but reloading restores the old project name. No final resolution is recorded.\",\n  \"latestMessage\": \"Project names now remain correct after saving and reloading. Separately, my exported billing CSV is missing its currency column.\"\n}",
        "question": "Compare priorIssue with latestMessage. Need prior context: either absent or relationship unclear. Same issue: latest continues or adds evidence for the unresolved prior problem. New issue: latest describes a different problem, even in the same product. Customer reports resolution: latest clearly says the prior problem is resolved with no new one. A distinct new problem plus prior resolution is New issue. Judge supplied reports only; never close, merge or update tickets.",
        "choices": [
          "Same issue",
          "New issue",
          "Customer reports resolution",
          "Need prior context"
        ]
      }
    }
  ],
  "consumer": "preview_choice_workflow_v2.py"
}
