{
  "example_kind": "original synthetic manual planning case",
  "slug": "experiment-task-unit-definition",
  "title": "Define the unit assigned in a work experiment",
  "scenario": "Synthetic planning case: A pilot assigns each of four teams to one work protocol. Each team then completes three task rehearsals. A recap calls the twelve task records twelve independently assigned experimental units.",
  "layout": "protocol",
  "dataset": {
    "heading": "Inspect the invented case records",
    "headers": [
      "Team",
      "Assigned protocol",
      "Task observations",
      "Assignment unit"
    ],
    "rows": [
      [
        "T1",
        "A",
        "3",
        "Team"
      ],
      [
        "T2",
        "A",
        "3",
        "Team"
      ],
      [
        "T3",
        "B",
        "3",
        "Team"
      ],
      [
        "T4",
        "B",
        "3",
        "Team"
      ]
    ]
  },
  "derivation": "Four teams×three observations=12 records, but assignment occurred four times at team level. Within-team observations may share people and conditions.",
  "result": "There are four assigned team units and twelve task observations in this design. Preserve their grouping; task count does not establish twelve independent assignments.",
  "boundary": "The guide distinguishes the assignment unit from the number of observed task records.",
  "limitations": "This synthetic design supplies no statistical model or independent-sample guarantee.",
  "sources": [
    "nist"
  ],
  "tasks": [
    [
      "Record the actual assignment unit",
      "Pilot owner",
      "The protocol was allocated to teams, not independently to each task."
    ],
    [
      "Preserve grouped observations",
      "Recorder",
      "Each task remains linked to its team exposure."
    ],
    [
      "Review analysis assumptions",
      "Method lead",
      "Any independence or effective-sample claim is justified separately; twelve rows alone are not twelve assignments."
    ]
  ],
  "faqs": [
    [
      "Can all twelve observations still be retained?",
      "Yes. Grouping and appropriate interpretation are the issue, not deleting useful records."
    ],
    [
      "Does team assignment prove randomness?",
      "No. The actual assignment method also needs documentation."
    ]
  ],
  "method_references": [
    {
      "id": "nist",
      "title": "NIST combinatorial testing",
      "url": "https://www.nist.gov/publications/combinatorial-testing",
      "scope": "Combination-coverage context. Invented review/state examples do not prove full fault coverage, certification or product behavior."
    }
  ]
}