Skip to content

[EFP 1] Constitution of the Organizational Architecture #15

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
BenCheung0422 wants to merge 2 commits into
base: main
Choose a base branch
from
Draft

[EFP 1] Constitution of the Organizational Architecture #15

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
24a54d9
EFP 1: Rename title
BenCheung0422 Feb 11, 2026
4194bed
EFP 1: Update EFP Classification
BenCheung0422 Feb 28, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
75 changes: 57 additions & 18 deletions efp/efp001/main.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,27 +1,31 @@
<?xml version="1.1" encoding="UTF-8" ?>
<efp xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../../efp.xsd"
efp="1" created="2025-01-26" category="process" status="provisional" title="Constitution of the Execution Architecture">
efp="1" created="2025-01-26" category="process" status="provisional" title="Constitution of the Organizational Architecture">
<metadata>
<pullRequests>
<pullRequest id="1"/>
<pullRequest id="3"/>
<pullRequest id="15"/>
</pullRequests>
</metadata>
<body>
<section title="Purpose and Scope">
<section title="Establishment">
<content>
<p>
This Constitution establishes the Execution Architecture of the <b>TerraModulus</b> 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 <b>TerraModulus</b> 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).
</p>
<p>
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.
</p>
<embed src="./constitution.svg"/>
</content>
</section>
<section title="Authority">
Expand Down Expand Up @@ -69,7 +73,8 @@
</list>
<p>
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.
</p>
<p>
In general, EFPs do not require the mandatory approval from the Executives.
Expand Down Expand Up @@ -187,6 +192,12 @@
methods are generally understood, except for the progressional development of the thoughts
to be included in the related ERDs.
</p>
<p>
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.
</p>
<p>
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
Expand All @@ -197,28 +208,51 @@
</p>
</content>
</section>
<section title="Categories">
<section title="Classification">
<content>
<p>
EFPs are classified into three categories:
EFPs are first classified into two types:
</p>
<list>
<li>
An <b>Informational</b> 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.
</li>
<li>
A <b>Normative</b> 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.
</li>
</list>
<p>
And then five categories:
</p>
<list>
<li>
An <b>Informational</b> EFP is non-normative and describes background, explanations
or other information about various topics. It may also provide insights and overviews
about certain topics.
<b>Organization</b> EFPs describe the overall system of organization of the Architecture
and relationships between different items or projects under the Architecture.
</li>
<li>
<b>Project</b> EFPs describe executions special to a particular project or
a specific range of projects for a given case.
</li>
<li>
<b>Governance</b> EFPs describe miscellaneous governing tasks or policies,
and management of governing systems like EFP, EPC and ERD.
</li>
<li>
A <b>Process</b> 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.
<b>Standard</b> EFPs describe descriptive standards, protocols and specifications.
</li>
<li>
A <b>Standard</b> 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.
<b>General</b> EFPs describe uncategorized miscellaneous information about anything else.
</li>
</list>
<p>
EFP categories can be understood as the scopes where the EFPs are applicable to.
</p>
</content>
</section>
</section>
Expand Down Expand Up @@ -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.
</p>
<p>
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.
</p>
</content>
</section>
<section title="Archival and Transparency">
Expand Down