{
  "example_kind": "original synthetic manual planning case",
  "slug": "schedule-float-review",
  "title": "Inspect a branch's available schedule float",
  "scenario": "Synthetic planning case: A six-day design branch and a four-day data branch feed a one-day assembly. The complete toy model has independent resources and a common start.",
  "layout": "network",
  "dataset": {
    "heading": "Inspect the invented case records",
    "headers": [
      "Branch or gate",
      "Earliest ready day",
      "Required by"
    ],
    "rows": [
      [
        "Design",
        "6",
        "Assembly start at 6"
      ],
      [
        "Data",
        "4",
        "Assembly start at 6"
      ],
      [
        "Assembly",
        "7 finish",
        "Both inputs ready"
      ]
    ]
  },
  "derivation": "The merge is driven by day six. Data can move from day four to day six: two days of model float; a three-day delay would make it ready at seven and push final finish to eight.",
  "result": "The data branch has two model days of available delay before it would push assembly beyond day six. Keep that float conditional on the unchanged network.",
  "boundary": "The decision sets a specific permissible-delay boundary for one nondriving branch.",
  "limitations": "The float belongs to this complete deterministic model. A changed resource calendar or edge can alter it.",
  "sources": [
    "schedule"
  ],
  "tasks": [
    [
      "Confirm the merge criterion",
      "Receiving owner",
      "Assembly requires both complete inputs."
    ],
    [
      "Calculate the allowable branch delay",
      "Scheduler",
      "Day six minus day four leaves two model days under the unchanged network."
    ],
    [
      "Record the float-consuming change",
      "Project lead",
      "Any data delay above two days reopens the finish decision."
    ]
  ],
  "faqs": [
    [
      "Is float free capacity?",
      "No. It is conditional schedule allowance, not extra people or permission to omit work."
    ],
    [
      "Can several downstream edits each spend the same float?",
      "Not independently. Recalculate the full affected network after changes."
    ]
  ],
  "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."
    }
  ]
}