According to the TOGAF standard, the need for the ADM process to be governed is to ensure that the architecture development and implementation activities are conducted in a consistent, coherent, and compliant manner1. Governance provides the means to verify that the method is being applied correctly and effectively, and that the architecture deliverables and artifacts meet the quality and standards criteria1. Governance also enables the management of risks, issues, changes, and dependencies that may arise during the ADM process1.
Some of the benefits of governing the ADM process are2:
*Improved alignment of the architecture with the business strategy and objectives
*Enhanced stakeholder engagement and communication
*Increased reuse and integration of architecture assets and resources
*Reduced complexity and duplication of architecture efforts
*Increased agility and adaptability of the architecture to changing needs and requirements
*Improved compliance and auditability of the architecture outcomes and outputs References: 1: Architecture Governance 2: Architecture Governance Benefits

"In addition to the method itself being iterative, there is also iteration within the ADM cycle, both among the individual phases and among the steps within a phase." www.opengroup.org Reference: The Open Group, TOGAF (archived TOGAF 8/9 materials) - Iteration within the ADM.

The TOGAF standard divides Enterprise Architecture into four primary architecture domains: business, data, application, and technology. These domains represent different aspects of an enterprise and how they relate to each other. The business domain defines the business strategy, governance, organization, and key business processes. The data domain describes the structure of the logical and physical data assets and data management resources. The application domain provides a blueprint for the individual applications to be deployed, their interactions, and their relationships to the core business processes. The technology domain describes the logical software and hardware capabilities that are required to support the deployment of business, data, and application services. Other domains, such as motivation, security, or governance, may span across these four primary domains. References:
The TOGAF Standard, Version 9.2 - Core Concepts
Domains - The Open Group
TOGAF Standard - Introduction - Definitions - The Open Group
The TOGAF Standard, Version 9.2 - Definitions - The Open Group
TOGAF and the history of enterprise architecture | Enable Architect

According to the TOGAF standard, the two statements provided refer to different scopes within which architecture can be developed:
Groups of countries, governments, or governmental organizations working together typically align with broader, often international, scopes of architecture that transcend individual enterprise boundaries.
Partnerships and alliances of businesses working together, such as a consortium or supply chain, refer to collaborative efforts that can define architecture at a scope involving multiple enterprises.
In both cases, the term "Architectures Scopes" is appropriate because it reflects the varying levels and contexts in which architectures can be defined, ranging from single business units to collaborative inter-organizational efforts.

* Phase G: Implementation Governance provides architectural oversight of the implementation. It ensures that the implementation conforms to the Target Architecture using Architecture Contracts and governance frameworks.
* Phase H: Architecture Change Management is about maintaining the architecture lifecycle and handling new requirements, not direct implementation oversight.
* Preliminary Phase is about setting up the architecture capability.
* Phase A is about developing the Architecture Vision.
Reference: TOGAF Standard, Version 9.2, Part II: ADM, Phase G.