{
  "kind": "original-bounded-choice-workflow",
  "version": 1,
  "scope": "Classify database-session ownership across overlapping tasks using explicit creation, sharing and serialization facts.",
  "question": "Review session ownership under the supplied client contract. Shared session means overlapping tasks use the same mutable session that is not safe for concurrent use. Separate sessions means each task creates its own session. Serialized means the same session is reused with explicit nonoverlap covering all its operations. Review takes precedence if identity, overlap, locking scope or client semantics are unknown/conflicting. Do not infer safety from separate variable names.",
  "choices": [
    "Shared session",
    "Separate sessions",
    "Serialized",
    "Review"
  ],
  "actions": {
    "Shared session": {
      "action": "preview_jev_concurrent_session_ownership",
      "payload": {
        "decision": "Shared session"
      },
      "pending": true
    },
    "Separate sessions": {
      "action": "preview_jev_concurrent_session_ownership",
      "payload": {
        "decision": "Separate sessions"
      },
      "pending": true
    },
    "Serialized": {
      "action": "preview_jev_concurrent_session_ownership",
      "payload": {
        "decision": "Serialized"
      },
      "pending": true
    },
    "Review": {
      "action": "preview_jev_concurrent_session_ownership",
      "payload": {
        "decision": "Review"
      },
      "pending": true
    }
  },
  "samples": [
    {
      "id": "case-1",
      "label": "Shared instance in gather",
      "expected": "Shared session",
      "request": {
        "context": "{\n  \"task\": \"Classify database-session ownership across overlapping tasks using explicit creation, sharing and serialization facts.\",\n  \"evidence\": {\n    \"creation\": \"One mutable session created before two tasks.\",\n    \"use\": \"Both overlapping tasks receive that exact instance.\",\n    \"contract\": \"This session is not safe for concurrent task use.\"\n  }\n}",
        "question": "Review session ownership under the supplied client contract. Shared session means overlapping tasks use the same mutable session that is not safe for concurrent use. Separate sessions means each task creates its own session. Serialized means the same session is reused with explicit nonoverlap covering all its operations. Review takes precedence if identity, overlap, locking scope or client semantics are unknown/conflicting. Do not infer safety from separate variable names.",
        "choices": [
          "Shared session",
          "Separate sessions",
          "Serialized",
          "Review"
        ]
      }
    },
    {
      "id": "case-2",
      "label": "Session created per task",
      "expected": "Separate sessions",
      "request": {
        "context": "{\n  \"task\": \"Classify database-session ownership across overlapping tasks using explicit creation, sharing and serialization facts.\",\n  \"evidence\": {\n    \"creation\": \"Each task enters its own session factory context.\",\n    \"use\": \"Concurrent tasks receive distinct session instances.\",\n    \"contract\": \"Each session belongs only to its creating task.\"\n  }\n}",
        "question": "Review session ownership under the supplied client contract. Shared session means overlapping tasks use the same mutable session that is not safe for concurrent use. Separate sessions means each task creates its own session. Serialized means the same session is reused with explicit nonoverlap covering all its operations. Review takes precedence if identity, overlap, locking scope or client semantics are unknown/conflicting. Do not infer safety from separate variable names.",
        "choices": [
          "Shared session",
          "Separate sessions",
          "Serialized",
          "Review"
        ]
      }
    },
    {
      "id": "case-3",
      "label": "Sequential reuse",
      "expected": "Serialized",
      "request": {
        "context": "{\n  \"task\": \"Classify database-session ownership across overlapping tasks using explicit creation, sharing and serialization facts.\",\n  \"evidence\": {\n    \"creation\": \"One session.\",\n    \"use\": \"Task A completes all session work before task B begins; no other users exist.\",\n    \"contract\": \"Sequential reuse is supported.\"\n  }\n}",
        "question": "Review session ownership under the supplied client contract. Shared session means overlapping tasks use the same mutable session that is not safe for concurrent use. Separate sessions means each task creates its own session. Serialized means the same session is reused with explicit nonoverlap covering all its operations. Review takes precedence if identity, overlap, locking scope or client semantics are unknown/conflicting. Do not infer safety from separate variable names.",
        "choices": [
          "Shared session",
          "Separate sessions",
          "Serialized",
          "Review"
        ]
      }
    },
    {
      "id": "case-4",
      "label": "Whole-operation lock",
      "expected": "Serialized",
      "request": {
        "context": "{\n  \"task\": \"Classify database-session ownership across overlapping tasks using explicit creation, sharing and serialization facts.\",\n  \"evidence\": {\n    \"creation\": \"One session.\",\n    \"use\": \"A single shared lock covers every use through transaction completion; all users follow it.\",\n    \"contract\": \"The client supports serialized reuse.\"\n  }\n}",
        "question": "Review session ownership under the supplied client contract. Shared session means overlapping tasks use the same mutable session that is not safe for concurrent use. Separate sessions means each task creates its own session. Serialized means the same session is reused with explicit nonoverlap covering all its operations. Review takes precedence if identity, overlap, locking scope or client semantics are unknown/conflicting. Do not infer safety from separate variable names.",
        "choices": [
          "Shared session",
          "Separate sessions",
          "Serialized",
          "Review"
        ]
      }
    },
    {
      "id": "case-5",
      "label": "Different variable names",
      "expected": "Review",
      "request": {
        "context": "{\n  \"task\": \"Classify database-session ownership across overlapping tasks using explicit creation, sharing and serialization facts.\",\n  \"evidence\": {\n    \"creation\": \"s1 and s2 are passed to tasks, but their identity is not supplied.\",\n    \"use\": \"Tasks overlap.\",\n    \"contract\": \"Concurrent use of one instance is unsupported.\"\n  }\n}",
        "question": "Review session ownership under the supplied client contract. Shared session means overlapping tasks use the same mutable session that is not safe for concurrent use. Separate sessions means each task creates its own session. Serialized means the same session is reused with explicit nonoverlap covering all its operations. Review takes precedence if identity, overlap, locking scope or client semantics are unknown/conflicting. Do not infer safety from separate variable names.",
        "choices": [
          "Shared session",
          "Separate sessions",
          "Serialized",
          "Review"
        ]
      }
    },
    {
      "id": "case-6",
      "label": "Partial lock",
      "expected": "Shared session",
      "request": {
        "context": "{\n  \"task\": \"Classify database-session ownership across overlapping tasks using explicit creation, sharing and serialization facts.\",\n  \"evidence\": {\n    \"creation\": \"One shared session.\",\n    \"use\": \"Tasks overlap; only construction is locked, while their session operations run concurrently.\",\n    \"contract\": \"The session does not support concurrent use.\"\n  }\n}",
        "question": "Review session ownership under the supplied client contract. Shared session means overlapping tasks use the same mutable session that is not safe for concurrent use. Separate sessions means each task creates its own session. Serialized means the same session is reused with explicit nonoverlap covering all its operations. Review takes precedence if identity, overlap, locking scope or client semantics are unknown/conflicting. Do not infer safety from separate variable names.",
        "choices": [
          "Shared session",
          "Separate sessions",
          "Serialized",
          "Review"
        ]
      }
    }
  ],
  "consumer": "preview_choice_workflow.py"
}
