{
  "kind": "original-bounded-choice-workflow",
  "version": 1,
  "scope": "Identify why a supplied analytics report lacks a requested answer, or recognize that its reported result already answers the question.",
  "question": "Use the question, catalog notes and query report. Ambiguous request: an unresolved meaning prevents one query. Missing field: a clear request needs an explicitly unavailable fact. No matches: a completed row-list query returned zero rows. Available: a reported answer, including a count of zero, other than an empty row list. Use Unclear when missing or conflicting evidence prevents these decisions. Do not execute SQL or infer data availability.",
  "choices": [
    "Missing field",
    "No matches",
    "Ambiguous request",
    "Available",
    "Unclear"
  ],
  "actions": {
    "Missing field": {
      "action": "preview_jev_data_answer_gap",
      "payload": {
        "decision": "Missing field"
      },
      "pending": true
    },
    "No matches": {
      "action": "preview_jev_data_answer_gap",
      "payload": {
        "decision": "No matches"
      },
      "pending": true
    },
    "Ambiguous request": {
      "action": "preview_jev_data_answer_gap",
      "payload": {
        "decision": "Ambiguous request"
      },
      "pending": true
    },
    "Available": {
      "action": "preview_jev_data_answer_gap",
      "payload": {
        "decision": "Available"
      },
      "pending": true
    },
    "Unclear": {
      "action": "preview_jev_data_answer_gap",
      "payload": {
        "decision": "Unclear"
      },
      "pending": true
    }
  },
  "samples": [
    {
      "id": "case-1",
      "label": "The required fact is not stored",
      "expected": "Missing field",
      "request": {
        "context": "{\n  \"task\": \"Identify why a supplied analytics report lacks a requested answer, or recognize that its reported result already answers the question.\",\n  \"evidence\": {\n    \"question\": \"What is the average owner-satisfaction rating for each vehicle make?\",\n    \"catalogNotes\": \"The available views contain vehicle make and specifications, but no owner-satisfaction ratings or source from which to obtain them.\",\n    \"queryReport\": \"No query was run because the required rating is unavailable.\"\n  }\n}",
        "question": "Use the question, catalog notes and query report. Ambiguous request: an unresolved meaning prevents one query. Missing field: a clear request needs an explicitly unavailable fact. No matches: a completed row-list query returned zero rows. Available: a reported answer, including a count of zero, other than an empty row list. Use Unclear when missing or conflicting evidence prevents these decisions. Do not execute SQL or infer data availability.",
        "choices": [
          "Missing field",
          "No matches",
          "Ambiguous request",
          "Available",
          "Unclear"
        ]
      }
    },
    {
      "id": "case-2",
      "label": "A supported query returns no vehicles",
      "expected": "No matches",
      "request": {
        "context": "{\n  \"task\": \"Identify why a supplied analytics report lacks a requested answer, or recognize that its reported result already answers the question.\",\n  \"evidence\": {\n    \"question\": \"List vehicles that have rear entertainment and rear-wheel drive.\",\n    \"catalogNotes\": \"Both attributes are available and their definitions are unambiguous.\",\n    \"queryReport\": \"The validated row-list query completed successfully for both conditions and returned zero rows.\"\n  }\n}",
        "question": "Use the question, catalog notes and query report. Ambiguous request: an unresolved meaning prevents one query. Missing field: a clear request needs an explicitly unavailable fact. No matches: a completed row-list query returned zero rows. Available: a reported answer, including a count of zero, other than an empty row list. Use Unclear when missing or conflicting evidence prevents these decisions. Do not execute SQL or infer data availability.",
        "choices": [
          "Missing field",
          "No matches",
          "Ambiguous request",
          "Available",
          "Unclear"
        ]
      }
    },
    {
      "id": "case-3",
      "label": "Best has no agreed measure",
      "expected": "Ambiguous request",
      "request": {
        "context": "{\n  \"task\": \"Identify why a supplied analytics report lacks a requested answer, or recognize that its reported result already answers the question.\",\n  \"evidence\": {\n    \"question\": \"Show the best vehicles.\",\n    \"catalogNotes\": \"Price, fuel use and cargo capacity are available; no ranking policy has been selected.\",\n    \"queryReport\": \"No query was formed because best could mean cheapest, most efficient or most spacious.\"\n  }\n}",
        "question": "Use the question, catalog notes and query report. Ambiguous request: an unresolved meaning prevents one query. Missing field: a clear request needs an explicitly unavailable fact. No matches: a completed row-list query returned zero rows. Available: a reported answer, including a count of zero, other than an empty row list. Use Unclear when missing or conflicting evidence prevents these decisions. Do not execute SQL or infer data availability.",
        "choices": [
          "Missing field",
          "No matches",
          "Ambiguous request",
          "Available",
          "Unclear"
        ]
      }
    },
    {
      "id": "case-4",
      "label": "An answer is present",
      "expected": "Available",
      "request": {
        "context": "{\n  \"task\": \"Identify why a supplied analytics report lacks a requested answer, or recognize that its reported result already answers the question.\",\n  \"evidence\": {\n    \"question\": \"What is the average listed price for the supplied current inventory?\",\n    \"catalogNotes\": \"Listed price in USD and the current-inventory scope are explicitly defined.\",\n    \"queryReport\": \"The validated aggregate query completed and returned average_listed_price_usd = 18400 for that inventory.\"\n  }\n}",
        "question": "Use the question, catalog notes and query report. Ambiguous request: an unresolved meaning prevents one query. Missing field: a clear request needs an explicitly unavailable fact. No matches: a completed row-list query returned zero rows. Available: a reported answer, including a count of zero, other than an empty row list. Use Unclear when missing or conflicting evidence prevents these decisions. Do not execute SQL or infer data availability.",
        "choices": [
          "Missing field",
          "No matches",
          "Ambiguous request",
          "Available",
          "Unclear"
        ]
      }
    },
    {
      "id": "case-5",
      "label": "Zero is the requested count",
      "expected": "Available",
      "request": {
        "context": "{\n  \"task\": \"Identify why a supplied analytics report lacks a requested answer, or recognize that its reported result already answers the question.\",\n  \"evidence\": {\n    \"question\": \"How many vehicles have rear entertainment and rear-wheel drive?\",\n    \"catalogNotes\": \"Both attributes and the inventory scope are explicitly defined.\",\n    \"queryReport\": \"The validated count query completed and returned one result row: matching_vehicle_count = 0.\"\n  }\n}",
        "question": "Use the question, catalog notes and query report. Ambiguous request: an unresolved meaning prevents one query. Missing field: a clear request needs an explicitly unavailable fact. No matches: a completed row-list query returned zero rows. Available: a reported answer, including a count of zero, other than an empty row list. Use Unclear when missing or conflicting evidence prevents these decisions. Do not execute SQL or infer data availability.",
        "choices": [
          "Missing field",
          "No matches",
          "Ambiguous request",
          "Available",
          "Unclear"
        ]
      }
    },
    {
      "id": "case-6",
      "label": "Execution outcome is unknown",
      "expected": "Unclear",
      "request": {
        "context": "{\n  \"task\": \"Identify why a supplied analytics report lacks a requested answer, or recognize that its reported result already answers the question.\",\n  \"evidence\": {\n    \"question\": \"List electric vehicles in the current inventory.\",\n    \"catalogNotes\": \"Fuel type and current inventory are defined and available.\",\n    \"queryReport\": \"The query was queued. Its completion status and result have not been supplied.\"\n  }\n}",
        "question": "Use the question, catalog notes and query report. Ambiguous request: an unresolved meaning prevents one query. Missing field: a clear request needs an explicitly unavailable fact. No matches: a completed row-list query returned zero rows. Available: a reported answer, including a count of zero, other than an empty row list. Use Unclear when missing or conflicting evidence prevents these decisions. Do not execute SQL or infer data availability.",
        "choices": [
          "Missing field",
          "No matches",
          "Ambiguous request",
          "Available",
          "Unclear"
        ]
      }
    }
  ],
  "consumer": "preview_choice_workflow.py"
}
