Listing or describing the plan's inputs (see 5.2) can be needed so that users can refer to them, so that consistency with the inputs can be checked while the plan is maintained, and so that changes to inputs can be checked for their effect on the plan. The plan should contain, or point to, the requirements the case has to satisfy. That can be a brief overview giving users the context of their work (a project outline, for example) or, in other situations, a full list of requirements drawn from the input documented information.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.