{
  "example_kind": "original synthetic manual planning case",
  "slug": "queue-stock-flow-reconciliation",
  "title": "Reconcile a work queue's stock and flows",
  "scenario": "Synthetic planning case: A review queue starts with ten distinct requests. Six arrive, five exit by accepted review and two transfer to another queue during the same bounded period.",
  "layout": "allocation",
  "dataset": {
    "heading": "Inspect the invented case records",
    "headers": [
      "Ledger line",
      "Requests",
      "Meaning"
    ],
    "rows": [
      [
        "Opening stock",
        "10",
        "Same queue and unit"
      ],
      [
        "Arrivals",
        "6",
        "New requests into queue"
      ],
      [
        "Accepted exits",
        "5",
        "Review outcome evidenced"
      ],
      [
        "Transfers out",
        "2",
        "Move to another queue"
      ],
      [
        "Closing stock",
        "9",
        "Reconciled expected count"
      ]
    ]
  },
  "derivation": "Closing=10+6−5−2=9. A closing count of eleven would omit transfers; treating all seven departures as accepted would overstate outcomes.",
  "result": "The expected closing queue is nine requests. Keep the two transfers separate from accepted exits; they reduce this queue without establishing delivered outcomes.",
  "boundary": "The artifact reconciles queue movements rather than simply counting work in progress.",
  "limitations": "The example assumes complete movement evidence and matching snapshots. A mathematical balance does not prove every event was correctly classified.",
  "sources": [
    "kanban"
  ],
  "tasks": [
    [
      "Freeze queue and unit definitions",
      "Queue owner",
      "Both snapshots count distinct review requests under one scope."
    ],
    [
      "Reconcile each movement",
      "Reporting reviewer",
      "Arrivals, accepted exits and transfers have separate evidence."
    ],
    [
      "Investigate a remaining mismatch",
      "Coordinator",
      "Any actual closing count different from nine receives a record-level reconciliation."
    ]
  ],
  "faqs": [
    [
      "Are transfers completed work?",
      "Not from this ledger. They are departures from this queue; acceptance is a different event."
    ],
    [
      "Can cancellations be ignored?",
      "No. If present, they need their own stated flow line and reason."
    ]
  ],
  "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."
    }
  ]
}