{
  "example_kind": "original synthetic manual planning case",
  "slug": "queue-snapshot-cohort-mismatch",
  "title": "Compare queues only when their membership aligns",
  "scenario": "Synthetic planning case: An opening worksheet includes projects P and Q: A/P,B/P,C/Q,D/Q. The closing worksheet changes to P only: A/P,B/P,E/P. E is a newly arrived P request; the later state of Q is not observed.",
  "layout": "evaluation",
  "dataset": {
    "heading": "Inspect the invented case records",
    "headers": [
      "View or bridge",
      "Included IDs",
      "Count",
      "Meaning"
    ],
    "rows": [
      [
        "Opening P+Q",
        "A,B,C,D",
        "4",
        "Old scope"
      ],
      [
        "Opening aligned to P",
        "A,B",
        "2",
        "Comparable opening"
      ],
      [
        "Excluded opening Q",
        "C,D",
        "2",
        "Outside new scope"
      ],
      [
        "Closing P",
        "A,B,E",
        "3",
        "New P arrival E"
      ]
    ]
  },
  "derivation": "The old opening total 4 comprises 2 P plus 2 Q. Aligned P change=3−2=+1, while raw view change=3−4=−1. Later Q outcomes remain unknown, not silently completed or deleted.",
  "result": "The raw view falls from four to three, but the aligned P cohort grows from two to three. Two excluded Q records explain the scope bridge; no accepted exit follows from the unmatched totals.",
  "boundary": "This bridges changed queue-view scope before comparing snapshots, rather than balancing transfers inside one unchanged queue.",
  "limitations": "The example assumes known P membership and E arrival. A changed view is not evidence of global service or record deletion.",
  "sources": [
    "kanban"
  ],
  "tasks": [
    [
      "Recover both view definitions",
      "Reporting owner",
      "The first worksheet covers P+Q and the second only P."
    ],
    [
      "Build the scope bridge",
      "Queue reviewer",
      "The comparable opening P set has two requests; two Q IDs are excluded."
    ],
    [
      "Interpret the aligned change",
      "Coordinator",
      "P grows by one arrival; the whole P+Q closing state is still unknown."
    ]
  ],
  "faqs": [
    [
      "Did one request get reviewed because four became three?",
      "No. The views use different scopes; the aligned P records show one arrival instead."
    ],
    [
      "Can Q records be called gone at the closing date?",
      "No. Their later state was not observed in the P-only worksheet."
    ]
  ],
  "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."
    }
  ]
}