{
  "example_kind": "original synthetic manual planning case",
  "slug": "multiple-terminal-milestone-plan",
  "title": "Separate finish dates for different milestones",
  "scenario": "Synthetic planning case: A pilot package needs two days of preparation and one of review. Wider rollout additionally needs three days of localization after pilot review; both endpoints have separate receivers.",
  "layout": "network",
  "dataset": {
    "heading": "Inspect the invented case records",
    "headers": [
      "Endpoint or activity",
      "Model duration",
      "Ready day"
    ],
    "rows": [
      [
        "Preparation",
        "2",
        "2"
      ],
      [
        "Pilot review",
        "1",
        "3"
      ],
      [
        "Pilot-ready milestone",
        "0",
        "3"
      ],
      [
        "Localization after review",
        "3",
        "6"
      ],
      [
        "Rollout-ready milestone",
        "0",
        "6"
      ]
    ]
  },
  "derivation": "Pilot readiness=2+1=3. Wider readiness=3+3=6. The additional localization does not erase the earlier bounded pilot endpoint.",
  "result": "Pilot-ready is day three and wider-rollout-ready is day six in the supplied sequence. Do not use one finish label for both receiving decisions.",
  "boundary": "The artifact separates terminal milestone scopes instead of declaring one global completion date.",
  "limitations": "Readiness milestones are scope-specific. The invented sequence does not prove live availability or successful rollout.",
  "sources": [
    "schedule"
  ],
  "tasks": [
    [
      "Name both receiving scopes",
      "Project owner",
      "Pilot and wider rollout have distinct accepted output boundaries."
    ],
    [
      "Trace each endpoint’s predecessors",
      "Planner",
      "Localization is required for rollout and is not silently required for pilot."
    ],
    [
      "Communicate two readiness decisions",
      "Receiving leads",
      "Day-three and day-six model results remain separately labelled and reviewed."
    ]
  ],
  "faqs": [
    [
      "Can the pilot begin while localization is unfinished?",
      "Only if its agreed scope does not require that localization; confirm the receiving boundary."
    ],
    [
      "Does pilot-ready imply all customers have access?",
      "No. This manual schedule says nothing about deployment or account entitlement."
    ]
  ],
  "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."
    }
  ]
}