{
  "example_kind": "original synthetic manual planning case",
  "slug": "dependency-cycle-start-gate",
  "title": "Detect a dependency cycle before commitment",
  "scenario": "Synthetic planning case: A requires the final output of B before starting. B requires the final output of C. C requires the final output of A. No accepted initial output exists.",
  "layout": "network",
  "dataset": {
    "heading": "Inspect the invented case records",
    "headers": [
      "Task",
      "Required completed input",
      "Can start initially?"
    ],
    "rows": [
      [
        "A",
        "B final output",
        "No"
      ],
      [
        "B",
        "C final output",
        "No"
      ],
      [
        "C",
        "A final output",
        "No"
      ]
    ]
  },
  "derivation": "A→B→C→A is circular in the required-input graph. Every task has an unmet predecessor; adding dates does not supply an initial completed output.",
  "result": "The three tasks have no permitted first start under the stated final-output requirements. Resolve a real boundary or initial-input change before committing the schedule.",
  "boundary": "The guide checks whether the declared final-input model has any executable first task.",
  "limitations": "Do not confuse a start-blocking dependency cycle with an intentional iterative process or a harmless communication loop.",
  "sources": [
    "schedule"
  ],
  "tasks": [
    [
      "Confirm each actual input need",
      "Receiving owners",
      "All three edges mean final usable output, not informal awareness."
    ],
    [
      "Identify the circular gate",
      "Planner",
      "The A/B/C cycle and absent initial output are recorded."
    ],
    [
      "Agree a genuine break",
      "Decision owner",
      "A supported staged input or changed dependency is accepted; no edge is erased just to make a chart work."
    ]
  ],
  "faqs": [
    [
      "Can I fix it by assigning A the earliest date?",
      "No. Its required B output is still missing."
    ],
    [
      "Does every feedback loop prohibit work?",
      "No. This example is specifically a circular requirement for final output before any start. Iterative workflows need different boundary definitions."
    ]
  ],
  "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."
    }
  ]
}