Hermes Bot
97 lines
8.8 KiB
Markdown
97 lines
8.8 KiB
Markdown
## Sprint 2: The Structure — Circles Over Hierarchy
|
||
|
||
**Maqsad:** Hifz al-Nasl (Preservation of Community)
|
||
**Framework:** Structure Quadrant — Functional / Divisional / Circular / Networked
|
||
**Principle:** Circles over hierarchy — authority flows to those closest to the work, not to those highest on the chart.
|
||
|
||
---
|
||
|
||
### 1. THE CHARTER (Mithaq)
|
||
|
||
We the people of this organization covenant to organize not as a ladder where some stand above others, but as a garden of interlocking circles — each rooted in a domain of work, each accountable to the whole. We reject the idolatry of hierarchy that crushes the soul and the chaos of flatness that starves direction. Instead, we choose circles: bounded autonomy, nested purpose, distributed stewardship.
|
||
|
||
This covenant mirrors the structure the Prophet ﷺ established in Madinah: a confederation of tribes and communities, each with its own internal governance, yet united under a common Mithaq. The Ummah was not a pyramid — it was a network of circles: the family, the clan, the neighborhood, the market, the army, the treasury. Each circle had its own leader (amir), but authority was not absolute. It was delegated, reviewed, and recallable.
|
||
|
||
We commit to circles over hierarchy because hierarchy hoards information and suffocates initiative. Circles release intelligence. Every circle in our organization shall have a clear purpose, a defined domain, and the authority to make decisions within it — no permission required, no bottleneck tolerated. This is how we preserve the community (Hifz al-Nasl): by ensuring every member has a voice, a role, and a responsibility.
|
||
|
||
---
|
||
|
||
### 2. SPRINT STRUCTURE (Hikma / Architecture)
|
||
|
||
**ORG_DESIGNER:**
|
||
Draw four circles on a page. Label them:
|
||
- **Strategy Circle** — holds the evolutionary purpose, long-term direction, capital allocation.
|
||
- **Operations Circle** — runs the core value streams, day-to-day delivery, customer-facing work.
|
||
- **People Circle** — stewards culture, hiring, learning, conflict, well-being.
|
||
- **Finance Circle** — manages revenue, expenses, Baitul Mal, transparency.
|
||
|
||
Each circle has a lead link (representative to the parent circle), a facilitator (meeting process), a secretary (records), and any number of roles. Roles are defined by purpose, domain, and accountabilities — not by job titles. A person can hold multiple roles across circles. No one reports to a boss; everyone reports to a role’s purpose.
|
||
|
||
This is the architecture of Teal: self-managing teams with clear boundaries. Circles are nested. The Strategy Circle makes high-level policy. The Operations Circle adapts it to reality. The People Circle ensures the humans are whole. The Finance Circle ensures the trust is honored. Decisions are made by consent — no objections unresolved.
|
||
|
||
**KHALIFAH:**
|
||
The Prophet ﷺ organized the Ummah through a layered structure of circles, not a chain of command. In Madinah, he appointed governors (umara) over regions, judges (qudat) over disputes, tax collectors (jubah) over zakat, market inspectors (muhtasib) over commerce, and military commanders (umara al-jaysh) over expeditions. Each operated within a defined domain. The Khalifah did not micromanage the muhtasib’s pricing decisions or the qadi’s rulings — he trusted the circle.
|
||
|
||
Classical Baitul Mal administration had its own circle: the treasurer (sahib bayt al-mal), the accountant (katib), the disburser (mustakhrij), the auditor (muhasib). Each had a role with clear accountabilities. The treasurer could not disburse without a signed order from the Khalifah (a check and balance). This is the same logic as a Holacracy circle: domains are protected, roles are bounded, and decisions are made at the appropriate level.
|
||
|
||
**When does hierarchy serve vs harm?**
|
||
Hierarchy serves when it is temporary and role-based — like a commander in battle or a project lead for a crisis. It harms when it becomes permanent, identity-based, and status-driven. The classical Khilafah had hierarchy of function, not of rank. The Khalifah was first among equals, not a supreme ruler. Circles preserve this: authority is attached to the role, not the person. When the role ends, the authority returns to the circle.
|
||
|
||
---
|
||
|
||
### 3. AUTHORITY MAP (Ikhtiyar / Delegation)
|
||
|
||
**ORG_DESIGNER:**
|
||
Authority is not given by a boss; it is defined by the circle’s governance process. Every role has a **Domain** — the exclusive area the role holds, where no one else can make decisions without consent. Every role also has **Accountabilities** — the ongoing activities expected of the role. And every role has **Purpose** — the why behind the role.
|
||
|
||
Decision-making in circles uses **Consent**: a proposal passes unless someone raises a reasoned objection that the proposal would harm the circle’s purpose. This is not consensus (everyone agrees) and not command (one person decides). It is “no one objects” — which is faster than consensus and safer than command.
|
||
|
||
**KHALIFAH:**
|
||
Classical **Ikhtiyar** (delegated authority) works the same way. The Khalifah delegates authority to a governor (amir) over a province. The governor has domain: he can collect taxes, appoint judges, maintain order — but he cannot declare war or change the currency. Those domains belong to the central Shura. If the governor exceeds his ikhtiyar, he is removed.
|
||
|
||
The principle is: **Authority must be bounded and reviewed.** The Prophet ﷺ said: “Whoever is put in charge of any affair of the Muslims and then appoints someone out of favoritism — then upon him is the curse of Allah” (Bukhari). This means ikhtiyar is a trust (amanah), not a right. It can be revoked if misused.
|
||
|
||
**Consent vs Command:**
|
||
- Command says: “I decide because I am above you.” This creates dependency and fear.
|
||
- Consent says: “You propose. I object only if it harms the purpose.” This creates ownership and speed.
|
||
|
||
In classical Shura, the Khalifah would propose a policy. The senior companions would object if it contradicted the Quran or Sunnah. If no valid objection, the policy passed. This is consent decision-making — not voting, not dictatorship.
|
||
|
||
**Practical Map for This Sprint:**
|
||
1. Every circle creates a **Domain Document** listing what is exclusively theirs to decide.
|
||
2. Every role holder creates a **Role Canvas** with purpose, domains, accountabilities.
|
||
3. No one can override a role’s domain without a governance meeting and consent.
|
||
|
||
This protects Hifz al-Nasl: when every person knows the boundaries of their authority, they can act boldly without fear of stepping on toes or being overridden.
|
||
|
||
---
|
||
|
||
### 4. TREASURY / BAITUL MAL (Trust)
|
||
|
||
**KHALIFAH:**
|
||
The Baitul Mal is not a bank account — it is an amanah (trust) of the community. The Prophet ﷺ and the early Khalifahs treated public funds as sacred. Umar ibn al-Khattab (RA) would walk the streets at night checking if anyone was hungry, then would personally go to the Baitul Mal to disburse funds. He refused to take a salary from the treasury for himself because he was wealthy — and when he did accept a stipend later, it was modest and publicly recorded.
|
||
|
||
In classical administration, the Baitul Mal had four categories of revenue:
|
||
- **Zakat** — obligatory charity for specific recipients.
|
||
- **Sadaqah/Jizyah/Kharaj** — voluntary and non-Muslim taxes.
|
||
- **Fay’/Ghanimah** — state property and war spoils.
|
||
- **Waqf** — endowments for perpetual benefit.
|
||
|
||
Every dirham was tracked. The treasurer (sahib bayt al-mal) kept a ledger. Disbursements required two signatures: the Khalifah and the treasurer. This is transparency by design.
|
||
|
||
**ORG_DESIGNER:**
|
||
Modern organizations must treat their treasury as Baitul Mal — a trust, not a private purse. This means:
|
||
- **Open books** — everyone in the organization can see revenue, expenses, and reserves at any time.
|
||
- **Allocation by consent** — the Finance Circle proposes a budget; the Strategy Circle consents or objects. No single person decides where money goes.
|
||
- **Compensation transparency** — every role’s compensation is public within the organization. This prevents favoritism and builds trust.
|
||
|
||
**Structure for This Sprint:**
|
||
1. Create a **Finance Circle** with roles: Treasurer (sahib), Accountant (katib), Auditor (muhasib), and Budget Steward.
|
||
2. Implement **Open Book Management**: publish a real-time dashboard of all financial flows.
|
||
3. Run a **Budget Consent Process**: each circle submits a proposal for its next quarter allocation. Finance Circle checks alignment with purpose, then consent is sought from the Strategy Circle.
|
||
|
||
Hifz al-Nasl (preservation of community) depends on financial trust. When the treasury is opaque, the community fragments. When it is open, the community coheres. The Baitul Mal model is not nostalgia — it is the most advanced organizational finance system for distributed trust.
|
||
|
||
---
|
||
|
||
*End of Part 1. Part 2 (Sprint 2 continued) will include: Principle (Hukm), Protocol, and Muhasaba (Retrospective).* |