{
  "kind": "original-bounded-choice-workflow",
  "version": 1,
  "scope": "Interpret two query-workload briefs against three fictional configured engine scopes to decide common-route compatibility, separate routes, unsupported requirements or missing input. Print a pending note, not a selected model, SQL or database execution.",
  "question": "Review queryBriefs against configuredEngines. Co-route: both complete requirements fit at least one common supplied engine. Separate routes: each fits an engine but none fits both. Unsupported query: a clear requirement fits no engine. Need requirements: either brief lacks enough facts to decide; prioritize this over other labels. Interpret stated workloads only; do not invent engine capabilities, estimate speed, generate SQL or execute queries.",
  "choices": [
    "Co-route",
    "Separate routes",
    "Unsupported query",
    "Need requirements"
  ],
  "actions": {
    "Co-route": {
      "action": "preview_query_route_compatibility",
      "payload": {
        "decision": "Co-route"
      },
      "pending": true
    },
    "Separate routes": {
      "action": "preview_query_route_compatibility",
      "payload": {
        "decision": "Separate routes"
      },
      "pending": true
    },
    "Unsupported query": {
      "action": "preview_query_route_compatibility",
      "payload": {
        "decision": "Unsupported query"
      },
      "pending": true
    },
    "Need requirements": {
      "action": "preview_query_route_compatibility",
      "payload": {
        "decision": "Need requirements"
      },
      "pending": true
    }
  },
  "samples": [
    {
      "id": "shared-read",
      "label": "Two selective reads",
      "expected": "Co-route",
      "request": {
        "context": "{\n  \"task\": \"Compare the two query briefs for route compatibility. Treat the engine scopes as the complete local configuration.\",\n  \"configuredEngines\": [\n    {\n      \"id\": \"point-read\",\n      \"scope\": \"Selective single-table reads; no large multi-table aggregates, geospatial predicates or writes.\"\n    },\n    {\n      \"id\": \"warehouse\",\n      \"scope\": \"Large multi-table aggregates; no geospatial predicates or writes. Selective single-table lookup is outside this configured scope.\"\n    },\n    {\n      \"id\": \"geo-filter\",\n      \"scope\": \"Geospatial predicates on one table; no multi-table aggregates or writes. Non-geospatial lookup is outside this configured scope.\"\n    }\n  ],\n  \"queryBriefs\": [\n    \"Read the current plan for a single specified workspace from one table.\",\n    \"Look up one specified project by its identifier in one table.\"\n  ]\n}",
        "question": "Review queryBriefs against configuredEngines. Co-route: both complete requirements fit at least one common supplied engine. Separate routes: each fits an engine but none fits both. Unsupported query: a clear requirement fits no engine. Need requirements: either brief lacks enough facts to decide; prioritize this over other labels. Interpret stated workloads only; do not invent engine capabilities, estimate speed, generate SQL or execute queries.",
        "choices": [
          "Co-route",
          "Separate routes",
          "Unsupported query",
          "Need requirements"
        ]
      }
    },
    {
      "id": "split-workloads",
      "label": "A lookup and a warehouse aggregate",
      "expected": "Separate routes",
      "request": {
        "context": "{\n  \"task\": \"Compare the two query briefs for route compatibility. A shared table format does not create a shared engine scope.\",\n  \"configuredEngines\": [\n    {\n      \"id\": \"point-read\",\n      \"scope\": \"Selective single-table reads; no large multi-table aggregates, geospatial predicates or writes.\"\n    },\n    {\n      \"id\": \"warehouse\",\n      \"scope\": \"Large multi-table aggregates; no geospatial predicates or writes. Selective single-table lookup is outside this configured scope.\"\n    },\n    {\n      \"id\": \"geo-filter\",\n      \"scope\": \"Geospatial predicates on one table; no multi-table aggregates or writes. Non-geospatial lookup is outside this configured scope.\"\n    }\n  ],\n  \"queryBriefs\": [\n    \"Find one project by its identifier in one table.\",\n    \"Aggregate a large event table joined with users and accounts by reporting month.\"\n  ]\n}",
        "question": "Review queryBriefs against configuredEngines. Co-route: both complete requirements fit at least one common supplied engine. Separate routes: each fits an engine but none fits both. Unsupported query: a clear requirement fits no engine. Need requirements: either brief lacks enough facts to decide; prioritize this over other labels. Interpret stated workloads only; do not invent engine capabilities, estimate speed, generate SQL or execute queries.",
        "choices": [
          "Co-route",
          "Separate routes",
          "Unsupported query",
          "Need requirements"
        ]
      }
    },
    {
      "id": "shared-geo",
      "label": "Two geospatial filters",
      "expected": "Co-route",
      "request": {
        "context": "{\n  \"task\": \"Compare the two query briefs for route compatibility. Keep geospatial requirements explicit.\",\n  \"configuredEngines\": [\n    {\n      \"id\": \"point-read\",\n      \"scope\": \"Selective single-table reads; no large multi-table aggregates, geospatial predicates or writes.\"\n    },\n    {\n      \"id\": \"warehouse\",\n      \"scope\": \"Large multi-table aggregates; no geospatial predicates or writes. Selective single-table lookup is outside this configured scope.\"\n    },\n    {\n      \"id\": \"geo-filter\",\n      \"scope\": \"Geospatial predicates on one table; no multi-table aggregates or writes. Non-geospatial lookup is outside this configured scope.\"\n    }\n  ],\n  \"queryBriefs\": [\n    \"Find locations within a supplied polygon using a geospatial predicate on one table.\",\n    \"Filter points by their distance from a supplied coordinate on one table.\"\n  ]\n}",
        "question": "Review queryBriefs against configuredEngines. Co-route: both complete requirements fit at least one common supplied engine. Separate routes: each fits an engine but none fits both. Unsupported query: a clear requirement fits no engine. Need requirements: either brief lacks enough facts to decide; prioritize this over other labels. Interpret stated workloads only; do not invent engine capabilities, estimate speed, generate SQL or execute queries.",
        "choices": [
          "Co-route",
          "Separate routes",
          "Unsupported query",
          "Need requirements"
        ]
      }
    },
    {
      "id": "unsupported-write",
      "label": "One request modifies data",
      "expected": "Unsupported query",
      "request": {
        "context": "{\n  \"task\": \"Compare the two query briefs for route compatibility. A clear unsupported requirement must remain visible.\",\n  \"configuredEngines\": [\n    {\n      \"id\": \"point-read\",\n      \"scope\": \"Selective single-table reads; no large multi-table aggregates, geospatial predicates or writes.\"\n    },\n    {\n      \"id\": \"warehouse\",\n      \"scope\": \"Large multi-table aggregates; no geospatial predicates or writes. Selective single-table lookup is outside this configured scope.\"\n    },\n    {\n      \"id\": \"geo-filter\",\n      \"scope\": \"Geospatial predicates on one table; no multi-table aggregates or writes. Non-geospatial lookup is outside this configured scope.\"\n    }\n  ],\n  \"queryBriefs\": [\n    \"Read one project by its identifier from one table.\",\n    \"Update the project owner stored in a table.\"\n  ]\n}",
        "question": "Review queryBriefs against configuredEngines. Co-route: both complete requirements fit at least one common supplied engine. Separate routes: each fits an engine but none fits both. Unsupported query: a clear requirement fits no engine. Need requirements: either brief lacks enough facts to decide; prioritize this over other labels. Interpret stated workloads only; do not invent engine capabilities, estimate speed, generate SQL or execute queries.",
        "choices": [
          "Co-route",
          "Separate routes",
          "Unsupported query",
          "Need requirements"
        ]
      }
    },
    {
      "id": "missing-second",
      "label": "An unspecified second query",
      "expected": "Need requirements",
      "request": {
        "context": "{\n  \"task\": \"Compare the two query briefs for route compatibility. Do not infer an absent workload from its neighbor.\",\n  \"configuredEngines\": [\n    {\n      \"id\": \"point-read\",\n      \"scope\": \"Selective single-table reads; no large multi-table aggregates, geospatial predicates or writes.\"\n    },\n    {\n      \"id\": \"warehouse\",\n      \"scope\": \"Large multi-table aggregates; no geospatial predicates or writes. Selective single-table lookup is outside this configured scope.\"\n    },\n    {\n      \"id\": \"geo-filter\",\n      \"scope\": \"Geospatial predicates on one table; no multi-table aggregates or writes. Non-geospatial lookup is outside this configured scope.\"\n    }\n  ],\n  \"queryBriefs\": [\n    \"Find points within a polygon in one table.\",\n    \"Run the other query quickly; no operation or data requirements are specified.\"\n  ]\n}",
        "question": "Review queryBriefs against configuredEngines. Co-route: both complete requirements fit at least one common supplied engine. Separate routes: each fits an engine but none fits both. Unsupported query: a clear requirement fits no engine. Need requirements: either brief lacks enough facts to decide; prioritize this over other labels. Interpret stated workloads only; do not invent engine capabilities, estimate speed, generate SQL or execute queries.",
        "choices": [
          "Co-route",
          "Separate routes",
          "Unsupported query",
          "Need requirements"
        ]
      }
    },
    {
      "id": "missing-over-write",
      "label": "An unknown workload alongside a write",
      "expected": "Need requirements",
      "request": {
        "context": "{\n  \"task\": \"Compare the two query briefs for route compatibility. Apply the explicit missing-requirements priority.\",\n  \"configuredEngines\": [\n    {\n      \"id\": \"point-read\",\n      \"scope\": \"Selective single-table reads; no large multi-table aggregates, geospatial predicates or writes.\"\n    },\n    {\n      \"id\": \"warehouse\",\n      \"scope\": \"Large multi-table aggregates; no geospatial predicates or writes. Selective single-table lookup is outside this configured scope.\"\n    },\n    {\n      \"id\": \"geo-filter\",\n      \"scope\": \"Geospatial predicates on one table; no multi-table aggregates or writes. Non-geospatial lookup is outside this configured scope.\"\n    }\n  ],\n  \"queryBriefs\": [\n    \"Update the project plan stored in a table.\",\n    \"Process the second request; its workload requirements are not supplied.\"\n  ]\n}",
        "question": "Review queryBriefs against configuredEngines. Co-route: both complete requirements fit at least one common supplied engine. Separate routes: each fits an engine but none fits both. Unsupported query: a clear requirement fits no engine. Need requirements: either brief lacks enough facts to decide; prioritize this over other labels. Interpret stated workloads only; do not invent engine capabilities, estimate speed, generate SQL or execute queries.",
        "choices": [
          "Co-route",
          "Separate routes",
          "Unsupported query",
          "Need requirements"
        ]
      }
    }
  ],
  "consumer": "preview_choice_workflow_v2.py"
}
