{
  "example_kind": "original synthetic manual planning case",
  "slug": "reset-state-rehearsal-ledger",
  "title": "Restore the declared starting state between rehearsals",
  "scenario": "Synthetic planning case: Two checks require approval absent at their declared origin: A starts pending and B starts ready. After check A sets approval present, check B is run without restoring that flag and passes a transition that should be rejected in B’s intended fixture.",
  "layout": "protocol",
  "dataset": {
    "heading": "Inspect the invented case records",
    "headers": [
      "Check",
      "Intended start",
      "Actual start",
      "Observed result"
    ],
    "rows": [
      [
        "A",
        "Pending; approval absent",
        "Pending; approval absent",
        "Approval set present"
      ],
      [
        "B",
        "Ready; approval absent",
        "Ready; approval present from A",
        "Accepted"
      ],
      [
        "B fresh",
        "Ready; approval absent",
        "Must verify after reset",
        "Expected rejection"
      ]
    ]
  },
  "derivation": "B’s requested origin state is ready in both descriptions, but its approval flag differs. Resetting a visible state label alone would not restore the full fixture vector.",
  "result": "Check B did not run its intended approval-absent fixture. Preserve its actual starting state and rerun after a verified reset before treating it as false-guard evidence.",
  "boundary": "This checks full starting-fixture restoration between rehearsals rather than general retry behavior.",
  "limitations": "The invented flag model is external; a reset procedure itself needs evidence and may not be available in a real product.",
  "sources": [
    "nist-state"
  ],
  "tasks": [
    [
      "Specify the full fixture vector",
      "Rehearsal owner",
      "Starting state and approval flag are both recorded."
    ],
    [
      "Inspect setup between runs",
      "Reviewer",
      "A’s retained approval flag explains why B does not test the intended condition."
    ],
    [
      "Verify the fresh fixture",
      "Acceptance lead",
      "A new B run records the reset flag and resulting rejection/unchanged state."
    ]
  ],
  "faqs": [
    [
      "Is B necessarily a software failure?",
      "No. The observation may match its actual true-guard input; the intended test setup was wrong."
    ],
    [
      "Can I edit the log to say approval absent?",
      "No. Preserve actual history and add a fresh correctly established run."
    ]
  ],
  "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."
    }
  ]
}