An architecture description must define projects as temporary efforts that create desired resource states, and must connect each project to a work breakdown structure of activities, performers and products. It must record project phases, measures, rules, dependencies and the project plan elements needed for acquisition, technology development and systems engineering, with measures and rules assigned at every level of the work breakdown. Project data should support JCIDS, PPBE, DAS, capability portfolio management, systems engineering and operations planning.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.