Auto-sync 2026-08-16 06:00:01

This commit is contained in:
Hermes Bot
2026-08-16 06:08:12 +08:00
commit e1d71a4ca8
32 changed files with 6072 additions and 0 deletions
+120
View File
@@ -0,0 +1,120 @@
# Sprint 3: Authority — Distributed Authority vs Centralized Command
**Maqsad:** Hifz alAql (Preservation of Mind / Clarity)
**Framework:** Authority Quadrant Command / Consent / Consult / Delegate
---
## 1. THE CHARTER
**Mithaq (Covenant)**
*We the people of this organization recognize that authority is not a prize to be seized, but an amanah to be carried. Clarity of authority preserves the mind (Hifz alAql) because ambiguity breeds confusion, resentment, and paralysis. Our covenant is this:*
*Authority shall be distributed to the closest point of competence, not hoarded at the top. Every role is a delegation (ikhtiyar) from the collective, revocable by consent. Command exists only where speed, safety, or sacred law require it—and even then, command is bounded by shura and hisbah.*
*We follow the sunnah of the Prophet ﷺ who delegated authority to governors, judges, and army commanders, yet remained accountable to the community. Consent-based decision making (sociocracy) mirrors classical ikhtiyar: the holder of a role may act within their domain unless a qualified objection arises. No one rules alone. No one is powerless.*
**ORG_DESIGNER:**
The charter declares a shift from “who has power over whom” to “who holds what clarity for what purpose.” Distributed authority is not anarchy; it is precision. Each role has a defined domain, and decisions are made by the person closest to the work, using consent of the circle.
**KHALIFAH:**
The Prophet ﷺ said, “Each of you is a shepherd and each of you is responsible for his flock” (Bukhārī). Authority is a trust (amānah) to serve, not to dominate. The Khilāfah distributed authority through wilayah (governance) and qaḍā’ (judiciary). Shura was not optional—it was the method for selecting leaders and deciding major matters. Command was reserved for emergencies (e.g., battle) and even then bounded by the Sharīʿah.
---
## 2. SPRINT STRUCTURE
**ORG_DESIGNER:**
This sprint, we build the *Authority Quadrant* as our structural backbone. Draw a 2×2 grid.
| | **Quick decision** | **Deliberate decision** |
|----------------|-------------------|------------------------|
| **High clarity** | **Delegate** Role holder decides alone, no consent needed. | **Consult** Role holder decides after seeking advice. |
| **Low clarity** | **Command** Leader decides with mandate, but bounded. | **Consent** Circle decides by raising objections. |
Every decision in the organization is classified into one of these four cells. The default (80% of decisions) should be **Delegate** or **Consent**. **Command** is an exception, not the rule.
We implement this through a **Role Constitution** document. Each circle (team) defines its roles, each role has a domain and a decision-making authority level. Any role holder can propose a change to their authority; the circle consents.
**KHALIFAH:**
This quadrant is not new. The classical Khilāfah used a similar structure:
- **Delegate (Tafwīḍ):** The Caliph delegated full authority to governors (wulāt) over their provinces, within the bounds of Sharīʿah. They acted without seeking permission for routine matters.
- **Consult (Shura):** The Caliph consulted senior companions (ahl al‑ḥall wa al‑ʿaqd) before declaring war or appointing judges. The decision remained his, but he was bound to listen.
- **Command (Amr):** In matters of urgent defense (jihād) or enforcing ḥudūd, a single commander could give binding orders. But even that commander was subject to hisbah (accountability) and could be removed by the Caliph.
- **Consent (Ijmaʿ or Muwāfaqah):** Major legislative matters required consensus of the scholars (ijmāʿ). In the organization, consent means no one in the circle has a reasoned objection. This mirrors the classical principle that a decision affecting the community requires their agreement unless harm is proven.
The Prophet ﷺ delegated authority to Muʿādh ibn Jabal when sending him to Yemen: “Facilitate, do not make difficult; give good news, do not repel.” He did not micromanage. He set principles (Sharīʿah) and trusted the delegate to apply them.
**When command is necessary:**
- **ORG_DESIGNER:** When a decision must be made in seconds (e.g., server outage, physical safety).
- **KHALIFAH:** When the Sharīʿah mandates a ruling (e.g., prohibition of ribā, enforcement of contracts). Command is not arbitrary; it is the execution of clear law.
This sprint, each circle will:
1. Define all roles and their decisionmaking authority level.
2. Create a “Decision Log” showing which quadrant applies to each type of decision.
3. Train every member on how to raise a consent objection vs a personal preference.
---
## 3. AUTHORITY MAP
**Ikhtiyar (Delegation) vs Command Consent vs Command**
**ORG_DESIGNER:**
The Authority Map is a living document. Draw a circle for each role. Inside the circle, write the roles **Domain** (what they own) and **Authority Level** (Delegate / Consult / Consent / Command). Outside the circle, write **Limits** (budget caps, policy boundaries, required approvals).
Example:
```
Role: Finance Lead
Domain: Approve expenses up to $10k, manage cash flow
Authority: Delegate (can act alone)
Limits: Cannot change budget allocations between departments without circle consent
```
This map is published transparently. Every member can see who holds what authority. This preserves Hifz alAql—no ambiguity, no power struggles, no secondguessing.
**KHALIFAH:**
Classical ikhtiyar was never absolute. The governor of a province had authority over taxation and defense, but could not change the Sharīʿah or impose new taxes without the Caliphs consent. The authority map is a modern version of the **ʿAhd (letter of appointment)** that the Caliph gave to each governor. It specified: “You shall judge by the Quran and Sunnah. You shall consult the people. You shall not take bribes.”
The Prophet ﷺ gave Muʿādh a clear authority map: “By what will you judge?” “By the Book of Allah.” “If not found?” “By the Sunnah of the Messenger of Allah.” “If not found?” “I will exert my own opinion (ijtihād).” The Prophet approved. That is delegation with boundaries.
**Consent vs Command:**
- **Consent** is the default for policy decisions that affect the whole circle. A proposal passes unless a circle member raises a **reasoned objection** based on harm to the organizations purpose or values. This is not consensus (everyone agrees) but consent (no one has a valid objection).
- **Command** is reserved for **clear rules** (Ḥukm Sharʿī) or **emergencies**. In a command, the leader decides alone but must explain their reasoning to the circle within 24 hours. The circle can then object and escalate.
**ORG_DESIGNER:**
The key insight: **Authority is not status; it is a service.** A role holder can be questioned about their decisions without it being insubordination. The hisbah (accountability) system ensures that authority is exercised with transparency.
**KHALIFAH:**
ʿUmar ibn alKhaṭṭāb used to walk the streets of Madinah at night, checking on the governors. He removed governors who acted unjustly. Authority without accountability is tyranny. The Authority Map makes every role holder visible and answerable.
---
## 4. TREASURY / BAYTUL MAL
**Baitul Mal as Trust Revenue, Allocation, Transparency**
**ORG_DESIGNER:**
Authority over money is the most sensitive domain. In this sprint, we establish the **Treasury Circle** with a clear authority map. The Treasury Circle holds the domain of “allocation of funds up to the annual budget approved by the General Circle.” Within that, the Treasurer role has **Delegate** authority for operational expenses up to 5% of the annual budget. Larger allocations require **Consent** of the Treasury Circle.
Transparency is nonnegotiable. Every transaction is logged in a public ledger (or at least accessible to all members). No secret budgets. No slush funds.
**KHALIFAH:**
Bayt alMal is a trust (amānah) for the Ummah, not the Caliphs personal treasury. The Prophet ﷺ distributed wealth immediately; he did not hoard. ʿUmar established a register (dīwān) to ensure fair distribution. The Caliph could not take a dirham without proper accounting.
The principle: **The one who holds the purse does not own the purse.** They are a steward. In the organization, the Treasurer must publish a monthly statement showing revenue, expenses, and reserves. Any member can request a detailed breakdown.
**Authority over Bayt alMal:**
- **Delegate:** The Treasurer can spend within predefined categories (e.g., salaries, rent, software subscriptions).
- **Consult:** For new initiatives under a certain threshold, the Treasurer consults the circle lead.
- **Consent:** Any change to the budget allocation or new expenditure above the threshold requires circle consent.
- **Command:** In a financial emergency (e.g., bank error, lawsuit), the Treasurer can act immediately but must report to the circle within 48 hours.
**ORG_DESIGNER:**
This sprint, each circle will define its own budget authority limits and publish them. The goal: **No one is surprised by where the money goes.** Clarity preserves Hifz alAql — no anxiety, no suspicion, no confusion.
**KHALIFAH:**
The Prophet ﷺ said, “The trustworthy treasurer who gives what he is commanded to give willingly is one of the two who give charity” (Bukhārī). Authority over the treasury is a form of charity when done with transparency and trust. We make it visible so that trust can flourish.