{
  "example_kind": "original synthetic manual planning case",
  "slug": "transition-coverage-work-matrix",
  "title": "Plan review coverage for allowed task transitions",
  "scenario": "Synthetic planning case: An external rehearsal model declares pending→ready, ready→accepted, ready→pending and pending→cancelled. Six recorded cases exercise only the first two edges.",
  "layout": "network",
  "dataset": {
    "heading": "Inspect the invented case records",
    "headers": [
      "Declared transition",
      "Recorded cases",
      "Coverage"
    ],
    "rows": [
      [
        "Pending → ready",
        "3",
        "Exercised"
      ],
      [
        "Ready → accepted",
        "3",
        "Exercised"
      ],
      [
        "Ready → pending",
        "0",
        "Unexercised"
      ],
      [
        "Pending → cancelled",
        "0",
        "Unexercised"
      ]
    ]
  },
  "derivation": "The unique exercised edge set has size two, while the declared edge set has size four: 2/4 coverage in this model. Case repetitions do not increase unique transition coverage.",
  "result": "Two of four declared transitions have rehearsal evidence. Preserve ready→pending and pending→cancelled as unexercised obligations rather than counting six cases as complete transition coverage.",
  "boundary": "The artifact distinguishes transition coverage from repeated case volume with a fully enumerated graph.",
  "limitations": "This invented state model does not describe native TeamBoostAI status transitions or complete test assurance.",
  "sources": [
    "nist-state"
  ],
  "tasks": [
    [
      "Freeze states and allowed edges",
      "Model owner",
      "The four edges are an explicit external contract."
    ],
    [
      "Map traces to unique edges",
      "Rehearsal reviewer",
      "The six runs cover only two declared transitions."
    ],
    [
      "Assign missing-edge rehearsals",
      "Acceptance lead",
      "Both remaining transitions have an expected state and an owned check."
    ]
  ],
  "faqs": [
    [
      "Does every edge need just one run?",
      "Not necessarily. Edge coverage is a count; input variation, guards and sequence behavior are additional dimensions."
    ],
    [
      "Does full edge coverage prove the model is correct?",
      "No. The declared model itself can omit required behavior."
    ]
  ],
  "method_references": [
    {
      "id": "nist-state",
      "title": "NIST: state-based and event-sequence testing context",
      "url": "https://csrc.nist.gov/Projects/automated-combinatorial-testing-for-software",
      "scope": "General context for state-based and event-sequence testing. All graphs, guards, fixtures and recovery contracts here are original toy definitions; the source does not certify their completeness or product behavior."
    }
  ]
}