{
  "example_kind": "original synthetic manual planning case",
  "slug": "flow-ratio-assumption-check",
  "title": "Check assumptions before using a flow ratio",
  "scenario": "Synthetic planning case: A single checkpoint shows six started, unfinished items. A different lookback reports three finished items per day. A draft divides six by three and promises every current item will finish in two days.",
  "layout": "evaluation",
  "dataset": {
    "heading": "Inspect the invented case records",
    "headers": [
      "Input",
      "Supplied value",
      "Evidence limitation"
    ],
    "rows": [
      [
        "Checkpoint stock",
        "6 items",
        "One snapshot, not a period average"
      ],
      [
        "Lookback throughput",
        "3 items/day",
        "Different observation window"
      ],
      [
        "Arithmetic quotient",
        "2 days",
        "Not observed individual duration"
      ]
    ]
  },
  "derivation": "6 items÷3 items/day=2 days dimensionally. Matching units alone cannot turn a single stock snapshot and another-period rate into a per-item deadline.",
  "result": "The quotient has a two-day unit under the supplied numbers, but it does not establish an individual completion time. Review scope, comparable averaging windows and flow conditions before any stronger interpretation.",
  "boundary": "The artifact audits the inference behind a stock/rate quotient, distinct from directly measuring item age or cycle time.",
  "limitations": "This example does not implement or validate a queueing theorem. Its mismatched observations are deliberately insufficient for a waiting-time claim.",
  "sources": [
    "kanban"
  ],
  "tasks": [
    [
      "Identify each observation window",
      "Flow reviewer",
      "Snapshot and throughput lookback are explicitly different evidence."
    ],
    [
      "Separate arithmetic from inference",
      "Planner",
      "The quotient is labelled an illustrative ratio, not a measured wait or promise."
    ],
    [
      "Collect the missing context",
      "Queue owner",
      "Comparable scope, period averages and actual item histories are reviewed before adopting a model."
    ]
  ],
  "faqs": [
    [
      "Does a day unit mean the quotient is a real duration?",
      "No. Dimensional consistency is necessary for arithmetic but does not establish the intended inference."
    ],
    [
      "Can current items have different remaining times?",
      "Yes. Their states, required work and receiving conditions may differ substantially."
    ]
  ],
  "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."
    }
  ]
}