An architecture description must define services, including business and software services, as units of work that a provider performs for a consumer, independent of how the service is built. It must capture service descriptions that cover visible functionality, quality of service, interfaces, data and applicable standards or policy, and show how services compose or are orchestrated. Service data should support JCIDS, PPBE, DAS, systems engineering, operations planning and portfolio management.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.