Each architecture has a life cycle of its own, running from the point it starts to the point it no longer applies or fits, and that life cycle gives direction to the processes of the entity being architected. The architecture hands owners and builders a technical contract through an architecture plan that sets out candidate systems, subsystems and enabling systems, and the environments, activities and outcomes should be tailored to the purpose, the organisation and the complexity of the problem and the solution.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.