Constitution of the Execution Architecture

This Constitution establishes the Execution Architecture of the TerraModulus Project as the foundational framework governing the creation, lifecycle and relationship of Execution Framework Proposals (EFPs), Executive Policy Charters (EPCs), Executive Research Dossier (ERDs) and Community Standards and Guidelines (CSG).

The Architecture consists of the Community and the Executives. All Members in the Community have their own rights and responsibility with respect to the Project.

This Constitution is the supreme authority within the Architecture.

All EFPs, EPCs, ERDs and CSG derive legitimacy from this Constitution.

This Constitution is limited to the scope of the Architecture. All activities within the Architecture are still covered by the local jurisdictions.

EFPs are community-driven, execution-defining, and immutable once finalized. They provide standards, methods, and structured execution plans. This includes but not limited to strategies, projects, guidelines and standards.

EFPs shall either:

1. outline how a project, procedure or initiative will be executed, managed, and monitored to achieve its objectives; or
2. explain or define a certain mechanism which would be applied onto the Architecture.

Both the Community and the Executives may initiate an EFP to the Architecture. The EFP might also take effects over the Project besides the Community and the Executives.

In general, EFPs do not require the mandatory approval from the Executives.

An EFP may represent the stance of the Executives or the Project in any aspect.

EPCs are executive-led, versioned, and policy-defining. They establish organizational principles, governance structures, and policies, but must always be initiated and guided by corresponding EFPs. Both EPCs and their associated EFPs must be approved by the Executives before becoming authoritative.

An EPC is a formal document with authoritative language that outlines the policies, principes, and governance structure for the Architecture. EPCs may serve as Rules and Regulations under the Architecture.

Any EFP in the draft, shall associate an EPC if the EFP is purposed to initiate an EPC. However, the association requires the Executives' approval.

All participants, including the Community and the Executives, are required to adhere to the EPCs whenever their designated administrative scope is applicable.

ERDs are structured summaries or compilations of research findings, insights, and recommendations to provide high-level overviews of research foundations and may inform EFPs and EPCs.

ERDs may involve consulting, market researching, policy analysis or strategy investigations. They may also be comprehensive on a particular topic which may affect the Execution of the Architecture.

CSG are derived directly from EPCs. They provide operational and administrative guidance for the Community.

On the whole, over the Architecture, document systems such as EFPs, EPCs, ERDs and CSG, have the special roles and purposes by their own definitions.

The details of processes, regulations and guidelines for each document system shall be defined clearly in their corresponding EPCs.

An EFP or EPC may directly inherit another EFP or EPC from another Governance System respectively, when both Systems share the same mandatory features. In the inheritance, terminology amendments aligning to the System shall be made in the same document.

EFPs are publicly visible and allow open project supervisions by the public, while keeping the project workflow streamlined enough. These could provide clear guidelines and information about various topics, so as the processes. This would also allow certain public involvement in the project while keeping certain intent of organized workflow.

The identifiers of EFPs shall be strictly sequential as the serial number starting at one. The identifier shall be assigned only when the initiation of the EFP is approved. After that, the document entry shall not be declined or removed regardless.

The title of an EFP shall not be changed once finalized.

Deprecation of an EFP must be caused by another EFP.

An EFP may involve the Architecture, a mechanism, a plan or a scheme. It may not be highly executive, but may involve certain objectives, deliverables, or boundaries of the Project. There may not be time constrains, but the milestones and objectives may be decided in the roadmap. Moreover, it would be intended to standardize and guide the Project or a process. Occasionally, certain EFPs may solicit feedback from the Community depending on the context, so EFPs may be updated and revised upon feedbacks or progressions. However, the topics or the themes of the EFPs should not be changed, or else a new EFP should be issued for the new content and updates. Certainly, detailed descriptions should always be included to ensure that the goals and methods are generally understood, except for the progressional development of the thoughts to be included in the related ERDs.

Once finalized, the EFPs shall become immutable, but maintenance and errata may be allowed. This includes minor content modifications without effects to the designated meanings and metadata changes of the documents.

The formats and management details should go into the corresponding EPC.

EFPs are classified into three categories:

• An Informational EFP is non-normative and describes background, explanations or other information about various topics. It may also provide insights and overviews about certain topics.
• A Process EFP is normative and describes or proposes a change to a Community or Project process, workflow or governance. It may also provide guidelines, processes, and best practices for the Community and/or the Project.
• A Standard EFP is normative and describes about a feature for the project, with descriptive standards, protocols or specifications. It may also include implementation change or interoperability standard for the project.

The Executive Leadership holds authority over the Executives.

The Executive Leadership shall be decided by the host organization of the Architecture without participation of the Community.

If available, a Chief Governance Officer may be assigned to cooperate with the Leadership in ensuring compliance with this Constitution.

The Executive Leadership and Chief Governance Officer together form the Supreme Governing Group. Amendments and explanations of this Constitution must be approved by the Supreme Governing Group.

The Executives holds authority over the Architecture. However, most executive operations over the Architecture require the formal process of an EFP to allow the oversight from the Community.

Essentially, the organization holds the supreme authority over the Architecture while the Community shall hold the majority authority besides the Executives.

If available, Governing Moderators may be selected from the Community to aid in the procedures of several document systems.

Fundamentally, all Members of the Community have the rights to supervise the Executives through participation in administrative activities.

Community Members may engage in discussions and initiations of EFPs, EPCs, and ERDs.

In cases of dereliction of duty by the Executives, the Community may challenge the Executives through corresponding procedures defined in EPCs.