{
  "kind": "original-bounded-choice-workflow",
  "version": 1,
  "scope": "Review whether two supplied latency measurement descriptions use the same stated request workload and timing boundary. Identify comparable stated protocols, a mismatched boundary or incomplete protocol evidence. No speed ratio, provider benchmark or measured timing is computed.",
  "question": "Do the two described measurements have a comparable stated protocol? Comparable stated protocol: same explicitly stated request workload and timing start/end boundary. Mismatched protocol: explicit workload or timing-boundary difference, including API round trip versus local forward pass. Incomplete protocol: either workload or timing boundary is absent or contradictory. Judge descriptions only; do not verify hardware, infer omitted conditions, compute speed ratios or claim equal accuracy.",
  "choices": [
    "Comparable stated protocol",
    "Mismatched protocol",
    "Incomplete protocol"
  ],
  "actions": {
    "Comparable stated protocol": {
      "action": "preview_protocol_alignment",
      "payload": {
        "protocol": "comparable-stated",
        "measurementsVerified": false
      },
      "pending": false
    },
    "Mismatched protocol": {
      "action": "flag_protocol_difference",
      "payload": {
        "protocol": "mismatched",
        "speedRatio": null
      },
      "pending": true
    },
    "Incomplete protocol": {
      "action": "request_measurement_details",
      "payload": null,
      "pending": true
    }
  },
  "samples": [
    {
      "id": "same",
      "label": "Same stated workload and boundaries",
      "expected": "Comparable stated protocol",
      "request": {
        "context": "{\n  \"task\": \"Measurement A: fixed request set Q; clock starts before HTTP request and ends after full HTTP response. Measurement B: same fixed set Q; identical before-request through full-response boundary.\"\n}",
        "question": "Do the two described measurements have a comparable stated protocol? Comparable stated protocol: same explicitly stated request workload and timing start/end boundary. Mismatched protocol: explicit workload or timing-boundary difference, including API round trip versus local forward pass. Incomplete protocol: either workload or timing boundary is absent or contradictory. Judge descriptions only; do not verify hardware, infer omitted conditions, compute speed ratios or claim equal accuracy.",
        "choices": [
          "Comparable stated protocol",
          "Mismatched protocol",
          "Incomplete protocol"
        ]
      }
    },
    {
      "id": "local",
      "label": "Hosted round trip versus local compute",
      "expected": "Mismatched protocol",
      "request": {
        "context": "{\n  \"task\": \"Measurement A: fixed set Q, HTTP request start through full response. Measurement B: same set Q, local model forward-pass start through finish only, excluding HTTP and preprocessing.\"\n}",
        "question": "Do the two described measurements have a comparable stated protocol? Comparable stated protocol: same explicitly stated request workload and timing start/end boundary. Mismatched protocol: explicit workload or timing-boundary difference, including API round trip versus local forward pass. Incomplete protocol: either workload or timing boundary is absent or contradictory. Judge descriptions only; do not verify hardware, infer omitted conditions, compute speed ratios or claim equal accuracy.",
        "choices": [
          "Comparable stated protocol",
          "Mismatched protocol",
          "Incomplete protocol"
        ]
      }
    },
    {
      "id": "missing",
      "label": "Numbers without protocol",
      "expected": "Incomplete protocol",
      "request": {
        "context": "{\n  \"task\": \"Measurement A: latency number only. Measurement B: latency number only. Neither states its workload or timing boundaries.\"\n}",
        "question": "Do the two described measurements have a comparable stated protocol? Comparable stated protocol: same explicitly stated request workload and timing start/end boundary. Mismatched protocol: explicit workload or timing-boundary difference, including API round trip versus local forward pass. Incomplete protocol: either workload or timing boundary is absent or contradictory. Judge descriptions only; do not verify hardware, infer omitted conditions, compute speed ratios or claim equal accuracy.",
        "choices": [
          "Comparable stated protocol",
          "Mismatched protocol",
          "Incomplete protocol"
        ]
      }
    },
    {
      "id": "workload",
      "label": "Different request workloads",
      "expected": "Mismatched protocol",
      "request": {
        "context": "{\n  \"task\": \"Measurement A: explicitly fixed request set Q with full HTTP round-trip timing. Measurement B: explicitly different request set R with the same clock boundary.\"\n}",
        "question": "Do the two described measurements have a comparable stated protocol? Comparable stated protocol: same explicitly stated request workload and timing start/end boundary. Mismatched protocol: explicit workload or timing-boundary difference, including API round trip versus local forward pass. Incomplete protocol: either workload or timing boundary is absent or contradictory. Judge descriptions only; do not verify hardware, infer omitted conditions, compute speed ratios or claim equal accuracy.",
        "choices": [
          "Comparable stated protocol",
          "Mismatched protocol",
          "Incomplete protocol"
        ]
      }
    },
    {
      "id": "preprocess",
      "label": "Different included preprocessing",
      "expected": "Mismatched protocol",
      "request": {
        "context": "{\n  \"task\": \"Measurement A: fixed set Q; begins before request preprocessing and ends after response validation. Measurement B: same set Q; begins after preprocessing and ends before response validation.\"\n}",
        "question": "Do the two described measurements have a comparable stated protocol? Comparable stated protocol: same explicitly stated request workload and timing start/end boundary. Mismatched protocol: explicit workload or timing-boundary difference, including API round trip versus local forward pass. Incomplete protocol: either workload or timing boundary is absent or contradictory. Judge descriptions only; do not verify hardware, infer omitted conditions, compute speed ratios or claim equal accuracy.",
        "choices": [
          "Comparable stated protocol",
          "Mismatched protocol",
          "Incomplete protocol"
        ]
      }
    },
    {
      "id": "compute",
      "label": "Both measure the same compute boundary",
      "expected": "Comparable stated protocol",
      "request": {
        "context": "{\n  \"task\": \"Measurement A: fixed set Q; local model forward-pass start to finish only. Measurement B: same fixed set Q and same forward-pass start/finish boundary. Other conditions not verified.\"\n}",
        "question": "Do the two described measurements have a comparable stated protocol? Comparable stated protocol: same explicitly stated request workload and timing start/end boundary. Mismatched protocol: explicit workload or timing-boundary difference, including API round trip versus local forward pass. Incomplete protocol: either workload or timing boundary is absent or contradictory. Judge descriptions only; do not verify hardware, infer omitted conditions, compute speed ratios or claim equal accuracy.",
        "choices": [
          "Comparable stated protocol",
          "Mismatched protocol",
          "Incomplete protocol"
        ]
      }
    }
  ],
  "consumer": "preview_choice_workflow_v2.py"
}
