{
  "kind": "original-bounded-choice-workflow",
  "version": 1,
  "scope": "Inspect whether an older input-driven response can replace the visible result for newer input.",
  "question": "Inspect overlap and result ownership. Need commit path: relevant facts are missing or conflicting. Otherwise first choose Not overlapping if concurrent requests are prevented, then Separate results if each response stays in its own displayed input-keyed view. For overlapping writes to one current view: Guard shown if an effective key, sequence or cancellation check prevents stale commits; Stale write possible if it does not. Debounce alone is not protection.",
  "choices": [
    "Guard shown",
    "Stale write possible",
    "Separate results",
    "Not overlapping",
    "Need commit path"
  ],
  "actions": {
    "Guard shown": {
      "action": "preview_jev_input_response_order",
      "payload": {
        "decision": "Guard shown"
      },
      "pending": true
    },
    "Stale write possible": {
      "action": "preview_jev_input_response_order",
      "payload": {
        "decision": "Stale write possible"
      },
      "pending": true
    },
    "Separate results": {
      "action": "preview_jev_input_response_order",
      "payload": {
        "decision": "Separate results"
      },
      "pending": true
    },
    "Not overlapping": {
      "action": "preview_jev_input_response_order",
      "payload": {
        "decision": "Not overlapping"
      },
      "pending": true
    },
    "Need commit path": {
      "action": "preview_jev_input_response_order",
      "payload": {
        "decision": "Need commit path"
      },
      "pending": true
    }
  },
  "samples": [
    {
      "id": "case-1",
      "label": "Unconditional result write",
      "expected": "Stale write possible",
      "request": {
        "context": "{\n  \"task\": \"Inspect whether an older input-driven response can replace the visible result for newer input.\",\n  \"evidence\": {\n    \"flow\": \"Typing a then ab starts two concurrent searches. Every resolved request writes its result into the same visible result state.\",\n    \"guard\": \"None; the complete commit path is supplied.\"\n  }\n}",
        "question": "Inspect overlap and result ownership. Need commit path: relevant facts are missing or conflicting. Otherwise first choose Not overlapping if concurrent requests are prevented, then Separate results if each response stays in its own displayed input-keyed view. For overlapping writes to one current view: Guard shown if an effective key, sequence or cancellation check prevents stale commits; Stale write possible if it does not. Debounce alone is not protection.",
        "choices": [
          "Guard shown",
          "Stale write possible",
          "Separate results",
          "Not overlapping",
          "Need commit path"
        ]
      }
    },
    {
      "id": "case-2",
      "label": "Sequence check",
      "expected": "Guard shown",
      "request": {
        "context": "{\n  \"task\": \"Inspect whether an older input-driven response can replace the visible result for newer input.\",\n  \"evidence\": {\n    \"flow\": \"Each search increments currentSequence and captures mine. A response writes the shared view only when mine equals currentSequence.\",\n    \"guard\": \"The equality check is applied immediately before every result commit.\"\n  }\n}",
        "question": "Inspect overlap and result ownership. Need commit path: relevant facts are missing or conflicting. Otherwise first choose Not overlapping if concurrent requests are prevented, then Separate results if each response stays in its own displayed input-keyed view. For overlapping writes to one current view: Guard shown if an effective key, sequence or cancellation check prevents stale commits; Stale write possible if it does not. Debounce alone is not protection.",
        "choices": [
          "Guard shown",
          "Stale write possible",
          "Separate results",
          "Not overlapping",
          "Need commit path"
        ]
      }
    },
    {
      "id": "case-3",
      "label": "Keyed history",
      "expected": "Separate results",
      "request": {
        "context": "{\n  \"task\": \"Inspect whether an older input-driven response can replace the visible result for newer input.\",\n  \"evidence\": {\n    \"flow\": \"Requests for a and ab may overlap, but their responses update separate history cards labeled with their respective input keys.\",\n    \"guard\": \"No card is relabeled or reused for another input.\"\n  }\n}",
        "question": "Inspect overlap and result ownership. Need commit path: relevant facts are missing or conflicting. Otherwise first choose Not overlapping if concurrent requests are prevented, then Separate results if each response stays in its own displayed input-keyed view. For overlapping writes to one current view: Guard shown if an effective key, sequence or cancellation check prevents stale commits; Stale write possible if it does not. Debounce alone is not protection.",
        "choices": [
          "Guard shown",
          "Stale write possible",
          "Separate results",
          "Not overlapping",
          "Need commit path"
        ]
      }
    },
    {
      "id": "case-4",
      "label": "Serialized search",
      "expected": "Not overlapping",
      "request": {
        "context": "{\n  \"task\": \"Inspect whether an older input-driven response can replace the visible result for newer input.\",\n  \"evidence\": {\n    \"flow\": \"The supplied implementation blocks another search until the active search finishes, and queues later input for a subsequent request.\",\n    \"guard\": \"At most one request runs at any time; result commits complete before the next starts.\"\n  }\n}",
        "question": "Inspect overlap and result ownership. Need commit path: relevant facts are missing or conflicting. Otherwise first choose Not overlapping if concurrent requests are prevented, then Separate results if each response stays in its own displayed input-keyed view. For overlapping writes to one current view: Guard shown if an effective key, sequence or cancellation check prevents stale commits; Stale write possible if it does not. Debounce alone is not protection.",
        "choices": [
          "Guard shown",
          "Stale write possible",
          "Separate results",
          "Not overlapping",
          "Need commit path"
        ]
      }
    },
    {
      "id": "case-5",
      "label": "Debounced but overlapping",
      "expected": "Stale write possible",
      "request": {
        "context": "{\n  \"task\": \"Inspect whether an older input-driven response can replace the visible result for newer input.\",\n  \"evidence\": {\n    \"flow\": \"A debounce delays starting each request. Once a request starts, later input can start another before it finishes. All responses unconditionally replace the same visible state.\",\n    \"guard\": \"No abort, sequence or current-key commit check.\"\n  }\n}",
        "question": "Inspect overlap and result ownership. Need commit path: relevant facts are missing or conflicting. Otherwise first choose Not overlapping if concurrent requests are prevented, then Separate results if each response stays in its own displayed input-keyed view. For overlapping writes to one current view: Guard shown if an effective key, sequence or cancellation check prevents stale commits; Stale write possible if it does not. Debounce alone is not protection.",
        "choices": [
          "Guard shown",
          "Stale write possible",
          "Separate results",
          "Not overlapping",
          "Need commit path"
        ]
      }
    },
    {
      "id": "case-6",
      "label": "Fetch only",
      "expected": "Need commit path",
      "request": {
        "context": "{\n  \"task\": \"Inspect whether an older input-driven response can replace the visible result for newer input.\",\n  \"evidence\": {\n    \"flow\": \"const result = await fetch(url);\",\n    \"guard\": null,\n    \"ownership\": null\n  }\n}",
        "question": "Inspect overlap and result ownership. Need commit path: relevant facts are missing or conflicting. Otherwise first choose Not overlapping if concurrent requests are prevented, then Separate results if each response stays in its own displayed input-keyed view. For overlapping writes to one current view: Guard shown if an effective key, sequence or cancellation check prevents stale commits; Stale write possible if it does not. Debounce alone is not protection.",
        "choices": [
          "Guard shown",
          "Stale write possible",
          "Separate results",
          "Not overlapping",
          "Need commit path"
        ]
      }
    }
  ],
  "consumer": "preview_choice_workflow.py"
}
