{
  "example_kind": "original synthetic manual planning case",
  "slug": "state-model-version-bridge",
  "title": "Bridge review evidence after a workflow model changes",
  "scenario": "Synthetic planning case: Model v1 permits A→B and B→C. Model v2 retains A→B, removes B→C, and adds B→D and D→C. Existing passing traces all name v1.",
  "layout": "network",
  "dataset": {
    "heading": "Inspect the invented case records",
    "headers": [
      "Edge",
      "v1 status",
      "v2 status",
      "Evidence action"
    ],
    "rows": [
      [
        "A → B",
        "Allowed",
        "Retained",
        "Check applicability of old proof"
      ],
      [
        "B → C",
        "Allowed",
        "Removed",
        "Historical only; not new-route proof"
      ],
      [
        "B → D",
        "Absent",
        "Added",
        "New check"
      ],
      [
        "D → C",
        "Absent",
        "Added",
        "New check"
      ]
    ]
  },
  "derivation": "v2’s declared edge set has three edges. Only A→B is shared with v1. Old B→C success reaches the same C endpoint but does not traverse the new intermediate D or its outgoing edge.",
  "result": "Retain applicable A→B evidence with its original version and inspect it against v2. The removed B→C route cannot prove either new v2 edge; plan B→D and D→C checks explicitly.",
  "boundary": "The artifact bridges changed graph edges across versions rather than copying an acceptance label or updating documentation.",
  "limitations": "Model version tags identify invented contracts, not product release compatibility or complete proof of unchanged behavior.",
  "sources": [
    "nist-state"
  ],
  "tasks": [
    [
      "Record both model identities",
      "Model owner",
      "The retained, removed and added edges are explicit."
    ],
    [
      "Check evidence applicability edge by edge",
      "Reviewer",
      "Same endpoint C is not substituted for proof of passing through D."
    ],
    [
      "Rehearse the changed route",
      "Delivery owner",
      "v2 traces include B→D→C with intermediate evidence."
    ]
  ],
  "faqs": [
    [
      "Must every old result be discarded?",
      "No. Relevant retained behavior may keep evidence after an applicability check."
    ],
    [
      "Is an unchanged final outcome enough?",
      "No when the accepted model requires new intermediate 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."
    }
  ]
}