{
  "example_kind": "original synthetic manual planning case",
  "slug": "partial-rollback-state-inventory",
  "title": "Inventory retained and reverted state after a rollback",
  "scenario": "Synthetic planning case: A synthetic external release has three state components: code version, config mode and a pending message. A rollback restores code v1 but leaves config new and the pending new-format message untouched. The stated recovery target is code v1, config old and no pending message.",
  "layout": "protocol",
  "dataset": {
    "heading": "Inspect the invented case records",
    "headers": [
      "State component",
      "Declared recovery target",
      "After code rollback",
      "Match"
    ],
    "rows": [
      [
        "Code version",
        "v1",
        "v1",
        "Yes"
      ],
      [
        "Config mode",
        "Old",
        "New",
        "No"
      ],
      [
        "Pending message",
        "None",
        "New-format message remains",
        "No"
      ]
    ]
  },
  "derivation": "The target vector is (v1,old,none), while the observed vector is (v1,new,pending). One component matches and two differ. This comparison does not authorize deletion or imply a safe compensation procedure.",
  "result": "The rollback matches only the code component of the declared target. Config and pending-message state need separate approved recovery decisions; do not label the whole system restored.",
  "boundary": "The artifact checks a multi-component recovery target after a partial rollback rather than assuming code version represents all state.",
  "limitations": "The invented inventory is a planning review, not an executable rollback runbook or assurance of a safe operational change.",
  "sources": [
    "nist-state"
  ],
  "tasks": [
    [
      "Declare the recovery vector",
      "Release owner",
      "All three target components and their evidence are explicit."
    ],
    [
      "Inspect each current component",
      "Reviewer",
      "Config and pending message are checked independently of code version."
    ],
    [
      "Choose approved remaining actions",
      "Operating owner",
      "Compatible config and message handling have their own review; uncertain effects remain unresolved."
    ]
  ],
  "faqs": [
    [
      "Should we delete the message immediately?",
      "Not from this worksheet. Its required handling, delivery history and authority need an actual operational decision."
    ],
    [
      "Can rollback still have useful partial success?",
      "Yes. Record the code restoration precisely without extending it to unmatched state components."
    ]
  ],
  "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."
    }
  ]
}