{
  "example_kind": "original synthetic manual planning case",
  "slug": "contingency-activation-lead-time",
  "title": "Compare contingency lead time with its trigger window",
  "scenario": "Synthetic planning case: An external plan needs a fallback ready at the start of day 10. Activation takes three full days. Its first proposed trigger checks readiness at the start of day 9.",
  "layout": "network",
  "dataset": {
    "heading": "Inspect the invented case records",
    "headers": [
      "Clock event",
      "Day boundary",
      "Implication"
    ],
    "rows": [
      [
        "Required fallback ready",
        "Start of day 10",
        "Deadline"
      ],
      [
        "Proposed trigger",
        "Start of day 9",
        "Three days ends at day 12"
      ],
      [
        "Latest compatible activation",
        "Start of day 7",
        "Three days ends at day 10"
      ]
    ]
  },
  "derivation": "With continuous full-day duration, finish=start+3. Hence 9+3=12, while 10−3=7. Arithmetic identifies a timing requirement; it cannot invent an early observable warning.",
  "result": "A day-9 trigger would finish activation at day 12 under the supplied duration. The latest compatible start is day 7; whether a useful trigger can be observed then remains a separate question.",
  "boundary": "This checks response lead time against the earliest useful observation, rather than simply adding scheduled work durations.",
  "limitations": "The toy clock excludes weekends, uncertainty and other work. No real fallback readiness is promised.",
  "sources": [
    "schedule"
  ],
  "tasks": [
    [
      "Fix the clock convention",
      "Planner",
      "Start-of-day boundaries and the three-day activation duration are explicit."
    ],
    [
      "Check latest feasible activation",
      "Reviewer",
      "The latest start is day 7 with no duration reserve in this model."
    ],
    [
      "Validate trigger observability",
      "Risk owner",
      "An actual condition observable by day 7 or a revised deadline/route is required; unknown early evidence is not presumed."
    ]
  ],
  "faqs": [
    [
      "Should we always activate at day 7?",
      "Not necessarily. The response choice needs actual evidence, authority and costs; this is only a compatibility boundary."
    ],
    [
      "Does day 7 guarantee readiness?",
      "No. It exactly fits the supplied duration without uncertainty or additional dependencies."
    ]
  ],
  "method_references": [
    {
      "id": "schedule",
      "title": "GAO Schedule Assessment Guide",
      "url": "https://www.gao.gov/products/gao-16-89g",
      "scope": "General schedule-model context. All records, local policies and arithmetic are original toy examples, not a certified or optimized schedule."
    }
  ]
}