{
  "example_kind": "original synthetic manual planning case",
  "slug": "review-attempts-versus-accepted-items",
  "title": "Separate review attempts from accepted outcomes",
  "scenario": "Synthetic planning case: Proof A requires two review attempts, B one and C three before acceptance. Each attempt occupies thirty supplied review-minutes; each proof is accepted once.",
  "layout": "evaluation",
  "dataset": {
    "heading": "Inspect the invented case records",
    "headers": [
      "Proof",
      "Attempts",
      "Accepted outcomes",
      "Review-minutes"
    ],
    "rows": [
      [
        "A",
        "2",
        "1",
        "60"
      ],
      [
        "B",
        "1",
        "1",
        "30"
      ],
      [
        "C",
        "3",
        "1",
        "90"
      ]
    ]
  },
  "derivation": "Attempts=2+1+3=6; accepted proofs=1+1+1=3. At thirty minutes per attempt, total demand=6×30=180 minutes, not 3×30.",
  "result": "The period contains six review attempts and three accepted proofs, using 180 stated minutes. Keep workload and outcome counts separate.",
  "boundary": "The decision reconciles repeated review service with distinct accepted outcomes.",
  "limitations": "Equal attempt duration is an invented assumption. Actual workload needs actual durations and meaningful review boundaries.",
  "sources": [
    "kanban"
  ],
  "tasks": [
    [
      "Preserve attempt histories",
      "Review recorder",
      "Each revision attempt remains linked to its proof identity."
    ],
    [
      "Reconcile service demand",
      "Capacity planner",
      "Six attempts consume 180 supplied minutes in this model."
    ],
    [
      "Label outcomes independently",
      "Reporting owner",
      "Three distinct accepted proofs are not reported as six deliveries."
    ]
  ],
  "faqs": [
    [
      "Are unsuccessful attempts automatically wasted work?",
      "No. They may reveal required corrections; this ledger records workload rather than judging value."
    ],
    [
      "Can attempt counts compare reviewers fairly?",
      "Not alone. Scope, difficulty, criteria and quality differ and need context."
    ]
  ],
  "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."
    }
  ]
}