{
  "status": "Illustrative acceptance plan, not an executable test suite or observed production result",
  "topic": "Workout program version history",
  "date": "2026-11-04",
  "sourceArticle": "https://aptixlabs.com/insights/workout-program-versioning-software",
  "setup": [
    "Use synthetic accounts and records",
    "Record the environment and implementation version",
    "Agree the expected product contract before testing"
  ],
  "reviewSequence": [
    "Define template assignment and session-history boundaries",
    "Choose which edits create a new version",
    "Show the effective date of future changes"
  ],
  "cases": [
    {
      "id": "1",
      "condition": "A completed session is reopened",
      "expectedBehavior": "Its original prescription is recoverable",
      "observedBehavior": null,
      "status": "not_run"
    },
    {
      "id": "2",
      "condition": "Coach edits a future week",
      "expectedBehavior": "Only the selected future scope changes",
      "observedBehavior": null,
      "status": "not_run"
    },
    {
      "id": "3",
      "condition": "An exercise label is renamed",
      "expectedBehavior": "Historical logs remain interpretable",
      "observedBehavior": null,
      "status": "not_run"
    }
  ],
  "tradeoff": "Full snapshots consume more storage than references, but references need strong version guarantees. Choose the smallest representation that can still reconstruct the historical prescription accurately."
}