Project ZMAM Doctrine

An Iraqi-rooted ecosystem, unhidden

Project ZMAM was founded in Babil — one of the oldest cities of Mesopotamia — on the conviction that technology built locally to global standards is more honest than any imported solution that doesn't understand its context. These roots aren't a marketing tagline; they're Axiom IX of the constitution itself: Community Empowerment.

1. 01

   Leadership is a mandate, not ownership

   The workspace, its work and its record belong to ZMAM and its members. The leader is a steward, not an owner.

2. 02

   The Founder holds final authority

   The Founder has the last word in any workspace. He may inspect, freeze, and remove the leader of any workspace, taking it himself or handing it to a successor, by a written reasoned decision. No leader decision or team opinion overrides him; whatever a leader cannot settle returns to him.

3. 03

   Appointment and signature

   Only the Founder appoints leaders of root workspaces; a branch leader appoints the leader of a sub-branch and the Founder is told of every appointment. Nobody takes leadership before reading and signing this charter and the "Work ownership and exit terms" document, and a new signature is required after every amendment. The tree is at most four levels deep.

4. 04

   The leader's duties

   A documented report at least monthly. Blockers handled within their deadline. Clear acceptance criteria and fairness between members. Work and decisions kept inside ZMAM. The team's repository registered under the platform account, with all of the team's code kept in it. A full handover when stepping down.

5. 05

   What a leader may not do

   No platform privileges. No speaking in the name of ZMAM or any official body. No collecting money from members and no promising profit or ownership that ZMAM has not approved in writing. No moving ZMAM project code outside the platform account, and no publishing or licensing it. No access to members' data outside the team and no leaking of the team's data.

6. 06

   Grounds for removal

   Leadership ends by the Founder's decision upon: (1) breaching the constitution or terms; (2) mistreating, blackmailing or discriminating against a member; (3) collecting money or promising profit or ownership without written approval; (4) moving the team's work and decisions outside ZMAM to hide them, or withholding information from the Founder; (5) impersonating a role or privilege; (6) leaking members' data; (7) refusing a reasoned order from the Founder; (8) inactivity: thirty days without activity in the workspace, or two consecutive months without a report. Removal may be immediate and without warning in cases 2 to 7.

7. 07

   Procedure

   A removal usually starts with freezing the workspace: writing stops, reading and the record remain. The leader is then removed with a written reason of at least ten characters, which is recorded and communicated. The former leader stays a plain member and any delegation they granted ends automatically. Removal never affects members' rights over completed work and their names on it.

8. 08

   A member's right to go to the Founder

   Every member may bring a complaint directly to the Founder through "Contact the admins" without going through their leader. A leader may not prevent or punish this.

9. 09

   Record and amendment

   The workspace event log is never deleted or edited and the Founder may review it at any time. The Founder may amend this charter; each amendment raises the version and requires leaders to sign again.

This volume is operational: signing, freezing, removal and the depth cap are enforced by the platform itself and recorded.