{
  "kind": "original-bounded-choice-workflow",
  "version": 1,
  "scope": "Match a contact\u2019s explicitly supplied primary project duty to a technical, procurement or rollout conversation track, preserving observers and unresolved multiple roles without scoring readiness or inferring authority.",
  "question": "Read responsibilityStatement. Technical evaluation: explicitly owns integration or technical testing. Procurement review: explicitly owns purchasing or vendor terms. Operational rollout: explicitly owns training or daily deployment. No assigned role: explicitly owns none of these responsibilities. Need role statement: absent, conflicting or multiple roles with no primary one. Judge stated duties only, never infer authority from title, company size or identity. No qualification or outreach.",
  "choices": [
    "Technical evaluation",
    "Procurement review",
    "Operational rollout",
    "No assigned role",
    "Need role statement"
  ],
  "actions": {
    "Technical evaluation": {
      "action": "review_technical_evaluation_topic",
      "payload": {
        "reviewLabel": "Technical evaluation",
        "externalActionPerformed": false
      },
      "pending": true
    },
    "Procurement review": {
      "action": "review_procurement_topic",
      "payload": {
        "reviewLabel": "Procurement review",
        "externalActionPerformed": false
      },
      "pending": true
    },
    "Operational rollout": {
      "action": "review_rollout_topic",
      "payload": {
        "reviewLabel": "Operational rollout",
        "externalActionPerformed": false
      },
      "pending": true
    },
    "No assigned role": {
      "action": "retain_observer_context",
      "payload": {
        "reviewLabel": "No assigned role",
        "externalActionPerformed": false
      },
      "pending": true
    },
    "Need role statement": {
      "action": "request_primary_role",
      "payload": {
        "reviewLabel": "Need role statement",
        "externalActionPerformed": false
      },
      "pending": true
    }
  },
  "samples": [
    {
      "id": "1",
      "label": "The contact owns integration testing",
      "expected": "Technical evaluation",
      "request": {
        "context": "{\n  \"task\": \"Review the supplied evidence under the explicit rule, preserving any missing or unresolved facts.\",\n  \"responsibilityStatement\": \"My job in this project is to test the API integration. Another person handles purchasing and rollout.\"\n}",
        "question": "Read responsibilityStatement. Technical evaluation: explicitly owns integration or technical testing. Procurement review: explicitly owns purchasing or vendor terms. Operational rollout: explicitly owns training or daily deployment. No assigned role: explicitly owns none of these responsibilities. Need role statement: absent, conflicting or multiple roles with no primary one. Judge stated duties only, never infer authority from title, company size or identity. No qualification or outreach.",
        "choices": [
          "Technical evaluation",
          "Procurement review",
          "Operational rollout",
          "No assigned role",
          "Need role statement"
        ]
      }
    },
    {
      "id": "2",
      "label": "The contact owns vendor-term review",
      "expected": "Procurement review",
      "request": {
        "context": "{\n  \"task\": \"Review the supplied evidence under the explicit rule, preserving any missing or unresolved facts.\",\n  \"responsibilityStatement\": \"For this project I review vendor terms and purchasing paperwork. I do not perform technical testing or training.\"\n}",
        "question": "Read responsibilityStatement. Technical evaluation: explicitly owns integration or technical testing. Procurement review: explicitly owns purchasing or vendor terms. Operational rollout: explicitly owns training or daily deployment. No assigned role: explicitly owns none of these responsibilities. Need role statement: absent, conflicting or multiple roles with no primary one. Judge stated duties only, never infer authority from title, company size or identity. No qualification or outreach.",
        "choices": [
          "Technical evaluation",
          "Procurement review",
          "Operational rollout",
          "No assigned role",
          "Need role statement"
        ]
      }
    },
    {
      "id": "3",
      "label": "The contact owns staff rollout",
      "expected": "Operational rollout",
      "request": {
        "context": "{\n  \"task\": \"Review the supplied evidence under the explicit rule, preserving any missing or unresolved facts.\",\n  \"responsibilityStatement\": \"I train the daily users and manage rollout. Technical evaluation and purchasing are assigned to other people.\"\n}",
        "question": "Read responsibilityStatement. Technical evaluation: explicitly owns integration or technical testing. Procurement review: explicitly owns purchasing or vendor terms. Operational rollout: explicitly owns training or daily deployment. No assigned role: explicitly owns none of these responsibilities. Need role statement: absent, conflicting or multiple roles with no primary one. Judge stated duties only, never infer authority from title, company size or identity. No qualification or outreach.",
        "choices": [
          "Technical evaluation",
          "Procurement review",
          "Operational rollout",
          "No assigned role",
          "Need role statement"
        ]
      }
    },
    {
      "id": "4",
      "label": "An observer without an assigned role",
      "expected": "No assigned role",
      "request": {
        "context": "{\n  \"task\": \"Review the supplied evidence under the explicit rule, preserving any missing or unresolved facts.\",\n  \"responsibilityStatement\": \"I am observing the project for academic research. I own none of the integration, purchasing or rollout work.\"\n}",
        "question": "Read responsibilityStatement. Technical evaluation: explicitly owns integration or technical testing. Procurement review: explicitly owns purchasing or vendor terms. Operational rollout: explicitly owns training or daily deployment. No assigned role: explicitly owns none of these responsibilities. Need role statement: absent, conflicting or multiple roles with no primary one. Judge stated duties only, never infer authority from title, company size or identity. No qualification or outreach.",
        "choices": [
          "Technical evaluation",
          "Procurement review",
          "Operational rollout",
          "No assigned role",
          "Need role statement"
        ]
      }
    },
    {
      "id": "5",
      "label": "Multiple roles without a primary one",
      "expected": "Need role statement",
      "request": {
        "context": "{\n  \"task\": \"Review the supplied evidence under the explicit rule, preserving any missing or unresolved facts.\",\n  \"responsibilityStatement\": \"I lead engineering and procurement. No primary responsibility for this conversation has been stated.\"\n}",
        "question": "Read responsibilityStatement. Technical evaluation: explicitly owns integration or technical testing. Procurement review: explicitly owns purchasing or vendor terms. Operational rollout: explicitly owns training or daily deployment. No assigned role: explicitly owns none of these responsibilities. Need role statement: absent, conflicting or multiple roles with no primary one. Judge stated duties only, never infer authority from title, company size or identity. No qualification or outreach.",
        "choices": [
          "Technical evaluation",
          "Procurement review",
          "Operational rollout",
          "No assigned role",
          "Need role statement"
        ]
      }
    },
    {
      "id": "6",
      "label": "Technical evaluation stated another way",
      "expected": "Technical evaluation",
      "request": {
        "context": "{\n  \"task\": \"Review the supplied evidence under the explicit rule, preserving any missing or unresolved facts.\",\n  \"responsibilityStatement\": \"I evaluate whether our code can consume the API response. Purchasing and staff onboarding are outside my assigned work.\"\n}",
        "question": "Read responsibilityStatement. Technical evaluation: explicitly owns integration or technical testing. Procurement review: explicitly owns purchasing or vendor terms. Operational rollout: explicitly owns training or daily deployment. No assigned role: explicitly owns none of these responsibilities. Need role statement: absent, conflicting or multiple roles with no primary one. Judge stated duties only, never infer authority from title, company size or identity. No qualification or outreach.",
        "choices": [
          "Technical evaluation",
          "Procurement review",
          "Operational rollout",
          "No assigned role",
          "Need role statement"
        ]
      }
    }
  ],
  "consumer": "preview_choice_workflow_v2.py"
}
