diff --git a/efp/efp001/main.xml b/efp/efp001/main.xml index dddedb9..b7808aa 100644 --- a/efp/efp001/main.xml +++ b/efp/efp001/main.xml @@ -1,10 +1,11 @@ + efp="1" created="2025-01-26" category="process" status="provisional" title="Constitution of the Organizational Architecture"> + @@ -12,16 +13,19 @@

- 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). + This Constitution establishes the Organizational Architecture of the TerraModulus Project + as the foundational framework governing the scope of the Project, including + the administration of the Community, and the underlying executive parts for the creations, + lifecycles and relationships of Execution Framework Proposals (EFPs), + Executive Policy Charters (EPCs), Executive Research Dossiers (ERDs) and + Community Standards and Guidelines (CSG).

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

+
@@ -69,7 +73,8 @@

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. + The EFP might also take effects over the entire Architecture besides + the Community and the Executives.

In general, EFPs do not require the mandatory approval from the Executives. @@ -187,6 +192,12 @@ methods are generally understood, except for the progressional development of the thoughts to be included in the related ERDs.

+

+ EFPs may contain both normative and non-normative content at the same time. It may be up to + the decision of the author(s) for the final interpretation of the contents, including but not + limited to the parts of whether the related contents are to be normative, non-normative or + outdated. +

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 @@ -197,28 +208,51 @@

-
+

- EFPs are classified into three categories: + EFPs are first classified into two types: +

+ +
  • + An Informational EFP is non-normative, and describes background, explanations + or other information about various topics to the public, without formally proposing anything. + It may also provide insights, overviews or advice about certain topics. +
    • +
  • + A Normative EFP is formal, and describes or propose normative features, changes, + mechanisms, processes, workflows, standards, protocols, specifications, or various principles. + It may also provide guidelines, recommendations, best practices to the Architecture, + or may include implementation change or interoperability standard for the Projects. + It may also be a realization or implementation of a standard or specification. +
    • +     +

    + And then five 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. + Organization EFPs describe the overall system of organization of the Architecture + and relationships between different items or projects under the Architecture. +
    • +
  • + Project EFPs describe executions special to a particular project or + a specific range of projects for a given case. +
    • +
  • + Governance EFPs describe miscellaneous governing tasks or policies, + and management of governing systems like EFP, EPC and ERD.
  • - 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. + Standard EFPs describe descriptive standards, protocols and specifications.
  • - 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. + General EFPs describe uncategorized miscellaneous information about anything else.
    • +

    + EFP categories can be understood as the scopes where the EFPs are applicable to. +

    @@ -378,6 +412,11 @@ should always be referred as this Constitution, so the necessity to mention the revision in the EFP document's title is negligible.

    +

    + It is possible that non-normative references to the latest version of this Constitution may be + made for the public's reference. In this case, all amendments should be included in the references, + and the actual EFPs of this Constitution remain authoritative over the references. +