Where a project's software is Class A, B or C, each Center Director, or designee, keeps one or more software cost repositories holding at least planned and actual effort and cost, planned and actual dates for major milestones, planned and actual values of key cost parameters (software size, requirements count, defect counts for maintenance projects, cost model inputs) and project descriptors such as software class, domain and requirements volatility.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.