The scope of the architecting work must say plainly which parts of the solution life cycle it covers, from the first concept through retirement and possible replacement, for instance by naming the phases or periods in scope. The scope must also take in the influences that shape the solution, including development, technology, business, operations, organisation, politics, economics, law, regulation, ecology and society, and not only its technical side.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.