{
  "example_kind": "original synthetic manual planning case",
  "slug": "queue-starvation-rotation-log",
  "title": "Inspect starvation in a queue rotation",
  "scenario": "Synthetic planning case: A declared rotation should give one review slot to class B in each two-slot cycle. The actual log of eight slots is A,A,A,A,A,A,A,A.",
  "layout": "protocol",
  "dataset": {
    "heading": "Inspect the invented case records",
    "headers": [
      "Two-slot cycle",
      "Actual service",
      "Declared B opportunity",
      "Observed B service"
    ],
    "rows": [
      [
        "1",
        "A,A",
        "1",
        "0"
      ],
      [
        "2",
        "A,A",
        "1",
        "0"
      ],
      [
        "3",
        "A,A",
        "1",
        "0"
      ],
      [
        "4",
        "A,A",
        "1",
        "0"
      ]
    ]
  },
  "derivation": "Four cycles×one declared B slot=4 opportunities; actual B service=0. Total service of eight says nothing about compliance with the work-class rotation.",
  "result": "Class B received zero of its four declared cycle opportunities. Inspect the repeated exception and restore an agreed service rule rather than calling eight completed A reviews proof that the rotation worked.",
  "boundary": "The artifact tests compliance with a declared recurring class-allocation rule, not simply age-based queue priority.",
  "limitations": "The log does not record eligibility or exception reasons. Retain that gap rather than attributing motives or guaranteeing fairness.",
  "sources": [
    "kanban"
  ],
  "tasks": [
    [
      "Check the governing rotation",
      "Queue owner",
      "One B slot per two-slot cycle is a real accepted policy for this example."
    ],
    [
      "Inspect exceptions by cycle",
      "Coordinator",
      "All four omitted B opportunities remain visible with their actual cause unresolved."
    ],
    [
      "Choose the service correction",
      "Decision owner",
      "The rotation or its authorized exceptions are explicitly changed and the next cycles are checked."
    ]
  ],
  "faqs": [
    [
      "Does zero B service prove deliberate neglect?",
      "No. Missing eligible B work or another accepted exception may explain it; inspect the actual conditions."
    ],
    [
      "Can eight completed items prove fairness?",
      "No. Fairness and required class coverage are different from total throughput."
    ]
  ],
  "method_references": [
    {
      "id": "kanban",
      "title": "The Kanban Guide",
      "url": "https://kanbanguides.org/the-kanban-guide/",
      "scope": "Workflow and flow-measure context. Queue policies and staffing scenarios are explicitly local examples, not delivery guarantees."
    }
  ]
}