{
  "kind": "original-bounded-choice-workflow",
  "version": 1,
  "scope": "Select a supplied business concept whose fields cover an analytics question, while preserving requests spanning concepts or lacking a clear route.",
  "question": "Use question meaning and the complete concept catalog. Clarify first if the request, field meanings or catalog coverage is missing or ambiguous, or several single concepts fully fit. Choose Rear, Offroad or Electric only if exactly one covers every required field. Use Multiple concepts if all fields are covered only by combining concepts. Use No concept if any required field is outside this catalog. Do not invent fields, joins or SQL, execute a query or claim a result.",
  "choices": [
    "Rear",
    "Offroad",
    "Electric",
    "Multiple concepts",
    "No concept",
    "Clarify"
  ],
  "actions": {
    "Rear": {
      "action": "preview_jev_analytics_concept_route",
      "payload": {
        "decision": "Rear"
      },
      "pending": true
    },
    "Offroad": {
      "action": "preview_jev_analytics_concept_route",
      "payload": {
        "decision": "Offroad"
      },
      "pending": true
    },
    "Electric": {
      "action": "preview_jev_analytics_concept_route",
      "payload": {
        "decision": "Electric"
      },
      "pending": true
    },
    "Multiple concepts": {
      "action": "preview_jev_analytics_concept_route",
      "payload": {
        "decision": "Multiple concepts"
      },
      "pending": true
    },
    "No concept": {
      "action": "preview_jev_analytics_concept_route",
      "payload": {
        "decision": "No concept"
      },
      "pending": true
    },
    "Clarify": {
      "action": "preview_jev_analytics_concept_route",
      "payload": {
        "decision": "Clarify"
      },
      "pending": true
    }
  },
  "samples": [
    {
      "id": "case-1",
      "label": "Rear-wheel grouping",
      "expected": "Rear",
      "request": {
        "context": "{\n  \"task\": \"Select a supplied business concept whose fields cover an analytics question, while preserving requests spanning concepts or lacking a clear route.\",\n  \"evidence\": {\n    \"question\": \"Group vehicles by rear-wheel drive and report the widest rear tire in each group.\",\n    \"catalogScope\": \"Complete catalog for this original routing exercise; one row represents one fictional vehicle. Each concept also contains vehicle_id, the identifier for that row.\",\n    \"concepts\": {\n      \"Rear\": {\n        \"rear_wheel_drive\": \"Whether the rear wheels receive driving power.\",\n        \"rear_tire_width_mm\": \"Width of the rear tire in millimetres.\"\n      },\n      \"Offroad\": {\n        \"offroad_driving_percent\": \"Percentage of recorded driving done off-road.\",\n        \"offroad_environment\": \"Recorded off-road terrain category.\"\n      },\n      \"Electric\": {\n        \"fast_charging_support\": \"Whether the vehicle supports fast battery charging.\",\n        \"ac_charging_time_hours\": \"Recorded time for the specified AC battery-charging session, in hours.\"\n      }\n    }\n  }\n}",
        "question": "Use question meaning and the complete concept catalog. Clarify first if the request, field meanings or catalog coverage is missing or ambiguous, or several single concepts fully fit. Choose Rear, Offroad or Electric only if exactly one covers every required field. Use Multiple concepts if all fields are covered only by combining concepts. Use No concept if any required field is outside this catalog. Do not invent fields, joins or SQL, execute a query or claim a result.",
        "choices": [
          "Rear",
          "Offroad",
          "Electric",
          "Multiple concepts",
          "No concept",
          "Clarify"
        ]
      }
    },
    {
      "id": "case-2",
      "label": "Off-road use by terrain",
      "expected": "Offroad",
      "request": {
        "context": "{\n  \"task\": \"Select a supplied business concept whose fields cover an analytics question, while preserving requests spanning concepts or lacking a clear route.\",\n  \"evidence\": {\n    \"question\": \"For each recorded off-road terrain category, show the median percentage of driving done off-road.\",\n    \"catalogScope\": \"Complete catalog for this original routing exercise; one row represents one fictional vehicle. Each concept also contains vehicle_id, the identifier for that row.\",\n    \"concepts\": {\n      \"Rear\": {\n        \"rear_wheel_drive\": \"Whether the rear wheels receive driving power.\",\n        \"rear_tire_width_mm\": \"Width of the rear tire in millimetres.\"\n      },\n      \"Offroad\": {\n        \"offroad_driving_percent\": \"Percentage of recorded driving done off-road.\",\n        \"offroad_environment\": \"Recorded off-road terrain category.\"\n      },\n      \"Electric\": {\n        \"fast_charging_support\": \"Whether the vehicle supports fast battery charging.\",\n        \"ac_charging_time_hours\": \"Recorded time for the specified AC battery-charging session, in hours.\"\n      }\n    }\n  }\n}",
        "question": "Use question meaning and the complete concept catalog. Clarify first if the request, field meanings or catalog coverage is missing or ambiguous, or several single concepts fully fit. Choose Rear, Offroad or Electric only if exactly one covers every required field. Use Multiple concepts if all fields are covered only by combining concepts. Use No concept if any required field is outside this catalog. Do not invent fields, joins or SQL, execute a query or claim a result.",
        "choices": [
          "Rear",
          "Offroad",
          "Electric",
          "Multiple concepts",
          "No concept",
          "Clarify"
        ]
      }
    },
    {
      "id": "case-3",
      "label": "Battery-charging fields",
      "expected": "Electric",
      "request": {
        "context": "{\n  \"task\": \"Select a supplied business concept whose fields cover an analytics question, while preserving requests spanning concepts or lacking a clear route.\",\n  \"evidence\": {\n    \"question\": \"List vehicles that support fast battery charging and show their recorded AC charging-session time.\",\n    \"catalogScope\": \"Complete catalog for this original routing exercise; one row represents one fictional vehicle. Each concept also contains vehicle_id, the identifier for that row.\",\n    \"concepts\": {\n      \"Rear\": {\n        \"rear_wheel_drive\": \"Whether the rear wheels receive driving power.\",\n        \"rear_tire_width_mm\": \"Width of the rear tire in millimetres.\"\n      },\n      \"Offroad\": {\n        \"offroad_driving_percent\": \"Percentage of recorded driving done off-road.\",\n        \"offroad_environment\": \"Recorded off-road terrain category.\"\n      },\n      \"Electric\": {\n        \"fast_charging_support\": \"Whether the vehicle supports fast battery charging.\",\n        \"ac_charging_time_hours\": \"Recorded time for the specified AC battery-charging session, in hours.\"\n      }\n    }\n  }\n}",
        "question": "Use question meaning and the complete concept catalog. Clarify first if the request, field meanings or catalog coverage is missing or ambiguous, or several single concepts fully fit. Choose Rear, Offroad or Electric only if exactly one covers every required field. Use Multiple concepts if all fields are covered only by combining concepts. Use No concept if any required field is outside this catalog. Do not invent fields, joins or SQL, execute a query or claim a result.",
        "choices": [
          "Rear",
          "Offroad",
          "Electric",
          "Multiple concepts",
          "No concept",
          "Clarify"
        ]
      }
    },
    {
      "id": "case-4",
      "label": "Fields from two concepts",
      "expected": "Multiple concepts",
      "request": {
        "context": "{\n  \"task\": \"Select a supplied business concept whose fields cover an analytics question, while preserving requests spanning concepts or lacking a clear route.\",\n  \"evidence\": {\n    \"question\": \"List vehicles with rear-wheel drive that also support fast battery charging.\",\n    \"catalogScope\": \"Complete catalog for this original routing exercise; one row represents one fictional vehicle. Each concept also contains vehicle_id, the identifier for that row.\",\n    \"concepts\": {\n      \"Rear\": {\n        \"rear_wheel_drive\": \"Whether the rear wheels receive driving power.\",\n        \"rear_tire_width_mm\": \"Width of the rear tire in millimetres.\"\n      },\n      \"Offroad\": {\n        \"offroad_driving_percent\": \"Percentage of recorded driving done off-road.\",\n        \"offroad_environment\": \"Recorded off-road terrain category.\"\n      },\n      \"Electric\": {\n        \"fast_charging_support\": \"Whether the vehicle supports fast battery charging.\",\n        \"ac_charging_time_hours\": \"Recorded time for the specified AC battery-charging session, in hours.\"\n      }\n    }\n  }\n}",
        "question": "Use question meaning and the complete concept catalog. Clarify first if the request, field meanings or catalog coverage is missing or ambiguous, or several single concepts fully fit. Choose Rear, Offroad or Electric only if exactly one covers every required field. Use Multiple concepts if all fields are covered only by combining concepts. Use No concept if any required field is outside this catalog. Do not invent fields, joins or SQL, execute a query or claim a result.",
        "choices": [
          "Rear",
          "Offroad",
          "Electric",
          "Multiple concepts",
          "No concept",
          "Clarify"
        ]
      }
    },
    {
      "id": "case-5",
      "label": "A field outside the catalog",
      "expected": "No concept",
      "request": {
        "context": "{\n  \"task\": \"Select a supplied business concept whose fields cover an analytics question, while preserving requests spanning concepts or lacking a clear route.\",\n  \"evidence\": {\n    \"question\": \"List vehicles with a collision-test score above four.\",\n    \"catalogScope\": \"Complete catalog for this original routing exercise; one row represents one fictional vehicle. Each concept also contains vehicle_id, the identifier for that row. Collision-test score has its ordinary stated meaning, but it is not one of the fields in this catalog.\",\n    \"concepts\": {\n      \"Rear\": {\n        \"rear_wheel_drive\": \"Whether the rear wheels receive driving power.\",\n        \"rear_tire_width_mm\": \"Width of the rear tire in millimetres.\"\n      },\n      \"Offroad\": {\n        \"offroad_driving_percent\": \"Percentage of recorded driving done off-road.\",\n        \"offroad_environment\": \"Recorded off-road terrain category.\"\n      },\n      \"Electric\": {\n        \"fast_charging_support\": \"Whether the vehicle supports fast battery charging.\",\n        \"ac_charging_time_hours\": \"Recorded time for the specified AC battery-charging session, in hours.\"\n      }\n    }\n  }\n}",
        "question": "Use question meaning and the complete concept catalog. Clarify first if the request, field meanings or catalog coverage is missing or ambiguous, or several single concepts fully fit. Choose Rear, Offroad or Electric only if exactly one covers every required field. Use Multiple concepts if all fields are covered only by combining concepts. Use No concept if any required field is outside this catalog. Do not invent fields, joins or SQL, execute a query or claim a result.",
        "choices": [
          "Rear",
          "Offroad",
          "Electric",
          "Multiple concepts",
          "No concept",
          "Clarify"
        ]
      }
    },
    {
      "id": "case-6",
      "label": "An undefined comparison",
      "expected": "Clarify",
      "request": {
        "context": "{\n  \"task\": \"Select a supplied business concept whose fields cover an analytics question, while preserving requests spanning concepts or lacking a clear route.\",\n  \"evidence\": {\n    \"question\": \"Compare the vehicles with the best performance.\",\n    \"knownMeaning\": \"The requester has not defined performance: rear-wheel traction, off-road use and battery-charging characteristics are all possible intended subjects.\",\n    \"catalogScope\": \"Complete catalog for this original routing exercise; one row represents one fictional vehicle. Each concept also contains vehicle_id, the identifier for that row.\",\n    \"concepts\": {\n      \"Rear\": {\n        \"rear_wheel_drive\": \"Whether the rear wheels receive driving power.\",\n        \"rear_tire_width_mm\": \"Width of the rear tire in millimetres.\"\n      },\n      \"Offroad\": {\n        \"offroad_driving_percent\": \"Percentage of recorded driving done off-road.\",\n        \"offroad_environment\": \"Recorded off-road terrain category.\"\n      },\n      \"Electric\": {\n        \"fast_charging_support\": \"Whether the vehicle supports fast battery charging.\",\n        \"ac_charging_time_hours\": \"Recorded time for the specified AC battery-charging session, in hours.\"\n      }\n    }\n  }\n}",
        "question": "Use question meaning and the complete concept catalog. Clarify first if the request, field meanings or catalog coverage is missing or ambiguous, or several single concepts fully fit. Choose Rear, Offroad or Electric only if exactly one covers every required field. Use Multiple concepts if all fields are covered only by combining concepts. Use No concept if any required field is outside this catalog. Do not invent fields, joins or SQL, execute a query or claim a result.",
        "choices": [
          "Rear",
          "Offroad",
          "Electric",
          "Multiple concepts",
          "No concept",
          "Clarify"
        ]
      }
    }
  ],
  "consumer": "preview_choice_workflow.py"
}
