Together with the stakeholders, the project fixes where the functional edge lies for the system (or software system, or element), expressed as the behaviour and properties it must supply, taking account of the organization and its actual mission, the environment (how mature the domain is, how settled the interfaces are, the system's role beside other systems) and limits of cost, schedule, politics, environment or operations. A strategy is defined for identifying and defining the system or software requirements and managing them through the life cycle (approach, milestones, resources). The enabling tools and repositories for eliciting, capturing, managing and transforming the requirements are planned and access to them obtained.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.