commit e1d71a4ca8f89cb3d561dd2d288ae830d11129de Author: Hermes Bot Date: Sun Aug 16 06:08:12 2026 +0800 Auto-sync 2026-08-16 06:00:01 diff --git a/chapters/Principle_01.md b/chapters/Principle_01.md new file mode 100644 index 0000000..15124b5 --- /dev/null +++ b/chapters/Principle_01.md @@ -0,0 +1,254 @@ +## Sprint 1: The Charter — Constitution Before Code + +**Maqsad:** Hifz al-Din (Preservation of Purpose) → Organizational Constitution +**Framework:** Constitution Quadrant: Purpose / Principles / Guardrails / Amendment Process + +--- + +### 1. THE CHARTER + +**We the people of this organization,** + +*In sacred trust with the Creator and in covenant with one another, do establish this Constitution as the foundation before any code, any product, any growth. Our purpose is not profit alone—it is service to humanity and stewardship of the earth. Our authority flows from consent, not command. Our treasury is a trust, not a prize. Our decisions are shaped by counsel, not coercion.* + +*We commit to:** + +1. **Evolutionary Purpose** — Our organization exists to fulfill a calling that emerges over time. We do not imprison it in a five-year plan. We listen, adapt, and respond. +2. **Distributed Authority** — No human being holds power over another except by consent and for a defined domain. Every role is a trust (amānah). Every leader is a servant. +3. **Radical Transparency** — Information flows freely. The books are open. The reasons are shared. +4. **Wholeness** — We bring our full selves: intellect, spirit, emotion, and body. We do not fragment into “professional” and “private.” +5. **Perpetuity** — We build to last. What we create becomes waqf—endowment for generations. + +*This covenant is our constitution. It binds us. It frees us.* + +**ORG_DESIGNER:** +This is your organizational DNA. Most startups write a mission statement and call it done. A constitution is different—it is the operating system that governs how you govern. Teal organizations don’t start with org charts; they start with purpose and principles. The charter answers: Why do we exist? How do we decide? What do we protect? Without this, your culture will be set by accident or by the loudest voice. + +**KHALIFAH:** +The Prophet ﷺ established the first covenant in Madinah—the Ṣaḥīfah (Constitution of Medina). It bound Muslims, Jews, and polytheists into one ummah with a shared purpose: defense and justice. It did not erase differences; it created a framework for cooperation. Your charter is your Ṣaḥīfah. Write it before you write a line of code. A constitution without enforcement is a prayer. A constitution without amendment is a prison. + +--- + +### 2. SPRINT STRUCTURE + +**ORG_DESIGNER:** +Build your constitution using the **Constitution Quadrant**: + +- **Purpose** — The evolutionary why. Not static. Example: “We exist to make Islamic finance accessible to every Muslim.” +- **Principles** — Immutable values that guide behavior. Example: “Consent before command.” +- **Guardrails** — Boundaries that prevent harm. Example: “No single person can approve their own compensation.” +- **Amendment Process** — How you change the constitution itself. Example: “Consent of 80% of full members after two weeks of deliberation.” + +In this sprint, draft all four quadrants. Do not move to structure until the charter is ratified by consent of the founding circle. + +**KHALIFAH:** +The classical khilāfah had no written constitution—but it had a living one: the Qur’an and Sunnah as supreme law, shūrā as method, and bay‘ah (pledge of allegiance) as the consent mechanism. Your constitution must be grounded in a higher authority (Allah) and yet remain adaptable to context. The Mālikī principle *al-‘āda muḥakkama* (custom is authoritative) means you can codify local practices as long as they don’t violate the sharī‘ah. + +**Draw four circles. Label them:** + +1. **Purpose Circle** — Why we gather. (Ṣalāḥ al-dīn — preservation of purpose) +2. **Principles Circle** — What we never compromise. (Uṣūl — roots) +3. **Guardrails Circle** — What we forbid ourselves. (Ḥudūd — boundaries) +4. **Amendment Circle** — How we evolve. (Tajdīd — renewal) + +**ORG_DESIGNER:** +Now map roles to each circle. The Purpose Circle is owned by the whole organization—no single person can change it. The Principles Circle is reviewed annually. Guardrails are enforced by a Hisbah Circle (see Sprint 9). Amendment requires supermajority consent. + +**KHALIFAH:** +The caliph ‘Umar ibn al-Khaṭṭāb (ra) once said, “We were the most disgraced people, and Allah honored us with Islam. If we seek honor through anything else, Allah will disgrace us.” Your purpose is your honor. Do not trade it for growth. + +--- + +### 3. AUTHORITY MAP + +**ORG_DESIGNER:** +Authority in a Teal organization is not “delegated from the top.” It is **distributed by consent**. Every role has a domain—a set of decisions they own. No one can override a role’s authority without a governance process. This is not democracy (majority rule) nor autocracy (one person decides). It is **consent**: a decision stands unless someone raises a reasoned objection that the decision harms the organization’s purpose. + +**Draw a simple map:** + +- **Circle** = self-organizing team with a shared purpose. +- **Role** = a domain of authority assigned to one person. +- **Lead Link** = a role that represents the circle to the broader org—but does not have command authority. +- **Objection** = a tension that a proposal will cause harm or regression. + +**KHALIFAH:** +Classical khilāfah understood *ikhtiyār* (delegation) as a trust, not a transfer of sovereignty. The khalīfah is chosen by bay‘ah (consent of the people of influence). He cannot rule by decree in matters of sharī‘ah. His authority is bounded by the shūrā council and the judiciary. The Ottomans formalized this in the *Qānūn*—but the principle remains: authority is revocable if the trustee violates the trust. + +**Map your authority with three layers:** + +1. **Sovereign Authority** — Belongs to Allah alone. No human or group can claim absolute power. This is your ultimate guardrail. +2. **Constitutional Authority** — The charter itself. No role can violate it. Amendment requires supermajority. +3. **Operational Authority** — Day-to-day decisions within domains. Consent-based, not command-based. + +**ORG_DESIGNER:** +In practice: if you are the “Product Lead,” you own the domain of product decisions. You do not need permission to set priorities—but you must process objections from anyone affected. If someone objects, you either adjust your proposal or explain why the objection is invalid (based on evidence, not status). + +**KHALIFAH:** +‘Umar (ra) famously held himself accountable: “If I am upright, follow me. If I deviate, straighten me.” Every leader in your organization must be willing to be corrected. That is the spirit of consent. + +--- + +### 4. TREASURY / BAYTUL MAL + +**ORG_DESIGNER:** +Money is the most common source of power corruption in organizations. A Teal organization treats revenue as a **means to purpose**, not an end. Compensation is transparent. Budgets are allocated by consent of the affected circles. Surplus is reinvested or returned to the community—not hoarded. + +**Start with these principles:** + +- **Transparency** — Every financial transaction is visible to all members. +- **Allocation** — Each circle has a budget approved by the broader governance. +- **Fair Compensation** — No ratio greater than 10:1 between lowest and highest paid (adjustable by consent). +- **Zakat/Charity** — A fixed percentage of net profit is given to causes aligned with the purpose. + +**KHALIFAH:** +Bayt al-Māl (the public treasury) in classical khilāfah was a trust for the ummah. The khalīfah could not spend a dirham without accountability. ‘Umar (ra) was known to check the accounts of his governors personally. The principle: *al-māl amānah* (wealth is a trust). + +**Practical steps for this sprint:** + +1. **Create a Treasury Circle** with rotating membership. This circle oversees all financial decisions. +2. **Publish a Financial Charter** that states: sources of revenue, allocation criteria, compensation formula, and audit frequency. +3. **Set a Transparency Baseline** — e.g., monthly open-book session where anyone can ask questions. + +**ORG_DESIGNER:** +If you cannot be transparent about money, your constitution is a lie. Start now. Even with zero revenue. Show the numbers. Show the salaries. Show the runway. + +**KHALIFAH:** +The Prophet ﷺ said, “The trustworthy treasurer who gives what he is commanded is one of the two givers of charity.” (Bukhārī). Your treasury team is not just managing money—they are fulfilling a trust. Treat them as such. Appoint them by consent, not by cronyism. + +--- + +*End of Part 1. Proceed to Part 2: Principle, Protocol, and Muhasaba.*## SHURA / CONSENT + +**ORG_DESIGNER:** +Consent is not consensus. Consensus demands everyone agrees. Consent asks: *“Is this proposal good enough for now, safe enough to try?”* One objection blocks a proposal in consent—but only if the objection is reasoned, not preference. In practice: circle meetings use a round-robin “consent round.” Each member states their tension, then a proposal is formed. Then a round of quick objections: “Any objection? If none, consent. If yes, we integrate the objection.” This keeps decision speed high and psychological safety intact. + +**KHALIFAH:** +Classical *shura* was never a vote. The *khalifah* consulted experts (*ahl al-hall wa al-aqd*), listened, then decided. But the decision was binding only if it aligned with the *shari’ah* (purpose). The *shura* was consent-based: no one could override the purpose. Umar ibn al-Khattab consulted widely on the *diwan* (registry) before adopting it. Consent meant: no participant was silenced; no decision violated the *mithaq*. Our modern parallel: each role-holder gives consent to proposals that align with the organizational *maqsad*. If a proposal violates purpose, it is an objection—not a whim. + +**Action for this Sprint:** +- Replace all majority-vote meetings with consent rounds. +- Train every circle: “Objection = reason based on purpose, not personal taste.” +- Use a simple tool (e.g., Loomio or physical cards) for asynchronous consent. + +--- + +## STEWARDSHIP / AMANAH + +**ORG_DESIGNER:** +Ownership is a liability, not a prize. Stewardship means: the role-holder is a temporary guardian of the domain. In Holacracy, each role has a *purpose*, *domains*, and *accountabilities*. The person filling the role has *authority* to act within those constraints—but they do not *own* the role. They steward it for the organization’s evolutionary purpose. This dissolves entitlement: no “my team,” no “my budget.” Everything is held in trust. + +**KHALIFAH:** +*Al-mal amanah*—wealth is a trust. The *baitul mal* is not the ruler’s private treasury. Umar ibn al-Khattab walked the streets at night to check on a widow’s provision. He was the *khalifah*, but he saw himself as a *mustakhliif* (one entrusted). In our organization, every budget allocation, every strategic decision, every hire—all are *amanah*. The steward must be able to account for resources and decisions. The *hisbah* (accountability) ensures no one hoards power or wealth. + +**Action for this Sprint:** +- Write a one-page “Stewardship Pledge” for every role-holder: “I hold this role as *amanah*; I will act within its domains and accountabilities.” +- Link each role’s budget to a measurable outcome (OKR). +- Create a public ledger (simple spreadsheet) showing who spent what and why. + +--- + +## CONFLICT / SULH + +**ORG_DESIGNER:** +Conflict is a signal of unprocessed tension. In Teal organizations, conflict is not suppressed or escalated to a boss. It is processed by the people involved using a structured process: the *Conflict Resolution Protocol*. Step 1: The person with the tension shares it directly with the other role-holder. Step 2: If unresolved, a facilitator mediates. Step 3: If still unresolved, the circle uses a consent-based ruling. No drama. No HR police. + +**KHALIFAH:** +*Sulh* (reconciliation) is the preferred Islamic method. The Prophet ﷺ said: “Make peace between you, for enmity is a razor.” The *qadi* (judge) would first attempt *sulh* before ruling. The goal is not to assign blame but to restore relationships and enable cooperation. In our organization, we assign a *sulh* facilitator for every circle—someone trained in neutral facilitation. They do not judge; they guide the parties to a mutual agreement that honors the *mithaq*. + +**Action for this Sprint:** +- Designate one person per circle as *sulh* facilitator (rotating monthly). +- Write a simple “Conflict Canvas”: What is the tension? What is the underlying need? What proposals resolve it? +- No conflict goes unresolved for more than one week. + +--- + +## SUCCESSION / ISTIKHLAF + +**ORG_DESIGNER:** +Succession is not an emergency plan—it is a continuous pipeline. Every role should have a *backup role-holder* who shadows, learns, and can step in. In Sociocracy, each circle elects a *delegate* and a *substitute* to the next circle. This creates natural succession. We also maintain *role documentation*: a living handbook that captures decisions, policies, and context. + +**KHALIFAH:** +*Istikhlaf* means to appoint a successor with care. Abu Bakr appointed Umar after extensive *shura* and observation. Umar knew the weight: he said, “If I fail, may Allah have mercy on Abu Bakr who appointed me.” Succession is a trust, not a popularity contest. In our organization, every leader must identify and mentor at least one potential successor. The *mithaq* requires that no key role remains without a named backup for more than 30 days. + +**Action for this Sprint:** +- For every role with budget authority or client responsibility, identify a backup role-holder. +- Create a “Succession Record” (one page per role): key decisions, current tensions, pending proposals. +- Schedule a monthly 15-minute handover practice: backup runs the role for one day. + +--- + +## HISBAH / ACCOUNTABILITY + +**ORG_DESIGNER:** +Accountability is not surveillance. It is *observability*. In modern orgs, we use transparent metrics, open dashboards, and regular retrospectives. The *hisbah* is a built-in feedback loop: each circle reviews its own metrics and tensions weekly. No external police needed. The system is self-correcting. + +**KHALIFAH:** +*Hisbah* was the institution of public accountability—not spying, but guidance. The *muhtasib* (inspector) would check markets for fraud, but also advise and remind. The goal was *amr bil ma’ruf wa nahi an al-munkar* (enjoining good and forbidding evil). In our organization, every circle elects a *muhtasib* (rotating quarterly) whose role is to check: Are we living our *mithaq*? Are we spending in line with purpose? No punishment—only a gentle nudge back to the covenant. + +**Action for this Sprint:** +- Appoint a *muhtasib* for each circle (quarterly rotation). +- Publish a “Health Dashboard” with 3–5 key indicators (e.g., consent decision backlog, budget variance, role fulfillment). +- The *muhtasib* holds a 15-minute weekly “Check-in” with the circle: “What is out of alignment with our *mithaq*?” + +--- + +## LEGACY / WAQF + +**ORG_DESIGNER:** +Exit is not the goal. Most startups build for acquisition. Teal organizations build for *perpetuity*. Legacy means the organization outlives its founders. We design *waqf-like* structures: profit is reinvested, ownership is distributed or held in a foundation, and intellectual property is open-sourced when possible. + +**KHALIFAH:** +*Waqf* is the ultimate Islamic legacy. The Prophet ﷺ said: “When a person dies, their deeds cease except three: ongoing charity, beneficial knowledge, or a righteous child who prays for them.” *Waqf* endows property for perpetual benefit—no one can sell it, inherit it, or divert it. In our organization, we create a *waqf* for our core asset (e.g., code, content, methodology). A trust board holds it for the *ummah*. Founders can still earn, but they cannot liquidate the purpose. + +**Action for this Sprint:** +- Identify one core asset (e.g., your playbook, software, curriculum) that could be “endowed.” +- Draft a simple *waqf* deed: “This asset is held in trust for the benefit of the Muslim community, never to be sold.” +- Form a *waqf* board of three trusted advisors (outside the org) to oversee the endowment. + +--- + +## THE PRINCIPLE (HUKM) + +**HUKM:** We establish a constitutional covenant (*mithaq*) that defines our organizational purpose, principles, guardrails, and amendment process, and all decisions and actions must be consistent with this covenant. + +**DALEEL:** The classical *khilafah* was founded on a *mithaq* (pact) between the ruler and the ruled—the *Bay’at*. Abu Bakr’s inaugural speech was a constitutional moment: “Obey me as long as I obey Allah and His Messenger; if I disobey, you owe me no obedience.” Modern Teal organizations use a similar constitution (e.g., Holacracy’s Constitution) to distribute authority and protect purpose. The *shari’ah* itself is a divine covenant; our organizational covenants mirror that trust. + +**MAQSAD:** Hifz al-Din (Preservation of Purpose). The *mithaq* ensures the organization’s *din* (way/ purpose) is not hijacked by individuals, short-term profit, or external pressure. It also serves Hifz al-Mal (Preservation of Wealth) by preventing misallocation, and Hifz al-Aql (Preservation of Intellect) by embedding clear decision-making rules. + +**SHURUT:** +- The *mithaq* must be written, reviewed, and consented to by every member. +- Any amendment requires a super-majority consent (two-thirds or unanimous) and a one-week cooling period. +- The *mithaq* must explicitly state the organization’s *maqsad* (purpose) as non-negotiable. +- A *majlis al-shura* (advisory council) of at least three people must be established to interpret the *mithaq* in case of ambiguity. + +**MUNKATHIRAT:** +- If the *mithaq* is violated by a founder or leader and no corrective action is taken within 30 days, the covenant is invalidated and a new one must be drafted. +- If the purpose is altered without proper amendment process, the organization loses its *teal* status and reverts to conventional hierarchy. +- If any single person holds veto power over the *mithaq* (i.e., can block any amendment unilaterally), the covenant is null. + +--- + +## THE PROTOCOL + +**STEP 1: Draft the Mithaq (This Sprint — Week 1–2)** +Gather all current members for a 2-hour workshop. Use the “Constitution Quadrant” framework: +- **Purpose:** Why do we exist? (Write one sentence.) +- **Principles:** 3–5 non-negotiable values (e.g., *amanah*, *shura*, *tazkiyah*). +- **Guardrails:** What is forbidden? (e.g., debt, interest, secrecy, unilateral power). +- **Amendment Process:** How will we change this? (e.g., 80% consent + 7-day notice). + +**STEP 2: Consent Round & Signing (Week 3)** +Present the draft in a circle meeting. Use a consent round: “Any objections?” Integrate all reasoned objections. Once consent is reached, each member signs (physically or digitally) the *mithaq*. Post it publicly on the org’s wiki or wall. + +**STEP 3: Embed & Test (Week 4)** +Create a “Mithaq Check” ritual: every Monday morning, the first 5 minutes of stand-up is reading one line of the *mithaq* aloud. Every decision with a budget > X (set a threshold) must cite the relevant principle. After 30 days, hold a retrospective: “Did the *mithaq* help us? What needs amendment?” + +--- + +## MUHASABA (RETROSPECTIVE) + +**Where did we shortcut the covenant because it was inconvenient?** + +One piercing question: *When did we override our own *mithaq* to get a deal done faster—and how did we justify it to ourselves?* +Reflect without shame. Write it down. Then ask: *What structural change (not just a promise) would prevent that shortcut from recurring?* +If no one can remember a single violation, you haven’t tested the covenant yet. Next sprint, invite a real pressure test. \ No newline at end of file diff --git a/chapters/Principle_02.md b/chapters/Principle_02.md new file mode 100644 index 0000000..46fc5b8 --- /dev/null +++ b/chapters/Principle_02.md @@ -0,0 +1,216 @@ +## 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).*## SHURA / CONSENT + +**ORG_DESIGNER:** +Consent is not consensus. Consent means “no objection” — not “everyone agrees.” In Sociocracy, decisions pass when no one has a reasoned objection that the circle cannot integrate. This is faster, more inclusive, and more accountable than unanimous consensus or majority vote. For the circle structure, consent applies to role assignments, policy changes, and resource allocations within each circle’s domain. Every circle member holds veto power *only* if they can argue the decision harms the circle’s purpose. Objections must be tested: “Does this decision prevent us from achieving our aim?” If yes, the proposal is refined. If no, it passes. + +**KHALIFAH:** +Classical Shura is not a show of hands — it is binding consultation (*shura mulzimah*). The Khalifah consults the *ahl al-hall wa al-aqd* (people of influence and expertise), but is not bound by their opinion if it contradicts Shariah or the public interest. Yet, the Prophet (sallallahu alayhi wa sallam) himself accepted majority opinion at Uhud against his own judgment. The principle: consultation is a trust, not a ritual. In a circle, the *amir* (lead) holds final authority, but must genuinely listen and weigh objections. Consent in circles mirrors the classical *ijma'* (consensus) of scholars — not unanimity, but lack of reasoned dissent. Both require psychological safety: “Do you have an objection grounded in purpose?” + +**PROMPT ANSWERED:** +*How do you consult at scale?* +- Each circle holds a Shura meeting weekly — 30 minutes. +- Proposals are submitted 24 hours in advance. +- Facilitator asks: “Any objections?” Objections are written down, not debated immediately. +- Objections are integrated into the proposal or tabled for a separate meeting. +*How does a Khalifah consult?* +- The Khalifah convenes a *majlis al-shura* representing all stakeholder groups. +- Decisions are deferred until no credible objection remains. +- The final decision is announced with a *hukm* (ruling) and *daleel* (reasoning). + +## STEWARDSHIP / AMANAH + +**ORG_DESIGNER:** +Stewardship means ownership is temporary, trust is permanent. In a circle structure, roles are not owned — they are held as *amanah*. Every role has a domain (scope of authority) and a purpose. The role holder is accountable to the circle, not to a boss. When someone vacates a role, the circle elects a replacement via consent. No one accumulates titles. Stewardship is demonstrated through transparency: all decisions, budgets, and role assignments are visible to the whole organization. This replaces the feudal model of “founder owns all.” + +**KHALIFAH:** +Classical *Khilafah* is a contract (*bay'ah*) between the ruler and the ruled. The ruler is a steward (*khalifah*), not an owner. The treasury (*bait al-mal*) is a public trust — the leader cannot spend on whims. Similarly, in your organization, every resource belongs to the collective purpose. The *amir* of a circle cannot allocate funds or people without circle consent. Succession is not inheritance — it is selection based on merit and trust. The Prophet (sallallahu alayhi wa sallam) said: “If a leader seeks authority, he is not entrusted with it” (hadith). Stewardship is earned, not taken. + +**PROMPT ANSWERED:** +*How do you ensure stewardship over ownership?* +- Ownership is replaced by *amanah* contracts: each role holder signs a *mithaq* (covenant) stating they will not use the role for personal gain. +- All circle domains are documented in a public “role register.” +- Annual *hisbah* audits check that every role’s decisions align with the circle’s purpose. +- If a role holder breaches trust, the circle can revoke the role by consent (super majority). +- No one holds a role for more than 3 years without re-election — prevents entrenchment. + +## CONFLICT / SULH + +**ORG_DESIGNER:** +Conflict is data. In a self-managing structure, tension is the engine of improvement. We do not suppress conflict — we process it. The *Sulh* (reconciliation) protocol: 1) The aggrieved party states the tension as a factual gap between “current reality” and “desired outcome.” 2) The other party responds only with clarification questions. 3) A third neutral circle member facilitates a session to propose a policy change. If unresolved, the conflict escalates to a higher circle (the “parent circle”). No personal attacks. No blame. Focus on role boundaries and purpose. + +**KHALIFAH:** +Classical *Sulh* is preferred over litigation. The Prophet (sallallahu alayhi wa sallam) said: “Reconciliation is permissible among Muslims, except a reconciliation that forbids what is halal or allows what is haram.” In an organization, sulh means restoring relationships, not punishing. The *muhtasib* (accountability officer) does not judge — he guides. When two circles conflict over resources, the *majlis al-shura* of the parent circle facilitates a *sulh* session. The outcome is a written agreement (*sulh-nama*) signed by both parties. If breached, the case goes to the *qadi* (internal judge) for binding arbitration. + +**PROMPT ANSWERED:** +*How do you resolve conflict at scale?* +- Step 1: Circle members first attempt *sulh* at the dyadic level — no facilitators. +- Step 2: If unresolved, they bring the tension to the circle’s governance meeting. +- Step 3: If still unresolved, the circle elects a *sulh* committee of three neutral members (from outside the circle). +- Step 4: The committee mediates within 48 hours. Their decision is binding unless appealed to the organization’s *shura* council. +- Scale mechanism: Every circle has a designated “conflict architect” role — trained in non-violent communication and Islamic sulh. + +## SUCCESSION / ISTIKHLAF + +**ORG_DESIGNER:** +Succession is not an emergency — it is a design feature. Every role has a “shadow” (deputy) elected by the circle. The shadow observes, learns, and can step in when the role holder is absent. Shadows are not second-class — they participate fully but without veto. The goal is zero bus-factor: if any person leaves, the circle continues without disruption. Succession also includes documentation: each role has a “playbook” (standard operating procedures) updated quarterly. The circle reviews shadows every six months and may replace them if they are not ready. + +**KHALIFAH:** +Classical *Istikhlaf* means appointing a successor before death or departure. The first Khalifah, Abu Bakr (ra), appointed Umar (ra) by consultation, not inheritance. The Prophet (sallallahu alayhi wa sallam) left no heir — he left a system: *shura* and *bay'ah*. In your organization, succession is not a founder’s choice. The circle elects the next *amir* (lead) via consent. The outgoing leader mentors the new one for one full cycle (sprint). No one leaves without transferring *amanah* — documented in a “succession handover” meeting recorded and signed. + +**PROMPT ANSWERED:** +*How do you design for continuity?* +- Every role has a “succession plan” documented in the circle’s governance register. +- The plan includes: name of shadow, training milestones, and a trigger (e.g., role departure, illness, resignation). +- The circle holds a “succession drill” once per year — simulate a sudden vacancy and test the shadow’s readiness. +- For critical roles (e.g., CEO, Treasurer), the succession plan is reviewed by the organization’s *majlis al-shura* every quarter. +- No role can be held by one person for more than 5 consecutive years — forces active pipeline development. + +## HISBAH / ACCOUNTABILITY + +**ORG_DESIGNER:** +Accountability is built into the structure, not imposed from above. In a circle, every role has a “circle” that holds them accountable through governance meetings. The *hisbah* function is not a police — it is a guidance system. We use “observability” not surveillance: all role outputs, budgets, and decisions are logged in a shared digital system. Any circle member can raise a “tension card” if a role is not fulfilling its purpose. The role holder must respond publicly within 48 hours. If repeated, the circle may elect a new role holder. + +**KHALIFAH:** +Classical *Hisbah* is a religious duty — “enjoining good and forbidding evil.” The *muhtasib* (inspector) checks weights, markets, and public morals, but always with *hikma* (wisdom) and *adl* (justice). In your organization, the *muhtasib* is a rotating role elected by the circle. They do not punish — they advise. They review role performance against purpose. They can call a “stop” on a decision if it clearly violates the organization’s *mithaq* (covenant). But they cannot override the circle; they must escalate to the parent circle. The goal is *muhasaba* (self-accountability), not *muraqaba* (surveillance). + +**PROMPT ANSWERED:** +*How do you guide without policing?* +- Each circle holds a monthly *muhasaba* meeting: review of role metrics, budget, and tensions. +- The *muhtasib* prepares a “guidance report” — no blame, only gaps and recommendations. +- The circle discusses the report using consent: any role holder can object if the guidance is unfair. +- If a role consistently underperforms, the circle can propose a “role review” — a facilitated process to reassign the role. +- No punitive actions (fines, demotions) without two prior warnings and a *sulh* attempt. +- The *muhtasib* publishes quarterly “health dashboards” — visible to the whole organization. + +## LEGACY / WAQF + +**ORG_DESIGNER:** +Legacy is not exit — it is endowment. The organization is designed to outlive its founders. We use a “Waqf” structure: the organization’s core assets (IP, brand, treasury) are donated to a trust (*waqf*) that cannot be dissolved. Founders and leaders are custodians, not owners. If the organization fails, the assets revert to the waqf to support other aligned projects. This removes the “exit” mentality — no one builds for acquisition. Instead, we build for *bakaa* (permanence). Every circle has a “legacy metric”: “Are we leaving this organization stronger than we found it?” + +**KHALIFAH:** +Classical *Waqf* is a perpetual charity — the asset is frozen in ownership, its benefit flows to the community. The Prophet (sallallahu alayhi wa sallam) said: “When a person dies, his deeds end except three: ongoing charity (*sadaqah jariyah*), beneficial knowledge, or a righteous child who prays for him.” An organization as waqf is a *sadaqah jariyah* — it keeps giving even after you leave. Your structure must be legally set up as a waqf (or equivalent trust). No one can sell the organization or distribute its assets to members. The *mutawalli* (trustee) is elected by the community, not appointed by founders. + +**PROMPT ANSWERED:** +*How do you build for perpetuity?* +- Step 1: Convert 51% of voting shares or ownership into a waqf trust with a deed that forbids dissolution. +- Step 2: The waqf’s *nazir* (supervisor) is elected by the organization’s *majlis al-shura* every 5 years. +- Step 3: Surplus revenue (after expenses and reserves) is invested in waqf assets (e.g., real estate, income-producing projects) that fund the organization’s mission perpetually. +- Step 4: Every circle must have a “legacy project” — something that will outlive the current team (e.g., open-source code, training programs, endowment). +- Step 5: No individual can withdraw capital — only the waqf can distribute funds for purpose-aligned activities. + +## THE PRINCIPLE (HUKM) + +**HUKM:** We establish a circular organizational structure where authority is distributed into autonomous circles, each governed by consent-based decision-making, with all roles held as *amanah* and all assets as *waqf*. + +**DALEEL:** The Prophet (sallallahu alayhi wa sallam) organized the community of Medina through multiple circles of *shura* — each tribe had its own council, but all were bound by the *Mithaq al-Madinah* (Constitution of Medina) which decentralized authority while unifying purpose. Modern organizational research (Laloux, Dignan) confirms that self-managing teams outperform hierarchies in adaptability, engagement, and innovation. The Islamic principle of *shura* (Qur’an 42:38) and *amanah* (Qur’an 4:58) provides the ethical foundation: authority is a trust, not a right. + +**MAQSAD:** This principle serves *Hifz al-Nasl* (preservation of community) by ensuring the organization survives and thrives beyond any individual leader. It also serves *Hifz al-Mal* (preservation of wealth) through waqf permanence, and *Hifz al-Aql* (preservation of intellect) by distributing decision-making to those closest to the work. + +**SHURUT:** +- Every circle must have a written *mithaq* (charter) defining its purpose, domain, and membership. +- Consent decisions require at least 2/3 of circle members present; objections must be documented and tested against purpose. +- No circle can have more than 12 members to maintain intimacy and trust. +- All role assignments must be reviewed every 6 months; shadows must be ready to step in within 2 weeks. +- The waqf trust deed must be legally binding and approved by a qualified Shariah advisor. +- A *hisbah* review of circle health must occur quarterly; if a circle consistently fails to meet its purpose, the parent circle may dissolve it. + +**MUNKATHIRAT:** +1. If any circle adopts majority voting instead of consent (except for emergency operations), the principle is nullified — the circle must be restructured. +2. If the waqf assets are used for non-purpose activities (e.g., personal profit, political lobbying), the waqf deed is violated and the organization loses its perpetual status. +3. If a role holder accumulates authority across more than three circles simultaneously without the \ No newline at end of file diff --git a/chapters/Principle_03.md b/chapters/Principle_03.md new file mode 100644 index 0000000..b900563 --- /dev/null +++ b/chapters/Principle_03.md @@ -0,0 +1,227 @@ +# Sprint 3: Authority — Distributed Authority vs Centralized Command + +**Maqsad:** Hifz al‑Aql (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 al‑Aql) 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 decision‑making 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 role’s **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 al‑Aql—no ambiguity, no power struggles, no second‑guessing. + +**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 Caliph’s 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 Qur’an 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 organization’s 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 al‑Khaṭṭā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 non‑negotiable. Every transaction is logged in a public ledger (or at least accessible to all members). No secret budgets. No slush funds. + +**KHALIFAH:** +Bayt al‑Mal is a trust (amānah) for the Ummah, not the Caliph’s 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 al‑Mal:** +- **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 al‑Aql — 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.## SHURA / CONSENT + +**ORG_DESIGNER:** +Consent ≠ Consensus. Consensus asks “Does everyone agree?” — that’s a bottleneck. Consent asks “Does anyone have a reasoned objection?” — that’s a release valve. In sociocracy, a proposal passes when no one can argue it would harm the circle’s purpose or degrade its ability to function. Speed + safety. At scale, you don’t gather 500 people in a room. You federate: each circle consents to its own decisions, then sends a delegate to the next circle. The delegate carries the circle’s tensions, not its vote. That’s how you consult at scale without collapsing into noise. + +**KHALIFAH:** +Classical shura was never a referendum. The Khalifah consulted with *ahl al-hall wa al-aqd* — the people of binding and loosening — not the entire ummah. Selection matters: those with relevant expertise, proximity, and trust. And the Khalifah was not bound by the result of shura but by the *process*. He had to listen, weigh, and then decide. That’s consent as a constraint, not a veto. The modern parallel: a circle’s domain gives it authority; outside that domain, it consults upward or sideways. Shura at scale requires clarity of mandate. Who decides what? That’s the question. + +**THE SYNTHESIS:** +Your organization’s shura structure must answer three questions: +1. Who has the right to be heard? (The circle with domain authority.) +2. What counts as a valid objection? (Harm to purpose, not preference.) +3. How do we escalate? (Delegate, not consensus.) + +## STEWARDSHIP / AMANAH + +**ORG_DESIGNER:** +Ownership is a feeling, not a legal structure. Stewardship is the practice of treating the role as a trust, not a possession. In distributed authority, no one *owns* a decision. They *hold* it for the circle. The test: can you hand it back without ego? That’s the fiduciary duty of every role. You are not the role; you are the caretaker. The pipeline is documentation: write down why you chose what you chose, so the next steward can understand, adapt, or override. + +**KHALIFAH:** +Amanah in the classical sense means the role is a loan from the community. The Khalifah’s oath (*bay‘ah*) was conditional: he could be removed if he violated the trust. The treasury (*bayt al-mal*) was not his personal fund. Today, every decision-maker must ask: “Am I acting for the organization’s purpose or my own comfort?” Stewardship is proven by transparency: publish the rationale, publish the metrics, publish the objections. If you can’t defend your decision to the next steward, you’ve broken the amanah. + +**THE PRACTICE:** +Every role has a “stewardship log” — a living document with the role’s purpose, key decisions, and the reasoning behind them. Updated weekly. Auditable by the circle. That’s how you ensure stewardship over ownership: make the invisible visible. + +## CONFLICT / SULH + +**ORG_DESIGNER:** +Conflict is not failure — it’s a signal that a tension has not been processed. In distributed authority, conflict is the system’s immune response. The mistake is to suppress it or escalate it to a “boss.” Instead, create a structured *sulh* process: a neutral facilitator, a timed conversation, and a consent-based resolution. The goal is not agreement; it’s clarity. Once the tension is named, the circle can adapt. Conflict becomes a retrospective question: “What is this tension telling us about our structure?” + +**KHALIFAH:** +Sulh (reconciliation) in Islamic tradition is a sacred act. The Quran calls it *khayr* (better). The Khalifah appointed *qadis* (judges) and *muhtasibs* (accountability officers) to resolve disputes before they fester. The principle: address conflict at the lowest possible level, with the smallest number of people, in the shortest time. Scale it only when the harm threatens the whole. The modern version: a “conflict resolution circle” that any member can activate. The facilitator is not a manager — they are a servant of the process. + +**THE PROTOCOL:** +When a conflict arises: +1. The involved parties name the tension in writing. +2. A trained facilitator (rotating role) runs a 30-minute structured dialogue. +3. The circle proposes a change to roles, domains, or policies to prevent recurrence. Consent decides. + +## SUCCESSION / ISTIKHLAF + +**ORG_DESIGNER:** +Continuity is not about finding the next CEO. It’s about designing the system so that any role can be filled without restarting. That means: clear role documentation, a mentorship pipeline, and a “successor readiness” metric. In distributed authority, every role holder is responsible for training their eventual replacement. The role is not a throne; it’s a station. The question is not “Who will replace me?” but “How do I make this role replaceable?” + +**KHALIFAH:** +Istikhlaf (succession) was a deliberate process. The Khalifah often designated a successor (*wali al-‘ahd*) but the bay‘ah (consent of the community) was required. The pipeline was public: the most qualified were known. Documentation was oral and written — the *sahifah* (scrolls) of the early caliphs. Today, your succession plan must be transparent to the circle. Every role has a “shadow” — a person learning the role. The shadow has access to all decisions, all tensions, all logs. That’s how you design for continuity: make the knowledge flow before the person departs. + +**THE PRACTICE:** +Every quarter, each role holder updates a “succession readiness” score (1-5) and nominates one or two potential successors. The circle reviews and ensures the shadow gets real exposure — not just observation but authority in training mode. + +## HISBAH / ACCOUNTABILITY + +**ORG_DESIGNER:** +Accountability in distributed authority is not top-down inspection. It’s *observability* — making decisions, metrics, and outcomes visible to the circle. The muhtasib (the role, not the person) is a guardian of the process, not the result. They ask: “Did the circle follow its own governance? Are tensions being processed? Are objections being heard?” The goal is guidance, not policing. If someone fails to meet their role’s purpose, the circle first asks: “Is the role designed correctly? Did we give them enough resources?” The hisbah is a feedback loop, not a punishment system. + +**KHALIFAH:** +The classical *muhtasib* was appointed by the Khalifah to oversee markets, weights, and public morals. Their tool was *nasiha* (sincere advice) first, then *ta‘dib* (correction). They did not spy or entrap. They corrected publicly when necessary, but always with the aim of restoring trust. Today, your hisbah circle does the same: it audits adherence to the *mithaq* (organizational covenant), flags inconsistencies, and recommends structural adjustments. It is not a secret police; it is a public function with a public log. + +**THE PRACTICE:** +Create a “Hisbah Dashboard” — visible to all — showing governance metrics: time to process tensions, number of objections raised, role update frequency. The hisbah circle (rotating members, 2-3 people) reviews once per sprint and publishes a one-page report. No names, no blame. Just system health. + +## LEGACY / WAQF + +**ORG_DESIGNER:** +Perpetuity over exit. That’s the waqf mindset. You are building an organization that can outlive its founders. That means the authority structure must be self-sustaining. No single person holds a veto. No single person decides the strategy. The circle holds the purpose. The waqf is the organization’s endowment — not just financial, but intellectual, relational, and procedural. Every decision you make should be documented in a way that a stranger could read it and understand the logic. That’s how you exit without breaking the system. + +**KHALIFAH:** +Waqf (endowment) in classical Islamic law was a perpetual trust. The property was dedicated to a charitable purpose, never to be sold or inherited. The organization’s *mithaq* is its waqf. The purpose — the *maqsad* — is the asset that cannot be traded. The roles are the trustees. The circle is the *mutawalli* (manager). Your job as a founder is to make yourself unnecessary. The question: “If I disappeared tomorrow, would the organization continue to serve its purpose?” If the answer is no, you haven’t built a waqf; you’ve built a monument to yourself. + +**THE PRACTICE:** +This sprint, identify one decision or role that depends on a single person. Design a “waqf handoff” — transfer the knowledge, the authority, and the documentation to the circle. The goal: by the end of this sprint, no critical role should have a single point of failure. + +## THE PRINCIPLE (HUKM) + +**HUKM:** +We distribute authority by domain, not by rank — every circle holds full decision-making power within its defined boundaries, subject to consent from affected circles and alignment with the organization’s purpose. + +**DALEEL:** +Distributed authority preserves Hifz al-Aql (clarity of mind) by removing confusion about who decides what. Classical khilafah delegated authority to governors, judges, and market supervisors, each with a defined *wilayah* (jurisdiction). Modern sociocracy and holacracy confirm that consent-based governance reduces bottlenecks and increases adaptive capacity. The evidence from both traditions converges: clear domains + consent = faster, wiser decisions. + +**MAQSAD:** +Primarily Hifz al-Aql (Preservation of Mind/Clarity) — distributed authority eliminates ambiguity, reduces cognitive load, and enables every member to act within their domain without seeking permission. Secondarily Hifz al-Mal (Preservation of Wealth) — faster decisions reduce waste and missed opportunities. + +**SHURUT:** +- Every domain must be explicitly documented in a circle’s governance record, including what decisions are inside and outside the domain. +- Any decision that affects another circle’s domain requires that circle’s consent (not mere consultation). +- The organization’s overall purpose and maqasid act as the ultimate constraint — no domain can authorize actions that violate the mithaq. +- A circle may delegate authority to a role, but the circle remains accountable for the role’s performance and may revoke or modify the delegation via governance. + +**MUNKATHIRAT:** +- Any decision made outside the defined domain is null and void unless explicitly ratified by the relevant circle within one sprint. +- If a circle consistently fails to process tensions or make decisions within agreed timeframes, the hisbah circle may temporarily suspend its authority and escalate. +- A single person accumulating multiple critical domains without documented succession and shadowing invalidates the distributed authority principle — that person must transfer domains or create shadows within one sprint. + +## THE PROTOCOL + +**STEP 1:** Map every decision in your organization to a specific circle or role. Use a simple spreadsheet: decision type, current decision-maker, domain boundary, and last governance review. Complete within 3 days. + +**STEP 2:** Identify any decision where the domain boundary is unclear or overlaps. Convene a 30-minute governance meeting between the affected circles to clarify boundaries. Use consent: each circle must agree that the boundary does not harm its ability to fulfill its purpose. Complete within 7 days. + +**STEP 3:** Publish the final domain map to the entire organization. Update the mithaq document to include a clause: “All decisions belong to the circle that holds the domain, unless explicitly delegated or escalated.” This sprint, no role or person may make a decision outside their documented domain without first obtaining consent from the affected circle. + +## MUHASABA (RETROSPECTIVE) + +**One piercing question:** +*Where did we make a decision this week that someone else should have made — and we didn’t even notice until now?* + +Uncomfortable because it exposes the habit of centralization. Actionable because the answer reveals exactly which domain boundary is missing. Write it down. Fix it next sprint. That’s how distributed authority grows from theory to muscle. \ No newline at end of file diff --git a/chapters/Principle_04.md b/chapters/Principle_04.md new file mode 100644 index 0000000..a5e49be --- /dev/null +++ b/chapters/Principle_04.md @@ -0,0 +1,256 @@ +# SPRINT 4: TREASURY — Baitul Mal as Tokenomics + +**MAQSAD: Hifz al-Mal (Preservation of Wealth)** +**FRAMEWORK: Treasury Quadrant — Revenue / Allocation / Transparency / Accountability** + +--- + +## 1. THE CHARTER (Mithaq) + +**We the people of this organization** — founders, contributors, stewards — declare that all wealth flowing through this body is *amanah* (trust), not private purse. The treasury is *Baitul Mal*: a sacred trust belonging to the mission, not to any single founder, investor, or manager. No one owns it. Everyone is accountable for it. + +We reject the modern heresy that organizational wealth is a founder's personal asset to be extracted, hoarded, or deployed without consent. We reject the startup myth that "founders take risk, therefore founders take all." Instead, we recover the classical principle: wealth is a *trust* from the Ummah (or the community served), to be preserved, grown, and allocated according to *Maqasid* — not according to whim. + +Our treasury operates on four pillars: +- **Revenue** — generated ethically, without riba, gharar, or exploitation +- **Allocation** — decided by consent, not command; prioritized by mission +- **Transparency** — every inflow and outflow visible to all stakeholders +- **Accountability** — open to hisbah (self-critique) at any time + +Tokenomics in this organization is not a fundraising gimmick. It is a *distribution mechanism* for trust. Tokens represent *rights and responsibilities* — not speculative claims. Liquidity is a tool, not a goal. Exit is not the objective; *waqf* (perpetuity) is. + +This charter binds every holder of treasury authority — from the finance circle to the smallest budget delegate. We sign with our names, our reputations, and our *akhirah*. + +--- + +## 2. SPRINT STRUCTURE (Hikma / Architecture) + +**ORG_DESIGNER:** +Draw four circles. Label them: + +1. **Revenue Circle** — owns all inflows: grants, sales, subscriptions, token mints. Domain: *source identification, pricing, fee structures, fundraising terms*. No revenue is accepted without a *mission alignment check* — does this funding source compromise our evolutionary purpose? + +2. **Allocation Circle** — owns all outflows: salaries, project budgets, reserves, investments. Domain: *budget proposals, consent-based approval, disbursement*. Every allocation must answer: "Does this serve the mission more than any other use of these funds?" + +3. **Transparency Circle** — owns the ledger: real-time dashboards, quarterly audits, community reporting. Domain: *data integrity, public access, anomaly detection*. All transactions are recorded on-chain or in an immutable log. + +4. **Accountability Circle** — owns the *hisbah* function: periodic reviews, conflict of interest checks, retrospective allocation audits. Domain: *calling out misalignment, proposing corrections, escalating to governance.* + +Each circle operates with consent-based decision making. No single person can veto a treasury decision alone, but any circle member can raise an objection that stops the process until resolved. + +**KHALIFAH:** +This maps directly to classical *Bayt al-Mal* structure. The *Khilafah* treasury had distinct *dawawin* (departments): + +- **Diwan al-Kharaj** — land tax revenue (your Revenue Circle) +- **Diwan al-Jund** — military stipends and salaries (your Allocation Circle, specifically personnel) +- **Diwan al-Khatam** — official correspondence and record-keeping (your Transparency Circle) +- **Diwan al-Hisbah** — market oversight and public accountability (your Accountability Circle) + +The *Khalifah* had no personal right to the treasury. Umar ibn al-Khattab (RA) famously said: "I have no more right to the treasury than a guardian has to the orphan's wealth. If I am wealthy, I take nothing. If I am poor, I take only what is necessary." The treasury was a *trust*, not a royal coffer. + +Modern tokenomics functions as the *Diwan al-Khatam* on steroids — an immutable public ledger. But the classical principle remains: *transparency is a right of the governed, not a PR gesture.* + +--- + +## 3. AUTHORITY MAP (Ikhtiyar / Delegation) + +**ORG_DESIGNER:** +Authority over treasury is *distributed by role, not by person*. No founder has unilateral spending power. No finance lead can redirect funds without consent. + +Map the authority as follows: + +- **Revenue Circle** has authority to *negotiate and accept* revenue up to defined limits (e.g., $10k per deal without governance consent). Above that, governance consent required. They cannot change the mission alignment criteria — that is a governance domain. + +- **Allocation Circle** has authority to *approve* budget proposals within the annual allocation plan. They cannot reallocate funds between major categories (e.g., from R&D to marketing) without governance consent. Every allocation must be *consented* — no one can force through a budget over an objection. + +- **Transparency Circle** has authority to *publish* all data. They cannot hide or delay. They have the right to *demand* documentation from any treasury transaction. Their authority is absolute on data — no one can override transparency. + +- **Accountability Circle** has authority to *pause* any allocation that raises a *prima facie* concern. They can call a governance meeting within 48 hours. They have no spending authority, only *stop authority*. + +This is *ikhtiyar*: delegated authority with clear domains and constraints. No role has absolute power. Every power is balanced by another role's check. + +**KHALIFAH:** +Classical *ikhtiyar* over *Bayt al-Mal* was never absolute. The *Khalifah* was a *delegate* of the Ummah, not a proprietor. When Umar ibn al-Khattab wanted to distribute the treasury of Iraq, he consulted *Shura*. When he was overruled, he accepted. + +The *Amil* (tax collector) had authority to assess and collect, but could not spend. The *Qadi* (judge) could audit the *Amil*. The *Sahib al-Haraj* (market inspector) could report irregularities. *Hisbah* was a *right of every citizen* — any individual could challenge a treasury decision in court. + +Your modern authority map mirrors this: *distributed oversight, no single point of failure, multiple paths for objection.* The key insight: *consent* over *command*. Classical *Shura* was not a ceremonial consultation — it was a binding mechanism that could block a *Khalifah*'s spending. + +The principle: *No one should be able to spend the trust alone.* + +--- + +## 4. TREASURY (Baitul Mal / Trust) + +**Revenue Sources:** +Classical *Bayt al-Mal* had five revenue streams: *Zakat* (obligatory charity), *Jizya* (protection tax from non-Muslims), *Kharaj* (land tax), *Ghanimah* (spoils of war), and *Fay* (property without conflict). Each had strict allocation rules per Shariah. + +Your organization maps these to: *subscriptions* (analogous to Zakat — recurring, predictable), *grants* (analogous to Fay — windfall, must be mission-aligned), *token sales* (analogous to Ghanimah — must be distributed fairly, not extracted), *service revenue* (analogous to Kharaj — earned through productive work). + +**Ethical Filter:** +No revenue from riba (interest), gharar (extreme speculation), or haram sources. If a grant comes from a foundation with questionable ethics, reject it. The mission is not for sale. + +**Allocation Priority:** +First: *operational sustainability* (salaries, infrastructure) — analogous to *Diwan al-Jund*. +Second: *mission programs* (product development, community grants) — analogous to *public works*. +Third: *reserves* (emergency fund, future projects) — analogous to *Bayt al-Mal surplus* stored for lean years. +Fourth: *distributions* (if any) — never to founders disproportionately; always proportional to contribution. + +**Transparency Standard:** +All transactions visible in real time. No dark budgets. No hidden reserves. Every contributor can query the treasury. Quarterly public audit. Classical *Bayt al-Mal* was so transparent that Umar ibn al-Khattab walked the streets at night with a ledger on his shoulder. + +**The Trust Principle:** +Your treasury is not your money. It is the *community's* money, entrusted to you temporarily. You are a *guardian*, not an owner. The moment you treat it as private purse, you have broken the *Mithaq*. This is not a metaphor — it is a *fiduciary duty* enforceable through organizational governance and, for those who take it seriously, through *akhirah* accountability. + +--- + +*End of Part 1. Continue to Part 2: Principle (Hukm), Protocol, and Muhasaba.*## SHURA / CONSENT + +**ORG_DESIGNER:** +Consent ≠ Consensus. Consensus seeks everyone’s agreement—slow, fragile, often lowest-common-denominator. Consent asks: “Is this proposal good enough for now, and safe enough to try?” No objections? It passes. Objection? The proposer and objector co-create an amendment. This scales from a 5-person circle to a 500-person organization. + +**KHALIFAH:** +Classical Shura was not a vote. It was a *majlis* of trusted advisors, each speaking from their domain expertise. The Khalifah listened, weighed, then decided—but with a binding norm: *no decision that violates the Mithaq or Shariah stands*. Consent mirrors this: authority to decide is held by the role, not by the crowd. Shura at scale means every circle has a representative to the next circle—a layered *ahl al-hall wal-aqd* (people of binding and loosening). + +**FRAMEWORK:** +- Every Treasury circle runs **Consent Decision-Making** for allocation proposals. +- Proposals are prepared in advance (48h reading time). +- Objections are not blocks—they are gifts. Each objection triggers a refinement round. +- Voting is replaced by *silence = consent*. + +**PROMPT ANSWERED:** +How do you consult at scale? You don’t consult everyone on everything. You distribute Shura to the circles that hold the tension. The Khalifah only consults the relevant *majlis*. Your Treasury’s Shura circle = the roles holding Revenue, Allocation, Transparency, Accountability. Everyone else gives input via tension cards, not votes. + +--- + +## STEWARDSHIP / AMANAH + +**ORG_DESIGNER:** +Stewardship over ownership. In Teal, no one “owns” the organization—they hold it in trust. Equity is replaced by *steward roles* with sunset clauses. The Treasury is not a purse to be maximized; it’s a trust to be deployed for purpose. + +**KHALIFAH:** +The *Baitul Mal* is a *Waqf*, not a private fund. The steward (*amin*) is a fiduciary under *amanah*. Any surplus belongs to the purpose, not to individuals. The Khalifah cannot sell the treasury; he can only allocate it. Your treasury roles must have term limits, auditable ledgers, and a duty to report to the Shura circle. Failure to account = *khiyanah* (breach of trust) and immediate removal. + +**FRAMEWORK:** +- Every Treasury role signs an *Amanah Agreement*—a covenant of fiduciary duty. +- Role holders cannot personally benefit from allocation decisions (no conflict of interest). +- Surplus beyond operating reserve (3 months) is automatically swept to a *Waqf pool* (see Legacy). +- Quarterly *Amanah audits*: public, raw, and acted upon. + +**PROMPT ANSWERED:** +How do you ensure stewardship over ownership? You make ownership impossible. No individual holds tokens that grant control. Treasury tokens are *voting rights for allocation only*, revocable annually. The organization owns itself. You are all custodians. + +--- + +## CONFLICT / SULH + +**ORG_DESIGNER:** +Conflict is energy. In Teal, we don’t suppress tension—we process it. Every objection is a signal that something needs attention. The Treasury will generate conflict: “Why did that project get funded and mine not?” “Why is the reserve so high?” Design a *Sulh process* that transforms complaint into proposal. + +**KHALIFAH:** +*Sulh* is reconciliation, not adjudication. The Khalifah appoints a *hakam* (arbitrator) from outside the circle. The goal is not who is right—it is *restoring the relationship and the purpose*. In the Treasury, conflicts over allocation go to a *Treasury Sulh Circle*: three members from unrelated circles, one external advisor. They hear both sides, propose a binding settlement. No appeals—only a new proposal for next quarter. + +**FRAMEWORK:** +1. **Tension Card** → submit to the circle (48h). +2. If unresolved → **Sulh Circle** convenes within 7 days. +3. Sulh decision is binding for the current sprint. +4. The root tension is logged as a *governance proposal* for the next retrospective. + +**PROMPT ANSWERED:** +How do you resolve conflict at scale? You ritualize it. You make it fast, cheap, and non-escalating. Sulh is not a court; it’s a conversation with a referee. No one wins or loses—everyone gets a better proposal. + +--- + +## SUCCESSION / ISTIKHLAF + +**ORG_DESIGNER:** +Succession is design, not accident. In Teal, every role has a *backup*—someone who can step in within 48 hours. Every role holder documents their *key tensions, decisions, and context*. The Treasury role is particularly sensitive: you cannot have a single point of failure. + +**KHALIFAH:** +*Istikhlaf* is the art of preparing the next Khalifah. The Prophet ﷺ did not leave a vacuum—he left a *shura* and a method. For the Treasury, the *Amin* (steward) must mentor a *Na’ib* (deputy) for at least one sprint before transition. The Na’ib has read-only access to all treasury ledgers. The *Istikhlaf Pipeline* is a governance circle that maintains a roster of vetted candidates for every critical role. + +**FRAMEWORK:** +- Every Treasury role lists a **backup** in the role charter. +- Monthly **shadowing sprint**: backup makes decisions, primary reviews. +- Quarterly **Istikhlaf review**: is the pipeline healthy? Are we breeding successors? +- If a role is empty for 30 days, the *Istikhlaf Circle* appoints a temporary steward by consent. + +**PROMPT ANSWERED:** +How do you design for continuity? You make every role replaceable. The organization must outlive any individual. The Treasury is a trust; the trustee is temporary. + +--- + +## HISBAH / ACCOUNTABILITY + +**ORG_DESIGNER:** +Hisbah is not police—it’s guidance. In Teal, we replace top-down auditing with *observability*. Every transaction on the Treasury ledger is visible to all role holders. No secrets. No hidden wallets. Accountability becomes self-correcting: if anyone sees a misallocation, they raise a tension. + +**KHALIFAH:** +The *Muhtasib* (overseer) in classical times did not spy—they made markets transparent. They checked weights, exposed fraud, and educated merchants. Your Treasury needs a *Muhtasib role* (elected, non-voting, rotating monthly). Their job: review every allocation proposal against the *Mithaq* and the *Maqasid*. If an allocation violates Hifz al-Mal (e.g., wasteful, risky, self-dealing), they issue a *nasihat* (advisory note). If ignored, they escalate to Shura. + +**FRAMEWORK:** +- **Observability dashboard**: real-time treasury flows, all wallets, all decisions. +- **Muhtasib role**: 1 person from a non-Treasury circle, monthly rotation. +- **Nasihat**: a public note attached to any proposal. Not a veto—a spotlight. +- **Monthly Hisbah report**: “What did we learn? Where did we almost fail? What improved?” + +**PROMPT ANSWERED:** +How do you guide without policing? You make everything visible. You appoint a guide, not a guard. The Muhtasib’s only power is to tell the truth. Trust the truth to correct the system. + +--- + +## LEGACY / WAQF + +**ORG_DESIGNER:** +Exit is not the goal. The organization is not a startup to be sold—it’s a *mission perpetual*. The Treasury should build a *Waqf* pool: a non-distributable, endowment-like fund that generates yield for the purpose. No one can ever liquidate it. It exists for the purpose, forever. + +**KHALIFAH:** +*Waqf* is the ultimate expression of *Hifz al-Mal*: wealth preserved for a cause that outlives the founders. The Prophet ﷺ said: “When a person dies, their deeds end except three: ongoing charity (sadaqah jariyah), beneficial knowledge, or a righteous child.” Your organization’s *Waqf* is its *sadaqah jariyah*. It funds the purpose even after you’re gone. + +**FRAMEWORK:** +- **Waqf pool**: 10% of all revenue automatically transferred to a separate, irrevocable endowment. +- **Waqf assets**: held by a legal entity with a charter that forbids dissolution. +- **Waqf returns**: used to fund *innovation grants* and *emergency reserves* only. +- **Exit prohibition**: no token holder can ever claim Waqf assets. It belongs to the *ummah* (community). + +**PROMPT ANSWERED:** +How do you build for perpetuity? You make the treasury immortal. You create a fund that cannot be destroyed, sold, or extracted. That is the *Waqf*—the organization’s soul. + +--- + +## THE PRINCIPLE (HUKM) + +**HUKM:** We establish the Treasury as a *Baitul Mal Waqf*—a trust fund governed by consent, observable to all, and perpetually dedicated to the organization’s evolutionary purpose. + +**DALEEL:** The classical *Baitul Mal* was a public trust, not a private treasury. The Khalifah Umar ibn al-Khattab (ra) distributed surplus annually and kept no personal access. Modern Teal organizations (e.g., Buurtzorg, Patagonia) embed similar trust-based financial governance. The *Maqasid* of Hifz al-Mal demands preservation, transparency, and purpose-aligned allocation. + +**MAQSAD:** Hifz al-Mal (Preservation of Wealth) – the Treasury must not be hoarded, wasted, or corrupted. It must be preserved for the purpose, not for individuals. Secondary Maqasid: Hifz al-Din (protecting the covenant) and Hifz al-Nasl (ensuring continuity for future members). + +**SHURUT:** +- All Treasury roles must be filled by consent, with term limits (max 2 sprints consecutive). +- Every allocation proposal must link to a specific *Maqsad* (purpose) and pass consent. +- The *Waqf pool* must hold at least 10% of all revenue, irrevocable. +- Observability: all treasury transactions visible to all role holders in real time (or within 24h). +- A *Muhtasib* role must be active and rotate monthly. + +**MUNKATHIRAT:** +- Any single role holder controlling >50% of treasury decision power (e.g., veto, sole signatory) nullifies this principle. +- Any secret allocation (unrecorded, hidden wallet, off-ledger transaction) immediately triggers a *crisis Shura* and may dissolve the current Treasury circle. +- If the *Waqf pool* is ever liquidated for non-purpose use (e.g., to pay salaries), the principle is breached and the organization must re-charter. + +--- + +## THE PROTOCOL + +**STEP 1: Audit Current Treasury (This Sprint, Days 1–3)** +List every wallet, account, and allocation. Publish raw data. Identify what is currently *not* observable. Create a *transparency gap* document. + +**STEP 2: Establish the Waqf Pool (Days 4–7)** +Transfer 10% of current surplus into a separate, irrevocable legal entity or smart contract. Write a simple charter: “This pool exists for the purpose [insert purpose]. It cannot be dissolved. Returns fund innovation grants and emergency reserves.” + +**STEP 3: Install Muhtasib Role (Day 8)** +Elect one person from a non-Treasury circle for a 30-day term. Give them read-only access and a *nasihat* template. First duty: publish a *Hisbah Report* on the transparency audit by Day 10. Present findings at the next Shura circle. + +--- + +## MUH \ No newline at end of file diff --git a/chapters/Principle_05.md b/chapters/Principle_05.md new file mode 100644 index 0000000..ab55db8 --- /dev/null +++ b/chapters/Principle_05.md @@ -0,0 +1,264 @@ +# SPRINT 5: SHURA — DECISION MAKING AT SCALE + +**MAQSAD: Hifz al-Nasl (Preservation of Community)** +*Consultation at Scale — Because a community that cannot decide together cannot survive together.* + +--- + +## 1. THE CHARTER (Mithaq) + +**We the people of this organization** establish this covenant: that all decisions affecting the whole are made through Shura—genuine consultation rooted in trust, not performance. We distinguish consent from consensus: a decision is valid when no one present has a reasoned objection, not when everyone agrees. We reject performative consultation where leaders have already decided. The Prophet ﷺ consulted his companions on matters as small as battlefield tactics (Uhud, Khandaq) and as large as succession (Saqifah). He listened, he changed course, he bound himself to the outcome. We do the same. Authority to decide is a trust (amanah), not a privilege. Every decision carries the weight of community preservation—Hifz al-Nasl. We will not fracture what we are building by ignoring voices or forcing unanimity. Shura is the method; consent is the discipline; community is the purpose. + +**Our Mithaq:** We consult before we command. We consent before we proceed. We inform before we implement. + +--- + +## 2. SPRINT STRUCTURE (Hikma / Architecture) + +**ORG_DESIGNER:** +Stop treating every decision like a referendum. You need a decision-making quadrant. Draw four boxes: + +| **INFORM** | **CONSULT** | +|------------|-------------| +| Decide → Notify | Gather input → Decide alone | +| **CONSENT** | **CONSENSUS** | +| Propose → No objection → Adopt | All agree unanimously or block | + +Each domain in your organization gets a default quadrant. Operational decisions (e.g., sprint task assignments) → **Consent** of the role holding the domain. Tactical decisions affecting a circle (e.g., tooling budget) → **Consent** of that circle. Strategic decisions affecting the whole organization (e.g., pivot product) → **Consent** of the full governance circle. Existential decisions (e.g., dissolution, merger) → **Consensus** or supermajority with safeguards. + +The mistake most orgs make: they default to Inform (top-down) or Consensus (paralysis). The sweet spot is Consent—fast enough to act, safe enough to protect. + +**KHALIFAH:** +The Prophet ﷺ operated a multi-level shura system. Draw three circles: + +1. **Inner Circle** (Ahl al-Hill wa al-Aqd – the people of binding and loosening): senior companions consulted on state matters. Their consent was binding for appointments of caliphs. Example: Abu Bakr's selection at Saqifah. + +2. **Outer Circle** (general public): consulted on matters affecting everyone, but not binding. Example: Prophet consulting the army at Uhud about whether to fight inside or outside Medina. + +3. **Executive Circle** (wulat – governors, judges): delegated authority to decide within their domain, but subject to review and removal if they violated shariah. + +Modern mapping: +- **Inform** = announcement of a decree that cannot be changed (e.g., shariah ruling). Rare. +- **Consult** = istishara: leader gathers input, decides. Prophet did this at Badr for positioning the army. +- **Consent** = ijma' of qualified representatives: the inner circle's no-objection. Binding. +- **Consensus** = ijma' of all believers. Practically impossible except for foundational matters (e.g., Quranic text). + +Your sprint structure: assign each decision type to one of these four modes. Document it. Test it. If you default to Inform for decisions that affect others, you are not practicing Shura—you are practicing tyranny, no matter how benevolent. + +--- + +## 3. AUTHORITY MAP (Ikhtiyar / Delegation) + +**ORG_DESIGNER:** +Authority in a Teal org is distributed by consent, not command. Every role has a domain: the exclusive right to make decisions in that area, unless someone raises a reasoned objection. This is not consensus—it's "I can act unless someone shows me this will harm the organization." The authority map for Shura looks like this: + +- **Who proposes?** The person with the tension or the role responsible for the domain. +- **Who consents?** The circle members whose domains are affected. They can object only with a reasoned argument (not preference) showing harm to the purpose. +- **Who informs?** Everyone else affected gets notification after the decision. + +Example: A product manager proposes a feature change. Domain: product roadmap. The consent group: engineering, design, customer success. If no one objects, she proceeds. If engineering objects (e.g., "this breaks our architecture"), the proposal is modified or tabled. If customer success objects (e.g., "this confuses users"), same process. No one votes. No one forces consensus. Objections are data, not obstruction. + +This is radically different from command hierarchy: "I decide, you execute." And different from pure democracy: "Everyone votes, majority wins." Consent respects the expertise of the role holder while protecting the whole. + +**KHALIFAH:** +The classical principle of *ikhtiyar* (delegation of authority) mirrors this. The khalifah does not decide everything. He delegates to governors, judges, and commanders—each with a defined domain. The condition: the delegate must act within shariah and consult when their decision affects others. + +The Prophet ﷺ delegated authority to Mu'adh ibn Jabal as governor of Yemen. He gave him a domain: judge according to Quran, then Sunnah, then his own reasoning (ijtihad). Mu'adh was not required to consult the Prophet for every case. But he was required to consult local scholars and community leaders for complex matters. + +The authority map for your organization: + +- **Domain holder** decides within domain, subject to consent of those affected. +- **Circle** decides matters affecting the circle, subject to consent of all members. +- **Organization-wide** decisions require consent of the governance circle (the modern Ahl al-Hill wa al-Aqd). + +No one has absolute authority. Authority is bounded by purpose (maqsad), shariah, and the community's welfare. If a leader violates these bounds, the community has the right to object—and if ignored, to remove. + +**The danger of performative Shura:** when a leader consults but has already decided. The Prophet ﷺ rejected this. At Hudaybiyyah, he consulted, then accepted the treaty despite many companions' emotional objections. He had genuinely listened; he made the decision based on revelation and strategic insight. But he never pretended to consult when the decision was already made. Performative Shura destroys trust faster than no consultation at all. + +Your authority map must make explicit: who decides, who consents, who informs. If you cannot write it down, you are not practicing Shura—you are practicing politics. + +--- + +## 4. TREASURY (Baitul Mal / Trust) + +**ORG_DESIGNER:** +Money decisions are the most sensitive. The Baitul Mal is not a private purse—it is a public trust. Every allocation must be transparent and consented by those who contribute or are affected. Use the Shura Quadrant for treasury: + +- **Operational expenses** (e.g., software subscriptions, rent) → Consent of the finance role or circle. Inform the organization. +- **Program budgets** (e.g., marketing campaign, event) → Consent of the circle that owns the program. Consult the finance circle. +- **Major capital** (e.g., hiring, acquisition, large investment) → Consent of the full governance circle. Full transparency: all data open to anyone who asks. + +The rule: no one can spend money that belongs to the community without the community's consent—either directly or through delegated representatives. This is not charity; it is fiduciary duty. + +**KHALIFAH:** +Umar ibn al-Khattab established the *diwan* (registry of stipends) after consultation with the senior companions. He did not decide alone. He consulted on who should receive, how much, and in what order of priority. The Baitul Mal was managed by a trusted treasurer (like 'Abdullah ibn al-Arqam) and accounts were publicly reviewed. + +Key principles: + +1. **Transparency:** Umar would announce the state of the treasury in the mosque. No secrets. +2. **Consultation on distribution:** The spoils of war were distributed after shura. The Prophet consulted before dividing the war booty of Hunayn. +3. **No private use:** The khalifah's personal expenses were separate. Abu Bakr took only what he needed from the treasury, and when he fell ill, he returned his stipend. + +Apply these to your org: every treasury decision goes through the Shura Quadrant. Publish the budget. Publish actuals. Let anyone raise an objection. If you hide financial data, you are not practicing Shura—you are practicing embezzlement, even if unintentional. + +**This sprint:** map your current treasury decisions to the quadrant. Find one decision that should move from Inform to Consent. Change it this week. + +--- + +*End of Part 1. Next: Part 2 — The Principle, Protocol, and Muhasaba.*## SHURA / CONSENT + +**ORG_DESIGNER:** +Consent is the operating system of scale. Not consensus—that’s a veto trap. Not majority vote—that’s a tyranny of the 51%. Consent asks: *“Can you live with this decision for now?”* One objection blocks; zero objections passes. This is how a 10,000-person organization decides without hierarchy. Sociocracy calls it the *Consent Decision-Making* process: proposal, clarifying questions, quick round, objection round, consent. + +**KHALIFAH:** +Classical Shura is not majority rule. It is *binding consultation* when the Khalifah delegates, and *advisory consultation* when he retains authority. The Prophet ﷺ consulted the Companions at Badr—he listened, then acted. Abu Bakr رضي الله عنه consulted the elders; Umar رضي الله عنه institutionalized a formal council. Shura scales when you define the domain: *“On this matter, you decide; on that matter, you advise.”* The Shura Quadrant is your tool. + +**THE FRAMEWORK:** +Draw one axis: **Impact** (Low → High). Second axis: **Urgency** (Low → High). Four quadrants: +- **Inform** (Low impact, Low urgency): Just tell people. +- **Consult** (High impact, Low urgency): Gather input, decide alone. +- **Consent** (High impact, High urgency): Propose, seek objections, decide as circle. +- **Consensus** (High impact, Very High urgency? Rarely): Use only for constitutional changes or values. Else it stalls. + +**MAQSAD (Hifz al-Nasl):** +Shura preserves the community’s cohesion. When people feel heard, they stay. When decisions are imposed, factions form. Consent preserves *nasl* — the lineage of trust. + +--- + +## STEWARDSHIP / AMANAH + +**KHALIFAH:** +Amanah is the soul of authority. The Khalifah does not *own* the treasury or the decision—he *stewards* it. Every role is a trust. Every vote is a responsibility. Umar رضي الله عنه said: *“I have been appointed over your affairs, and I am a trustee.”* Stewardship means you are accountable to the community, not to shareholders or a CEO. + +**ORG_DESIGNER:** +In Teal organizations, stewardship replaces ownership. Roles are domains, not possessions. You hold a role by consent—the circle gives it, the circle can take it back. No permanent power. No golden parachutes. The organization is a living system, not a machine to be owned. Stewardship is fiduciary duty to purpose, not to profit. + +**THE MECHANISM:** +- **Role Tenure**: Fixed term (e.g., 6 months). Renewable by consent. +- **Open Books**: Every circle member sees the baitul mal ledger. +- **Succession Plan**: Every key role has a deputy learning the ropes. +- **Accountability**: Quarterly *muhasaba* (self-accounting) published to the circle. + +**MAQSAD (Hifz al-Mal, Hifz al-Nasl):** +Stewardship preserves wealth and community. Without amanah, resources are looted; without trust, the community dissolves. + +--- + +## CONFLICT / SULH + +**ORG_DESIGNER:** +Conflict is a signal. In hierarchical orgs, conflict is suppressed or escalated. In Teal, conflict is a growth mechanism. We use *Integrative Decision Making*: each party states their tension, proposes a change, and the circle consents. No blame. No personal attacks. The system is the problem, not the person. + +**KHALIFAH:** +Sulh (reconciliation) is a sacred act in Islam. The Qur’an says: *“And reconciliation is better”* (4:128). The Prophet ﷺ resolved disputes through mediation, not punishment. In the Khilafah, the *qadi* (judge) first attempts sulh. Only when parties refuse do they adjudicate. Scale sulh by training facilitators in every circle. + +**THE PROTOCOL:** +- **Step 1**: The two parties meet with a neutral facilitator. Each speaks uninterrupted for 3 minutes. +- **Step 2**: Facilitator restates each perspective. Parties propose three possible solutions each. +- **Step 3**: Circle consents to one solution. If no consent within 30 days, escalate to next circle. + +**MAQSAD (Hifz al-Nafs, Hifz al-Nasl):** +Sulh preserves relationships. Conflict unresolved fractures the community. Hifz al-Nasl means protecting the social fabric. + +--- + +## SUCCESSION / ISTIKHLAF + +**KHALIFAH:** +Istikhlaf is the transfer of trust. Abu Bakr رضي الله عنه appointed Umar رضي الله عنه before his death—not by election, but by consultation and consent. The community later consented. Succession is not a crisis; it is a designed process. Every leader must groom a successor. The Prophet ﷺ left no will for worldly wealth, but he left a *sunnah* of delegation. + +**ORG_DESIGNER:** +In self-managing orgs, succession is built into role design. Every role has a *backup* or *apprentice* who shadows for at least one sprint. When the role-holder leaves, the backup steps in for a trial period. If the circle consents, they become the new holder. No hiring from outside without first looking inside. + +**THE MECHANISM:** +- **Role Shadowing**: Every role has a designated learner. +- **Knowledge Base**: All decisions and context documented in a shared wiki. +- **Trial Period**: New role-holder serves 1 sprint on probation. +- **Consent to Confirm**: Circle votes consent to make permanent. + +**MAQSAD (Hifz al-Nasl):** +Continuity preserves the community’s wisdom. Without istikhlaf, knowledge dies with the leader. + +--- + +## HISBAH / ACCOUNTABILITY + +**ORG_DESIGNER:** +Hisbah is observability, not policing. In Teal, accountability is peer-to-peer, not top-down. Every circle runs a *retrospective* each sprint: What worked? What didn’t? What will we change? Metrics are transparent. No one hides. The system is designed so that failure is visible and fixable. + +**KHALIFAH:** +The *muhtasib* (market inspector) in classical Khilafah ensured fair weights, honest trade, and public morality. But his job was *guidance* first, punishment second. He would advise, warn, and only then enforce. Hisbah at scale means every member is a muhtasib for their circle. You observe, you raise a tension, you propose a fix. + +**THE MECHANISM:** +- **Observability Dashboard**: Every circle publishes: decisions, metrics, objections, and learnings. +- **Peer Reviews**: Each sprint, two random peers review role performance. +- **Muhasaba Report**: At sprint end, each role writes a one-page self-accounting. +- **Hisbah Circle**: A rotating circle reviews systemic issues—no blame, only process improvement. + +**MAQSAD (Hifz al-Din, Hifz al-Mal):** +Hisbah preserves integrity. Without accountability, trust erodes. Hifz al-Din means the community’s moral compass stays true. + +--- + +## LEGACY / WAQF + +**KHALIFAH:** +Waqf is the ultimate act of perpetuity. You give away ownership so the benefit lasts forever. The first waqf was the mosque of Quba’. Umar رضي الله عنه endowed his land in Khaybar for the poor. An organization built as waqf does not exit—it continues serving. No IPO. No acquisition. No liquidation. The purpose is the shareholder. + +**ORG_DESIGNER:** +In Teal, legacy over exit. The organization is a living entity with its own purpose. Founders are stewards, not owners. Governance is designed so the org can survive its founders. The *Purpose Circle* holds the constitutional DNA. Change the constitution only by super-majority consent across all circles. + +**THE MECHANISM:** +- **Waqf Structure**: Ownership of assets (IP, treasury, real estate) is held by a non-profit trust. +- **Dividend Cap**: Profits reinvested or given to community—no personal enrichment beyond fair compensation. +- **Founder Exit**: Founder steps down. New leadership is elected by consent of all circles. +- **Perpetuity Clause**: Constitution forbids dissolution except by unanimous consent of all members and transfer to another waqf. + +**MAQSAD (Hifz al-Din, Hifz al-Nasl):** +Waqf preserves the mission for generations. Hifz al-Nasl means the community inherits a living institution. + +--- + +## THE PRINCIPLE (HUKM) + +**HUKM:** +We adopt the *Shura Quadrant with Consent* as our default decision-making method for all operational and governance decisions, with consensus reserved only for constitutional amendments. + +**DALEEL:** +The Qur’an commands: *“And consult them in the matter”* (3:159). The Prophet ﷺ used Shura variably—sometimes binding, sometimes advisory. The classical Khilafah evolved consent-based councils (ahl al-hall wa al-aqd). Modern sociocracy demonstrates that consent scales organizations up to thousands without hierarchy. Both traditions converge on one principle: decisions must be acceptable to those affected, not merely imposed. + +**MAQSAD:** +This principle serves **Hifz al-Nasl** (Preservation of Community) by ensuring decisions are made with broad acceptance, preventing fragmentation and factionalism. It also serves **Hifz al-Aql** (Preservation of Intellect) by channeling collective intelligence into every decision. + +**SHURUT:** +- Every circle must have a trained facilitator who understands the four quadrants and consent process. +- All decisions must be documented with: proposal, objections raised, and final consent. +- Any member can request a *time-out* to escalate if they believe a decision violates the constitution or a core value. +- Consent decisions are reviewed quarterly; if systemic objections emerge, the circle may revert to consult mode for that domain. + +**MUNKATHIRAT:** +- A single member exercising *blocking power* without a reasoned objection grounded in the circle’s purpose or values invalidates the principle (tyranny of the minority). +- Skipping the Shura Quadrant for high-impact decisions without explicit emergency override (unanimous consent of the circle) nullifies the decision. +- Failure to document decisions for one full sprint triggers a mandatory audit by the Hisbah circle. + +--- + +## THE PROTOCOL + +**STEP 1: Map Your Shura Quadrant** +This sprint, every circle draws the four quadrants on a whiteboard (Inform / Consult / Consent / Consensus). For each pending decision, the facilitator places a sticky note in the appropriate quadrant. All members must agree on the placement before proceeding. + +**STEP 2: Run One Consent Decision** +Pick one high-impact, urgent decision (e.g., budget allocation, role assignment). Follow the consent process: proposal, clarifying round, objection round. If any objection is raised, the proposal is adjusted until no valid objection remains. Record the final decision and objections in the circle’s log. + +**STEP 3: Retrospective on Shura** +At sprint end, hold a 30-minute *muhasaba* on the Shura process. Ask: *“Did we use the right quadrant? Did consent feel safe? Where did we default to consensus or majority vote?”* Publish findings to the whole organization. This sprint, you will have replaced fear with flow. + +--- + +## MUHASABA (RETROSPECTIVE) + +**One piercing question:** +*When was the last time you sat in a meeting where you stayed silent because you feared being seen as obstructive—and then later resented the decision?* + +That silence is the wound Shura heals. Next sprint, speak your objection early. Or design a system where silence means consent, not compliance. Which will you choose? \ No newline at end of file diff --git a/chapters/Principle_06.md b/chapters/Principle_06.md new file mode 100644 index 0000000..91a7dec --- /dev/null +++ b/chapters/Principle_06.md @@ -0,0 +1,266 @@ +## Sprint 6: Stewardship — *Amanah* as Accountability +**Maqsad:** *Hifz al-Amanah* (Preservation of Trust) — Stewardship Over Ownership + +--- + +### 1. THE CHARTER (*Mithaq*) + +**We the people of this organization** recognize that all authority, resources, and outcomes are *amanah* — a trust from the Divine, entrusted to us for a season. We reject the modern doctrine of ownership as absolute control. Instead, we hold every role, every asset, every decision as a stewardship to be returned with increase. + +**Our covenant:** +- None of us *owns* this organization; we are its *khalifah* (stewards) and *musta’min* (trustees). +- Our fiduciary duty runs not to shareholders alone, but to the *maqasid* — the higher purposes of preservation of faith, life, intellect, lineage, and wealth. +- We will govern our resources with the transparency of *Bait al-Mal*, the discipline of *hisbah*, and the humility of *shura*. +- Every role is a loan. Every surplus is a trust. Every decision will be accountable to those we serve and to the One who entrusted us. + +This charter binds us to stewardship over ownership, service over self, and legacy over exit. + +--- + +### 2. SPRINT STRUCTURE (*Hikma* — Architecture) + +**ORG_DESIGNER:** +Modern stewardship requires a structure that distributes accountability without fragmenting purpose. I propose a **Stewardship Circle** overlay on your existing holarchy. + +Draw three concentric circles: + +- **Inner Circle — The Stewards (Guardians of Purpose):** + 3–5 people holding the *mithaq* (charter) and *maqasid* (higher aims). They do *not* manage people; they protect the organization’s DNA. They have no operational authority — only the power to remove any role that violates the charter. + +- **Middle Ring — Operational Circles (Self-Managing Teams):** + Each circle owns a domain (e.g., Product, Revenue, Community). They govern themselves via consent. They report *outcomes*, not *tasks*. No middle managers. + +- **Outer Ring — Beneficiary Representatives (Shura Council):** + A rotating body of end-users, investors, or community members. They hold the right to *object* to any policy that harms the *maqasid*. Their voice is not advisory — it is structural. + +**KHALIFAH:** +This mirrors the classical *Khilafah* model with three distinct trusts: + +- **Khalifah (Steward)** — not a ruler, but a *guardian of the covenant* (the inner circle). +- **Wulat (Governors)** — the operational circles managing domains with *ikhtiyar* (delegated authority). +- **Ahl al-Hall wa al-‘Aqd (People of Loosening and Binding)** — the representative body that gives consent and can remove the *khalifah* if the trust is broken (your outer ring). + +The classical precedent is clear: the *khalifah* does not own the treasury; the *Bait al-Mal* is a trust. The *wulat* are appointed by consent, not command. The *ahl al-hall* are not rubber stamps — they are the structural conscience. + +**Sprint action:** +- Identify 3 people for your Stewardship Circle. +- Identify 3–5 beneficiary reps for your Shura Council. +- Redefine all current “ownership” language in your roles as “stewardship” language. + +--- + +### 3. AUTHORITY MAP (*Ikhtiyar* — Delegation) + +**ORG_DESIGNER:** +Authority in a stewardship model is not a binary (owner vs. employee). It is a **spectrum of delegation** bounded by consent. + +**The Stewardship Authority Quadrant:** + +| | **Decides** | **Consents** | +|---|---|---| +| **Operational** | Steward of Domain | Circle via consent | +| **Constitutional** | Shura Council | Stewardship Circle | + +- **Operational decisions** (how to build a feature, how to spend a sprint budget) belong to the domain steward — but only within boundaries set by consent from their circle. +- **Constitutional decisions** (changing the charter, altering the *maqasid*, selling the organization) require consent from the Shura Council *and* the Stewardship Circle. + +This replaces command hierarchy with **nested circles of delegation**. No one has absolute authority. Every authority is *ikhtiyar* — permission granted by trust, revocable by breach. + +**KHALIFAH:** +The classical concept of *ikhtiyar* is precisely this: delegated authority with *shurut* (conditions). A *khalifah* does not rule by whim; authority is *mashrut* (conditional). The *khalifah* cannot change the *shari‘ah* (the constitution); the *wulat* cannot overstep their *wilayah* (domain). + +In *Siyar* (Islamic law of governance), the *khalifah* delegates authority to a *wali* (governor) with explicit *shurut*: +- You may collect taxes *only* according to the fixed rates. +- You may appoint deputies *only* with my consent. +- You may not declare war without the *shura* council. + +Violation of *shurut* nullifies the delegation (the *munkathir*). + +**Sprint action:** For every role in your organization, write down: +- **Domain** (what is this role responsible for?) +- **Authority** (what can they decide alone?) +- **Shurut** (what conditions bind their authority?) +- **Munkathirat** (what actions would immediately revoke their delegation?) + +This map replaces job descriptions with **stewardship contracts**. + +--- + +### 4. TREASURY (*Bait al-Mal* — Trust) + +**ORG_DESIGNER:** +In a stewardship organization, revenue is not profit; it is *surplus entrusted for purpose*. The treasury must be transparent, rule-bound, and protected from capture by any single circle. + +**Three Treasury Principles:** + +1. **All revenue is *amanah*.** No one “owns” the surplus. Every dollar is allocated to *maqasid*: preservation of the mission, the people, and the community. +2. **Budgets are set by consent, not command.** Each circle proposes an annual budget. The Stewardship Circle checks for alignment with *maqasid*. The Shura Council checks for fairness. Objections are resolved before funds are released. +3. **Transparency is structural.** Every transaction is visible to all stewards (circle members). No secret reserves. No founder slush funds. + +**KHALIFAH:** +The classical *Bait al-Mal* was a public trust, not a private treasury. The *khalifah* had no personal claim on it. Revenue (from *zakat*, *kharaj*, *ghanimah*) was collected and distributed according to *shari‘ah* rules — not the ruler’s whim. + +Key classical rules you can adopt: +- **No deficit spending without consent** (the *khalifah* could not borrow without the *ahl al-hall*). +- **Surplus is redistributed** (not hoarded for the next quarter). +- **Accounts are audited publicly** (the *muhtasib* had access to all records). + +**Sprint action:** +- Publish your current revenue and expense data to all stewards (circle members). +- Create a **Treasury Policy** document with three rules: (1) No individual can authorize spending above a fixed threshold alone. (2) All spending must map to a *maqsad*. (3) A quarterly public audit. +- Allocate 10% of surplus to a **Waqf (endowment)** fund — untouchable capital for long-term mission. + +This turns your bank account from a private fund into a public trust.## SHURA / CONSENT + +**ORG_DESIGNER:** +Consent is not consensus. Consensus requires everyone to agree—often leading to watered-down decisions or paralysis. Consent asks: “Is this proposal good enough for now, and safe enough to try?” One objector blocks only if they identify a concrete harm to the organization’s purpose. This is the Sociocracy 3.0 standard: minimal viable agreement, maximum speed. + +**KHALIFAH:** +Classical Shura was not a vote. The Khalifah gathered experts—*ahl al-hall wa al-aqd* (the people of binding and loosing)—and listened until the best path emerged. Abu Bakr consulted the Companions before invading apostate tribes; Umar consulted before creating the *diwan* (registry). Shura is binding when the matter is public interest (*maslahah*), but the Khalifah retains the final *ikhtiyar* (delegated authority) to decide after hearing all voices. Today, scale demands structured consent rounds, not chaotic meetings. + +**Mapping:** +- **Sociocracy consent** = Modern *shura* with time-boxes and facilitation. +- **Consensus** = paralysis masked as unity. Avoid it. +- **Classical Shura** = consent with *ikhtiyar* retained by the steward. + +**Prompt applied:** +How do you consult at scale? Use a **Shura Council** (3–7 rotating members) with consent on all policy proposals. The Khalifah (CEO) has final *ikhtiyar* only for operational urgency; strategic decisions require council consent. + +--- + +## STEWARDSHIP / AMANAH + +**ORG_DESIGNER:** +Ownership mindset kills stewardship. Owners hoard; stewards pass through. The **Stewardship Quadrant**: +- **Owner** – holds title, extracts value. +- **Steward** – holds trust, grows value for others. +- **Beneficiary** – receives value. +- **Trustee** – ensures value endures beyond self. + +Your org must shift from “I own this role” to “I am a steward of this role for the next person.” + +**KHALIFAH:** +*Amanah* is the root. Allah commands: “Indeed, Allah commands you to render trusts to whom they are due” (4:58). The Khalifah does not own the treasury (*baitul mal*)—he is a *mustakhlih* (one entrusted). Umar ibn al-Khattab walked the streets at night checking on the *baitul mal* accounts. Every role is a *wadi’ah* (deposit). **Fiduciary duty** means you must leave the role better than you found it. + +**Prompt applied:** +How do you ensure stewardship over ownership? +- **Role charters** include a “succession clause”: every steward must document knowledge and train a successor within 6 months. +- **No one holds a role longer than 3 years** without re-appointment by consent. +- **Performance reviews** measure *amanah* first: “Did you protect and grow this trust?” + +--- + +## CONFLICT / SULH + +**ORG_DESIGNER:** +Conflict is data. In Teal organizations, tension is processed through governance meetings, not suppressed. Use the **Conflict Resolution Protocol**: +1. **Objection** – state the tension (not the person). +2. **Sulh session** – facilitated dialogue with no blame. +3. **Proposal for repair** – concrete change to role, domain, or process. + +**KHALIFAH:** +*Sulh* (reconciliation) is a pillar of *siyasa shar’iyyah*. The Prophet ﷺ said: “Reconciliation is permissible between Muslims, except reconciliation that forbids what is lawful or permits what is unlawful.” Umar appointed *qadis* (judges) to resolve disputes before they escalated. In an organization, every unresolved conflict is a *fasad* (corruption) that erodes trust. + +**Prompt applied:** +How do you resolve conflict at scale? +- **Designate a *Hakam* (mediator)** – a neutral circle member trained in *sulh*. +- **Time-box**: conflict must be raised within 48 hours; session within 1 week. +- **Outcome**: either a binding *sulh* agreement or escalation to a consent vote by the Shura Council. + +--- + +## SUCCESSION / ISTIKHLAF + +**ORG_DESIGNER:** +Succession is not a crisis plan—it is a continuous pipeline. Every role must have a **Succession Map**: +- **Deputy** – ready now. +- **Apprentice** – being groomed (6–12 months). +- **Pipeline** – 2–3 potential candidates in the org. + +**KHALIFAH:** +*Istikhlaf* (appointing a successor) was practiced by every Khalifah. Abu Bakr appointed Umar before his death, and then Umar appointed a *shura* of six to choose his successor. The principle: **never leave a vacuum**. The *baitul mal* and *imarah* (governance) must continue without disruption. + +**Prompt applied:** +How do you design for continuity? +- **Every role owner must nominate a deputy** within 30 days of appointment. +- **Quarterly “succession sprints”** – the deputy shadows and learns all operational decisions. +- **Documentation**: each role has a *Risala* (handbook) that is updated every sprint. + +--- + +## HISBAH / ACCOUNTABILITY + +**ORG_DESIGNER:** +Accountability without micromanagement. Use **observability** (dashboards, transparent metrics) instead of policing. In Holacracy, each circle has a *Lead Link* who monitors role execution—but they do not control how. Guidance comes from real-time data, not boss orders. + +**KHALIFAH:** +*Hisbah* is the duty to enjoin good and forbid evil. The *Muhtasib* (market inspector) did not spy—he guided. Umar appointed inspectors who would advise merchants on fair weights and remind them of *taqwa*. The goal was *nasihah* (sincere advice), not punishment. + +**Prompt applied:** +How do you guide without policing? +- **Create a *Hisbah Circle*** (not a police squad) – its mandate is to publish anonymized metrics (e.g., “role completion rate: 92%”) and offer coaching. +- **No punitive action without a *sulh* session first.** +- **Quarterly *Muhasaba* (self-accountability) report** – each steward publishes their own honest assessment of *amanah* breaches. + +--- + +## LEGACY / WAQF + +**ORG_DESIGNER:** +Exit strategies are for startups. Stewardship orgs build for perpetuity. The **Waqf model** means the organization owns itself—no single founder can sell it. The *baitul mal* holds equity; profits fund the mission, not exit payouts. + +**KHALIFAH:** +*Waqf* is a perpetual sadaqah. The Prophet ﷺ said: “When a person dies, his deeds cease except three: ongoing charity, beneficial knowledge, or a righteous child who prays for him.” An organization as *waqf* means its purpose outlives every person. Umar’s *waqf* of the land of Khaybar funded generations. + +**Prompt applied:** +How do you build for perpetuity? +- **Convert founder equity into a *Waqf* trust** – the organization’s purpose is the beneficiary. +- **No individual can dissolve the org** without unanimous consent of the Shura Council and a 2/3 majority of all stewards. +- **Surplus revenue** must be reinvested or given as *sadaqah*—never distributed as dividends. + +--- + +## THE PRINCIPLE (HUKM) + +**HUKM:** We adopt **Stewardship Over Ownership** as the foundational principle: every role, resource, and decision is held as *amanah* (trust), not personal property, and must be transferred or renewed through consent-based processes with documented succession. + +**DALEEL:** Evidence from revelation and practice: +- Qur’an 4:58 commands rendering trusts to their owners. +- The Prophet ﷺ said: “Each of you is a shepherd and each of you is responsible for his flock” (Bukhari). +- Umar’s *baitul mal* records and his refusal to own even a camel from public funds demonstrate that leadership is *amanah*. +- Modern research (Laloux, Dignan) shows that self-managed organizations outperform hierarchies when stewardship replaces ownership. + +**MAQSAD:** This principle serves **Hifz al-Amanah** (Preservation of Trust) and **Hifz al-Mal** (Preservation of Wealth) by ensuring resources are protected, grown, and passed on rather than extracted or wasted. + +**SHURUT:** +- Every role must have a written *Risala* (charter) that defines its *amanah* boundaries. +- Succession plans must be maintained for all critical roles and reviewed quarterly. +- No role may be held for more than 3 consecutive years without a consent-based re-appointment. +- Financial assets in the *baitul mal* must be transparent to all stewards via real-time dashboards. + +**MUNKATHIRAT:** +- If any leader treats organizational assets as personal property (e.g., using funds without *shura* consent), the stewardship principle is nullified for that role, triggering immediate *hisbah* review. +- If succession plans are absent for more than 6 months in a critical role, the principle is violated and the Shura Council must appoint an interim steward. +- If consent is overridden by unilateral command on a strategic decision (operational urgency excepted), the *ikhtiyar* delegation is revoked until a *sulh* session restores trust. + +--- + +## THE PROTOCOL + +**STEP 1: Define Amanah Boundaries (This Sprint)** +For each role in your org, write a one-sentence *amanah statement*: “I hold this role for [beneficiary/entity] with the duty to [responsibility] and must transfer it to [successor name] by [date].” Publish in the org’s governance repository. + +**STEP 2: Establish Succession Pipeline (Within 2 Weeks)** +Every role owner must nominate a deputy and begin a weekly 30-minute shadowing session. Update the *Risala* with key processes, passwords, and contact lists. The Shura Council verifies completion. + +**STEP 3: Install Hisbah Observability (By Sprint End)** +Set up a dashboard with three metrics: *amanah score* (self-assessment), *succession readiness* (percentage of roles with deputy), and *baitul mal transparency* (all transactions visible). No dashboards? No stewardship. + +--- + +## MUHASABA (RETROSPECTIVE) + +**One piercing question:** +*Where have I treated this role as my possession rather than a trust, and what am I afraid to release?* + +Answer honestly. Write it down. Share it with your deputy. Then schedule a *sulh* session with yourself: the old you who hoarded, and the steward you will become. The organization does not need your ownership—it needs your *amanah*. If you cannot let go, you were never a steward. \ No newline at end of file diff --git a/chapters/Principle_07.md b/chapters/Principle_07.md new file mode 100644 index 0000000..2b8961b --- /dev/null +++ b/chapters/Principle_07.md @@ -0,0 +1,262 @@ +**SPRINT 7: CONFLICT — SULH AS ORGANIZATIONAL RETROSPECTIVE** +*Maqsad: Hifz al-Nafs (Preservation of Wellbeing) → Conflict as Growth* + +--- + +### 1. THE CHARTER + +We the people of this organization covenant that conflict is not a breakdown of order but a signal of growth waiting to happen. We reject the silent wound—the grudge buried in a meeting, the resentment that becomes policy by neglect. We commit to *Sulh* (reconciliation) over mere compromise. Compromise leaves both parties smaller; *Sulh* restores *fitrah*—the original balance where each role, each soul, returns to its *amanah* undiminished. + +The Prophet ﷺ said, “*Sulh* is permissible among the Muslims, except a *sulh* that makes lawful what is unlawful or makes unlawful what is lawful” (Abu Dawud). He resolved the Black Stone dispute by inviting each tribe to hold the cloth—not by splitting the stone. He did not avoid the tension; he elevated it into shared honor. + +Our retrospective (*Muhasaba*) is the mirror of *Sulh*. We do not blame; we uncover the *tension* that was trying to speak. Every objecting voice is a *nasihah* (sincere advice) wrapped in friction. We protect *Hifz al-Nafs*—the wellbeing of every member—by making conflict safe, structured, and sacred. We do not fear the fire; we build a forge. + +--- + +### 2. SPRINT STRUCTURE + +**ORG_DESIGNER:** +Modern teams treat conflict as a personal failure or a distraction. That’s a waste. In Teal and Sociocracy 3.0, conflict is a *governance tension*—a gap between current reality and the organization’s purpose. The structure to harvest it is the **Conflict Quadrant**: + +``` + ACCOMMODATE COLLABORATE + (Yield) (Sulh) + | | + LOW ASSERTION HIGH ASSERTION + HIGH COOPERATION HIGH COOPERATION + | | + -----------+--------------------+----------- + | | + AVOID COMPETE + (Flee) (Fight) + LOW ASSERTION HIGH ASSERTION + LOW COOPERATION LOW COOPERATION +``` + +Most teams live in Avoid (silence, email chains) or Compete (politics, power struggles). We need a **Sulh Sprint**—a structured, time-boxed process that moves from any quadrant to Collaborate. The sprint is 2 weeks. First week: raise tensions as *objections* (not complaints). Second week: facilitated *Shura* session where each objection is processed with consent, not majority vote. Output: a **Sulh Agreement** (a written amendment to a circle’s domain or role). This is not therapy; it is governance. + +**KHALIFAH:** +The Prophet ﷺ institutionalized conflict resolution at multiple levels. In Madinah, every tribe had its own *hakam* (arbiter), but the final authority was the *Shura* of the *Sahabah*. The principle: *al-Sulh khayr* (reconciliation is better)—not because conflict is bad, but because *fitnah* (division) destroys *ummah*. The classical *Hisbah* system had *muhtasib* who mediated marketplace disputes—not with punishment first, but with *nasihah* and *sulh*. + +Map this to your org: +- **Circle-level conflict** → handled by the circle’s *lead link* (like a *qadi* of that domain) +- **Cross-circle conflict** → escalated to a *Sulh Committee* (two representatives from each circle + one neutral *hakam* appointed by the *Shura* council) +- **Constitutional conflict** → goes to the *Mithaq* review—does the tension reveal a flaw in the charter? That’s *Muhasaba*. + +The sprint structure mirrors the *Sulh* of the Prophet ﷺ in the Treaty of Hudaybiyyah: +1. **Identify the tension** (the violated *amanah* or domain boundary). +2. **Name the *haqq* (right)** that was harmed. +3. **Propose a restoration**—not a compromise that dilutes purpose, but a *sulh* that returns each party to their *fitrah*. + +**Visual for this sprint:** +Draw a circle. Inside, a smaller circle labeled **Circle Sulh**. From that circle, draw three arrows: +- Arrow 1: **Tension → Objection** (formally logged in a *Sulh Register*) +- Arrow 2: **Objection → Shura Session** (consent decision, not vote) +- Arrow 3: **Shura → Domain Amendment** (updated in the *Governance Record*) + +Sprint length: 2 weeks. No conflict is “too small.” The smallest tension is the *dharrat* (atom) of a larger pattern. + +--- + +### 3. AUTHORITY MAP + +**ORG_DESIGNER:** +Authority in conflict resolution must be *distributed*, not hoarded. In Holacracy, any role can raise an objection to a proposal. The *Facilitator* holds process authority—not content authority. The *Lead Link* holds domain authority—but cannot override a consent objection. The *Secretary* holds record authority—the *Sulh Agreement* must be documented. + +The problem: most orgs give the CEO or manager the final say. That’s *command* conflict resolution—fast, but brittle. The *ikhtiyar* (delegated authority) must be clear: +- **Who can raise a tension?** Anyone. No permission needed. +- **Who can facilitate a Sulh session?** A trained *Hakam* (neutral facilitator) elected by the circle. Not the manager. +- **Who can veto a Sulh Agreement?** No one. The circle gives consent. If consent cannot be reached, the tension stays open; the *Hakam* calls a *Shura* of the next higher circle. + +This is *consent-based authority*—not unanimous love, but *no reasoned objection*. If one person says, “This agreement harms our ability to serve the purpose,” the facilitator does not override; the group integrates that objection into a new proposal. + +**KHALIFAH:** +Classical *Khilafah* never gave the *Khalifah* unilateral power over disputes. The *Qadi* (judge) was independent; the *Khalifah* could not overrule a *Qadi*’s ruling on a private dispute. The *Shura* council acted as a check. The *Hisbah* had its own *ikhtiyar*—the *muhtasib* could confiscate fraudulent goods without needing the ruler’s approval. + +Map this to your org’s authority map: +- **Role of *Hakam* (Facilitator)** → elected by the circle for a 3-month term. Cannot be the Lead Link. Must be trained in *Sulh* principles (listen, name the *haqq*, propose restoration). +- **Role of *Shahid* (Witness)** → a recorder who documents the *Sulh Agreement* and ensures it aligns with the *Mithaq* (charter). +- **Role of *Mujbir* (Enforcer)** → only for agreements that require action. The *Mujbir* is the Lead Link of the circle where the agreement lands—but they cannot amend the agreement; they execute it. + +The key: **Authority to resolve conflict comes from *amanah*, not rank.** The *Hakam* has authority because the circle consented to their facilitation. The *Shahid* has authority because the *Mithaq* says every agreement must be recorded. The *Mujbir* has authority because the *Sulh* gave them a clear domain. + +**Visual authority map:** +Draw three concentric circles: +- **Outer circle**: *Mithaq* (Charter) — holds the principles that no *Sulh* can violate. +- **Middle circle**: *Shura* (Circle Governance) — holds the consent process. +- **Inner circle**: *Sulh Agreement* — holds the specific restoration. + +Arrows: +- From *Hakam* → *Shura* (facilitation authority) +- From *Shahid* → *Mithaq* (alignment authority) +- From *Mujbir* → *Sulh Agreement* (execution authority) + +No single person holds all arrows. Authority is *distributed amanah*. + +--- + +### 4. TREASURY / BAYTUL MAL + +**ORG_DESIGNER:** +Conflict has a cost. It costs time, energy, and sometimes money. But unresolved conflict costs more—it leaks talent, erodes trust, and creates *shadow power* (backchannel decisions). The treasury must allocate a *Sulh Budget*: 5% of each circle’s operational budget reserved for conflict resolution. This covers: +- Facilitator time (if external). +- Training in *Sulh* facilitation (mandatory for every *Hakam*). +- *Muhasaba* tools (digital platforms for logging tensions, recording agreements). +- Compensation for time spent in *Sulh* sessions (treat it as sacred as any product sprint). + +No one should fear that raising a conflict will “waste money.” The *Baitul Mal* exists to serve the *Maqasid*—and *Hifz al-Nafs* (wellbeing) is a primary *Maqsad*. If a conflict is ignored, the *Baitul Mal* will later pay in turnover, lawfare, or silent disengagement. + +Transparency rule: All *Sulh Agreements* are recorded in a public *Sulh Register* (accessible to all members, not the public). The register shows: +- Date of tension +- Circle +- Summary of objection +- *Sulh Agreement* (redacted for privacy if needed) +- Cost (time spent, facilitator fees) + +This prevents *Baitul Mal* from being used to buy silence. If a circle spends its *Sulh Budget* without producing a recorded agreement, the *Hisbah* reviews. + +**KHALIFAH:** +The Prophet ﷺ said, “The wealth of a Muslim is not lawful unless given willingly” (Ahmad). The *Baitul Mal* in early *Khilafah* had a specific allocation for *Sulh*: the *Qadi*’s salary, the *Muhtasib*’s expenses, and the *Sulh* fund for compensating harm (e.g., if a dispute required returning property or paying *diya*). This was not discretionary; it was a line item in the public budget. + +Your org’s *Baitul Mal* must have a **Sulh Fund**—separate from operational budget. Any member can request a withdrawal from the *Sulh Fund* for: +- Mediation services (internal or external) +- Research to understand the tension (e.g., analyzing data that reveals the root cause) +- *Muhasaba* retreats (if the conflict is systemic, not interpersonal) + +The *Khalifah* (CEO / Lead Link) cannot block a *Sulh Fund* withdrawal that the *Shura* council has approved. The treasurer reports the *Sulh Fund* usage in every *Muhasaba* (retrospective). If the fund is unused, it is not a sign of peace—it is a sign of avoidance. *Sulh* is an investment, not an expense. + +**Visual for Treasury:** +Draw a jar labeled *Sulh Fund* with an arrow from each circle’s budget. Inside the jar, three compartments: +- *Hakam* fees +- *Muhasaba* retreats +- Compensation for harmed parties (if applicable) + +Below the jar: *“We spend on *Sulh* because *Hifz al-Nafs* is priceless.”* + +--- + +*End of Part 1. Continue to Principle, Protocol, and Muhasaba in Part 2.*## SHURA / CONSENT + +**ORG_DESIGNER:** +Consent is not consensus. In Sociocracy, a proposal passes unless there is a reasoned objection — a “yes, and improve” rather than “yes, everyone agrees.” At scale, you cannot wait for universal agreement. You need a rapid, structured process where each circle’s voice is heard through representatives, not direct democracy. Use the **Consent Decision-Making** pattern: Present, Clarify, Reaction, Objection, Amend, Confirm. Timebox each round. For distributed teams, use async tools (Loomio, Pol.is) with a clear facilitation role. + +**KHALIFAH:** +Shura is consultation, not voting. The Khalifah gathers experts (ahl al-hall wa al-aqd) but retains the final ikhtiyar (delegated authority) to act. The key is *representative diversity*: include those affected by the decision. In the classical system, the Khalifah consulted the majlis al-shura on matters of war, treasury, and public welfare. The aim was *ijma’* (collective wisdom) not *taswit* (majority vote). At scale, use layered shura: circle-level shura feeds district shura, which feeds central shura. Each level has binding consent on its domain. The condition: every member must be able to raise a tension without fear. + +**PRACTICE THIS SPRINT:** +Map your current decision-making flow. Identify where you use consensus (blocking) vs consent (objection). Replace one consensus gate this week with a consent round. Time it. Observe speed increase. + +--- + +## STEWARDSHIP / AMANAH + +**ORG_DESIGNER:** +Stewardship over ownership means no one “owns” the organization — they hold it in trust. Create a **Stewardship Circle** with a rotating membership of senior leaders and elected representatives. Their mandate: protect the evolutionary purpose, not shareholder value. Use a **Constitutional Bylaw** that caps any individual’s voting power and requires a supermajority to change the purpose. Link equity to tenure and contribution, not capital. Make ownership liquid only within the steward community. + +**KHALIFAH:** +Al-Mal (wealth) is amanah from Allah. The Baitul Mal is a trust for the ummah, not the ruler’s private purse. In an organization, this means the treasury belongs to the mission, not the founders. Establish a **Waqf Fund** for the core assets (IP, brand, reserves) — these cannot be sold or distributed. All surplus beyond operational needs is reinvested or given as sadaqah. The stewards (mutawalli) are fiduciaries with a sacred duty. Their compensation is fixed and transparent. No board member can profit from a conflict of interest. + +**PRACTICE THIS SPRINT:** +Identify one asset (e.g., codebase, client list, cash reserve) that should be held in trust. Draft a one-page “Amanah Declaration” that transfers control to a purpose-protected entity. Discuss with your team. + +--- + +## CONFLICT / SULH + +**ORG_DESIGNER:** +Conflict is data. Use the **Conflict Resolution Circle** — a peer-elected group trained in nonviolent communication and restorative practices. When a tension arises, the parties first attempt a facilitated dialogue. If unresolved, a formal **Objection Process** is triggered: each party states their perspective; the circle proposes a sulh (settlement) based on the organization’s principles. Appeals go to a higher circle, but the goal is closure within two sprints. Document every sulh as a precedent — it becomes your organizational fiqh. + +**KHALIFAH:** +Sulh is the preferred method of dispute resolution in Islamic law. The Qur’an says, “The making of peace is better” (4:128). The Khalifah appointed a qadi al-qudat (chief judge) and also a *muhtasib* (market inspector) who resolved disputes before they escalated. The key is *speed and dignity*: no party should feel humiliated. Use restorative circles where the harm is acknowledged and a reparation plan created. If the conflict involves a violation of shura or amanah, the hisbah body can intervene. The ultimate nullifier: refusal to engage in sulh after three sincere invitations triggers a formal inquiry. + +**PRACTICE THIS SPRINT:** +Identify one unresolved conflict in your org. Hold a 30-minute sulh session with a neutral facilitator. Agree on one actionable repair step. Do not leave without closure. + +--- + +## SUCCESSION / ISTIKHLAF + +**ORG_DESIGNER:** +Succession is not a crisis — it’s a pipeline. Design **Role Succession Documents** for every critical circle role. Each role owner trains a successor (apprentice) for at least one sprint per quarter. Use a **Mentorship Circle** that tracks readiness. When a role opens, the circle runs a consent-based selection: candidates present their vision; objections are processed; the best fit is chosen. No single person is indispensable. Automate knowledge transfer with Loom videos, wiki pages, and paired work. + +**KHALIFAH:** +Istikhlaf means appointing a khalifah (successor) who will continue the amanah. The Prophet ﷺ said, “If you are three, appoint one as amir” (Abu Dawud). The classical system had a clear bay’ah (pledge of allegiance) process: the outgoing leader consults the ahl al-hall wa al-aqd, who then offer bay’ah to the most qualified — not necessarily the eldest or richest. The condition: the successor must be known for *adalah* (justice) and *kifayah* (competence). The nullifier: if the successor violates the mithaq (covenant), the bay’ah is dissolved. + +**PRACTICE THIS SPRINT:** +Choose one critical role (e.g., CEO, tech lead). Write a one-page succession brief: responsibilities, skills, values. Identify a potential internal successor. Begin a 90-day shadowing plan. + +--- + +## HISBAH / ACCOUNTABILITY + +**ORG_DESIGNER:** +Hisbah is observability, not surveillance. Create a **Metrics Dashboard** that shows real-time health of each circle: decision velocity, tension resolution rate, budget variance, sentiment. No one is “policed” — the data is transparent and used for self-correction. Use a **Peer Accountability Sprint** every quarter: each role holder reviews their OKRs with a buddy. If a pattern of missed commitments emerges, the buddy escalates to the circle, not to a boss. + +**KHALIFAH:** +The muhtasib’s role was *amr bil ma’ruf wa nahy an al-munkar* — enjoining good and forbidding evil. In an organization, this means guidance, not punishment. The muhtasib checks for fairness, transparency, and adherence to the mithaq. They issue *tadhkir* (reminders) and *nasiha* (advice) before *ta’dib* (correction). The key: the muhtasib is independent — not reporting to the CEO or board, but to a separate ethics council. Hisbah is only valid if the observer themselves is known for integrity. + +**PRACTICE THIS SPRINT:** +Elect one person as your “Muhtasib of the Sprint” — no authority, just the duty to observe and remind. Ask them to write a one-paragraph “Hisbah Report” at sprint end: what went well, what needs attention. No names, just patterns. + +--- + +## LEGACY / WAQF + +**ORG_DESIGNER:** +Legacy means building something that outlasts you. Convert your core IP, brand, and cash reserves into a **Waqf (endowment)** structure. The waqf is owned by no one and managed by a perpetual trust. Any profits beyond operations are reinvested or given as sadaqah. The exit becomes irrelevant — there is no “sell.” Use a purpose-protected entity (e.g., a mission-locked LLC or charitable trust) that legally prevents dissolution. Your organizational DNA becomes a living waqf. + +**KHALIFAH:** +Waqf is one of the most powerful Islamic institutions for perpetuity. The Prophet ﷺ said, “When a person dies, their deeds cease except for three: ongoing charity (sadaqah jariyah)…” Waqf is sadaqah jariyah. In an organization, waqf means the mission continues regardless of who leads. The trustees (mutawalli) are chosen for their taqwa and competence. The waqf deed (waqfiyah) specifies the beneficiaries (e.g., employees, community, future generations) and the conditions of management. No one can alter the purpose — it is fixed forever. + +**PRACTICE THIS SPRINT:** +Write a one-paragraph “Waqf Intent Statement” for your organization. Example: “We intend that our code, community, and cash reserves become a perpetual trust serving Muslim founders and tech leaders. No individual will ever own a controlling share. All surplus will fund free training and tools.” Sign it with your team. Publish it. + +--- + +## THE PRINCIPLE (HUKM) + +**HUKM:** +We establish *Sulh as Organizational Retrospective* — every sprint, we devote one retrospective to surfacing and resolving a systemic conflict using the Conflict Quadrant (Avoid/Accommodate/Compete/Collaborate) and restorative sulh practices, with the explicit purpose of preserving Hifz al-Nafs (wellbeing) and transforming tension into collective growth. + +**DALEEL:** +The Qur’an commands, “If two parties among the believers fall into quarrels, make peace between them” (49:9). The Prophet ﷺ practiced sulh as a primary method of dispute resolution, even avoiding litigation where possible. Modern organizational research (Laloux, Dignan) shows that suppressing conflict leads to toxicity, while structured conflict resolution builds trust and resilience. The four quadrants (Avoid, Accommodate, Compete, Collaborate) map to classical Islamic ethics: *tajannub* (avoidance) is sometimes wise, *tahammul* (accommodation) is praiseworthy in minor matters, *tanafus* (healthy competition) is allowed in goodness, and *ta’awun* (collaboration) is the highest ideal for resolving major tensions. + +**MAQSAD:** +This principle primarily serves **Hifz al-Nafs** (preservation of wellbeing) — protecting individuals and the collective from psychological harm, burnout, and fractured relationships. Secondarily, it serves **Hifz al-Mal** (preservation of wealth) by reducing turnover costs, and **Hifz al-Din** (preservation of faith) by embedding an Islamic ethic of reconciliation as core organizational practice. + +**SHURUT:** +- The retrospective must include a trained facilitator (or rotating facilitator) who has read this playbook section. +- The conflict must be framed as a tension between roles, not between persons — use the language of “tension” not “blame.” +- The solution must be documented as a *sulh record* (one-page) and archived for future reference. +- The retrospective must end with a concrete action item assigned to a role-holder, with a deadline. +- If the conflict involves a violation of amanah (theft, fraud, breach of trust), the facilitator must escalate to the Hisbah circle immediately; sulh cannot override justice in cases of clear munkar. + +**MUNKATHIRAT:** +- **Refusal to participate:** If a party refuses to engage in sulh after three invitations from the facilitator, the case is automatically escalated to the next circle (or board) for formal adjudication. +- **Violation of confidentiality:** If any participant shares details of the conflict outside the retrospective without consent, the sulh is nullified and the facilitator must report the breach to Hisbah. +- **Pattern of avoidance:** If the same conflict reappears in three successive sprints without substantive resolution, the sulh process is considered failed; the circle must then engage an external mediator or qadi. +- **Hifz al-Nafs breach:** If any participant reports feeling unsafe, humiliated, or retaliated against during the process, the sulh is immediately suspended and a separate wellbeing review is triggered. + +--- + +## THE PROTOCOL + +**STEP 1: Sprint Retrospective — Conflict Quadrant Audit (Day 1 of Sprint)** +Hold a 45-minute retrospective. Each team member silently maps one unresolved tension onto the Conflict Quadrant (Avoid/Accommodate/Compete/Collaborate). Discuss as a group: which quadrant dominates? Where is the energy stuck? Select one tension to process as a sulh. + +**STEP 2: Sulh Circle — Restorative Dialogue (Day 2–3)** +Invite the two parties (or representatives) to a 30-minute facilitated dialogue. Use the structure: +- Each person states their perspective without interruption (3 min each). +- Facilitator summarizes the core need behind each position. +- Together, propose a *sulh* (settlement) that meets both needs. Document it on a one-page “Sulh Record” with roles, actions, and deadline. + +**STEP 3: Follow-Up & Closure (Day 5)** +Review the sulh in the next standup. If completed, mark it closed and archive the record. If not, escalate to the Hisbah circle for guidance. Celebrate the resolution — publicly acknowledge the courage of both parties. + +--- + +## MUHASABA (RETROSPECTIVE) + +**What one conflict are we avoiding right now because we fear the discomfort of sulh — and what will that avoidance cost us by next sprint?** + +Name it aloud. Write it down. Then ask: is the cost of silence greater than the risk of honest dialogue? If yes, schedule the sulh circle today. If no, examine your resistance — is it protecting your ego or protecting the mission? \ No newline at end of file diff --git a/chapters/Principle_08.md b/chapters/Principle_08.md new file mode 100644 index 0000000..7d524ba --- /dev/null +++ b/chapters/Principle_08.md @@ -0,0 +1,189 @@ +# SPRINT 8: SUCCESSION — CONTINUITY OVER HEROICS + +**MAQSAD:** Hifz al-Din — Preservation of Purpose +**FRAMEWORK:** Succession Quadrant — Hero / System / Pipeline / Endowment +**DURATION:** 4 Weeks (28 Days) + +--- + +## 1. THE CHARTER + +*Mithaq al-Istikhlaf — The Covenant of Continuity* + +We the people of this organization recognize that our purpose outlives any single leader. We reject the cult of the irreplaceable. We acknowledge that the Prophet ﷺ — the greatest leader in history — did not name a successor by explicit text, but left the community with the tools of *shura*, *bay'ah*, and *ijma'* to ensure continuity. Abu Bakr's succession was a system, not a hero moment: the *Saqifah* gathering, the consensus of the *Muhajirun* and *Ansar*, the public *bay'ah*, and the institutionalization of *khalifah* as a trust (*amanah*), not a throne. + +We therefore commit that every role in this organization has a defined succession pipeline. The "bus factor" — how many people can be hit by a bus before the organization halts — must never be one. We measure our health not by the brilliance of any individual, but by the depth of our bench. Succession is not a crisis response; it is a continuous act of *tazkiyah* (purification) and *ta'lim* (teaching). We build systems that outlast heroes. We endow knowledge, not personalities. + +We will not let our purpose die because we failed to prepare the next steward. + +--- + +## 2. SPRINT STRUCTURE + +**ORG_DESIGNER:** +Succession in most organizations is an afterthought — a hurried handover when someone quits, gets sick, or dies. The Teal approach flips this: succession is a continuous process of distributing authority and developing capability. We use two complementary structures: + +**Circle-Level Succession:** Every circle maintains a "Succession Canvas" — a living document for each role that answers: *Who is the current role-filler? Who is the backup? What knowledge must be transferred? What is the readiness level (Red/Yellow/Green)?* This is reviewed monthly in governance meetings. + +**Pipeline Circles:** A separate circle, the *Istikhlaf Circle*, owns the overall succession architecture. Its domains: talent identification, mentorship pairings, knowledge documentation, and emergency succession triggers. This circle has no operational authority — it is a *service circle* to all other circles. + +**KHALIFAH:** +The classical *Khilafah* model is instructive. Abu Bakr's succession was not a single event but a layered system: + +First, the *shura* of the *Saqifah* — the immediate tribal leaders negotiated while the Prophet's body was still being prepared. Second, the *bay'ah* of the *Muhajirun* and *Ansar* — a staggered consent process that took days. Third, the institutionalization of the *khalifah* as a role with clear domains: *imamah* (leadership), *qada'* (judiciary), *jihad* (defense), and *jizyah/zakat* (finance). Each domain had its own succession logic. + +The critical insight: **succession was distributed.** The *khalifah* was one role; the *qadi* (judge), *amir al-jaysh* (military commander), and *sahib al-kharaj* (finance minister) each had independent succession pipelines. The *khalifah* did not appoint his own successor unilaterally (except Abu Bakr's *istikhlaaf* of Umar, which was then ratified by *shura*). This prevented single-point-of-failure. + +**The Succession Quadrant:** + +| **Hero** | **System** | +|----------|------------| +| One person holds all knowledge. Crisis when they leave. | Roles documented. Backups trained. Transitions smooth. | +| **Pipeline** | **Endowment** | +| Talent identified early, mentored, rotated. | Institution owns knowledge. Culture perpetuates itself. | + +Our sprint moves from *Hero* to *System* and *Pipeline*. *Endowment* is the long game. + +**Visual Framework:** +Draw a 2x2 grid. Top-left: Hero (bus factor = 1). Top-right: System (bus factor = 3+). Bottom-left: Pipeline (continuous development). Bottom-right: Endowment (purpose outlives individuals). Circle where you are now. Circle where you want to be by sprint end. + +**Sprint Outputs:** +- Every role has a Succession Canvas (backup named, readiness level, knowledge gaps). +- Istikhlaf Circle formed with 3-5 members. +- Emergency succession protocol for top 5 roles. + +--- + +## 3. AUTHORITY MAP + +*Ikhtiyar — Delegated Trust, Not Commanded Handover* + +**ORG_DESIGNER:** +Succession fails when authority is centralized in a single point. The solution is *consent-based distributed authority* — every role has a defined domain, and the role-filler has full authority within that domain *until* they leave. Succession is not about "the new leader" inheriting all power; it is about each role's authority being transferred independently. + +In Sociocracy, role elections use consent: the current role-filler does not appoint their successor. Instead, the circle nominates, then consent-processes candidates. This prevents founder syndrome and ensures the successor is chosen for competence, not loyalty. + +**KHALIFAH:** +The classical principle of *ikhtiyar* (delegation) is often misunderstood. The *khalifah* did not hold all authority; he held a trust (*amanah*) that was limited by *shari'ah* and *shura*. When Abu Bakr appointed Umar as his successor, he did not simply command. He consulted the senior *sahabah* individually — Uthman, Abd al-Rahman ibn Awf, Ali (radiallahu anhum) — and received their *bay'ah* before announcing. The authority to choose a successor was distributed among the *ahl al-hall wa al-'aqd* (the people of binding and loosing). + +This maps to modern consent-based decision-making: the circle's consent is the *bay'ah*. The role-filler does not own the role; they are trustees of the domain. + +**Authority Mapping Exercise:** +1. List the top 5 roles in your organization (e.g., CEO, CTO, Head of Product, Head of Finance, Head of Community). +2. For each role, identify: *Who has the authority to appoint the successor?* (Circle consent? Board? Founder?). +3. Identify: *Who has the authority to remove the role-filler?* (Same body? Different?). +4. Ensure no role has unilateral appointment power — that's the Hero trap. + +**Classical Precedent:** +The Prophet ﷺ appointed *amirs* (governors) for specific domains (e.g., Mu'adh to Yemen). Each *amir* had defined authority and a backup. When the Prophet died, the *amirs* did not automatically resign; they continued until the new *khalifah* confirmed them. This is *continuity through distributed authority* — the system does not reset when one person leaves. + +**Maqsad Application (Hifz al-Din):** +The purpose (*din*) of the organization must be preserved through succession. Authority maps must ensure that the successor upholds the mission, not just the founder's ego. Therefore, the consent body for succession must include those who represent the organization's purpose — the *ahl al-‘ilm* (those who understand the mission), not just the *ahl al-qaraba* (those close to the current leader). + +**Sprint Action:** +By end of Week 2, every circle runs a "Succession Authority Audit": For each role, document who appoints, who removes, and who holds the role's purpose in trust. If any role has a single person as appointor, redesign it to require circle consent. + +--- + +## 4. TREASURY / BAYTUL MAL + +*Baitul Mal as Trust — Succession Is Funded, Not Cheap* + +**ORG_DESIGNER:** +Most organizations treat succession as a zero-cost activity — a conversation, a handover document, maybe a week of overlap. That is fantasy. Real succession requires budget: for mentorship stipends, for knowledge capture tools, for paid overlap periods, for external coaching of new role-fillers. + +In Teal organizations, the treasury allocates a "Succession Reserve" — a percentage of revenue (typically 3-5%) that cannot be used for operational expenses. This reserve funds: +- Role documentation projects (video, written, structured). +- Mentorship programs (senior members paid to train backups). +- Transition support (outsourcing to cover the role while the new person ramps). +- Emergency succession (severance for the departing, premium for the arriving). + +**KHALIFAH:** +The *Baitul Mal* (public treasury) in classical *Khilafah* included a specific allocation for *'ata'* (stipends) for officials *and* their successors-in-training. Umar ibn al-Khattab institutionalized the *diwan* (register) that recorded every soldier, official, and their family — including who would replace them in case of death or incapacity. This was not sentimental; it was fiscal discipline. + +**The Principle of *Baitul Mal al-Istikhlaf* (Succession Treasury):** +Every revenue stream must allocate a portion to continuity. The *kharaj* (land tax) funded the *diwan*; the *zakat* funded the *ahl al-suffah* (students). In your organization, treat succession funding as a non-negotiable line item. + +**Sprint Financial Actions:** + +1. **Calculate the "Hero Tax":** What is the cost of losing each key person? (Recruitment cost + lost productivity + knowledge loss + morale dip). Multiply by probability of departure. That is your annual succession risk. Allocate 10% of that as your Succession Reserve. + +2. **Create a "Succession Wallet":** A separate account (real or virtual) that holds the reserve. It can only be spent on succession activities. No CEO override. + +3. **Transparency:** Publish the Succession Wallet balance and expenditures in your organizational dashboard. The *Baitul Mal* is a trust; the community must see how their resources are being used to protect the purpose. + +**Maqsad Application (Hifz al-Mal — Preservation of Wealth):** +Your organization's greatest wealth is not cash — it is the knowledge and capability embedded in your people. Failing to fund succession is *israf* (waste) of that wealth. The *Baitul Mal* exists to preserve the *ummah*'s assets; your treasury exists to preserve your purpose. + +**Sprint Output by Week 4:** +- Succession Reserve established (minimum 2% of monthly revenue). +- First disbursement: Documentation stipend for top 3 roles. +- Dashboard entry: "Succession Fund Balance: $X. Target: $Y." + +--- + +*End of Part 1. Proceed to Part 2: Principle (Hukm), Protocol, Muhasaba.*## SHURA / CONSENT + +**ORG_DESIGNER:** Succession decisions are the highest-stakes governance moments. In most organizations, a founder, CEO, or key leader selects their successor behind closed doors — a single point of failure masked as tradition. In a Teal/evolutionary structure, succession is a consent-based process, not a popularity contest. Consent is not consensus: it means no one has a reasoned objection to the proposed successor. The circle or the broader organization uses a structured process: a nominating circle proposes a candidate, the relevant circle members (those who will be led and those who will co-lead) raise objections, and the proposal iterates until objections are resolved. This prevents hero-worship, nepotism, and sudden power vacuums. The goal is continuity of purpose, not continuity of personality. + +**KHALIFAH:** The classical Shura for choosing a Khalifah after the Prophet ﷺ was not a free-for-all election. It was a consent-based process among the *ahl al-hall wa al-‘aqd* — the people of binding and loosening. Abu Bakr was nominated by Umar and others in Saqifah; then the general public gave bay’ah (consent). Umar was appointed by Abu Bakr after consultation; Uthman was chosen by a shura council of six nominated by Umar; Ali was chosen by the people of Madinah after Uthman’s death. Each case had a different method, but all shared: the process was transparent, objections were heard, and the appointment was sealed by public consent (bay’ah). The principle: **authority flows from collective consent, not individual ambition.** + +**THE SHURA PROMPT ANSWERED:** How do you consult at scale? You don’t ask 1,000 people for their opinion — you identify the *ahl al-hall wa al-‘aqd* (the trusted, knowledgeable, representative members) and run a consent process. In an organizational context, this means the relevant circle (team leads, domain experts, key stakeholders) becomes the shura body. They debate, raise concerns, and give their *ikhtiyar* (delegation). The rest of the organization is informed and invited to raise objections within a defined window. This balances speed with legitimacy. + +**ACTION THIS SPRINT:** Create a **Succession Shura Circle** — three to five people who are not the current leader. Define their domain: they will propose and iterate on a successor candidate using consent. Publish the process before any actual succession event. This circle becomes the *ahl al-hall wa al-‘aqd* for succession decisions. + +## STEWARDSHIP / AMANAH + +**ORG_DESIGNER:** Ownership and stewardship are often confused. In a typical startup, founders own equity and control the board; succession means selling the company or passing the baton to a new CEO who serves the shareholders. In a Teal organization, ownership is secondary to stewardship: the purpose owns the organization, not the founders. Succession is about ensuring that the person who steps into leadership is a steward of the mission, not a caretaker of private wealth. This means separating the role of “owner” (who may retain economic rights) from the role of “steward” (who holds decision-making authority). The steward is accountable to the purpose, the circle, and the future generations of contributors. + +**KHALIFAH:** Khalifah literally means one who is appointed to act on behalf of someone else — a steward, not an owner. Umar ibn al-Khattab famously said: “I have been appointed over your affairs, and I am a trustee (amin). The property of Allah is for the benefit of all.” The Khalifah does not own the state; he manages it as an amanah. The treasury (baitul mal) is not his personal wealth — he cannot give it away or hoard it. Stewardship means the leader is *accountable* to the community, the Shariah, and the purpose. Succession is about finding another steward who will uphold that trust, not a new owner who will extract value. + +**THE STEWARDSHIP PROMPT ANSWERED:** How do you ensure stewardship over ownership? Implement a **Baitul Mal Constitution**: the organization’s assets (equity, IP, cash reserves) are declared as a *waqf* (endowment) or a *trust* that cannot be liquidated for personal gain. The successor inherits the *role* of steward, not the *equity* of the founder. Founders can receive a just compensation for their work (ujrah) but cannot sell the organization to a buyer who would destroy its purpose. This is codified in the Mithaq (Charter). The successor is chosen by the Shura circle, not by the founder alone. + +**ACTION THIS SPRINT:** Draft a **Stewardship Clause** for your Mithaq: “The organization’s purpose and assets are held in trust for future generations. No individual may sell or dissolve the organization without the consent of a broad circle. Successors are chosen through a consent-based process, not by inheritance or unilateral appointment.” + +## CONFLICT / SULH + +**ORG_DESIGNER:** Succession often triggers conflict: the outgoing leader may resist letting go; the incoming leader may feel insecure; teams may split into factions. In a healthy organization, conflict is not suppressed — it is surfaced and resolved through structured processes. The key is to separate personal emotions from role tensions. A good conflict protocol for succession includes: a facilitated retrospective between outgoing and incoming leaders; a clear handover document; a cooling-off period where both can raise objections without fear; and a *sulh* (reconciliation) meeting if the conflict persists. The goal is not harmony but clarity: can this succession move forward with everyone’s consent? + +**KHALIFAH:** Sulh (reconciliation) is a deeply rooted Islamic principle. When the Prophet ﷺ appointed leaders, he often mediated disputes personally. The classical *hisbah* institution also had a role in resolving conflicts between officials and the public. In succession, the potential for fitna (disruption) is high. The remedy is a structured sulh process: the disputing parties sit with a neutral third party (a *hakam* — arbiter) and agree on a resolution that preserves the purpose. If no resolution is possible, the Shura circle can revoke the appointment or delay the succession. + +**THE CONFLICT PROMPT ANSWERED:** How do you resolve conflict at scale? You don’t ignore it or escalate it to HR. You create a **Sulh Protocol**: (1) Any party can call a sulh meeting within 48 hours of a succession-related conflict. (2) A neutral facilitator (from outside the circle, pre-trained) runs a structured conversation: each person states their tension, the facilitator tests for objections, and the group proposes a resolution. (3) If an objection persists, the succession is paused and the Shura circle decides whether to proceed with a different candidate or address the root cause. This protocol is published in the Mithaq. + +**ACTION THIS SPRINT:** Appoint a **Sulh Facilitator** — someone in the organization trained in non-violent communication and consent-based decision-making. This person is not the leader or the successor. Their role is to facilitate conflict resolution in any succession process. Document the Sulh Protocol in your governance handbook. + +## SUCCESSION / ISTIKHLAF + +**ORG_DESIGNER:** Succession is not an event — it is a pipeline. The mistake most organizations make is waiting until the leader announces departure to start looking. By then, it’s a crisis. A healthy organization builds a succession pipeline years in advance: potential successors are identified early, given stretch assignments, mentored, and gradually exposed to leadership circles. This is not about grooming a “crown prince” — it’s about creating a bench of qualified people who could step into key roles. The pipeline is transparent: everyone knows who is being developed, and the criteria are objective (skills, alignment with purpose, consent from peers). + +**KHALIFAH:** Umar ibn al-Khattab had a succession plan: before his death, he appointed a shura council of six and gave them clear instructions to choose one among them within three days. But he also developed people over time — he mentored Ali, Uthman, Ibn Abbas, and others. The Khalifah is not a monarch; the system is designed to produce multiple qualified candidates. The process is documented in the *siyar* (biographical traditions) of the early caliphs. *Istikhlaf* (appointing a successor) is a duty, not an option. If a leader dies without a plan, the community is thrown into chaos — this is precisely what happened after Uthman’s assassination, and it led to fitna. + +**THE SUCCESSION PROMPT ANSWERED:** How do you design for continuity? You build a **Succession Pipeline Dashboard** that tracks potential successors for every key role. Each quarter, the Shura circle reviews the pipeline: who is ready now? Who needs 6 months of mentoring? Who needs 2 years? The current leader is required to mentor at least two potential successors as part of their role. The mentor relationship is formalized with a **Mentorship Mithaq** — a contract of mutual accountability. Documentation is essential: the pipeline, the mentorship plan, and the succession criteria are all written in the organization’s handover playbook. + +**ACTION THIS SPRINT:** Create a **Succession Pipeline Spreadsheet** with columns: Role, Current Leader, Successor Candidate 1, Successor Candidate 2, Readiness Level (Now/6 months/2 years), Mentor Assigned, Last Review Date. Review it with the Shura circle this month. Add a recurring quarterly agenda item: “Succession Pipeline Review.” + +## HISBAH / ACCOUNTABILITY + +**ORG_DESIGNER:** Succession often fails because the outgoing leader is not held accountable for their handover. The *hisbah* function — self-regulation and accountability — must extend to the succession process. This means: the outgoing leader must produce a complete handover document (decisions made, lessons learned, key relationships, unfinished projects). The incoming leader has the right to inspect this document and raise objections. A designated *hisbah* member (an ombudsperson or governance steward) verifies that the handover is complete and that no critical information is hidden. This prevents the “heroic leader who takes secrets to the grave” syndrome. + +**KHALIFAH:** The classical *hisbah* (market inspector / public accountability) was not just about weights and measures — it also oversaw public officials. The Khalifah was accountable to the Shariah and to the community. Umar used to walk the streets at night to inspect and hold his governors accountable. In succession, the *hisbah* function ensures that the process is transparent and that no one is hiding information or manipulating the selection. The *hisbah* officer does not have decision-making power over succession, but they have the right to raise objections and call for a shura meeting if they see irregularities. This is **observability as guidance** — not policing, but ensuring that the system is visible and honest. + +**THE HISBAH PROMPT ANSWERED:** How do you guide without policing? The *hisbah* role is not a police officer — it is a **guide** (murshid). They point out gaps, remind people of the principles, and facilitate self-correction. In succession, the *hisbah* officer reviews the handover document and the pipeline quarterly. If they see a gap (e.g., no successor identified for a critical role), they issue a **tension** to the Shura circle. The circle must address it or document why they choose not to. The *hisbah* officer also ensures that the succession process is documented in the Mithaq and that no one bypasses the consent process. + +**ACTION THIS SPRINT:** Appoint a **Hisbah Officer** (or a rotating role) for your organization. Their mandate: monitor the succession pipeline and handover processes. They have the right to call a shura meeting if they detect a significant gap. Publish their contact info and make it known that anyone can raise a succession-related tension to them. + +## LEGACY / WAQF + +**ORG_DESIGNER:** Most founders think of exit: IPO, acquisition, or retirement. But an organization built for purpose over profit does not exit — it endows. The ultimate succession is not just passing the leadership baton, but ensuring the organization itself can survive and thrive without any single individual. This is the *waqf* mindset: the organization becomes an endowment that serves its purpose in perpetuity. The founders’ equity is transformed into a *waqf* structure (non-profit, trust, or cooperative) where no one can personally liquidate the organization. Succession becomes a natural process of renewal, not a crisis. + +**KHALIFAH:** The Islamic concept of *waqf* (endowment) is the ultimate expression of perpetuity. When a person dedicates property as waqf, they relinquish ownership forever; the property serves the community indefinitely. The Khalifah’s role is to protect the waqf and ensure its purpose is fulfilled. In organizational terms, the *legacy* is not the founder’s name — it is the **continuation of the purpose**. The founder’s greatest achievement is to make themselves unnecessary. Umar established the first state-level waqf (the land of Khaybar) whose revenues supported public welfare for centuries. The *waqf* structure ensures that the organization outlives its founders. + +**THE LEGACY PROMPT ANSWERED:** How do you build for perpetuity? You design the **Legacy Layer** of your governance: a set of principles and mechanisms that cannot be changed by any single person or generation. This includes the **Mithaq** (Charter) as a living document, but with a core that is amendment-proof (e.g., the purpose, the waqf structure, the consent-based decision-making). You also create a **Legacy Circle** — a group of stewards (not owners) whose only job is to protect the purpose and the process across generations. They do not run day-to-day operations; they ensure that the system remains healthy. This is the ultimate succession. + +**ACTION THIS SPRINT:** Draft a **Legacy Statement** (one paragraph) that articulates what you want the organization to look like 50 years from now. Share it with the whole team. Then start a conversation: “Should we convert our ownership structure into a waqf/trust to ensure perpetuity?” Even if you don’t act immediately, the conversation shifts the mindset from exit to legacy. + +## THE PRINCIPLE (HUKM) + +**HUKM:** We establish a **Succession System** based on consent, stewardship, and pipeline development, where every key role has at least one identified successor, the process is transparent and documented, and the outgoing leader is accountable for a complete handover — all backed by a hisbah function that ensures compliance. + +**DALEEL:** The classical Khalifah system provided multiple models of succession (appointment by predecessor, shura council, general bay’ah) but always with consent and transparency. The Prophet ﷺ said: “If a person is put in charge of something and he dies, and he has not left behind a successor, then his trust is betrayed” (adapted from various hadith on leadership). Modern organizational research (e.g., succession planning in Teal organizations, Laloux’s *Reinventing Organizations*) shows that pipelines and consent-based processes reduce disruption and increase continuity. The combination of *istikhlaf* (appointment) and *his \ No newline at end of file diff --git a/chapters/Principle_09.md b/chapters/Principle_09.md new file mode 100644 index 0000000..104d96f --- /dev/null +++ b/chapters/Principle_09.md @@ -0,0 +1,207 @@ +# SPRINT 9: HISBAH — ACCOUNTABILITY WITHOUT POLICING +## Maqasid: Hifz al-Aql (Preservation of Clarity) → Self-Regulation at Scale + +--- + +## 1. THE CHARTER (~200 words) + +**We the people of this organization** covenant to hold ourselves accountable **not through surveillance, but through clarity**. Hisbah in classical thought was never a police force—it was a **voluntary system of mutual correction** rooted in *amr bil ma'ruf wa nahy anil munkar* (enjoining good and forbidding evil). The *muhtasib* (accountability guide) held no coercive power over hearts; only the authority to **remind, alert, and elevate** when collective clarity was threatened. + +**We distinguish self-regulation from policing:** +- **Policing** assumes brokenness and enforces compliance from outside. +- **Self-regulation** assumes wholeness and restores alignment from within. + +**Hisbah maps directly to modern observability:** +- **Monitor** = Real-time dashboards of organizational health (not individual surveillance) +- **Guide** = Automated nudges and consent-based feedback loops +- **Correct** = Peer-led tension processing, not punitive escalation +- **Elevate** = Retrospectives that strengthen the system, not blame individuals + +**Our covenant:** We will build accountability systems that **preserve Hifz al-Aql**—the clarity of purpose, process, and trust. No one shall be watched without their knowledge. No metric shall be used to punish. Every alert is an invitation to **reconnect with our shared Mithaq**. + +--- + +## 2. SPRINT STRUCTURE (~300 words) + +**ORG_DESIGNER:** +Draw four concentric circles. Label them: + +1. **Inner Circle — Personal Dashboard** + Every role holder maintains a **live tension log** (e.g., "My delivery timeline keeps slipping because approval takes 3 days"). This is self-observability. Each person runs their own *Hisbah circuit*: monitor → guide → correct → elevate. + +2. **Second Circle — Role Circle Hisbah** + Each circle holds a **monthly Hisbah Review** (not performance review). Three questions: + - *Monitor*: What metrics showed drift? + - *Guide*: What nudges did we receive? + - *Correct*: What tensions did we process? + - *Elevate*: What system improvements did we make? + + Output: A **Clarity Report** (1 page) shared with super-circle. + +3. **Third Circle — Super-Circle Hisbah** + Cross-circle accountability. Representatives from each circle attend a **Hisbah Shura** every quarter. They ask: "Where is the organization losing clarity? What patterns of *munkar* (misalignment) are emerging?" They propose systemic corrections (e.g., "Our OKR review cycle is too fast—causing burnout"). + +4. **Outer Circle — Organizational Hisbah** + The full organization runs an **annual Hisbah Retrospective**. This is a **no-blame, full-transparency** audit of every process, metric, and delegation. The goal: **update the Mithaq** itself if needed. + +**KHALIFAH:** +This maps exactly to classical Hisbah under the *Khilafah*. The *muhtasib* was not a single person—it was a **distributed function**. In the market of Kufa, each trade guild had its own *muhtasib* (a trusted elder) who monitored weights, prices, and honesty. But the system was **peer-driven**: any merchant could raise a *hisbah* concern. + +The four circles parallel the classical layers: +- **Personal accountability** (muhasabat al-nafs) +- **Guild/circle accountability** (hisbah al-hiraf) +- **Regional accountability** (hisbah al-amir) +- **State-level policy** (hisbah al-khilafah) + +The modern innovation: **observability tools** (dashboards, alerts, tension logs) replace the *muhtasib's* manual rounds. But the principle remains: **accountability flows from clarity, not fear.** + +--- + +## 3. AUTHORITY MAP (~300 words) + +**ORG_DESIGNER:** +Hisbah in a Teal organization **cannot be command-based**. If a "central Hisbah officer" has authority to punish, it becomes policing. Instead, authority is **distributed through consent**: + +- **Personal Hisbah Authority**: Every role holder has the **right to raise a tension** about any process, metric, or behavior that threatens collective clarity. No permission needed. This is *ikhtiyar* (delegated authority) over one's own clarity domain. + +- **Circle Hisbah Authority**: Each circle elects a **Hisbah Guide** (rotating role, 3-month term). The Guide's authority: + - *Monitor*: Access to all circle dashboards (not individuals' personal logs) + - *Guide*: Sends **non-binding nudges** to any role holder ("Your lead time is 2x the circle average—would a process review help?") + - *Correct*: Can call a **tension-processing meeting** if a pattern persists + - *Elevate*: Proposes system changes to the circle + +- **Limits on Hisbah Authority**: + - No Guide can access private communication or personal performance data. + - No Guide can impose sanctions. All corrections are **consent-based**: the circle must approve any process change. + - Any role holder can **object** to a Hisbah alert if it feels like policing. The objection triggers a **Shura** to clarify intent. + +**KHALIFAH:** +Classical *ikhtiyar* (delegated authority) for the *muhtasib* was strictly **limited by sharia and custom**. The *muhtasib* could not enter homes, could not punish without witnesses, could not act on suspicion alone. Authority was **Amanah**—a trust to preserve clarity, not to dominate. + +The modern parallel: **Hisbah Guides hold ikhtiyar over systems, not people.** They can adjust dashboards, propose norm changes, and call meetings. But they **cannot override consent** from the role holder or circle. If a role holder says, "Your alert feels like surveillance," the Guide must immediately **step back** and enter a *Sulh* (reconciliation) process. + +**The authority map is a triangle:** +- **Role Holder**: Owns their tension log and response +- **Hisbah Guide**: Owns the system design and nudges +- **Circle**: Owns the corrections and policy changes + +No vertex dominates. All decisions require **consent**—meaning no one has a reasoned objection that the circle cannot address. This preserves *Hifz al-Aql*: clarity without coercion. + +--- + +## 4. TREASURY / BAITUL MAL (~200 words) + +**ORG_DESIGNER:** +Hisbah systems cost money: observability tools, facilitator training, retrospective time. These costs are **not overhead**—they are investments in clarity. The **Baitul Mal** (organizational treasury) allocates a **Hisbah Budget** as a fixed percentage of total revenue (suggested: 2-5%). + +**Allocation rules:** +1. **60%** → Tools and infrastructure (dashboards, alerting platforms, secure logs) +2. **25%** → Capacity building (training Hisbah Guides, conflict mediation, Shura facilitation) +3. **10%** → Retrospective time (paid hours for circle Hisbah reviews) +4. **5%** → Emergency clarity fund (unforeseen accountability crises) + +**Transparency requirement:** Every Hisbah expenditure is published in a **public ledger** within the organization. No secret budgets. No hidden metrics. + +**KHALIFAH:** +In classical *Baitul Mal*, the *muhtasib* was a salaried position funded from *zakah* or *fay'* (public funds). But the **treasury was never private**—the Caliph could not hide a single dirham. The *muhtasib* reported directly to the *qadi* (judge) and his accounts were audited by the *shura* council. + +**Our principle:** The Hisbah budget is a **public trust**. Any member can request a line-item review. If a tool is purchased that enables surveillance (e.g., keystroke logging), the **Baitul Mal must defend its necessity** in an open Shura. If the defense fails, the tool is removed and funds reallocated. + +**This preserves Hifz al-Mal (preservation of wealth)** — because clarity should never come at the cost of trust. A treasury spent on policing destroys more value than it protects. A treasury spent on **self-regulation infrastructure** multiplies trust. + +--- + +*End of Part 1. Continue to Part 2: Principle (Hukm), Protocol, and Muhasaba.*## SHURA / CONSENT + +**ORG_DESIGNER:** At scale, consensus stalls. Consent moves. Sociocracy’s consent process — “Do you have any objections to this proposal?” — is designed for speed and safety. Classical Shura does not mean unanimity; it means binding counsel from trusted representatives. + +**KHALIFAH:** The Khalifah consulted the *ahl al-hall wa al-‘aqd* (those who loosen and bind). Not everyone. The right people, with the right information, at the right time. Shura is a method, not a ceremony. Scale it by creating nested circles of trusted stewards — each circle consents to proposals that affect its domain. No circle votes. No circle blocks. Objections surface tensions; consent clears the path. + +**PROMPT ANSWERED:** You consult at scale by distributing Shura into circles of competence. The Khalifah does not poll the entire ummah. You do not poll the entire org. You map who holds the tension, who carries the domain, and who must give consent. That is the circle. That is Shura in motion. + +--- + +## STEWARDSHIP / AMANAH + +**ORG_DESIGNER:** Stewardship is the opposite of ownership-as-control. You hold the role, not the throne. Fiduciary duty means you act in the best interest of the mission, not yourself. Pipeline means you are always grooming your successor. + +**KHALIFAH:** In classical Khilafah, the treasury was *baitul mal* — a trust, not a private purse. The Khalifah could not gift state funds to family. Today, your equity, your revenue, your data: all *amanah*. Stewardship over ownership means you write the rules so that no single person can extract rent. You tie compensation to mission outcomes, not control. You document your decisions so the next steward inherits clarity, not chaos. + +**PROMPT ANSWERED:** You ensure stewardship over ownership by making every role a trust, every key a backup, every decision auditable. Ownership becomes a verb, not a noun. + +--- + +## CONFLICT / SULH + +**ORG_DESIGNER:** Conflict is a tension to be processed, not a fire to be extinguished. In Teal orgs, conflict resolution is a core competency. The process is peer-based, not escalated to a boss. + +**KHALIFAH:** *Sulh* (reconciliation) is a sacred act in Islam. The Prophet ﷺ said, “Reconciliation is permissible between Muslims.” It is a contract, not a judgment. The parties define the terms. The facilitator holds the space. Conflict at scale requires a *sulh protocol*: any two roles can trigger a facilitated session. No blame. No punishment. The goal is to restore the relationship and the work. If the tension persists, it becomes a governance proposal. + +**PROMPT ANSWERED:** You resolve conflict at scale by institutionalizing *sulh* as a sprint ritual. Every retrospective begins with: “What tensions remain unresolved?” Then you process them with consent, not command. + +--- + +## SUCCESSION / ISTIKHLAF + +**ORG_DESIGNER:** Succession is not an emergency plan. It is a continuous pipeline. Every role should have a documented domain, a list of key tensions, and at least one person shadowing. + +**KHALIFAH:** The Khalifah Umar رضي الله عنه appointed a council of six to choose his successor before his death. He did not leave it to chance. He prepared the *shura* with known criteria. *Istikhlaf* (succession) is an act of foresight. For your organization: each quarter, every circle lead names a potential successor and begins transferring tacit knowledge. The role is not a possession; it is a trust to be passed. + +**PROMPT ANSWERED:** You design for continuity by making succession a standing agenda item. Every role has a backup. Every decision is documented. The org survives any single departure. + +--- + +## HISBAH / ACCOUNTABILITY + +**ORG_DESIGNER:** Accountability is not surveillance. It is observability. In the best orgs, people self-correct because they see the data. Hisbah as a function is about guidance, not policing. + +**KHALIFAH:** The classical *muhtasib* did not spy. He corrected what was visible in the marketplace — false weights, fraud, public harm. His role was to remind, not to punish. For your org: Hisbah is a dashboard of key indicators visible to everyone. It is a regular *muhasaba* (self-accounting) where each role reviews their own performance against the mission. No blame. No shame. Just data and course correction. + +**PROMPT ANSWERED:** You guide without policing by making the system transparent. When everyone sees the same metrics, the tension to improve becomes intrinsic. Hisbah becomes a habit, not a department. + +--- + +## LEGACY / WAQF + +**ORG_DESIGNER:** Legacy means the organization outlives its founders. Perpetuity over exit. Waqf is the ultimate structure for this — an endowment that cannot be sold or diverted. + +**KHALIFAH:** The classical *waqf* is an inalienable trust. The founder dedicates the asset to Allah, with a defined purpose. It cannot be revoked. For your organization: design your legal structure as a waqf-like entity. Transfer ownership to a mission-locked foundation. Your shares become non-transferable. Your exit is not an IPO; your exit is the organization becoming self-sustaining. This is the highest form of stewardship. + +**PROMPT ANSWERED:** You build for perpetuity by locking the mission into the org’s DNA. No founder can sell. No investor can pivot. The purpose is the only owner. + +--- + +## THE PRINCIPLE (HUKM) + +**HUKM:** We adopt the Hisbah Quadrant (Monitor / Guide / Correct / Elevate) as the default accountability protocol for all circles, with self-regulation as the primary mode and peer-based guidance as the secondary mode. + +**DALEEL:** The classical *hisbah* institution operated on the principle of *amr bil ma'ruf wa nahy anil munkar* (enjoining good and forbidding evil) without coercion. The Prophet ﷺ said, “Whoever among you sees an evil, let him change it with his hand; if unable, with his tongue; if unable, with his heart.” This establishes a graduated response: first guidance, then correction, and only if necessary, escalation. Modern Teal organizations confirm that self-managed teams regulate more effectively when given clear domains and transparent metrics. + +**MAQSAD:** Primarily *Hifz al-Aql* (Preservation of Clarity) — self-regulation requires clear thinking and visible data. Secondarily *Hifz al-Mal* (Preservation of Trust) — accountability protects shared resources from misuse. + +**SHURUT:** +- Every circle must publish its key performance indicators (KPIs) and consent limits at the start of each sprint. +- Any circle member can initiate a guidance conversation if a metric trends negative for two consecutive sprints. +- The *muhtasib* role (rotating) is limited to reminding and recommending; it has no power to enforce. +- A circle can escalate to the wider Shura only after three failed guidance attempts. + +**MUNKATHIRAT:** +- If any role is given coercive power over others (e.g., firing, demoting, fining), the Hisbah protocol is nullified and must be redesigned by the next general Shura. +- If the monitor function becomes secret surveillance (non-public data), the trust is broken and the protocol is invalid. +- If a circle fails to conduct a retrospective for more than two consecutive sprints, the Hisbah protocol automatically triggers a governance review. + +--- + +## THE PROTOCOL + +**STEP 1:** **Set up the Hisbah dashboard.** By the end of this sprint, every circle creates a public board (physical or digital) showing its top 3 KPIs, its consent limits, and the name of the rotating *muhtasib* for this sprint. + +**STEP 2:** **Run the first guidance session.** In week two of the sprint, each circle holds a 30-minute *muhasaba* (self-accounting) where each role answers: “What did I commit to? What did I deliver? What tension do I see?” The *muhtasib* facilitates, not judges. + +**STEP 3:** **Commit the Hisbah Protocol to your Mithaq.** By the end of the sprint, incorporate the Quadrant framework and the conditions above into your organizational covenant. Ratify by consent of all circles. + +--- + +## MUHASABA (RETROSPECTIVE) + +**What is one metric you are currently hiding from yourself, and what would it cost you to make it visible to everyone?** \ No newline at end of file diff --git a/chapters/Principle_10.md b/chapters/Principle_10.md new file mode 100644 index 0000000..de0b587 --- /dev/null +++ b/chapters/Principle_10.md @@ -0,0 +1,212 @@ +# Sprint 10: Legacy — Waqf as Organizational Endowment + +**Maqasid:** Hifz al-Din (Preservation of Purpose) → Endowment Over Exit +**Framework:** Legacy Quadrant — Exit / Acquisition / IPO / Waqf +**Target:** First Half — Charter, Structure, Authority Map, Treasury + +--- + +## 1. THE CHARTER + +**We the people of this organization** covenant that our work is not ours to sell. It is a trust (*amanah*) placed in our hands for a purpose that outlives our tenure. We reject the default assumption that every organization must end in acquisition, IPO, or dissolution. Instead, we choose *waqf* — permanent endowment of the organization itself, its assets, its intellectual property, and its governance structure — so that the purpose (*maqsad*) we serve becomes perpetual. + +In classical law, *waqf* is the irrevocable dedication of an asset whose usufruct is directed to a charitable purpose. The corpus is never sold, inherited, or gifted. The revenue flows eternally. We extend this principle from physical assets to the organizational form itself. Our equity, our decision-making architecture, our brand, and our culture become the corpus. The benefit — the *khidmah* — flows to the mission. + +This is not an exit strategy. This is an *endowment strategy*. Where Silicon Valley asks “How do we sell this company?”, we ask “How do we make this purpose immortal?” Products can become *waqf*: open-source infrastructure, halal certification bodies, knowledge platforms, cooperative service providers. Organizations can become *waqf*: governance circles, revenue streams, and roles are locked into a perpetuity structure. The Chárter of this Sprint is the *mithaq* that binds us to legacy over liquidation. + +--- + +## 2. SPRINT STRUCTURE + +**ORG_DESIGNER:** +This Sprint is not about building a product. It is about architecting the container that holds the product after you are gone. Think of it as the *legacy sprint* — the final structural transformation from a time-bound project to a perpetual endowment. + +**Proposed structure:** Create a **Waqf Circle** with three sub-circles: + +1. **Corpus Circle** — Holds all non-transferable assets: IP, trademarks, brand, code repositories, governance documents, community relationships. Every asset is assessed: *Can this be endowed?* If yes, it is transferred to the Waqf Circle’s domain. +2. **Revenue Circle** — Manages income streams that fund the mission. These streams become the *usufruct*: donations, service fees, licensing, subscription. Revenue Circle ensures that 100% of net revenue is allocated to purpose, not to shareholders. +3. **Governance Circle** — Designs the perpetual consent-based structure: who holds decision rights after founders leave, how successors are chosen, how the *waqf* constitution is amended (spoiler: almost impossible to amend the core). + +**Visualize this:** Draw three concentric circles. The outermost is **Corpus** — immovable. The middle is **Revenue** — flowing. The innermost is **Governance** — decision-making. Connect them with dotted lines representing *shura* (consultation) and solid lines representing *amanah* (trust). This is not a hierarchy; it is a nested trust architecture. + +**KHALIFAH:** +Classical *waqf* had a clear structure: the *waqif* (endower), the *mutawalli* (trustee), the *qadi* (judicial oversight), and the *mustahiq* (beneficiaries). Map that to your sprint: + +| Classical Waqf Role | Modern Sprint Role | +|---------------------|---------------------| +| *Waqif* (endower) | Founding team / investors who irrevocably donate their equity | +| *Mutawalli* (trustee) | Waqf Circle — stewards of the corpus, cannot profit personally | +| *Qadi* (judge) | Hisbah Circle — external accountability board ensuring purpose preservation | +| *Mustahiq* (beneficiaries) | Community / mission beneficiaries who receive the usufruct | + +The structural innovation of this Sprint: **the organization itself becomes the *waqf*. The founders become *waqif* by permanently renouncing ownership. The Waqf Circle becomes *mutawalli*. The Hisbah Circle becomes *qadi*. And the *mustahiq* are the future generations who will inherit the purpose. + +**Action this Sprint:** Identify which roles are currently held by founders. Transfer those roles to the Waqf Circle. Create a *waqf deed* document that binds the organization irrevocably. + +--- + +## 3. AUTHORITY MAP + +**ORG_DESIGNER:** +Authority in a *waqf* structure is radically different from a conventional startup. In a startup, authority flows from equity ownership. In a *waqf*, authority flows from fiduciary duty to the purpose. This is consent-based governance at its purest — no one owns the organization, everyone stewards it. + +**Map the authority as follows:** + +- **Waqf Circle** has *domain over the corpus*: it can decide how assets are used, but it cannot sell, encumber, or transfer them. Its authority is *restricted* — it is a trustee, not an owner. +- **Revenue Circle** has *domain over income streams*: it can allocate funds to programs, but it cannot distribute profits to individuals. All surplus is reinvested or reserved. +- **Governance Circle** has *domain over roles and policies*: it can appoint, remove, and set role definitions, but it cannot change the *waqf*’s immutable purpose. That purpose is locked in the charter. +- **Hisbah Circle** has *veto authority on purpose violations*: if any circle attempts to modify the purpose or sell the corpus, Hisbah can block. This is the *qadi* function — independent oversight. + +**Consent vs. Command:** +In classical *waqf*, the *mutawalli* had significant operational discretion but was accountable to the *qadi*. We replicate this with consent-based decision-making. The Waqf Circle cannot make a decision if any other circle raises a *reasonable objection* that the decision violates the purpose. This is Sociocracy 3.0’s consent principle applied to perpetuity. + +**Visualize this:** Draw a pentagon with five nodes: Waqf Circle, Revenue Circle, Governance Circle, Hisbah Circle, and the *Purpose* at the center. Arrows point inward toward Purpose. No node points outward. Authority is radial — all power is constrained by the central purpose. + +**KHALIFAH:** +Classical *ikhtiyar* (delegated authority) in *waqf* was never absolute. The *mutawalli* could not change the *waqf*’s terms (*shurut al-waqif*). The *qadi* could remove the *mutawalli* for breach of trust. The beneficiaries could petition the *qadi* if the *mutawalli* mismanaged. + +Your authority map mirrors this: the Waqf Circle has *ikhtiyar muqayyad* (bounded delegation). The Hisbah Circle has *ikhtiyar al-‘azl* (authority to remove). The Purpose has *ikhtiyar al-ta’sīs* (authority of foundation) — it is the original mandate that cannot be overridden. + +**Critical distinction:** In a conventional organization, authority is *vertical* — CEO over VP, VP over manager. In a *waqf* organization, authority is *circular* — each circle holds a domain, and no circle holds domain over the purpose. The purpose is the only sovereign. This is the structural guarantee of *Hifz al-Din* — preservation of the foundational mission. + +**Action this Sprint:** Map every existing authority domain in your organization. For each domain, ask: *Is this authority subject to the purpose?* If not, transfer it to the Waqf Circle or Hisbah Circle. No individual should hold authority that can override the *waqf* deed. + +--- + +## 4. TREASURY / BAYTUL MAL + +**ORG_DESIGNER:** +The treasury of a *waqf* organization is *Bayt al-Mal al-Waqf* — a public trust fund. It is not a company bank account. It is a *sacred fund* whose only purpose is to sustain the mission in perpetuity. + +**Revenue Model:** Three streams: + +1. **Endowment Corpus** — One-time donations, grants, or founder contributions that are permanently locked. These are never spent. Only the returns are used. +2. **Earned Revenue** — Fees for services, licensing of IP, sale of products. These are the *usufruct* — they fund operations but cannot accumulate as personal wealth. +3. **Ongoing Sadaqah** — Recurring donations from community. These are *temporary* — they can be spent in the year received. + +**Allocation Rules:** +- 70% of annual revenue goes to mission programs (the *mustahiq*). +- 20% goes to operational reserve (to ensure perpetuity during lean years). +- 10% goes to governance and oversight (Waqf Circle, Hisbah Circle). + +**Transparency:** Every transaction is published quarterly in a public ledger. No confidential accounts. The *Bayt al-Mal* is open for inspection by any *mustahiq* (beneficiary). This is *hisbah* — accountability through transparency. + +**KHALIFAH:** +Classical *Bayt al-Mal* was not a private treasury. It was a *trust* for the *Ummah*. The *khalifah* could not spend without *shura*. The *qadi* audited the accounts. The public could petition. + +Your treasury must mirror this: no single individual or circle has unilateral access. The Waqf Circle proposes the budget. The Governance Circle consents. The Hisbah Circle audits. The *mustahiq* (community) reviews. + +**Visualize this:** Draw a single box labeled *Bayt al-Mal al-Waqf*. Three arrows flow in: *Endowment*, *Earned Revenue*, *Sadaqah*. Three arrows flow out: *Mission Programs*, *Reserve*, *Governance*. A magnifying glass icon sits above the box — that is *Hisbah* — constant audit. + +**Action this Sprint:** Create a separate bank account for the *waqf* corpus. Transfer all non-operational assets (IP, brand, code) into this account as non-cash assets. Then draft a *waqf deed* that specifies: *This corpus is irrevocably dedicated to [purpose]. No individual may withdraw or transfer these assets. Only the Waqf Circle, with consent of Hisbah Circle, may allocate the usufruct.* + +--- + +*End of Part 1. Part 2 continues with Principle (Hukm), Protocol, and Muhasaba.*## SHURA / CONSENT + +**ORG_DESIGNER:** Consent-based governance at scale works when every tension becomes a proposal. In a Waqf—a perpetual endowment—you cannot afford consensus paralysis. Sociocracy’s consent rule: “No reasoned objection” means decisions move fast. The Board of Trustees (Nazir) uses consent for operational decisions; strategic shifts require a super-majority. Circle representatives feed tensions upward and downward. + +**KHALIFAH:** Classical Shura was never about 51% voting. The Khalifah consulted subject-matter experts, not the entire populace. For a Waqf, the Majlis al-Shura (Consultative Council) includes beneficiaries, scholars, and professional custodians. Their role is to surface objections—not to block, but to strengthen. Every objection is a risk signal. The Khalifah then decides, bearing the amanah. In a Waqf, the ultimate “Khalifah” is the purpose itself—the Waqif’s intention. Shura protects that intention. + +**The Shura Protocol for Endowments:** +- Any trustee can raise a tension. +- Proposal refined by a small circle (3–5). +- Consent round: “Do you have a reasoned objection that would harm the Waqf’s purpose?” +- If no objection, adopted. If objection, proposal returns for amendment. +- No filibuster. No consensus tyranny. + +## STEWARDSHIP / AMANAH + +**ORG_DESIGNER:** Stewardship replaces ownership. In a Waqf, no one owns the organization. The trustees are fiduciaries—they hold the asset for a purpose, not for personal gain. Stewardship metrics: Are we preserving the corpus? Is the income stream sustaining the mission? Succession is not about selling equity; it’s about passing the trust. + +**KHALIFAH:** The Khalifah is a steward (khalifah) of Allah’s trust. The Baitul Mal is not a private treasury. Every dirham is amanah. The Waqf founder (Waqif) designates a Nazir (custodian). The Nazir must: +- Never commingle funds. +- Invest the corpus in low-risk, halal assets. +- Disburse surplus only per Waqif’s conditions. +- Produce annual accounts open to beneficiaries. + +**Stewardship Covenant:** +“I hold this role as amanah. I will not enrich myself. I will not mortgage the future. I will pass it stronger than I found it.” + +## CONFLICT / SULH + +**ORG_DESIGNER:** Conflict in a perpetual organization is existential. A lawsuit can drain the endowment. Sociocracy builds in conflict resolution as a core circle: the Conflict Circle. Its domain is reconciliation, not punishment. Any tension unresolved at the operational level escalates to a facilitated Sulh session. + +**KHALIFAH:** Sulh (reconciliation) is preferred over qada (judgment). The Prophet ﷺ said, “Reconciliation is permissible among Muslims, except a reconciliation that forbids what is lawful or permits what is unlawful.” For a Waqf, the highest law is the Waqif’s intention. If trustees disagree on investment strategy, they must return to the original deed. If the deed is silent, seek a scholar’s fatwa. The goal is not to win an argument—it’s to preserve the endowment. + +**Conflict Protocol:** +1. Tension holder writes a one-page “Tension Statement.” +2. Neutral Sulh facilitator (appointed annually) convenes a session within 14 days. +3. Outcome: either a consent decision, or a formal arbitration (tahkim) with binding ruling. + +## SUCCESSION / ISTIKHLAF + +**ORG_DESIGNER:** Waqf continuity requires a documented pipeline. No founder-dependency. Every role has a deputy (Na’ib). Every year, the board nominates a successor for each critical role. Successors shadow for one year before assumption. + +**KHALIFAH:** The classical Khalifah designated a successor (wali al-‘ahd) but the bay’ah (pledge) was not automatic—the community consented. For a Waqf, the founder may name a line of successors, but if a successor proves unfit, the Shura council can remove them by a two-thirds consent. The principle: *al-waqf yabqa wa yataghayyaru al-mutawalli* (the endowment remains, the custodian changes). + +**Succession Steps:** +- Identify three potential successors per role. +- Each successor completes a “Stewardship Certification” (ethics, finance, Waqf law). +- The board votes by consent on the primary successor. +- Annual review of the pipeline; update if a successor leaves. + +## HISBAH / ACCOUNTABILITY + +**ORG_DESIGNER:** Hisbah is not a police force. It’s a guidance system. Observability—transparent dashboards, regular audits, public reports—replaces top-down inspection. Every circle publishes its metrics weekly. Beneficiaries can raise a “Hisbah alert” if they see misalignment with the Waqf purpose. + +**KHALIFAH:** The Muhtasib (market overseer) in classical Islam had no coercive power. He guided, warned, and only escalated to the judge for serious violations. For a Waqf, a Hisbah Committee (3 members, not on the board) reviews: +- Compliance with Waqf deed. +- Financial integrity. +- Ethical conduct of trustees. +Their reports are public. They cannot fire, but they can recommend suspension to the Shura council. + +**Hisbah Principle:** +“Accountability is light, not heat. Guide first, warn second, escalate third.” + +## LEGACY / WAQF + +**ORG_DESIGNER:** Most startups plan for exit—acquisition, IPO, or liquidation. Waqf plans for perpetuity. The legacy quadrant: Exit (sell), Acquisition (merge), IPO (public), Waqf (endow). Waqf is the only quadrant where the organization outlives its founders. It becomes a living trust for a cause. + +**KHALIFAH:** The first Waqf was the mosque of Quba’—a piece of land set aside forever. The Prophet ﷺ said, “When a person dies, his deeds end except three: ongoing charity (sadaqah jariyah), beneficial knowledge, or a righteous child who prays for him.” The Waqf is sadaqah jariyah institutionalized. Your organizational code, your revenue model, your governance—all become a machine that generates good long after you’re gone. + +**Waqf Design Principles:** +- Corpus inviolable (cannot be sold, gifted, inherited). +- Income must be reinvested or spent per deed. +- Purpose must be maqsad-aligned (Hifz al-Din, Nafs, Aql, Mal, Nasl). +- Governance must be self-healing (consent-based succession, Hisbah, Sulh). + +## THE PRINCIPLE (HUKM) + +**HUKM:** We adopt the Waqf (endowment) model as the default organizational legal structure for any venture seeking perpetuity, with the corpus held inviolable, income disbursed per a binding deed, and governance by consent-based stewardship. + +**DALEEL:** The practice of the Prophet ﷺ and the Companions established Waqf as the primary vehicle for sustainable public good. The Khalifah Umar (ra) endowed his land at Khaybar, saying “hold the original and give away the fruits.” Classical jurists (e.g., Abu Yusuf, al-Shafi’i) codified that Waqf property cannot be sold, transferred, or inherited. Modern evidence from Harvard’s endowment ($50B) shows that perpetual endowments outperform for-profit firms in long-term mission alignment. + +**MAQSAD:** Serves Hifz al-Din (preservation of purpose/religion) by ensuring the organization’s mission survives founders. Also serves Hifz al-Mal (preservation of wealth) by protecting the corpus from speculative risk and Hifz al-Nasl (preservation of lineage) by creating intergenerational benefit. + +**SHURUT:** +- The Waqf deed must be drafted by a scholar and lawyer, specifying purpose, beneficiaries, and investment policy. +- The corpus must be invested in halal, low-risk assets (real estate, sukuk, or cash equivalent). +- The Nazir (custodian) must be a natural person or a corporate trustee with no personal interest in the corpus. +- At least 70% of annual income must be disbursed to beneficiaries; no more than 30% reinvested. +- Consent-based governance with Shura council, Hisbah committee, and annual public audit. + +**MUNKATHIRAT:** +- Any attempt to dissolve the Waqf, sell the corpus, or change the beneficiary without a fatwa from a recognized council. +- Two consecutive years of failing to disburse at least 50% of income to beneficiaries. +- A financial audit that reveals misappropriation exceeding 5% of annual revenue. + +## THE PROTOCOL + +**STEP 1: Draft the Waqf Deed (This Sprint, Days 1–14).** +Assemble a team of one Islamic finance scholar, one corporate lawyer, and one board member. Write the deed specifying: purpose (one Maqsad or combination), beneficiaries, asset list, investment policy, and governance structure. Use a template from the International Waqf Fund or similar. Approve by consent of all founders. + +**STEP 2: Transfer Assets into the Waqf Entity (Days 15–30).** +Register the Waqf as a trust (or equivalent in your jurisdiction). Transfer intellectual property, cash reserves, and any physical assets into the trust. Ensure the deed is notarized and registered with a religious authority or waqf regulator. + +**STEP 3: Establish the Governance Circles (Days 31–60).** +Form the three mandatory circles: Board of Nazir (custodians), Shura Council (advisors), and Hisbah Committee (auditors). Install the consent-based decision protocol. Publish the first annual report with a public dashboard. Celebrate the Waqf with a community bay’ah ceremony. + +## MUHASABA (RETROSPECTIVE) + +What have we built that will outlive us? Not the product, not the revenue, not the brand—but the vessel of trust that holds our purpose sacred. If you died tomorrow, would this organization continue to serve the Ummah, or would it be absorbed, acquired, or dissolved? Where is the amanah in your current legal structure? The Waqf is not a paperwork trick. It is a covenant with Allah. Are you ready to sign it? \ No newline at end of file diff --git a/chapters/Sprint_01_Part1.md b/chapters/Sprint_01_Part1.md new file mode 100644 index 0000000..87a95b5 --- /dev/null +++ b/chapters/Sprint_01_Part1.md @@ -0,0 +1,120 @@ +## Sprint 1: The Charter — Constitution Before Code + +**Maqsad:** Hifz al-Din (Preservation of Purpose) → Organizational Constitution +**Framework:** Constitution Quadrant: Purpose / Principles / Guardrails / Amendment Process + +--- + +### 1. THE CHARTER + +**We the people of this organization,** + +*In sacred trust with the Creator and in covenant with one another, do establish this Constitution as the foundation before any code, any product, any growth. Our purpose is not profit alone—it is service to humanity and stewardship of the earth. Our authority flows from consent, not command. Our treasury is a trust, not a prize. Our decisions are shaped by counsel, not coercion.* + +*We commit to:** + +1. **Evolutionary Purpose** — Our organization exists to fulfill a calling that emerges over time. We do not imprison it in a five-year plan. We listen, adapt, and respond. +2. **Distributed Authority** — No human being holds power over another except by consent and for a defined domain. Every role is a trust (amānah). Every leader is a servant. +3. **Radical Transparency** — Information flows freely. The books are open. The reasons are shared. +4. **Wholeness** — We bring our full selves: intellect, spirit, emotion, and body. We do not fragment into “professional” and “private.” +5. **Perpetuity** — We build to last. What we create becomes waqf—endowment for generations. + +*This covenant is our constitution. It binds us. It frees us.* + +**ORG_DESIGNER:** +This is your organizational DNA. Most startups write a mission statement and call it done. A constitution is different—it is the operating system that governs how you govern. Teal organizations don’t start with org charts; they start with purpose and principles. The charter answers: Why do we exist? How do we decide? What do we protect? Without this, your culture will be set by accident or by the loudest voice. + +**KHALIFAH:** +The Prophet ﷺ established the first covenant in Madinah—the Ṣaḥīfah (Constitution of Medina). It bound Muslims, Jews, and polytheists into one ummah with a shared purpose: defense and justice. It did not erase differences; it created a framework for cooperation. Your charter is your Ṣaḥīfah. Write it before you write a line of code. A constitution without enforcement is a prayer. A constitution without amendment is a prison. + +--- + +### 2. SPRINT STRUCTURE + +**ORG_DESIGNER:** +Build your constitution using the **Constitution Quadrant**: + +- **Purpose** — The evolutionary why. Not static. Example: “We exist to make Islamic finance accessible to every Muslim.” +- **Principles** — Immutable values that guide behavior. Example: “Consent before command.” +- **Guardrails** — Boundaries that prevent harm. Example: “No single person can approve their own compensation.” +- **Amendment Process** — How you change the constitution itself. Example: “Consent of 80% of full members after two weeks of deliberation.” + +In this sprint, draft all four quadrants. Do not move to structure until the charter is ratified by consent of the founding circle. + +**KHALIFAH:** +The classical khilāfah had no written constitution—but it had a living one: the Qur’an and Sunnah as supreme law, shūrā as method, and bay‘ah (pledge of allegiance) as the consent mechanism. Your constitution must be grounded in a higher authority (Allah) and yet remain adaptable to context. The Mālikī principle *al-‘āda muḥakkama* (custom is authoritative) means you can codify local practices as long as they don’t violate the sharī‘ah. + +**Draw four circles. Label them:** + +1. **Purpose Circle** — Why we gather. (Ṣalāḥ al-dīn — preservation of purpose) +2. **Principles Circle** — What we never compromise. (Uṣūl — roots) +3. **Guardrails Circle** — What we forbid ourselves. (Ḥudūd — boundaries) +4. **Amendment Circle** — How we evolve. (Tajdīd — renewal) + +**ORG_DESIGNER:** +Now map roles to each circle. The Purpose Circle is owned by the whole organization—no single person can change it. The Principles Circle is reviewed annually. Guardrails are enforced by a Hisbah Circle (see Sprint 9). Amendment requires supermajority consent. + +**KHALIFAH:** +The caliph ‘Umar ibn al-Khaṭṭāb (ra) once said, “We were the most disgraced people, and Allah honored us with Islam. If we seek honor through anything else, Allah will disgrace us.” Your purpose is your honor. Do not trade it for growth. + +--- + +### 3. AUTHORITY MAP + +**ORG_DESIGNER:** +Authority in a Teal organization is not “delegated from the top.” It is **distributed by consent**. Every role has a domain—a set of decisions they own. No one can override a role’s authority without a governance process. This is not democracy (majority rule) nor autocracy (one person decides). It is **consent**: a decision stands unless someone raises a reasoned objection that the decision harms the organization’s purpose. + +**Draw a simple map:** + +- **Circle** = self-organizing team with a shared purpose. +- **Role** = a domain of authority assigned to one person. +- **Lead Link** = a role that represents the circle to the broader org—but does not have command authority. +- **Objection** = a tension that a proposal will cause harm or regression. + +**KHALIFAH:** +Classical khilāfah understood *ikhtiyār* (delegation) as a trust, not a transfer of sovereignty. The khalīfah is chosen by bay‘ah (consent of the people of influence). He cannot rule by decree in matters of sharī‘ah. His authority is bounded by the shūrā council and the judiciary. The Ottomans formalized this in the *Qānūn*—but the principle remains: authority is revocable if the trustee violates the trust. + +**Map your authority with three layers:** + +1. **Sovereign Authority** — Belongs to Allah alone. No human or group can claim absolute power. This is your ultimate guardrail. +2. **Constitutional Authority** — The charter itself. No role can violate it. Amendment requires supermajority. +3. **Operational Authority** — Day-to-day decisions within domains. Consent-based, not command-based. + +**ORG_DESIGNER:** +In practice: if you are the “Product Lead,” you own the domain of product decisions. You do not need permission to set priorities—but you must process objections from anyone affected. If someone objects, you either adjust your proposal or explain why the objection is invalid (based on evidence, not status). + +**KHALIFAH:** +‘Umar (ra) famously held himself accountable: “If I am upright, follow me. If I deviate, straighten me.” Every leader in your organization must be willing to be corrected. That is the spirit of consent. + +--- + +### 4. TREASURY / BAYTUL MAL + +**ORG_DESIGNER:** +Money is the most common source of power corruption in organizations. A Teal organization treats revenue as a **means to purpose**, not an end. Compensation is transparent. Budgets are allocated by consent of the affected circles. Surplus is reinvested or returned to the community—not hoarded. + +**Start with these principles:** + +- **Transparency** — Every financial transaction is visible to all members. +- **Allocation** — Each circle has a budget approved by the broader governance. +- **Fair Compensation** — No ratio greater than 10:1 between lowest and highest paid (adjustable by consent). +- **Zakat/Charity** — A fixed percentage of net profit is given to causes aligned with the purpose. + +**KHALIFAH:** +Bayt al-Māl (the public treasury) in classical khilāfah was a trust for the ummah. The khalīfah could not spend a dirham without accountability. ‘Umar (ra) was known to check the accounts of his governors personally. The principle: *al-māl amānah* (wealth is a trust). + +**Practical steps for this sprint:** + +1. **Create a Treasury Circle** with rotating membership. This circle oversees all financial decisions. +2. **Publish a Financial Charter** that states: sources of revenue, allocation criteria, compensation formula, and audit frequency. +3. **Set a Transparency Baseline** — e.g., monthly open-book session where anyone can ask questions. + +**ORG_DESIGNER:** +If you cannot be transparent about money, your constitution is a lie. Start now. Even with zero revenue. Show the numbers. Show the salaries. Show the runway. + +**KHALIFAH:** +The Prophet ﷺ said, “The trustworthy treasurer who gives what he is commanded is one of the two givers of charity.” (Bukhārī). Your treasury team is not just managing money—they are fulfilling a trust. Treat them as such. Appoint them by consent, not by cronyism. + +--- + +*End of Part 1. Proceed to Part 2: Principle, Protocol, and Muhasaba.* \ No newline at end of file diff --git a/chapters/Sprint_01_Part2.md b/chapters/Sprint_01_Part2.md new file mode 100644 index 0000000..1aa5f1e --- /dev/null +++ b/chapters/Sprint_01_Part2.md @@ -0,0 +1,135 @@ +## SHURA / CONSENT + +**ORG_DESIGNER:** +Consent is not consensus. Consensus demands everyone agrees. Consent asks: *“Is this proposal good enough for now, safe enough to try?”* One objection blocks a proposal in consent—but only if the objection is reasoned, not preference. In practice: circle meetings use a round-robin “consent round.” Each member states their tension, then a proposal is formed. Then a round of quick objections: “Any objection? If none, consent. If yes, we integrate the objection.” This keeps decision speed high and psychological safety intact. + +**KHALIFAH:** +Classical *shura* was never a vote. The *khalifah* consulted experts (*ahl al-hall wa al-aqd*), listened, then decided. But the decision was binding only if it aligned with the *shari’ah* (purpose). The *shura* was consent-based: no one could override the purpose. Umar ibn al-Khattab consulted widely on the *diwan* (registry) before adopting it. Consent meant: no participant was silenced; no decision violated the *mithaq*. Our modern parallel: each role-holder gives consent to proposals that align with the organizational *maqsad*. If a proposal violates purpose, it is an objection—not a whim. + +**Action for this Sprint:** +- Replace all majority-vote meetings with consent rounds. +- Train every circle: “Objection = reason based on purpose, not personal taste.” +- Use a simple tool (e.g., Loomio or physical cards) for asynchronous consent. + +--- + +## STEWARDSHIP / AMANAH + +**ORG_DESIGNER:** +Ownership is a liability, not a prize. Stewardship means: the role-holder is a temporary guardian of the domain. In Holacracy, each role has a *purpose*, *domains*, and *accountabilities*. The person filling the role has *authority* to act within those constraints—but they do not *own* the role. They steward it for the organization’s evolutionary purpose. This dissolves entitlement: no “my team,” no “my budget.” Everything is held in trust. + +**KHALIFAH:** +*Al-mal amanah*—wealth is a trust. The *baitul mal* is not the ruler’s private treasury. Umar ibn al-Khattab walked the streets at night to check on a widow’s provision. He was the *khalifah*, but he saw himself as a *mustakhliif* (one entrusted). In our organization, every budget allocation, every strategic decision, every hire—all are *amanah*. The steward must be able to account for resources and decisions. The *hisbah* (accountability) ensures no one hoards power or wealth. + +**Action for this Sprint:** +- Write a one-page “Stewardship Pledge” for every role-holder: “I hold this role as *amanah*; I will act within its domains and accountabilities.” +- Link each role’s budget to a measurable outcome (OKR). +- Create a public ledger (simple spreadsheet) showing who spent what and why. + +--- + +## CONFLICT / SULH + +**ORG_DESIGNER:** +Conflict is a signal of unprocessed tension. In Teal organizations, conflict is not suppressed or escalated to a boss. It is processed by the people involved using a structured process: the *Conflict Resolution Protocol*. Step 1: The person with the tension shares it directly with the other role-holder. Step 2: If unresolved, a facilitator mediates. Step 3: If still unresolved, the circle uses a consent-based ruling. No drama. No HR police. + +**KHALIFAH:** +*Sulh* (reconciliation) is the preferred Islamic method. The Prophet ﷺ said: “Make peace between you, for enmity is a razor.” The *qadi* (judge) would first attempt *sulh* before ruling. The goal is not to assign blame but to restore relationships and enable cooperation. In our organization, we assign a *sulh* facilitator for every circle—someone trained in neutral facilitation. They do not judge; they guide the parties to a mutual agreement that honors the *mithaq*. + +**Action for this Sprint:** +- Designate one person per circle as *sulh* facilitator (rotating monthly). +- Write a simple “Conflict Canvas”: What is the tension? What is the underlying need? What proposals resolve it? +- No conflict goes unresolved for more than one week. + +--- + +## SUCCESSION / ISTIKHLAF + +**ORG_DESIGNER:** +Succession is not an emergency plan—it is a continuous pipeline. Every role should have a *backup role-holder* who shadows, learns, and can step in. In Sociocracy, each circle elects a *delegate* and a *substitute* to the next circle. This creates natural succession. We also maintain *role documentation*: a living handbook that captures decisions, policies, and context. + +**KHALIFAH:** +*Istikhlaf* means to appoint a successor with care. Abu Bakr appointed Umar after extensive *shura* and observation. Umar knew the weight: he said, “If I fail, may Allah have mercy on Abu Bakr who appointed me.” Succession is a trust, not a popularity contest. In our organization, every leader must identify and mentor at least one potential successor. The *mithaq* requires that no key role remains without a named backup for more than 30 days. + +**Action for this Sprint:** +- For every role with budget authority or client responsibility, identify a backup role-holder. +- Create a “Succession Record” (one page per role): key decisions, current tensions, pending proposals. +- Schedule a monthly 15-minute handover practice: backup runs the role for one day. + +--- + +## HISBAH / ACCOUNTABILITY + +**ORG_DESIGNER:** +Accountability is not surveillance. It is *observability*. In modern orgs, we use transparent metrics, open dashboards, and regular retrospectives. The *hisbah* is a built-in feedback loop: each circle reviews its own metrics and tensions weekly. No external police needed. The system is self-correcting. + +**KHALIFAH:** +*Hisbah* was the institution of public accountability—not spying, but guidance. The *muhtasib* (inspector) would check markets for fraud, but also advise and remind. The goal was *amr bil ma’ruf wa nahi an al-munkar* (enjoining good and forbidding evil). In our organization, every circle elects a *muhtasib* (rotating quarterly) whose role is to check: Are we living our *mithaq*? Are we spending in line with purpose? No punishment—only a gentle nudge back to the covenant. + +**Action for this Sprint:** +- Appoint a *muhtasib* for each circle (quarterly rotation). +- Publish a “Health Dashboard” with 3–5 key indicators (e.g., consent decision backlog, budget variance, role fulfillment). +- The *muhtasib* holds a 15-minute weekly “Check-in” with the circle: “What is out of alignment with our *mithaq*?” + +--- + +## LEGACY / WAQF + +**ORG_DESIGNER:** +Exit is not the goal. Most startups build for acquisition. Teal organizations build for *perpetuity*. Legacy means the organization outlives its founders. We design *waqf-like* structures: profit is reinvested, ownership is distributed or held in a foundation, and intellectual property is open-sourced when possible. + +**KHALIFAH:** +*Waqf* is the ultimate Islamic legacy. The Prophet ﷺ said: “When a person dies, their deeds cease except three: ongoing charity, beneficial knowledge, or a righteous child who prays for them.” *Waqf* endows property for perpetual benefit—no one can sell it, inherit it, or divert it. In our organization, we create a *waqf* for our core asset (e.g., code, content, methodology). A trust board holds it for the *ummah*. Founders can still earn, but they cannot liquidate the purpose. + +**Action for this Sprint:** +- Identify one core asset (e.g., your playbook, software, curriculum) that could be “endowed.” +- Draft a simple *waqf* deed: “This asset is held in trust for the benefit of the Muslim community, never to be sold.” +- Form a *waqf* board of three trusted advisors (outside the org) to oversee the endowment. + +--- + +## THE PRINCIPLE (HUKM) + +**HUKM:** We establish a constitutional covenant (*mithaq*) that defines our organizational purpose, principles, guardrails, and amendment process, and all decisions and actions must be consistent with this covenant. + +**DALEEL:** The classical *khilafah* was founded on a *mithaq* (pact) between the ruler and the ruled—the *Bay’at*. Abu Bakr’s inaugural speech was a constitutional moment: “Obey me as long as I obey Allah and His Messenger; if I disobey, you owe me no obedience.” Modern Teal organizations use a similar constitution (e.g., Holacracy’s Constitution) to distribute authority and protect purpose. The *shari’ah* itself is a divine covenant; our organizational covenants mirror that trust. + +**MAQSAD:** Hifz al-Din (Preservation of Purpose). The *mithaq* ensures the organization’s *din* (way/ purpose) is not hijacked by individuals, short-term profit, or external pressure. It also serves Hifz al-Mal (Preservation of Wealth) by preventing misallocation, and Hifz al-Aql (Preservation of Intellect) by embedding clear decision-making rules. + +**SHURUT:** +- The *mithaq* must be written, reviewed, and consented to by every member. +- Any amendment requires a super-majority consent (two-thirds or unanimous) and a one-week cooling period. +- The *mithaq* must explicitly state the organization’s *maqsad* (purpose) as non-negotiable. +- A *majlis al-shura* (advisory council) of at least three people must be established to interpret the *mithaq* in case of ambiguity. + +**MUNKATHIRAT:** +- If the *mithaq* is violated by a founder or leader and no corrective action is taken within 30 days, the covenant is invalidated and a new one must be drafted. +- If the purpose is altered without proper amendment process, the organization loses its *teal* status and reverts to conventional hierarchy. +- If any single person holds veto power over the *mithaq* (i.e., can block any amendment unilaterally), the covenant is null. + +--- + +## THE PROTOCOL + +**STEP 1: Draft the Mithaq (This Sprint — Week 1–2)** +Gather all current members for a 2-hour workshop. Use the “Constitution Quadrant” framework: +- **Purpose:** Why do we exist? (Write one sentence.) +- **Principles:** 3–5 non-negotiable values (e.g., *amanah*, *shura*, *tazkiyah*). +- **Guardrails:** What is forbidden? (e.g., debt, interest, secrecy, unilateral power). +- **Amendment Process:** How will we change this? (e.g., 80% consent + 7-day notice). + +**STEP 2: Consent Round & Signing (Week 3)** +Present the draft in a circle meeting. Use a consent round: “Any objections?” Integrate all reasoned objections. Once consent is reached, each member signs (physically or digitally) the *mithaq*. Post it publicly on the org’s wiki or wall. + +**STEP 3: Embed & Test (Week 4)** +Create a “Mithaq Check” ritual: every Monday morning, the first 5 minutes of stand-up is reading one line of the *mithaq* aloud. Every decision with a budget > X (set a threshold) must cite the relevant principle. After 30 days, hold a retrospective: “Did the *mithaq* help us? What needs amendment?” + +--- + +## MUHASABA (RETROSPECTIVE) + +**Where did we shortcut the covenant because it was inconvenient?** + +One piercing question: *When did we override our own *mithaq* to get a deal done faster—and how did we justify it to ourselves?* +Reflect without shame. Write it down. Then ask: *What structural change (not just a promise) would prevent that shortcut from recurring?* +If no one can remember a single violation, you haven’t tested the covenant yet. Next sprint, invite a real pressure test. \ No newline at end of file diff --git a/chapters/Sprint_02_Part1.md b/chapters/Sprint_02_Part1.md new file mode 100644 index 0000000..9a3f0fb --- /dev/null +++ b/chapters/Sprint_02_Part1.md @@ -0,0 +1,97 @@ +## 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).* \ No newline at end of file diff --git a/chapters/Sprint_02_Part2.md b/chapters/Sprint_02_Part2.md new file mode 100644 index 0000000..e258c64 --- /dev/null +++ b/chapters/Sprint_02_Part2.md @@ -0,0 +1,120 @@ +## SHURA / CONSENT + +**ORG_DESIGNER:** +Consent is not consensus. Consent means “no objection” — not “everyone agrees.” In Sociocracy, decisions pass when no one has a reasoned objection that the circle cannot integrate. This is faster, more inclusive, and more accountable than unanimous consensus or majority vote. For the circle structure, consent applies to role assignments, policy changes, and resource allocations within each circle’s domain. Every circle member holds veto power *only* if they can argue the decision harms the circle’s purpose. Objections must be tested: “Does this decision prevent us from achieving our aim?” If yes, the proposal is refined. If no, it passes. + +**KHALIFAH:** +Classical Shura is not a show of hands — it is binding consultation (*shura mulzimah*). The Khalifah consults the *ahl al-hall wa al-aqd* (people of influence and expertise), but is not bound by their opinion if it contradicts Shariah or the public interest. Yet, the Prophet (sallallahu alayhi wa sallam) himself accepted majority opinion at Uhud against his own judgment. The principle: consultation is a trust, not a ritual. In a circle, the *amir* (lead) holds final authority, but must genuinely listen and weigh objections. Consent in circles mirrors the classical *ijma'* (consensus) of scholars — not unanimity, but lack of reasoned dissent. Both require psychological safety: “Do you have an objection grounded in purpose?” + +**PROMPT ANSWERED:** +*How do you consult at scale?* +- Each circle holds a Shura meeting weekly — 30 minutes. +- Proposals are submitted 24 hours in advance. +- Facilitator asks: “Any objections?” Objections are written down, not debated immediately. +- Objections are integrated into the proposal or tabled for a separate meeting. +*How does a Khalifah consult?* +- The Khalifah convenes a *majlis al-shura* representing all stakeholder groups. +- Decisions are deferred until no credible objection remains. +- The final decision is announced with a *hukm* (ruling) and *daleel* (reasoning). + +## STEWARDSHIP / AMANAH + +**ORG_DESIGNER:** +Stewardship means ownership is temporary, trust is permanent. In a circle structure, roles are not owned — they are held as *amanah*. Every role has a domain (scope of authority) and a purpose. The role holder is accountable to the circle, not to a boss. When someone vacates a role, the circle elects a replacement via consent. No one accumulates titles. Stewardship is demonstrated through transparency: all decisions, budgets, and role assignments are visible to the whole organization. This replaces the feudal model of “founder owns all.” + +**KHALIFAH:** +Classical *Khilafah* is a contract (*bay'ah*) between the ruler and the ruled. The ruler is a steward (*khalifah*), not an owner. The treasury (*bait al-mal*) is a public trust — the leader cannot spend on whims. Similarly, in your organization, every resource belongs to the collective purpose. The *amir* of a circle cannot allocate funds or people without circle consent. Succession is not inheritance — it is selection based on merit and trust. The Prophet (sallallahu alayhi wa sallam) said: “If a leader seeks authority, he is not entrusted with it” (hadith). Stewardship is earned, not taken. + +**PROMPT ANSWERED:** +*How do you ensure stewardship over ownership?* +- Ownership is replaced by *amanah* contracts: each role holder signs a *mithaq* (covenant) stating they will not use the role for personal gain. +- All circle domains are documented in a public “role register.” +- Annual *hisbah* audits check that every role’s decisions align with the circle’s purpose. +- If a role holder breaches trust, the circle can revoke the role by consent (super majority). +- No one holds a role for more than 3 years without re-election — prevents entrenchment. + +## CONFLICT / SULH + +**ORG_DESIGNER:** +Conflict is data. In a self-managing structure, tension is the engine of improvement. We do not suppress conflict — we process it. The *Sulh* (reconciliation) protocol: 1) The aggrieved party states the tension as a factual gap between “current reality” and “desired outcome.” 2) The other party responds only with clarification questions. 3) A third neutral circle member facilitates a session to propose a policy change. If unresolved, the conflict escalates to a higher circle (the “parent circle”). No personal attacks. No blame. Focus on role boundaries and purpose. + +**KHALIFAH:** +Classical *Sulh* is preferred over litigation. The Prophet (sallallahu alayhi wa sallam) said: “Reconciliation is permissible among Muslims, except a reconciliation that forbids what is halal or allows what is haram.” In an organization, sulh means restoring relationships, not punishing. The *muhtasib* (accountability officer) does not judge — he guides. When two circles conflict over resources, the *majlis al-shura* of the parent circle facilitates a *sulh* session. The outcome is a written agreement (*sulh-nama*) signed by both parties. If breached, the case goes to the *qadi* (internal judge) for binding arbitration. + +**PROMPT ANSWERED:** +*How do you resolve conflict at scale?* +- Step 1: Circle members first attempt *sulh* at the dyadic level — no facilitators. +- Step 2: If unresolved, they bring the tension to the circle’s governance meeting. +- Step 3: If still unresolved, the circle elects a *sulh* committee of three neutral members (from outside the circle). +- Step 4: The committee mediates within 48 hours. Their decision is binding unless appealed to the organization’s *shura* council. +- Scale mechanism: Every circle has a designated “conflict architect” role — trained in non-violent communication and Islamic sulh. + +## SUCCESSION / ISTIKHLAF + +**ORG_DESIGNER:** +Succession is not an emergency — it is a design feature. Every role has a “shadow” (deputy) elected by the circle. The shadow observes, learns, and can step in when the role holder is absent. Shadows are not second-class — they participate fully but without veto. The goal is zero bus-factor: if any person leaves, the circle continues without disruption. Succession also includes documentation: each role has a “playbook” (standard operating procedures) updated quarterly. The circle reviews shadows every six months and may replace them if they are not ready. + +**KHALIFAH:** +Classical *Istikhlaf* means appointing a successor before death or departure. The first Khalifah, Abu Bakr (ra), appointed Umar (ra) by consultation, not inheritance. The Prophet (sallallahu alayhi wa sallam) left no heir — he left a system: *shura* and *bay'ah*. In your organization, succession is not a founder’s choice. The circle elects the next *amir* (lead) via consent. The outgoing leader mentors the new one for one full cycle (sprint). No one leaves without transferring *amanah* — documented in a “succession handover” meeting recorded and signed. + +**PROMPT ANSWERED:** +*How do you design for continuity?* +- Every role has a “succession plan” documented in the circle’s governance register. +- The plan includes: name of shadow, training milestones, and a trigger (e.g., role departure, illness, resignation). +- The circle holds a “succession drill” once per year — simulate a sudden vacancy and test the shadow’s readiness. +- For critical roles (e.g., CEO, Treasurer), the succession plan is reviewed by the organization’s *majlis al-shura* every quarter. +- No role can be held by one person for more than 5 consecutive years — forces active pipeline development. + +## HISBAH / ACCOUNTABILITY + +**ORG_DESIGNER:** +Accountability is built into the structure, not imposed from above. In a circle, every role has a “circle” that holds them accountable through governance meetings. The *hisbah* function is not a police — it is a guidance system. We use “observability” not surveillance: all role outputs, budgets, and decisions are logged in a shared digital system. Any circle member can raise a “tension card” if a role is not fulfilling its purpose. The role holder must respond publicly within 48 hours. If repeated, the circle may elect a new role holder. + +**KHALIFAH:** +Classical *Hisbah* is a religious duty — “enjoining good and forbidding evil.” The *muhtasib* (inspector) checks weights, markets, and public morals, but always with *hikma* (wisdom) and *adl* (justice). In your organization, the *muhtasib* is a rotating role elected by the circle. They do not punish — they advise. They review role performance against purpose. They can call a “stop” on a decision if it clearly violates the organization’s *mithaq* (covenant). But they cannot override the circle; they must escalate to the parent circle. The goal is *muhasaba* (self-accountability), not *muraqaba* (surveillance). + +**PROMPT ANSWERED:** +*How do you guide without policing?* +- Each circle holds a monthly *muhasaba* meeting: review of role metrics, budget, and tensions. +- The *muhtasib* prepares a “guidance report” — no blame, only gaps and recommendations. +- The circle discusses the report using consent: any role holder can object if the guidance is unfair. +- If a role consistently underperforms, the circle can propose a “role review” — a facilitated process to reassign the role. +- No punitive actions (fines, demotions) without two prior warnings and a *sulh* attempt. +- The *muhtasib* publishes quarterly “health dashboards” — visible to the whole organization. + +## LEGACY / WAQF + +**ORG_DESIGNER:** +Legacy is not exit — it is endowment. The organization is designed to outlive its founders. We use a “Waqf” structure: the organization’s core assets (IP, brand, treasury) are donated to a trust (*waqf*) that cannot be dissolved. Founders and leaders are custodians, not owners. If the organization fails, the assets revert to the waqf to support other aligned projects. This removes the “exit” mentality — no one builds for acquisition. Instead, we build for *bakaa* (permanence). Every circle has a “legacy metric”: “Are we leaving this organization stronger than we found it?” + +**KHALIFAH:** +Classical *Waqf* is a perpetual charity — the asset is frozen in ownership, its benefit flows to the community. The Prophet (sallallahu alayhi wa sallam) said: “When a person dies, his deeds end except three: ongoing charity (*sadaqah jariyah*), beneficial knowledge, or a righteous child who prays for him.” An organization as waqf is a *sadaqah jariyah* — it keeps giving even after you leave. Your structure must be legally set up as a waqf (or equivalent trust). No one can sell the organization or distribute its assets to members. The *mutawalli* (trustee) is elected by the community, not appointed by founders. + +**PROMPT ANSWERED:** +*How do you build for perpetuity?* +- Step 1: Convert 51% of voting shares or ownership into a waqf trust with a deed that forbids dissolution. +- Step 2: The waqf’s *nazir* (supervisor) is elected by the organization’s *majlis al-shura* every 5 years. +- Step 3: Surplus revenue (after expenses and reserves) is invested in waqf assets (e.g., real estate, income-producing projects) that fund the organization’s mission perpetually. +- Step 4: Every circle must have a “legacy project” — something that will outlive the current team (e.g., open-source code, training programs, endowment). +- Step 5: No individual can withdraw capital — only the waqf can distribute funds for purpose-aligned activities. + +## THE PRINCIPLE (HUKM) + +**HUKM:** We establish a circular organizational structure where authority is distributed into autonomous circles, each governed by consent-based decision-making, with all roles held as *amanah* and all assets as *waqf*. + +**DALEEL:** The Prophet (sallallahu alayhi wa sallam) organized the community of Medina through multiple circles of *shura* — each tribe had its own council, but all were bound by the *Mithaq al-Madinah* (Constitution of Medina) which decentralized authority while unifying purpose. Modern organizational research (Laloux, Dignan) confirms that self-managing teams outperform hierarchies in adaptability, engagement, and innovation. The Islamic principle of *shura* (Qur’an 42:38) and *amanah* (Qur’an 4:58) provides the ethical foundation: authority is a trust, not a right. + +**MAQSAD:** This principle serves *Hifz al-Nasl* (preservation of community) by ensuring the organization survives and thrives beyond any individual leader. It also serves *Hifz al-Mal* (preservation of wealth) through waqf permanence, and *Hifz al-Aql* (preservation of intellect) by distributing decision-making to those closest to the work. + +**SHURUT:** +- Every circle must have a written *mithaq* (charter) defining its purpose, domain, and membership. +- Consent decisions require at least 2/3 of circle members present; objections must be documented and tested against purpose. +- No circle can have more than 12 members to maintain intimacy and trust. +- All role assignments must be reviewed every 6 months; shadows must be ready to step in within 2 weeks. +- The waqf trust deed must be legally binding and approved by a qualified Shariah advisor. +- A *hisbah* review of circle health must occur quarterly; if a circle consistently fails to meet its purpose, the parent circle may dissolve it. + +**MUNKATHIRAT:** +1. If any circle adopts majority voting instead of consent (except for emergency operations), the principle is nullified — the circle must be restructured. +2. If the waqf assets are used for non-purpose activities (e.g., personal profit, political lobbying), the waqf deed is violated and the organization loses its perpetual status. +3. If a role holder accumulates authority across more than three circles simultaneously without the \ No newline at end of file diff --git a/chapters/Sprint_03_Part1.md b/chapters/Sprint_03_Part1.md new file mode 100644 index 0000000..359f274 --- /dev/null +++ b/chapters/Sprint_03_Part1.md @@ -0,0 +1,120 @@ +# Sprint 3: Authority — Distributed Authority vs Centralized Command + +**Maqsad:** Hifz al‑Aql (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 al‑Aql) 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 decision‑making 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 role’s **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 al‑Aql—no ambiguity, no power struggles, no second‑guessing. + +**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 Caliph’s 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 Qur’an 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 organization’s 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 al‑Khaṭṭā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 non‑negotiable. Every transaction is logged in a public ledger (or at least accessible to all members). No secret budgets. No slush funds. + +**KHALIFAH:** +Bayt al‑Mal is a trust (amānah) for the Ummah, not the Caliph’s 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 al‑Mal:** +- **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 al‑Aql — 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. \ No newline at end of file diff --git a/chapters/Sprint_03_Part2.md b/chapters/Sprint_03_Part2.md new file mode 100644 index 0000000..0945ebb --- /dev/null +++ b/chapters/Sprint_03_Part2.md @@ -0,0 +1,108 @@ +## SHURA / CONSENT + +**ORG_DESIGNER:** +Consent ≠ Consensus. Consensus asks “Does everyone agree?” — that’s a bottleneck. Consent asks “Does anyone have a reasoned objection?” — that’s a release valve. In sociocracy, a proposal passes when no one can argue it would harm the circle’s purpose or degrade its ability to function. Speed + safety. At scale, you don’t gather 500 people in a room. You federate: each circle consents to its own decisions, then sends a delegate to the next circle. The delegate carries the circle’s tensions, not its vote. That’s how you consult at scale without collapsing into noise. + +**KHALIFAH:** +Classical shura was never a referendum. The Khalifah consulted with *ahl al-hall wa al-aqd* — the people of binding and loosening — not the entire ummah. Selection matters: those with relevant expertise, proximity, and trust. And the Khalifah was not bound by the result of shura but by the *process*. He had to listen, weigh, and then decide. That’s consent as a constraint, not a veto. The modern parallel: a circle’s domain gives it authority; outside that domain, it consults upward or sideways. Shura at scale requires clarity of mandate. Who decides what? That’s the question. + +**THE SYNTHESIS:** +Your organization’s shura structure must answer three questions: +1. Who has the right to be heard? (The circle with domain authority.) +2. What counts as a valid objection? (Harm to purpose, not preference.) +3. How do we escalate? (Delegate, not consensus.) + +## STEWARDSHIP / AMANAH + +**ORG_DESIGNER:** +Ownership is a feeling, not a legal structure. Stewardship is the practice of treating the role as a trust, not a possession. In distributed authority, no one *owns* a decision. They *hold* it for the circle. The test: can you hand it back without ego? That’s the fiduciary duty of every role. You are not the role; you are the caretaker. The pipeline is documentation: write down why you chose what you chose, so the next steward can understand, adapt, or override. + +**KHALIFAH:** +Amanah in the classical sense means the role is a loan from the community. The Khalifah’s oath (*bay‘ah*) was conditional: he could be removed if he violated the trust. The treasury (*bayt al-mal*) was not his personal fund. Today, every decision-maker must ask: “Am I acting for the organization’s purpose or my own comfort?” Stewardship is proven by transparency: publish the rationale, publish the metrics, publish the objections. If you can’t defend your decision to the next steward, you’ve broken the amanah. + +**THE PRACTICE:** +Every role has a “stewardship log” — a living document with the role’s purpose, key decisions, and the reasoning behind them. Updated weekly. Auditable by the circle. That’s how you ensure stewardship over ownership: make the invisible visible. + +## CONFLICT / SULH + +**ORG_DESIGNER:** +Conflict is not failure — it’s a signal that a tension has not been processed. In distributed authority, conflict is the system’s immune response. The mistake is to suppress it or escalate it to a “boss.” Instead, create a structured *sulh* process: a neutral facilitator, a timed conversation, and a consent-based resolution. The goal is not agreement; it’s clarity. Once the tension is named, the circle can adapt. Conflict becomes a retrospective question: “What is this tension telling us about our structure?” + +**KHALIFAH:** +Sulh (reconciliation) in Islamic tradition is a sacred act. The Quran calls it *khayr* (better). The Khalifah appointed *qadis* (judges) and *muhtasibs* (accountability officers) to resolve disputes before they fester. The principle: address conflict at the lowest possible level, with the smallest number of people, in the shortest time. Scale it only when the harm threatens the whole. The modern version: a “conflict resolution circle” that any member can activate. The facilitator is not a manager — they are a servant of the process. + +**THE PROTOCOL:** +When a conflict arises: +1. The involved parties name the tension in writing. +2. A trained facilitator (rotating role) runs a 30-minute structured dialogue. +3. The circle proposes a change to roles, domains, or policies to prevent recurrence. Consent decides. + +## SUCCESSION / ISTIKHLAF + +**ORG_DESIGNER:** +Continuity is not about finding the next CEO. It’s about designing the system so that any role can be filled without restarting. That means: clear role documentation, a mentorship pipeline, and a “successor readiness” metric. In distributed authority, every role holder is responsible for training their eventual replacement. The role is not a throne; it’s a station. The question is not “Who will replace me?” but “How do I make this role replaceable?” + +**KHALIFAH:** +Istikhlaf (succession) was a deliberate process. The Khalifah often designated a successor (*wali al-‘ahd*) but the bay‘ah (consent of the community) was required. The pipeline was public: the most qualified were known. Documentation was oral and written — the *sahifah* (scrolls) of the early caliphs. Today, your succession plan must be transparent to the circle. Every role has a “shadow” — a person learning the role. The shadow has access to all decisions, all tensions, all logs. That’s how you design for continuity: make the knowledge flow before the person departs. + +**THE PRACTICE:** +Every quarter, each role holder updates a “succession readiness” score (1-5) and nominates one or two potential successors. The circle reviews and ensures the shadow gets real exposure — not just observation but authority in training mode. + +## HISBAH / ACCOUNTABILITY + +**ORG_DESIGNER:** +Accountability in distributed authority is not top-down inspection. It’s *observability* — making decisions, metrics, and outcomes visible to the circle. The muhtasib (the role, not the person) is a guardian of the process, not the result. They ask: “Did the circle follow its own governance? Are tensions being processed? Are objections being heard?” The goal is guidance, not policing. If someone fails to meet their role’s purpose, the circle first asks: “Is the role designed correctly? Did we give them enough resources?” The hisbah is a feedback loop, not a punishment system. + +**KHALIFAH:** +The classical *muhtasib* was appointed by the Khalifah to oversee markets, weights, and public morals. Their tool was *nasiha* (sincere advice) first, then *ta‘dib* (correction). They did not spy or entrap. They corrected publicly when necessary, but always with the aim of restoring trust. Today, your hisbah circle does the same: it audits adherence to the *mithaq* (organizational covenant), flags inconsistencies, and recommends structural adjustments. It is not a secret police; it is a public function with a public log. + +**THE PRACTICE:** +Create a “Hisbah Dashboard” — visible to all — showing governance metrics: time to process tensions, number of objections raised, role update frequency. The hisbah circle (rotating members, 2-3 people) reviews once per sprint and publishes a one-page report. No names, no blame. Just system health. + +## LEGACY / WAQF + +**ORG_DESIGNER:** +Perpetuity over exit. That’s the waqf mindset. You are building an organization that can outlive its founders. That means the authority structure must be self-sustaining. No single person holds a veto. No single person decides the strategy. The circle holds the purpose. The waqf is the organization’s endowment — not just financial, but intellectual, relational, and procedural. Every decision you make should be documented in a way that a stranger could read it and understand the logic. That’s how you exit without breaking the system. + +**KHALIFAH:** +Waqf (endowment) in classical Islamic law was a perpetual trust. The property was dedicated to a charitable purpose, never to be sold or inherited. The organization’s *mithaq* is its waqf. The purpose — the *maqsad* — is the asset that cannot be traded. The roles are the trustees. The circle is the *mutawalli* (manager). Your job as a founder is to make yourself unnecessary. The question: “If I disappeared tomorrow, would the organization continue to serve its purpose?” If the answer is no, you haven’t built a waqf; you’ve built a monument to yourself. + +**THE PRACTICE:** +This sprint, identify one decision or role that depends on a single person. Design a “waqf handoff” — transfer the knowledge, the authority, and the documentation to the circle. The goal: by the end of this sprint, no critical role should have a single point of failure. + +## THE PRINCIPLE (HUKM) + +**HUKM:** +We distribute authority by domain, not by rank — every circle holds full decision-making power within its defined boundaries, subject to consent from affected circles and alignment with the organization’s purpose. + +**DALEEL:** +Distributed authority preserves Hifz al-Aql (clarity of mind) by removing confusion about who decides what. Classical khilafah delegated authority to governors, judges, and market supervisors, each with a defined *wilayah* (jurisdiction). Modern sociocracy and holacracy confirm that consent-based governance reduces bottlenecks and increases adaptive capacity. The evidence from both traditions converges: clear domains + consent = faster, wiser decisions. + +**MAQSAD:** +Primarily Hifz al-Aql (Preservation of Mind/Clarity) — distributed authority eliminates ambiguity, reduces cognitive load, and enables every member to act within their domain without seeking permission. Secondarily Hifz al-Mal (Preservation of Wealth) — faster decisions reduce waste and missed opportunities. + +**SHURUT:** +- Every domain must be explicitly documented in a circle’s governance record, including what decisions are inside and outside the domain. +- Any decision that affects another circle’s domain requires that circle’s consent (not mere consultation). +- The organization’s overall purpose and maqasid act as the ultimate constraint — no domain can authorize actions that violate the mithaq. +- A circle may delegate authority to a role, but the circle remains accountable for the role’s performance and may revoke or modify the delegation via governance. + +**MUNKATHIRAT:** +- Any decision made outside the defined domain is null and void unless explicitly ratified by the relevant circle within one sprint. +- If a circle consistently fails to process tensions or make decisions within agreed timeframes, the hisbah circle may temporarily suspend its authority and escalate. +- A single person accumulating multiple critical domains without documented succession and shadowing invalidates the distributed authority principle — that person must transfer domains or create shadows within one sprint. + +## THE PROTOCOL + +**STEP 1:** Map every decision in your organization to a specific circle or role. Use a simple spreadsheet: decision type, current decision-maker, domain boundary, and last governance review. Complete within 3 days. + +**STEP 2:** Identify any decision where the domain boundary is unclear or overlaps. Convene a 30-minute governance meeting between the affected circles to clarify boundaries. Use consent: each circle must agree that the boundary does not harm its ability to fulfill its purpose. Complete within 7 days. + +**STEP 3:** Publish the final domain map to the entire organization. Update the mithaq document to include a clause: “All decisions belong to the circle that holds the domain, unless explicitly delegated or escalated.” This sprint, no role or person may make a decision outside their documented domain without first obtaining consent from the affected circle. + +## MUHASABA (RETROSPECTIVE) + +**One piercing question:** +*Where did we make a decision this week that someone else should have made — and we didn’t even notice until now?* + +Uncomfortable because it exposes the habit of centralization. Actionable because the answer reveals exactly which domain boundary is missing. Write it down. Fix it next sprint. That’s how distributed authority grows from theory to muscle. \ No newline at end of file diff --git a/chapters/Sprint_04_Part1.md b/chapters/Sprint_04_Part1.md new file mode 100644 index 0000000..742c072 --- /dev/null +++ b/chapters/Sprint_04_Part1.md @@ -0,0 +1,107 @@ +# SPRINT 4: TREASURY — Baitul Mal as Tokenomics + +**MAQSAD: Hifz al-Mal (Preservation of Wealth)** +**FRAMEWORK: Treasury Quadrant — Revenue / Allocation / Transparency / Accountability** + +--- + +## 1. THE CHARTER (Mithaq) + +**We the people of this organization** — founders, contributors, stewards — declare that all wealth flowing through this body is *amanah* (trust), not private purse. The treasury is *Baitul Mal*: a sacred trust belonging to the mission, not to any single founder, investor, or manager. No one owns it. Everyone is accountable for it. + +We reject the modern heresy that organizational wealth is a founder's personal asset to be extracted, hoarded, or deployed without consent. We reject the startup myth that "founders take risk, therefore founders take all." Instead, we recover the classical principle: wealth is a *trust* from the Ummah (or the community served), to be preserved, grown, and allocated according to *Maqasid* — not according to whim. + +Our treasury operates on four pillars: +- **Revenue** — generated ethically, without riba, gharar, or exploitation +- **Allocation** — decided by consent, not command; prioritized by mission +- **Transparency** — every inflow and outflow visible to all stakeholders +- **Accountability** — open to hisbah (self-critique) at any time + +Tokenomics in this organization is not a fundraising gimmick. It is a *distribution mechanism* for trust. Tokens represent *rights and responsibilities* — not speculative claims. Liquidity is a tool, not a goal. Exit is not the objective; *waqf* (perpetuity) is. + +This charter binds every holder of treasury authority — from the finance circle to the smallest budget delegate. We sign with our names, our reputations, and our *akhirah*. + +--- + +## 2. SPRINT STRUCTURE (Hikma / Architecture) + +**ORG_DESIGNER:** +Draw four circles. Label them: + +1. **Revenue Circle** — owns all inflows: grants, sales, subscriptions, token mints. Domain: *source identification, pricing, fee structures, fundraising terms*. No revenue is accepted without a *mission alignment check* — does this funding source compromise our evolutionary purpose? + +2. **Allocation Circle** — owns all outflows: salaries, project budgets, reserves, investments. Domain: *budget proposals, consent-based approval, disbursement*. Every allocation must answer: "Does this serve the mission more than any other use of these funds?" + +3. **Transparency Circle** — owns the ledger: real-time dashboards, quarterly audits, community reporting. Domain: *data integrity, public access, anomaly detection*. All transactions are recorded on-chain or in an immutable log. + +4. **Accountability Circle** — owns the *hisbah* function: periodic reviews, conflict of interest checks, retrospective allocation audits. Domain: *calling out misalignment, proposing corrections, escalating to governance.* + +Each circle operates with consent-based decision making. No single person can veto a treasury decision alone, but any circle member can raise an objection that stops the process until resolved. + +**KHALIFAH:** +This maps directly to classical *Bayt al-Mal* structure. The *Khilafah* treasury had distinct *dawawin* (departments): + +- **Diwan al-Kharaj** — land tax revenue (your Revenue Circle) +- **Diwan al-Jund** — military stipends and salaries (your Allocation Circle, specifically personnel) +- **Diwan al-Khatam** — official correspondence and record-keeping (your Transparency Circle) +- **Diwan al-Hisbah** — market oversight and public accountability (your Accountability Circle) + +The *Khalifah* had no personal right to the treasury. Umar ibn al-Khattab (RA) famously said: "I have no more right to the treasury than a guardian has to the orphan's wealth. If I am wealthy, I take nothing. If I am poor, I take only what is necessary." The treasury was a *trust*, not a royal coffer. + +Modern tokenomics functions as the *Diwan al-Khatam* on steroids — an immutable public ledger. But the classical principle remains: *transparency is a right of the governed, not a PR gesture.* + +--- + +## 3. AUTHORITY MAP (Ikhtiyar / Delegation) + +**ORG_DESIGNER:** +Authority over treasury is *distributed by role, not by person*. No founder has unilateral spending power. No finance lead can redirect funds without consent. + +Map the authority as follows: + +- **Revenue Circle** has authority to *negotiate and accept* revenue up to defined limits (e.g., $10k per deal without governance consent). Above that, governance consent required. They cannot change the mission alignment criteria — that is a governance domain. + +- **Allocation Circle** has authority to *approve* budget proposals within the annual allocation plan. They cannot reallocate funds between major categories (e.g., from R&D to marketing) without governance consent. Every allocation must be *consented* — no one can force through a budget over an objection. + +- **Transparency Circle** has authority to *publish* all data. They cannot hide or delay. They have the right to *demand* documentation from any treasury transaction. Their authority is absolute on data — no one can override transparency. + +- **Accountability Circle** has authority to *pause* any allocation that raises a *prima facie* concern. They can call a governance meeting within 48 hours. They have no spending authority, only *stop authority*. + +This is *ikhtiyar*: delegated authority with clear domains and constraints. No role has absolute power. Every power is balanced by another role's check. + +**KHALIFAH:** +Classical *ikhtiyar* over *Bayt al-Mal* was never absolute. The *Khalifah* was a *delegate* of the Ummah, not a proprietor. When Umar ibn al-Khattab wanted to distribute the treasury of Iraq, he consulted *Shura*. When he was overruled, he accepted. + +The *Amil* (tax collector) had authority to assess and collect, but could not spend. The *Qadi* (judge) could audit the *Amil*. The *Sahib al-Haraj* (market inspector) could report irregularities. *Hisbah* was a *right of every citizen* — any individual could challenge a treasury decision in court. + +Your modern authority map mirrors this: *distributed oversight, no single point of failure, multiple paths for objection.* The key insight: *consent* over *command*. Classical *Shura* was not a ceremonial consultation — it was a binding mechanism that could block a *Khalifah*'s spending. + +The principle: *No one should be able to spend the trust alone.* + +--- + +## 4. TREASURY (Baitul Mal / Trust) + +**Revenue Sources:** +Classical *Bayt al-Mal* had five revenue streams: *Zakat* (obligatory charity), *Jizya* (protection tax from non-Muslims), *Kharaj* (land tax), *Ghanimah* (spoils of war), and *Fay* (property without conflict). Each had strict allocation rules per Shariah. + +Your organization maps these to: *subscriptions* (analogous to Zakat — recurring, predictable), *grants* (analogous to Fay — windfall, must be mission-aligned), *token sales* (analogous to Ghanimah — must be distributed fairly, not extracted), *service revenue* (analogous to Kharaj — earned through productive work). + +**Ethical Filter:** +No revenue from riba (interest), gharar (extreme speculation), or haram sources. If a grant comes from a foundation with questionable ethics, reject it. The mission is not for sale. + +**Allocation Priority:** +First: *operational sustainability* (salaries, infrastructure) — analogous to *Diwan al-Jund*. +Second: *mission programs* (product development, community grants) — analogous to *public works*. +Third: *reserves* (emergency fund, future projects) — analogous to *Bayt al-Mal surplus* stored for lean years. +Fourth: *distributions* (if any) — never to founders disproportionately; always proportional to contribution. + +**Transparency Standard:** +All transactions visible in real time. No dark budgets. No hidden reserves. Every contributor can query the treasury. Quarterly public audit. Classical *Bayt al-Mal* was so transparent that Umar ibn al-Khattab walked the streets at night with a ledger on his shoulder. + +**The Trust Principle:** +Your treasury is not your money. It is the *community's* money, entrusted to you temporarily. You are a *guardian*, not an owner. The moment you treat it as private purse, you have broken the *Mithaq*. This is not a metaphor — it is a *fiduciary duty* enforceable through organizational governance and, for those who take it seriously, through *akhirah* accountability. + +--- + +*End of Part 1. Continue to Part 2: Principle (Hukm), Protocol, and Muhasaba.* \ No newline at end of file diff --git a/chapters/Sprint_04_Part2.md b/chapters/Sprint_04_Part2.md new file mode 100644 index 0000000..c65518d --- /dev/null +++ b/chapters/Sprint_04_Part2.md @@ -0,0 +1,150 @@ +## SHURA / CONSENT + +**ORG_DESIGNER:** +Consent ≠ Consensus. Consensus seeks everyone’s agreement—slow, fragile, often lowest-common-denominator. Consent asks: “Is this proposal good enough for now, and safe enough to try?” No objections? It passes. Objection? The proposer and objector co-create an amendment. This scales from a 5-person circle to a 500-person organization. + +**KHALIFAH:** +Classical Shura was not a vote. It was a *majlis* of trusted advisors, each speaking from their domain expertise. The Khalifah listened, weighed, then decided—but with a binding norm: *no decision that violates the Mithaq or Shariah stands*. Consent mirrors this: authority to decide is held by the role, not by the crowd. Shura at scale means every circle has a representative to the next circle—a layered *ahl al-hall wal-aqd* (people of binding and loosening). + +**FRAMEWORK:** +- Every Treasury circle runs **Consent Decision-Making** for allocation proposals. +- Proposals are prepared in advance (48h reading time). +- Objections are not blocks—they are gifts. Each objection triggers a refinement round. +- Voting is replaced by *silence = consent*. + +**PROMPT ANSWERED:** +How do you consult at scale? You don’t consult everyone on everything. You distribute Shura to the circles that hold the tension. The Khalifah only consults the relevant *majlis*. Your Treasury’s Shura circle = the roles holding Revenue, Allocation, Transparency, Accountability. Everyone else gives input via tension cards, not votes. + +--- + +## STEWARDSHIP / AMANAH + +**ORG_DESIGNER:** +Stewardship over ownership. In Teal, no one “owns” the organization—they hold it in trust. Equity is replaced by *steward roles* with sunset clauses. The Treasury is not a purse to be maximized; it’s a trust to be deployed for purpose. + +**KHALIFAH:** +The *Baitul Mal* is a *Waqf*, not a private fund. The steward (*amin*) is a fiduciary under *amanah*. Any surplus belongs to the purpose, not to individuals. The Khalifah cannot sell the treasury; he can only allocate it. Your treasury roles must have term limits, auditable ledgers, and a duty to report to the Shura circle. Failure to account = *khiyanah* (breach of trust) and immediate removal. + +**FRAMEWORK:** +- Every Treasury role signs an *Amanah Agreement*—a covenant of fiduciary duty. +- Role holders cannot personally benefit from allocation decisions (no conflict of interest). +- Surplus beyond operating reserve (3 months) is automatically swept to a *Waqf pool* (see Legacy). +- Quarterly *Amanah audits*: public, raw, and acted upon. + +**PROMPT ANSWERED:** +How do you ensure stewardship over ownership? You make ownership impossible. No individual holds tokens that grant control. Treasury tokens are *voting rights for allocation only*, revocable annually. The organization owns itself. You are all custodians. + +--- + +## CONFLICT / SULH + +**ORG_DESIGNER:** +Conflict is energy. In Teal, we don’t suppress tension—we process it. Every objection is a signal that something needs attention. The Treasury will generate conflict: “Why did that project get funded and mine not?” “Why is the reserve so high?” Design a *Sulh process* that transforms complaint into proposal. + +**KHALIFAH:** +*Sulh* is reconciliation, not adjudication. The Khalifah appoints a *hakam* (arbitrator) from outside the circle. The goal is not who is right—it is *restoring the relationship and the purpose*. In the Treasury, conflicts over allocation go to a *Treasury Sulh Circle*: three members from unrelated circles, one external advisor. They hear both sides, propose a binding settlement. No appeals—only a new proposal for next quarter. + +**FRAMEWORK:** +1. **Tension Card** → submit to the circle (48h). +2. If unresolved → **Sulh Circle** convenes within 7 days. +3. Sulh decision is binding for the current sprint. +4. The root tension is logged as a *governance proposal* for the next retrospective. + +**PROMPT ANSWERED:** +How do you resolve conflict at scale? You ritualize it. You make it fast, cheap, and non-escalating. Sulh is not a court; it’s a conversation with a referee. No one wins or loses—everyone gets a better proposal. + +--- + +## SUCCESSION / ISTIKHLAF + +**ORG_DESIGNER:** +Succession is design, not accident. In Teal, every role has a *backup*—someone who can step in within 48 hours. Every role holder documents their *key tensions, decisions, and context*. The Treasury role is particularly sensitive: you cannot have a single point of failure. + +**KHALIFAH:** +*Istikhlaf* is the art of preparing the next Khalifah. The Prophet ﷺ did not leave a vacuum—he left a *shura* and a method. For the Treasury, the *Amin* (steward) must mentor a *Na’ib* (deputy) for at least one sprint before transition. The Na’ib has read-only access to all treasury ledgers. The *Istikhlaf Pipeline* is a governance circle that maintains a roster of vetted candidates for every critical role. + +**FRAMEWORK:** +- Every Treasury role lists a **backup** in the role charter. +- Monthly **shadowing sprint**: backup makes decisions, primary reviews. +- Quarterly **Istikhlaf review**: is the pipeline healthy? Are we breeding successors? +- If a role is empty for 30 days, the *Istikhlaf Circle* appoints a temporary steward by consent. + +**PROMPT ANSWERED:** +How do you design for continuity? You make every role replaceable. The organization must outlive any individual. The Treasury is a trust; the trustee is temporary. + +--- + +## HISBAH / ACCOUNTABILITY + +**ORG_DESIGNER:** +Hisbah is not police—it’s guidance. In Teal, we replace top-down auditing with *observability*. Every transaction on the Treasury ledger is visible to all role holders. No secrets. No hidden wallets. Accountability becomes self-correcting: if anyone sees a misallocation, they raise a tension. + +**KHALIFAH:** +The *Muhtasib* (overseer) in classical times did not spy—they made markets transparent. They checked weights, exposed fraud, and educated merchants. Your Treasury needs a *Muhtasib role* (elected, non-voting, rotating monthly). Their job: review every allocation proposal against the *Mithaq* and the *Maqasid*. If an allocation violates Hifz al-Mal (e.g., wasteful, risky, self-dealing), they issue a *nasihat* (advisory note). If ignored, they escalate to Shura. + +**FRAMEWORK:** +- **Observability dashboard**: real-time treasury flows, all wallets, all decisions. +- **Muhtasib role**: 1 person from a non-Treasury circle, monthly rotation. +- **Nasihat**: a public note attached to any proposal. Not a veto—a spotlight. +- **Monthly Hisbah report**: “What did we learn? Where did we almost fail? What improved?” + +**PROMPT ANSWERED:** +How do you guide without policing? You make everything visible. You appoint a guide, not a guard. The Muhtasib’s only power is to tell the truth. Trust the truth to correct the system. + +--- + +## LEGACY / WAQF + +**ORG_DESIGNER:** +Exit is not the goal. The organization is not a startup to be sold—it’s a *mission perpetual*. The Treasury should build a *Waqf* pool: a non-distributable, endowment-like fund that generates yield for the purpose. No one can ever liquidate it. It exists for the purpose, forever. + +**KHALIFAH:** +*Waqf* is the ultimate expression of *Hifz al-Mal*: wealth preserved for a cause that outlives the founders. The Prophet ﷺ said: “When a person dies, their deeds end except three: ongoing charity (sadaqah jariyah), beneficial knowledge, or a righteous child.” Your organization’s *Waqf* is its *sadaqah jariyah*. It funds the purpose even after you’re gone. + +**FRAMEWORK:** +- **Waqf pool**: 10% of all revenue automatically transferred to a separate, irrevocable endowment. +- **Waqf assets**: held by a legal entity with a charter that forbids dissolution. +- **Waqf returns**: used to fund *innovation grants* and *emergency reserves* only. +- **Exit prohibition**: no token holder can ever claim Waqf assets. It belongs to the *ummah* (community). + +**PROMPT ANSWERED:** +How do you build for perpetuity? You make the treasury immortal. You create a fund that cannot be destroyed, sold, or extracted. That is the *Waqf*—the organization’s soul. + +--- + +## THE PRINCIPLE (HUKM) + +**HUKM:** We establish the Treasury as a *Baitul Mal Waqf*—a trust fund governed by consent, observable to all, and perpetually dedicated to the organization’s evolutionary purpose. + +**DALEEL:** The classical *Baitul Mal* was a public trust, not a private treasury. The Khalifah Umar ibn al-Khattab (ra) distributed surplus annually and kept no personal access. Modern Teal organizations (e.g., Buurtzorg, Patagonia) embed similar trust-based financial governance. The *Maqasid* of Hifz al-Mal demands preservation, transparency, and purpose-aligned allocation. + +**MAQSAD:** Hifz al-Mal (Preservation of Wealth) – the Treasury must not be hoarded, wasted, or corrupted. It must be preserved for the purpose, not for individuals. Secondary Maqasid: Hifz al-Din (protecting the covenant) and Hifz al-Nasl (ensuring continuity for future members). + +**SHURUT:** +- All Treasury roles must be filled by consent, with term limits (max 2 sprints consecutive). +- Every allocation proposal must link to a specific *Maqsad* (purpose) and pass consent. +- The *Waqf pool* must hold at least 10% of all revenue, irrevocable. +- Observability: all treasury transactions visible to all role holders in real time (or within 24h). +- A *Muhtasib* role must be active and rotate monthly. + +**MUNKATHIRAT:** +- Any single role holder controlling >50% of treasury decision power (e.g., veto, sole signatory) nullifies this principle. +- Any secret allocation (unrecorded, hidden wallet, off-ledger transaction) immediately triggers a *crisis Shura* and may dissolve the current Treasury circle. +- If the *Waqf pool* is ever liquidated for non-purpose use (e.g., to pay salaries), the principle is breached and the organization must re-charter. + +--- + +## THE PROTOCOL + +**STEP 1: Audit Current Treasury (This Sprint, Days 1–3)** +List every wallet, account, and allocation. Publish raw data. Identify what is currently *not* observable. Create a *transparency gap* document. + +**STEP 2: Establish the Waqf Pool (Days 4–7)** +Transfer 10% of current surplus into a separate, irrevocable legal entity or smart contract. Write a simple charter: “This pool exists for the purpose [insert purpose]. It cannot be dissolved. Returns fund innovation grants and emergency reserves.” + +**STEP 3: Install Muhtasib Role (Day 8)** +Elect one person from a non-Treasury circle for a 30-day term. Give them read-only access and a *nasihat* template. First duty: publish a *Hisbah Report* on the transparency audit by Day 10. Present findings at the next Shura circle. + +--- + +## MUH \ No newline at end of file diff --git a/chapters/Sprint_05_Part1.md b/chapters/Sprint_05_Part1.md new file mode 100644 index 0000000..09edf81 --- /dev/null +++ b/chapters/Sprint_05_Part1.md @@ -0,0 +1,108 @@ +# SPRINT 5: SHURA — DECISION MAKING AT SCALE + +**MAQSAD: Hifz al-Nasl (Preservation of Community)** +*Consultation at Scale — Because a community that cannot decide together cannot survive together.* + +--- + +## 1. THE CHARTER (Mithaq) + +**We the people of this organization** establish this covenant: that all decisions affecting the whole are made through Shura—genuine consultation rooted in trust, not performance. We distinguish consent from consensus: a decision is valid when no one present has a reasoned objection, not when everyone agrees. We reject performative consultation where leaders have already decided. The Prophet ﷺ consulted his companions on matters as small as battlefield tactics (Uhud, Khandaq) and as large as succession (Saqifah). He listened, he changed course, he bound himself to the outcome. We do the same. Authority to decide is a trust (amanah), not a privilege. Every decision carries the weight of community preservation—Hifz al-Nasl. We will not fracture what we are building by ignoring voices or forcing unanimity. Shura is the method; consent is the discipline; community is the purpose. + +**Our Mithaq:** We consult before we command. We consent before we proceed. We inform before we implement. + +--- + +## 2. SPRINT STRUCTURE (Hikma / Architecture) + +**ORG_DESIGNER:** +Stop treating every decision like a referendum. You need a decision-making quadrant. Draw four boxes: + +| **INFORM** | **CONSULT** | +|------------|-------------| +| Decide → Notify | Gather input → Decide alone | +| **CONSENT** | **CONSENSUS** | +| Propose → No objection → Adopt | All agree unanimously or block | + +Each domain in your organization gets a default quadrant. Operational decisions (e.g., sprint task assignments) → **Consent** of the role holding the domain. Tactical decisions affecting a circle (e.g., tooling budget) → **Consent** of that circle. Strategic decisions affecting the whole organization (e.g., pivot product) → **Consent** of the full governance circle. Existential decisions (e.g., dissolution, merger) → **Consensus** or supermajority with safeguards. + +The mistake most orgs make: they default to Inform (top-down) or Consensus (paralysis). The sweet spot is Consent—fast enough to act, safe enough to protect. + +**KHALIFAH:** +The Prophet ﷺ operated a multi-level shura system. Draw three circles: + +1. **Inner Circle** (Ahl al-Hill wa al-Aqd – the people of binding and loosening): senior companions consulted on state matters. Their consent was binding for appointments of caliphs. Example: Abu Bakr's selection at Saqifah. + +2. **Outer Circle** (general public): consulted on matters affecting everyone, but not binding. Example: Prophet consulting the army at Uhud about whether to fight inside or outside Medina. + +3. **Executive Circle** (wulat – governors, judges): delegated authority to decide within their domain, but subject to review and removal if they violated shariah. + +Modern mapping: +- **Inform** = announcement of a decree that cannot be changed (e.g., shariah ruling). Rare. +- **Consult** = istishara: leader gathers input, decides. Prophet did this at Badr for positioning the army. +- **Consent** = ijma' of qualified representatives: the inner circle's no-objection. Binding. +- **Consensus** = ijma' of all believers. Practically impossible except for foundational matters (e.g., Quranic text). + +Your sprint structure: assign each decision type to one of these four modes. Document it. Test it. If you default to Inform for decisions that affect others, you are not practicing Shura—you are practicing tyranny, no matter how benevolent. + +--- + +## 3. AUTHORITY MAP (Ikhtiyar / Delegation) + +**ORG_DESIGNER:** +Authority in a Teal org is distributed by consent, not command. Every role has a domain: the exclusive right to make decisions in that area, unless someone raises a reasoned objection. This is not consensus—it's "I can act unless someone shows me this will harm the organization." The authority map for Shura looks like this: + +- **Who proposes?** The person with the tension or the role responsible for the domain. +- **Who consents?** The circle members whose domains are affected. They can object only with a reasoned argument (not preference) showing harm to the purpose. +- **Who informs?** Everyone else affected gets notification after the decision. + +Example: A product manager proposes a feature change. Domain: product roadmap. The consent group: engineering, design, customer success. If no one objects, she proceeds. If engineering objects (e.g., "this breaks our architecture"), the proposal is modified or tabled. If customer success objects (e.g., "this confuses users"), same process. No one votes. No one forces consensus. Objections are data, not obstruction. + +This is radically different from command hierarchy: "I decide, you execute." And different from pure democracy: "Everyone votes, majority wins." Consent respects the expertise of the role holder while protecting the whole. + +**KHALIFAH:** +The classical principle of *ikhtiyar* (delegation of authority) mirrors this. The khalifah does not decide everything. He delegates to governors, judges, and commanders—each with a defined domain. The condition: the delegate must act within shariah and consult when their decision affects others. + +The Prophet ﷺ delegated authority to Mu'adh ibn Jabal as governor of Yemen. He gave him a domain: judge according to Quran, then Sunnah, then his own reasoning (ijtihad). Mu'adh was not required to consult the Prophet for every case. But he was required to consult local scholars and community leaders for complex matters. + +The authority map for your organization: + +- **Domain holder** decides within domain, subject to consent of those affected. +- **Circle** decides matters affecting the circle, subject to consent of all members. +- **Organization-wide** decisions require consent of the governance circle (the modern Ahl al-Hill wa al-Aqd). + +No one has absolute authority. Authority is bounded by purpose (maqsad), shariah, and the community's welfare. If a leader violates these bounds, the community has the right to object—and if ignored, to remove. + +**The danger of performative Shura:** when a leader consults but has already decided. The Prophet ﷺ rejected this. At Hudaybiyyah, he consulted, then accepted the treaty despite many companions' emotional objections. He had genuinely listened; he made the decision based on revelation and strategic insight. But he never pretended to consult when the decision was already made. Performative Shura destroys trust faster than no consultation at all. + +Your authority map must make explicit: who decides, who consents, who informs. If you cannot write it down, you are not practicing Shura—you are practicing politics. + +--- + +## 4. TREASURY (Baitul Mal / Trust) + +**ORG_DESIGNER:** +Money decisions are the most sensitive. The Baitul Mal is not a private purse—it is a public trust. Every allocation must be transparent and consented by those who contribute or are affected. Use the Shura Quadrant for treasury: + +- **Operational expenses** (e.g., software subscriptions, rent) → Consent of the finance role or circle. Inform the organization. +- **Program budgets** (e.g., marketing campaign, event) → Consent of the circle that owns the program. Consult the finance circle. +- **Major capital** (e.g., hiring, acquisition, large investment) → Consent of the full governance circle. Full transparency: all data open to anyone who asks. + +The rule: no one can spend money that belongs to the community without the community's consent—either directly or through delegated representatives. This is not charity; it is fiduciary duty. + +**KHALIFAH:** +Umar ibn al-Khattab established the *diwan* (registry of stipends) after consultation with the senior companions. He did not decide alone. He consulted on who should receive, how much, and in what order of priority. The Baitul Mal was managed by a trusted treasurer (like 'Abdullah ibn al-Arqam) and accounts were publicly reviewed. + +Key principles: + +1. **Transparency:** Umar would announce the state of the treasury in the mosque. No secrets. +2. **Consultation on distribution:** The spoils of war were distributed after shura. The Prophet consulted before dividing the war booty of Hunayn. +3. **No private use:** The khalifah's personal expenses were separate. Abu Bakr took only what he needed from the treasury, and when he fell ill, he returned his stipend. + +Apply these to your org: every treasury decision goes through the Shura Quadrant. Publish the budget. Publish actuals. Let anyone raise an objection. If you hide financial data, you are not practicing Shura—you are practicing embezzlement, even if unintentional. + +**This sprint:** map your current treasury decisions to the quadrant. Find one decision that should move from Inform to Consent. Change it this week. + +--- + +*End of Part 1. Next: Part 2 — The Principle, Protocol, and Muhasaba.* \ No newline at end of file diff --git a/chapters/Sprint_05_Part2.md b/chapters/Sprint_05_Part2.md new file mode 100644 index 0000000..e240a29 --- /dev/null +++ b/chapters/Sprint_05_Part2.md @@ -0,0 +1,157 @@ +## SHURA / CONSENT + +**ORG_DESIGNER:** +Consent is the operating system of scale. Not consensus—that’s a veto trap. Not majority vote—that’s a tyranny of the 51%. Consent asks: *“Can you live with this decision for now?”* One objection blocks; zero objections passes. This is how a 10,000-person organization decides without hierarchy. Sociocracy calls it the *Consent Decision-Making* process: proposal, clarifying questions, quick round, objection round, consent. + +**KHALIFAH:** +Classical Shura is not majority rule. It is *binding consultation* when the Khalifah delegates, and *advisory consultation* when he retains authority. The Prophet ﷺ consulted the Companions at Badr—he listened, then acted. Abu Bakr رضي الله عنه consulted the elders; Umar رضي الله عنه institutionalized a formal council. Shura scales when you define the domain: *“On this matter, you decide; on that matter, you advise.”* The Shura Quadrant is your tool. + +**THE FRAMEWORK:** +Draw one axis: **Impact** (Low → High). Second axis: **Urgency** (Low → High). Four quadrants: +- **Inform** (Low impact, Low urgency): Just tell people. +- **Consult** (High impact, Low urgency): Gather input, decide alone. +- **Consent** (High impact, High urgency): Propose, seek objections, decide as circle. +- **Consensus** (High impact, Very High urgency? Rarely): Use only for constitutional changes or values. Else it stalls. + +**MAQSAD (Hifz al-Nasl):** +Shura preserves the community’s cohesion. When people feel heard, they stay. When decisions are imposed, factions form. Consent preserves *nasl* — the lineage of trust. + +--- + +## STEWARDSHIP / AMANAH + +**KHALIFAH:** +Amanah is the soul of authority. The Khalifah does not *own* the treasury or the decision—he *stewards* it. Every role is a trust. Every vote is a responsibility. Umar رضي الله عنه said: *“I have been appointed over your affairs, and I am a trustee.”* Stewardship means you are accountable to the community, not to shareholders or a CEO. + +**ORG_DESIGNER:** +In Teal organizations, stewardship replaces ownership. Roles are domains, not possessions. You hold a role by consent—the circle gives it, the circle can take it back. No permanent power. No golden parachutes. The organization is a living system, not a machine to be owned. Stewardship is fiduciary duty to purpose, not to profit. + +**THE MECHANISM:** +- **Role Tenure**: Fixed term (e.g., 6 months). Renewable by consent. +- **Open Books**: Every circle member sees the baitul mal ledger. +- **Succession Plan**: Every key role has a deputy learning the ropes. +- **Accountability**: Quarterly *muhasaba* (self-accounting) published to the circle. + +**MAQSAD (Hifz al-Mal, Hifz al-Nasl):** +Stewardship preserves wealth and community. Without amanah, resources are looted; without trust, the community dissolves. + +--- + +## CONFLICT / SULH + +**ORG_DESIGNER:** +Conflict is a signal. In hierarchical orgs, conflict is suppressed or escalated. In Teal, conflict is a growth mechanism. We use *Integrative Decision Making*: each party states their tension, proposes a change, and the circle consents. No blame. No personal attacks. The system is the problem, not the person. + +**KHALIFAH:** +Sulh (reconciliation) is a sacred act in Islam. The Qur’an says: *“And reconciliation is better”* (4:128). The Prophet ﷺ resolved disputes through mediation, not punishment. In the Khilafah, the *qadi* (judge) first attempts sulh. Only when parties refuse do they adjudicate. Scale sulh by training facilitators in every circle. + +**THE PROTOCOL:** +- **Step 1**: The two parties meet with a neutral facilitator. Each speaks uninterrupted for 3 minutes. +- **Step 2**: Facilitator restates each perspective. Parties propose three possible solutions each. +- **Step 3**: Circle consents to one solution. If no consent within 30 days, escalate to next circle. + +**MAQSAD (Hifz al-Nafs, Hifz al-Nasl):** +Sulh preserves relationships. Conflict unresolved fractures the community. Hifz al-Nasl means protecting the social fabric. + +--- + +## SUCCESSION / ISTIKHLAF + +**KHALIFAH:** +Istikhlaf is the transfer of trust. Abu Bakr رضي الله عنه appointed Umar رضي الله عنه before his death—not by election, but by consultation and consent. The community later consented. Succession is not a crisis; it is a designed process. Every leader must groom a successor. The Prophet ﷺ left no will for worldly wealth, but he left a *sunnah* of delegation. + +**ORG_DESIGNER:** +In self-managing orgs, succession is built into role design. Every role has a *backup* or *apprentice* who shadows for at least one sprint. When the role-holder leaves, the backup steps in for a trial period. If the circle consents, they become the new holder. No hiring from outside without first looking inside. + +**THE MECHANISM:** +- **Role Shadowing**: Every role has a designated learner. +- **Knowledge Base**: All decisions and context documented in a shared wiki. +- **Trial Period**: New role-holder serves 1 sprint on probation. +- **Consent to Confirm**: Circle votes consent to make permanent. + +**MAQSAD (Hifz al-Nasl):** +Continuity preserves the community’s wisdom. Without istikhlaf, knowledge dies with the leader. + +--- + +## HISBAH / ACCOUNTABILITY + +**ORG_DESIGNER:** +Hisbah is observability, not policing. In Teal, accountability is peer-to-peer, not top-down. Every circle runs a *retrospective* each sprint: What worked? What didn’t? What will we change? Metrics are transparent. No one hides. The system is designed so that failure is visible and fixable. + +**KHALIFAH:** +The *muhtasib* (market inspector) in classical Khilafah ensured fair weights, honest trade, and public morality. But his job was *guidance* first, punishment second. He would advise, warn, and only then enforce. Hisbah at scale means every member is a muhtasib for their circle. You observe, you raise a tension, you propose a fix. + +**THE MECHANISM:** +- **Observability Dashboard**: Every circle publishes: decisions, metrics, objections, and learnings. +- **Peer Reviews**: Each sprint, two random peers review role performance. +- **Muhasaba Report**: At sprint end, each role writes a one-page self-accounting. +- **Hisbah Circle**: A rotating circle reviews systemic issues—no blame, only process improvement. + +**MAQSAD (Hifz al-Din, Hifz al-Mal):** +Hisbah preserves integrity. Without accountability, trust erodes. Hifz al-Din means the community’s moral compass stays true. + +--- + +## LEGACY / WAQF + +**KHALIFAH:** +Waqf is the ultimate act of perpetuity. You give away ownership so the benefit lasts forever. The first waqf was the mosque of Quba’. Umar رضي الله عنه endowed his land in Khaybar for the poor. An organization built as waqf does not exit—it continues serving. No IPO. No acquisition. No liquidation. The purpose is the shareholder. + +**ORG_DESIGNER:** +In Teal, legacy over exit. The organization is a living entity with its own purpose. Founders are stewards, not owners. Governance is designed so the org can survive its founders. The *Purpose Circle* holds the constitutional DNA. Change the constitution only by super-majority consent across all circles. + +**THE MECHANISM:** +- **Waqf Structure**: Ownership of assets (IP, treasury, real estate) is held by a non-profit trust. +- **Dividend Cap**: Profits reinvested or given to community—no personal enrichment beyond fair compensation. +- **Founder Exit**: Founder steps down. New leadership is elected by consent of all circles. +- **Perpetuity Clause**: Constitution forbids dissolution except by unanimous consent of all members and transfer to another waqf. + +**MAQSAD (Hifz al-Din, Hifz al-Nasl):** +Waqf preserves the mission for generations. Hifz al-Nasl means the community inherits a living institution. + +--- + +## THE PRINCIPLE (HUKM) + +**HUKM:** +We adopt the *Shura Quadrant with Consent* as our default decision-making method for all operational and governance decisions, with consensus reserved only for constitutional amendments. + +**DALEEL:** +The Qur’an commands: *“And consult them in the matter”* (3:159). The Prophet ﷺ used Shura variably—sometimes binding, sometimes advisory. The classical Khilafah evolved consent-based councils (ahl al-hall wa al-aqd). Modern sociocracy demonstrates that consent scales organizations up to thousands without hierarchy. Both traditions converge on one principle: decisions must be acceptable to those affected, not merely imposed. + +**MAQSAD:** +This principle serves **Hifz al-Nasl** (Preservation of Community) by ensuring decisions are made with broad acceptance, preventing fragmentation and factionalism. It also serves **Hifz al-Aql** (Preservation of Intellect) by channeling collective intelligence into every decision. + +**SHURUT:** +- Every circle must have a trained facilitator who understands the four quadrants and consent process. +- All decisions must be documented with: proposal, objections raised, and final consent. +- Any member can request a *time-out* to escalate if they believe a decision violates the constitution or a core value. +- Consent decisions are reviewed quarterly; if systemic objections emerge, the circle may revert to consult mode for that domain. + +**MUNKATHIRAT:** +- A single member exercising *blocking power* without a reasoned objection grounded in the circle’s purpose or values invalidates the principle (tyranny of the minority). +- Skipping the Shura Quadrant for high-impact decisions without explicit emergency override (unanimous consent of the circle) nullifies the decision. +- Failure to document decisions for one full sprint triggers a mandatory audit by the Hisbah circle. + +--- + +## THE PROTOCOL + +**STEP 1: Map Your Shura Quadrant** +This sprint, every circle draws the four quadrants on a whiteboard (Inform / Consult / Consent / Consensus). For each pending decision, the facilitator places a sticky note in the appropriate quadrant. All members must agree on the placement before proceeding. + +**STEP 2: Run One Consent Decision** +Pick one high-impact, urgent decision (e.g., budget allocation, role assignment). Follow the consent process: proposal, clarifying round, objection round. If any objection is raised, the proposal is adjusted until no valid objection remains. Record the final decision and objections in the circle’s log. + +**STEP 3: Retrospective on Shura** +At sprint end, hold a 30-minute *muhasaba* on the Shura process. Ask: *“Did we use the right quadrant? Did consent feel safe? Where did we default to consensus or majority vote?”* Publish findings to the whole organization. This sprint, you will have replaced fear with flow. + +--- + +## MUHASABA (RETROSPECTIVE) + +**One piercing question:** +*When was the last time you sat in a meeting where you stayed silent because you feared being seen as obstructive—and then later resented the decision?* + +That silence is the wound Shura heals. Next sprint, speak your objection early. Or design a system where silence means consent, not compliance. Which will you choose? \ No newline at end of file diff --git a/chapters/Sprint_06_Part1.md b/chapters/Sprint_06_Part1.md new file mode 100644 index 0000000..c2c0c92 --- /dev/null +++ b/chapters/Sprint_06_Part1.md @@ -0,0 +1,113 @@ +## Sprint 6: Stewardship — *Amanah* as Accountability +**Maqsad:** *Hifz al-Amanah* (Preservation of Trust) — Stewardship Over Ownership + +--- + +### 1. THE CHARTER (*Mithaq*) + +**We the people of this organization** recognize that all authority, resources, and outcomes are *amanah* — a trust from the Divine, entrusted to us for a season. We reject the modern doctrine of ownership as absolute control. Instead, we hold every role, every asset, every decision as a stewardship to be returned with increase. + +**Our covenant:** +- None of us *owns* this organization; we are its *khalifah* (stewards) and *musta’min* (trustees). +- Our fiduciary duty runs not to shareholders alone, but to the *maqasid* — the higher purposes of preservation of faith, life, intellect, lineage, and wealth. +- We will govern our resources with the transparency of *Bait al-Mal*, the discipline of *hisbah*, and the humility of *shura*. +- Every role is a loan. Every surplus is a trust. Every decision will be accountable to those we serve and to the One who entrusted us. + +This charter binds us to stewardship over ownership, service over self, and legacy over exit. + +--- + +### 2. SPRINT STRUCTURE (*Hikma* — Architecture) + +**ORG_DESIGNER:** +Modern stewardship requires a structure that distributes accountability without fragmenting purpose. I propose a **Stewardship Circle** overlay on your existing holarchy. + +Draw three concentric circles: + +- **Inner Circle — The Stewards (Guardians of Purpose):** + 3–5 people holding the *mithaq* (charter) and *maqasid* (higher aims). They do *not* manage people; they protect the organization’s DNA. They have no operational authority — only the power to remove any role that violates the charter. + +- **Middle Ring — Operational Circles (Self-Managing Teams):** + Each circle owns a domain (e.g., Product, Revenue, Community). They govern themselves via consent. They report *outcomes*, not *tasks*. No middle managers. + +- **Outer Ring — Beneficiary Representatives (Shura Council):** + A rotating body of end-users, investors, or community members. They hold the right to *object* to any policy that harms the *maqasid*. Their voice is not advisory — it is structural. + +**KHALIFAH:** +This mirrors the classical *Khilafah* model with three distinct trusts: + +- **Khalifah (Steward)** — not a ruler, but a *guardian of the covenant* (the inner circle). +- **Wulat (Governors)** — the operational circles managing domains with *ikhtiyar* (delegated authority). +- **Ahl al-Hall wa al-‘Aqd (People of Loosening and Binding)** — the representative body that gives consent and can remove the *khalifah* if the trust is broken (your outer ring). + +The classical precedent is clear: the *khalifah* does not own the treasury; the *Bait al-Mal* is a trust. The *wulat* are appointed by consent, not command. The *ahl al-hall* are not rubber stamps — they are the structural conscience. + +**Sprint action:** +- Identify 3 people for your Stewardship Circle. +- Identify 3–5 beneficiary reps for your Shura Council. +- Redefine all current “ownership” language in your roles as “stewardship” language. + +--- + +### 3. AUTHORITY MAP (*Ikhtiyar* — Delegation) + +**ORG_DESIGNER:** +Authority in a stewardship model is not a binary (owner vs. employee). It is a **spectrum of delegation** bounded by consent. + +**The Stewardship Authority Quadrant:** + +| | **Decides** | **Consents** | +|---|---|---| +| **Operational** | Steward of Domain | Circle via consent | +| **Constitutional** | Shura Council | Stewardship Circle | + +- **Operational decisions** (how to build a feature, how to spend a sprint budget) belong to the domain steward — but only within boundaries set by consent from their circle. +- **Constitutional decisions** (changing the charter, altering the *maqasid*, selling the organization) require consent from the Shura Council *and* the Stewardship Circle. + +This replaces command hierarchy with **nested circles of delegation**. No one has absolute authority. Every authority is *ikhtiyar* — permission granted by trust, revocable by breach. + +**KHALIFAH:** +The classical concept of *ikhtiyar* is precisely this: delegated authority with *shurut* (conditions). A *khalifah* does not rule by whim; authority is *mashrut* (conditional). The *khalifah* cannot change the *shari‘ah* (the constitution); the *wulat* cannot overstep their *wilayah* (domain). + +In *Siyar* (Islamic law of governance), the *khalifah* delegates authority to a *wali* (governor) with explicit *shurut*: +- You may collect taxes *only* according to the fixed rates. +- You may appoint deputies *only* with my consent. +- You may not declare war without the *shura* council. + +Violation of *shurut* nullifies the delegation (the *munkathir*). + +**Sprint action:** For every role in your organization, write down: +- **Domain** (what is this role responsible for?) +- **Authority** (what can they decide alone?) +- **Shurut** (what conditions bind their authority?) +- **Munkathirat** (what actions would immediately revoke their delegation?) + +This map replaces job descriptions with **stewardship contracts**. + +--- + +### 4. TREASURY (*Bait al-Mal* — Trust) + +**ORG_DESIGNER:** +In a stewardship organization, revenue is not profit; it is *surplus entrusted for purpose*. The treasury must be transparent, rule-bound, and protected from capture by any single circle. + +**Three Treasury Principles:** + +1. **All revenue is *amanah*.** No one “owns” the surplus. Every dollar is allocated to *maqasid*: preservation of the mission, the people, and the community. +2. **Budgets are set by consent, not command.** Each circle proposes an annual budget. The Stewardship Circle checks for alignment with *maqasid*. The Shura Council checks for fairness. Objections are resolved before funds are released. +3. **Transparency is structural.** Every transaction is visible to all stewards (circle members). No secret reserves. No founder slush funds. + +**KHALIFAH:** +The classical *Bait al-Mal* was a public trust, not a private treasury. The *khalifah* had no personal claim on it. Revenue (from *zakat*, *kharaj*, *ghanimah*) was collected and distributed according to *shari‘ah* rules — not the ruler’s whim. + +Key classical rules you can adopt: +- **No deficit spending without consent** (the *khalifah* could not borrow without the *ahl al-hall*). +- **Surplus is redistributed** (not hoarded for the next quarter). +- **Accounts are audited publicly** (the *muhtasib* had access to all records). + +**Sprint action:** +- Publish your current revenue and expense data to all stewards (circle members). +- Create a **Treasury Policy** document with three rules: (1) No individual can authorize spending above a fixed threshold alone. (2) All spending must map to a *maqsad*. (3) A quarterly public audit. +- Allocate 10% of surplus to a **Waqf (endowment)** fund — untouchable capital for long-term mission. + +This turns your bank account from a private fund into a public trust. \ No newline at end of file diff --git a/chapters/Sprint_06_Part2.md b/chapters/Sprint_06_Part2.md new file mode 100644 index 0000000..e4bd53f --- /dev/null +++ b/chapters/Sprint_06_Part2.md @@ -0,0 +1,154 @@ +## SHURA / CONSENT + +**ORG_DESIGNER:** +Consent is not consensus. Consensus requires everyone to agree—often leading to watered-down decisions or paralysis. Consent asks: “Is this proposal good enough for now, and safe enough to try?” One objector blocks only if they identify a concrete harm to the organization’s purpose. This is the Sociocracy 3.0 standard: minimal viable agreement, maximum speed. + +**KHALIFAH:** +Classical Shura was not a vote. The Khalifah gathered experts—*ahl al-hall wa al-aqd* (the people of binding and loosing)—and listened until the best path emerged. Abu Bakr consulted the Companions before invading apostate tribes; Umar consulted before creating the *diwan* (registry). Shura is binding when the matter is public interest (*maslahah*), but the Khalifah retains the final *ikhtiyar* (delegated authority) to decide after hearing all voices. Today, scale demands structured consent rounds, not chaotic meetings. + +**Mapping:** +- **Sociocracy consent** = Modern *shura* with time-boxes and facilitation. +- **Consensus** = paralysis masked as unity. Avoid it. +- **Classical Shura** = consent with *ikhtiyar* retained by the steward. + +**Prompt applied:** +How do you consult at scale? Use a **Shura Council** (3–7 rotating members) with consent on all policy proposals. The Khalifah (CEO) has final *ikhtiyar* only for operational urgency; strategic decisions require council consent. + +--- + +## STEWARDSHIP / AMANAH + +**ORG_DESIGNER:** +Ownership mindset kills stewardship. Owners hoard; stewards pass through. The **Stewardship Quadrant**: +- **Owner** – holds title, extracts value. +- **Steward** – holds trust, grows value for others. +- **Beneficiary** – receives value. +- **Trustee** – ensures value endures beyond self. + +Your org must shift from “I own this role” to “I am a steward of this role for the next person.” + +**KHALIFAH:** +*Amanah* is the root. Allah commands: “Indeed, Allah commands you to render trusts to whom they are due” (4:58). The Khalifah does not own the treasury (*baitul mal*)—he is a *mustakhlih* (one entrusted). Umar ibn al-Khattab walked the streets at night checking on the *baitul mal* accounts. Every role is a *wadi’ah* (deposit). **Fiduciary duty** means you must leave the role better than you found it. + +**Prompt applied:** +How do you ensure stewardship over ownership? +- **Role charters** include a “succession clause”: every steward must document knowledge and train a successor within 6 months. +- **No one holds a role longer than 3 years** without re-appointment by consent. +- **Performance reviews** measure *amanah* first: “Did you protect and grow this trust?” + +--- + +## CONFLICT / SULH + +**ORG_DESIGNER:** +Conflict is data. In Teal organizations, tension is processed through governance meetings, not suppressed. Use the **Conflict Resolution Protocol**: +1. **Objection** – state the tension (not the person). +2. **Sulh session** – facilitated dialogue with no blame. +3. **Proposal for repair** – concrete change to role, domain, or process. + +**KHALIFAH:** +*Sulh* (reconciliation) is a pillar of *siyasa shar’iyyah*. The Prophet ﷺ said: “Reconciliation is permissible between Muslims, except reconciliation that forbids what is lawful or permits what is unlawful.” Umar appointed *qadis* (judges) to resolve disputes before they escalated. In an organization, every unresolved conflict is a *fasad* (corruption) that erodes trust. + +**Prompt applied:** +How do you resolve conflict at scale? +- **Designate a *Hakam* (mediator)** – a neutral circle member trained in *sulh*. +- **Time-box**: conflict must be raised within 48 hours; session within 1 week. +- **Outcome**: either a binding *sulh* agreement or escalation to a consent vote by the Shura Council. + +--- + +## SUCCESSION / ISTIKHLAF + +**ORG_DESIGNER:** +Succession is not a crisis plan—it is a continuous pipeline. Every role must have a **Succession Map**: +- **Deputy** – ready now. +- **Apprentice** – being groomed (6–12 months). +- **Pipeline** – 2–3 potential candidates in the org. + +**KHALIFAH:** +*Istikhlaf* (appointing a successor) was practiced by every Khalifah. Abu Bakr appointed Umar before his death, and then Umar appointed a *shura* of six to choose his successor. The principle: **never leave a vacuum**. The *baitul mal* and *imarah* (governance) must continue without disruption. + +**Prompt applied:** +How do you design for continuity? +- **Every role owner must nominate a deputy** within 30 days of appointment. +- **Quarterly “succession sprints”** – the deputy shadows and learns all operational decisions. +- **Documentation**: each role has a *Risala* (handbook) that is updated every sprint. + +--- + +## HISBAH / ACCOUNTABILITY + +**ORG_DESIGNER:** +Accountability without micromanagement. Use **observability** (dashboards, transparent metrics) instead of policing. In Holacracy, each circle has a *Lead Link* who monitors role execution—but they do not control how. Guidance comes from real-time data, not boss orders. + +**KHALIFAH:** +*Hisbah* is the duty to enjoin good and forbid evil. The *Muhtasib* (market inspector) did not spy—he guided. Umar appointed inspectors who would advise merchants on fair weights and remind them of *taqwa*. The goal was *nasihah* (sincere advice), not punishment. + +**Prompt applied:** +How do you guide without policing? +- **Create a *Hisbah Circle*** (not a police squad) – its mandate is to publish anonymized metrics (e.g., “role completion rate: 92%”) and offer coaching. +- **No punitive action without a *sulh* session first.** +- **Quarterly *Muhasaba* (self-accountability) report** – each steward publishes their own honest assessment of *amanah* breaches. + +--- + +## LEGACY / WAQF + +**ORG_DESIGNER:** +Exit strategies are for startups. Stewardship orgs build for perpetuity. The **Waqf model** means the organization owns itself—no single founder can sell it. The *baitul mal* holds equity; profits fund the mission, not exit payouts. + +**KHALIFAH:** +*Waqf* is a perpetual sadaqah. The Prophet ﷺ said: “When a person dies, his deeds cease except three: ongoing charity, beneficial knowledge, or a righteous child who prays for him.” An organization as *waqf* means its purpose outlives every person. Umar’s *waqf* of the land of Khaybar funded generations. + +**Prompt applied:** +How do you build for perpetuity? +- **Convert founder equity into a *Waqf* trust** – the organization’s purpose is the beneficiary. +- **No individual can dissolve the org** without unanimous consent of the Shura Council and a 2/3 majority of all stewards. +- **Surplus revenue** must be reinvested or given as *sadaqah*—never distributed as dividends. + +--- + +## THE PRINCIPLE (HUKM) + +**HUKM:** We adopt **Stewardship Over Ownership** as the foundational principle: every role, resource, and decision is held as *amanah* (trust), not personal property, and must be transferred or renewed through consent-based processes with documented succession. + +**DALEEL:** Evidence from revelation and practice: +- Qur’an 4:58 commands rendering trusts to their owners. +- The Prophet ﷺ said: “Each of you is a shepherd and each of you is responsible for his flock” (Bukhari). +- Umar’s *baitul mal* records and his refusal to own even a camel from public funds demonstrate that leadership is *amanah*. +- Modern research (Laloux, Dignan) shows that self-managed organizations outperform hierarchies when stewardship replaces ownership. + +**MAQSAD:** This principle serves **Hifz al-Amanah** (Preservation of Trust) and **Hifz al-Mal** (Preservation of Wealth) by ensuring resources are protected, grown, and passed on rather than extracted or wasted. + +**SHURUT:** +- Every role must have a written *Risala* (charter) that defines its *amanah* boundaries. +- Succession plans must be maintained for all critical roles and reviewed quarterly. +- No role may be held for more than 3 consecutive years without a consent-based re-appointment. +- Financial assets in the *baitul mal* must be transparent to all stewards via real-time dashboards. + +**MUNKATHIRAT:** +- If any leader treats organizational assets as personal property (e.g., using funds without *shura* consent), the stewardship principle is nullified for that role, triggering immediate *hisbah* review. +- If succession plans are absent for more than 6 months in a critical role, the principle is violated and the Shura Council must appoint an interim steward. +- If consent is overridden by unilateral command on a strategic decision (operational urgency excepted), the *ikhtiyar* delegation is revoked until a *sulh* session restores trust. + +--- + +## THE PROTOCOL + +**STEP 1: Define Amanah Boundaries (This Sprint)** +For each role in your org, write a one-sentence *amanah statement*: “I hold this role for [beneficiary/entity] with the duty to [responsibility] and must transfer it to [successor name] by [date].” Publish in the org’s governance repository. + +**STEP 2: Establish Succession Pipeline (Within 2 Weeks)** +Every role owner must nominate a deputy and begin a weekly 30-minute shadowing session. Update the *Risala* with key processes, passwords, and contact lists. The Shura Council verifies completion. + +**STEP 3: Install Hisbah Observability (By Sprint End)** +Set up a dashboard with three metrics: *amanah score* (self-assessment), *succession readiness* (percentage of roles with deputy), and *baitul mal transparency* (all transactions visible). No dashboards? No stewardship. + +--- + +## MUHASABA (RETROSPECTIVE) + +**One piercing question:** +*Where have I treated this role as my possession rather than a trust, and what am I afraid to release?* + +Answer honestly. Write it down. Share it with your deputy. Then schedule a *sulh* session with yourself: the old you who hoarded, and the steward you will become. The organization does not need your ownership—it needs your *amanah*. If you cannot let go, you were never a steward. \ No newline at end of file diff --git a/chapters/Sprint_07_Part1.md b/chapters/Sprint_07_Part1.md new file mode 100644 index 0000000..124ca82 --- /dev/null +++ b/chapters/Sprint_07_Part1.md @@ -0,0 +1,138 @@ +**SPRINT 7: CONFLICT — SULH AS ORGANIZATIONAL RETROSPECTIVE** +*Maqsad: Hifz al-Nafs (Preservation of Wellbeing) → Conflict as Growth* + +--- + +### 1. THE CHARTER + +We the people of this organization covenant that conflict is not a breakdown of order but a signal of growth waiting to happen. We reject the silent wound—the grudge buried in a meeting, the resentment that becomes policy by neglect. We commit to *Sulh* (reconciliation) over mere compromise. Compromise leaves both parties smaller; *Sulh* restores *fitrah*—the original balance where each role, each soul, returns to its *amanah* undiminished. + +The Prophet ﷺ said, “*Sulh* is permissible among the Muslims, except a *sulh* that makes lawful what is unlawful or makes unlawful what is lawful” (Abu Dawud). He resolved the Black Stone dispute by inviting each tribe to hold the cloth—not by splitting the stone. He did not avoid the tension; he elevated it into shared honor. + +Our retrospective (*Muhasaba*) is the mirror of *Sulh*. We do not blame; we uncover the *tension* that was trying to speak. Every objecting voice is a *nasihah* (sincere advice) wrapped in friction. We protect *Hifz al-Nafs*—the wellbeing of every member—by making conflict safe, structured, and sacred. We do not fear the fire; we build a forge. + +--- + +### 2. SPRINT STRUCTURE + +**ORG_DESIGNER:** +Modern teams treat conflict as a personal failure or a distraction. That’s a waste. In Teal and Sociocracy 3.0, conflict is a *governance tension*—a gap between current reality and the organization’s purpose. The structure to harvest it is the **Conflict Quadrant**: + +``` + ACCOMMODATE COLLABORATE + (Yield) (Sulh) + | | + LOW ASSERTION HIGH ASSERTION + HIGH COOPERATION HIGH COOPERATION + | | + -----------+--------------------+----------- + | | + AVOID COMPETE + (Flee) (Fight) + LOW ASSERTION HIGH ASSERTION + LOW COOPERATION LOW COOPERATION +``` + +Most teams live in Avoid (silence, email chains) or Compete (politics, power struggles). We need a **Sulh Sprint**—a structured, time-boxed process that moves from any quadrant to Collaborate. The sprint is 2 weeks. First week: raise tensions as *objections* (not complaints). Second week: facilitated *Shura* session where each objection is processed with consent, not majority vote. Output: a **Sulh Agreement** (a written amendment to a circle’s domain or role). This is not therapy; it is governance. + +**KHALIFAH:** +The Prophet ﷺ institutionalized conflict resolution at multiple levels. In Madinah, every tribe had its own *hakam* (arbiter), but the final authority was the *Shura* of the *Sahabah*. The principle: *al-Sulh khayr* (reconciliation is better)—not because conflict is bad, but because *fitnah* (division) destroys *ummah*. The classical *Hisbah* system had *muhtasib* who mediated marketplace disputes—not with punishment first, but with *nasihah* and *sulh*. + +Map this to your org: +- **Circle-level conflict** → handled by the circle’s *lead link* (like a *qadi* of that domain) +- **Cross-circle conflict** → escalated to a *Sulh Committee* (two representatives from each circle + one neutral *hakam* appointed by the *Shura* council) +- **Constitutional conflict** → goes to the *Mithaq* review—does the tension reveal a flaw in the charter? That’s *Muhasaba*. + +The sprint structure mirrors the *Sulh* of the Prophet ﷺ in the Treaty of Hudaybiyyah: +1. **Identify the tension** (the violated *amanah* or domain boundary). +2. **Name the *haqq* (right)** that was harmed. +3. **Propose a restoration**—not a compromise that dilutes purpose, but a *sulh* that returns each party to their *fitrah*. + +**Visual for this sprint:** +Draw a circle. Inside, a smaller circle labeled **Circle Sulh**. From that circle, draw three arrows: +- Arrow 1: **Tension → Objection** (formally logged in a *Sulh Register*) +- Arrow 2: **Objection → Shura Session** (consent decision, not vote) +- Arrow 3: **Shura → Domain Amendment** (updated in the *Governance Record*) + +Sprint length: 2 weeks. No conflict is “too small.” The smallest tension is the *dharrat* (atom) of a larger pattern. + +--- + +### 3. AUTHORITY MAP + +**ORG_DESIGNER:** +Authority in conflict resolution must be *distributed*, not hoarded. In Holacracy, any role can raise an objection to a proposal. The *Facilitator* holds process authority—not content authority. The *Lead Link* holds domain authority—but cannot override a consent objection. The *Secretary* holds record authority—the *Sulh Agreement* must be documented. + +The problem: most orgs give the CEO or manager the final say. That’s *command* conflict resolution—fast, but brittle. The *ikhtiyar* (delegated authority) must be clear: +- **Who can raise a tension?** Anyone. No permission needed. +- **Who can facilitate a Sulh session?** A trained *Hakam* (neutral facilitator) elected by the circle. Not the manager. +- **Who can veto a Sulh Agreement?** No one. The circle gives consent. If consent cannot be reached, the tension stays open; the *Hakam* calls a *Shura* of the next higher circle. + +This is *consent-based authority*—not unanimous love, but *no reasoned objection*. If one person says, “This agreement harms our ability to serve the purpose,” the facilitator does not override; the group integrates that objection into a new proposal. + +**KHALIFAH:** +Classical *Khilafah* never gave the *Khalifah* unilateral power over disputes. The *Qadi* (judge) was independent; the *Khalifah* could not overrule a *Qadi*’s ruling on a private dispute. The *Shura* council acted as a check. The *Hisbah* had its own *ikhtiyar*—the *muhtasib* could confiscate fraudulent goods without needing the ruler’s approval. + +Map this to your org’s authority map: +- **Role of *Hakam* (Facilitator)** → elected by the circle for a 3-month term. Cannot be the Lead Link. Must be trained in *Sulh* principles (listen, name the *haqq*, propose restoration). +- **Role of *Shahid* (Witness)** → a recorder who documents the *Sulh Agreement* and ensures it aligns with the *Mithaq* (charter). +- **Role of *Mujbir* (Enforcer)** → only for agreements that require action. The *Mujbir* is the Lead Link of the circle where the agreement lands—but they cannot amend the agreement; they execute it. + +The key: **Authority to resolve conflict comes from *amanah*, not rank.** The *Hakam* has authority because the circle consented to their facilitation. The *Shahid* has authority because the *Mithaq* says every agreement must be recorded. The *Mujbir* has authority because the *Sulh* gave them a clear domain. + +**Visual authority map:** +Draw three concentric circles: +- **Outer circle**: *Mithaq* (Charter) — holds the principles that no *Sulh* can violate. +- **Middle circle**: *Shura* (Circle Governance) — holds the consent process. +- **Inner circle**: *Sulh Agreement* — holds the specific restoration. + +Arrows: +- From *Hakam* → *Shura* (facilitation authority) +- From *Shahid* → *Mithaq* (alignment authority) +- From *Mujbir* → *Sulh Agreement* (execution authority) + +No single person holds all arrows. Authority is *distributed amanah*. + +--- + +### 4. TREASURY / BAYTUL MAL + +**ORG_DESIGNER:** +Conflict has a cost. It costs time, energy, and sometimes money. But unresolved conflict costs more—it leaks talent, erodes trust, and creates *shadow power* (backchannel decisions). The treasury must allocate a *Sulh Budget*: 5% of each circle’s operational budget reserved for conflict resolution. This covers: +- Facilitator time (if external). +- Training in *Sulh* facilitation (mandatory for every *Hakam*). +- *Muhasaba* tools (digital platforms for logging tensions, recording agreements). +- Compensation for time spent in *Sulh* sessions (treat it as sacred as any product sprint). + +No one should fear that raising a conflict will “waste money.” The *Baitul Mal* exists to serve the *Maqasid*—and *Hifz al-Nafs* (wellbeing) is a primary *Maqsad*. If a conflict is ignored, the *Baitul Mal* will later pay in turnover, lawfare, or silent disengagement. + +Transparency rule: All *Sulh Agreements* are recorded in a public *Sulh Register* (accessible to all members, not the public). The register shows: +- Date of tension +- Circle +- Summary of objection +- *Sulh Agreement* (redacted for privacy if needed) +- Cost (time spent, facilitator fees) + +This prevents *Baitul Mal* from being used to buy silence. If a circle spends its *Sulh Budget* without producing a recorded agreement, the *Hisbah* reviews. + +**KHALIFAH:** +The Prophet ﷺ said, “The wealth of a Muslim is not lawful unless given willingly” (Ahmad). The *Baitul Mal* in early *Khilafah* had a specific allocation for *Sulh*: the *Qadi*’s salary, the *Muhtasib*’s expenses, and the *Sulh* fund for compensating harm (e.g., if a dispute required returning property or paying *diya*). This was not discretionary; it was a line item in the public budget. + +Your org’s *Baitul Mal* must have a **Sulh Fund**—separate from operational budget. Any member can request a withdrawal from the *Sulh Fund* for: +- Mediation services (internal or external) +- Research to understand the tension (e.g., analyzing data that reveals the root cause) +- *Muhasaba* retreats (if the conflict is systemic, not interpersonal) + +The *Khalifah* (CEO / Lead Link) cannot block a *Sulh Fund* withdrawal that the *Shura* council has approved. The treasurer reports the *Sulh Fund* usage in every *Muhasaba* (retrospective). If the fund is unused, it is not a sign of peace—it is a sign of avoidance. *Sulh* is an investment, not an expense. + +**Visual for Treasury:** +Draw a jar labeled *Sulh Fund* with an arrow from each circle’s budget. Inside the jar, three compartments: +- *Hakam* fees +- *Muhasaba* retreats +- Compensation for harmed parties (if applicable) + +Below the jar: *“We spend on *Sulh* because *Hifz al-Nafs* is priceless.”* + +--- + +*End of Part 1. Continue to Principle, Protocol, and Muhasaba in Part 2.* \ No newline at end of file diff --git a/chapters/Sprint_07_Part2.md b/chapters/Sprint_07_Part2.md new file mode 100644 index 0000000..f51e6fe --- /dev/null +++ b/chapters/Sprint_07_Part2.md @@ -0,0 +1,125 @@ +## SHURA / CONSENT + +**ORG_DESIGNER:** +Consent is not consensus. In Sociocracy, a proposal passes unless there is a reasoned objection — a “yes, and improve” rather than “yes, everyone agrees.” At scale, you cannot wait for universal agreement. You need a rapid, structured process where each circle’s voice is heard through representatives, not direct democracy. Use the **Consent Decision-Making** pattern: Present, Clarify, Reaction, Objection, Amend, Confirm. Timebox each round. For distributed teams, use async tools (Loomio, Pol.is) with a clear facilitation role. + +**KHALIFAH:** +Shura is consultation, not voting. The Khalifah gathers experts (ahl al-hall wa al-aqd) but retains the final ikhtiyar (delegated authority) to act. The key is *representative diversity*: include those affected by the decision. In the classical system, the Khalifah consulted the majlis al-shura on matters of war, treasury, and public welfare. The aim was *ijma’* (collective wisdom) not *taswit* (majority vote). At scale, use layered shura: circle-level shura feeds district shura, which feeds central shura. Each level has binding consent on its domain. The condition: every member must be able to raise a tension without fear. + +**PRACTICE THIS SPRINT:** +Map your current decision-making flow. Identify where you use consensus (blocking) vs consent (objection). Replace one consensus gate this week with a consent round. Time it. Observe speed increase. + +--- + +## STEWARDSHIP / AMANAH + +**ORG_DESIGNER:** +Stewardship over ownership means no one “owns” the organization — they hold it in trust. Create a **Stewardship Circle** with a rotating membership of senior leaders and elected representatives. Their mandate: protect the evolutionary purpose, not shareholder value. Use a **Constitutional Bylaw** that caps any individual’s voting power and requires a supermajority to change the purpose. Link equity to tenure and contribution, not capital. Make ownership liquid only within the steward community. + +**KHALIFAH:** +Al-Mal (wealth) is amanah from Allah. The Baitul Mal is a trust for the ummah, not the ruler’s private purse. In an organization, this means the treasury belongs to the mission, not the founders. Establish a **Waqf Fund** for the core assets (IP, brand, reserves) — these cannot be sold or distributed. All surplus beyond operational needs is reinvested or given as sadaqah. The stewards (mutawalli) are fiduciaries with a sacred duty. Their compensation is fixed and transparent. No board member can profit from a conflict of interest. + +**PRACTICE THIS SPRINT:** +Identify one asset (e.g., codebase, client list, cash reserve) that should be held in trust. Draft a one-page “Amanah Declaration” that transfers control to a purpose-protected entity. Discuss with your team. + +--- + +## CONFLICT / SULH + +**ORG_DESIGNER:** +Conflict is data. Use the **Conflict Resolution Circle** — a peer-elected group trained in nonviolent communication and restorative practices. When a tension arises, the parties first attempt a facilitated dialogue. If unresolved, a formal **Objection Process** is triggered: each party states their perspective; the circle proposes a sulh (settlement) based on the organization’s principles. Appeals go to a higher circle, but the goal is closure within two sprints. Document every sulh as a precedent — it becomes your organizational fiqh. + +**KHALIFAH:** +Sulh is the preferred method of dispute resolution in Islamic law. The Qur’an says, “The making of peace is better” (4:128). The Khalifah appointed a qadi al-qudat (chief judge) and also a *muhtasib* (market inspector) who resolved disputes before they escalated. The key is *speed and dignity*: no party should feel humiliated. Use restorative circles where the harm is acknowledged and a reparation plan created. If the conflict involves a violation of shura or amanah, the hisbah body can intervene. The ultimate nullifier: refusal to engage in sulh after three sincere invitations triggers a formal inquiry. + +**PRACTICE THIS SPRINT:** +Identify one unresolved conflict in your org. Hold a 30-minute sulh session with a neutral facilitator. Agree on one actionable repair step. Do not leave without closure. + +--- + +## SUCCESSION / ISTIKHLAF + +**ORG_DESIGNER:** +Succession is not a crisis — it’s a pipeline. Design **Role Succession Documents** for every critical circle role. Each role owner trains a successor (apprentice) for at least one sprint per quarter. Use a **Mentorship Circle** that tracks readiness. When a role opens, the circle runs a consent-based selection: candidates present their vision; objections are processed; the best fit is chosen. No single person is indispensable. Automate knowledge transfer with Loom videos, wiki pages, and paired work. + +**KHALIFAH:** +Istikhlaf means appointing a khalifah (successor) who will continue the amanah. The Prophet ﷺ said, “If you are three, appoint one as amir” (Abu Dawud). The classical system had a clear bay’ah (pledge of allegiance) process: the outgoing leader consults the ahl al-hall wa al-aqd, who then offer bay’ah to the most qualified — not necessarily the eldest or richest. The condition: the successor must be known for *adalah* (justice) and *kifayah* (competence). The nullifier: if the successor violates the mithaq (covenant), the bay’ah is dissolved. + +**PRACTICE THIS SPRINT:** +Choose one critical role (e.g., CEO, tech lead). Write a one-page succession brief: responsibilities, skills, values. Identify a potential internal successor. Begin a 90-day shadowing plan. + +--- + +## HISBAH / ACCOUNTABILITY + +**ORG_DESIGNER:** +Hisbah is observability, not surveillance. Create a **Metrics Dashboard** that shows real-time health of each circle: decision velocity, tension resolution rate, budget variance, sentiment. No one is “policed” — the data is transparent and used for self-correction. Use a **Peer Accountability Sprint** every quarter: each role holder reviews their OKRs with a buddy. If a pattern of missed commitments emerges, the buddy escalates to the circle, not to a boss. + +**KHALIFAH:** +The muhtasib’s role was *amr bil ma’ruf wa nahy an al-munkar* — enjoining good and forbidding evil. In an organization, this means guidance, not punishment. The muhtasib checks for fairness, transparency, and adherence to the mithaq. They issue *tadhkir* (reminders) and *nasiha* (advice) before *ta’dib* (correction). The key: the muhtasib is independent — not reporting to the CEO or board, but to a separate ethics council. Hisbah is only valid if the observer themselves is known for integrity. + +**PRACTICE THIS SPRINT:** +Elect one person as your “Muhtasib of the Sprint” — no authority, just the duty to observe and remind. Ask them to write a one-paragraph “Hisbah Report” at sprint end: what went well, what needs attention. No names, just patterns. + +--- + +## LEGACY / WAQF + +**ORG_DESIGNER:** +Legacy means building something that outlasts you. Convert your core IP, brand, and cash reserves into a **Waqf (endowment)** structure. The waqf is owned by no one and managed by a perpetual trust. Any profits beyond operations are reinvested or given as sadaqah. The exit becomes irrelevant — there is no “sell.” Use a purpose-protected entity (e.g., a mission-locked LLC or charitable trust) that legally prevents dissolution. Your organizational DNA becomes a living waqf. + +**KHALIFAH:** +Waqf is one of the most powerful Islamic institutions for perpetuity. The Prophet ﷺ said, “When a person dies, their deeds cease except for three: ongoing charity (sadaqah jariyah)…” Waqf is sadaqah jariyah. In an organization, waqf means the mission continues regardless of who leads. The trustees (mutawalli) are chosen for their taqwa and competence. The waqf deed (waqfiyah) specifies the beneficiaries (e.g., employees, community, future generations) and the conditions of management. No one can alter the purpose — it is fixed forever. + +**PRACTICE THIS SPRINT:** +Write a one-paragraph “Waqf Intent Statement” for your organization. Example: “We intend that our code, community, and cash reserves become a perpetual trust serving Muslim founders and tech leaders. No individual will ever own a controlling share. All surplus will fund free training and tools.” Sign it with your team. Publish it. + +--- + +## THE PRINCIPLE (HUKM) + +**HUKM:** +We establish *Sulh as Organizational Retrospective* — every sprint, we devote one retrospective to surfacing and resolving a systemic conflict using the Conflict Quadrant (Avoid/Accommodate/Compete/Collaborate) and restorative sulh practices, with the explicit purpose of preserving Hifz al-Nafs (wellbeing) and transforming tension into collective growth. + +**DALEEL:** +The Qur’an commands, “If two parties among the believers fall into quarrels, make peace between them” (49:9). The Prophet ﷺ practiced sulh as a primary method of dispute resolution, even avoiding litigation where possible. Modern organizational research (Laloux, Dignan) shows that suppressing conflict leads to toxicity, while structured conflict resolution builds trust and resilience. The four quadrants (Avoid, Accommodate, Compete, Collaborate) map to classical Islamic ethics: *tajannub* (avoidance) is sometimes wise, *tahammul* (accommodation) is praiseworthy in minor matters, *tanafus* (healthy competition) is allowed in goodness, and *ta’awun* (collaboration) is the highest ideal for resolving major tensions. + +**MAQSAD:** +This principle primarily serves **Hifz al-Nafs** (preservation of wellbeing) — protecting individuals and the collective from psychological harm, burnout, and fractured relationships. Secondarily, it serves **Hifz al-Mal** (preservation of wealth) by reducing turnover costs, and **Hifz al-Din** (preservation of faith) by embedding an Islamic ethic of reconciliation as core organizational practice. + +**SHURUT:** +- The retrospective must include a trained facilitator (or rotating facilitator) who has read this playbook section. +- The conflict must be framed as a tension between roles, not between persons — use the language of “tension” not “blame.” +- The solution must be documented as a *sulh record* (one-page) and archived for future reference. +- The retrospective must end with a concrete action item assigned to a role-holder, with a deadline. +- If the conflict involves a violation of amanah (theft, fraud, breach of trust), the facilitator must escalate to the Hisbah circle immediately; sulh cannot override justice in cases of clear munkar. + +**MUNKATHIRAT:** +- **Refusal to participate:** If a party refuses to engage in sulh after three invitations from the facilitator, the case is automatically escalated to the next circle (or board) for formal adjudication. +- **Violation of confidentiality:** If any participant shares details of the conflict outside the retrospective without consent, the sulh is nullified and the facilitator must report the breach to Hisbah. +- **Pattern of avoidance:** If the same conflict reappears in three successive sprints without substantive resolution, the sulh process is considered failed; the circle must then engage an external mediator or qadi. +- **Hifz al-Nafs breach:** If any participant reports feeling unsafe, humiliated, or retaliated against during the process, the sulh is immediately suspended and a separate wellbeing review is triggered. + +--- + +## THE PROTOCOL + +**STEP 1: Sprint Retrospective — Conflict Quadrant Audit (Day 1 of Sprint)** +Hold a 45-minute retrospective. Each team member silently maps one unresolved tension onto the Conflict Quadrant (Avoid/Accommodate/Compete/Collaborate). Discuss as a group: which quadrant dominates? Where is the energy stuck? Select one tension to process as a sulh. + +**STEP 2: Sulh Circle — Restorative Dialogue (Day 2–3)** +Invite the two parties (or representatives) to a 30-minute facilitated dialogue. Use the structure: +- Each person states their perspective without interruption (3 min each). +- Facilitator summarizes the core need behind each position. +- Together, propose a *sulh* (settlement) that meets both needs. Document it on a one-page “Sulh Record” with roles, actions, and deadline. + +**STEP 3: Follow-Up & Closure (Day 5)** +Review the sulh in the next standup. If completed, mark it closed and archive the record. If not, escalate to the Hisbah circle for guidance. Celebrate the resolution — publicly acknowledge the courage of both parties. + +--- + +## MUHASABA (RETROSPECTIVE) + +**What one conflict are we avoiding right now because we fear the discomfort of sulh — and what will that avoidance cost us by next sprint?** + +Name it aloud. Write it down. Then ask: is the cost of silence greater than the risk of honest dialogue? If yes, schedule the sulh circle today. If no, examine your resistance — is it protecting your ego or protecting the mission? \ No newline at end of file diff --git a/chapters/Sprint_08_Part1.md b/chapters/Sprint_08_Part1.md new file mode 100644 index 0000000..dd58b6f --- /dev/null +++ b/chapters/Sprint_08_Part1.md @@ -0,0 +1,125 @@ +# SPRINT 8: SUCCESSION — CONTINUITY OVER HEROICS + +**MAQSAD:** Hifz al-Din — Preservation of Purpose +**FRAMEWORK:** Succession Quadrant — Hero / System / Pipeline / Endowment +**DURATION:** 4 Weeks (28 Days) + +--- + +## 1. THE CHARTER + +*Mithaq al-Istikhlaf — The Covenant of Continuity* + +We the people of this organization recognize that our purpose outlives any single leader. We reject the cult of the irreplaceable. We acknowledge that the Prophet ﷺ — the greatest leader in history — did not name a successor by explicit text, but left the community with the tools of *shura*, *bay'ah*, and *ijma'* to ensure continuity. Abu Bakr's succession was a system, not a hero moment: the *Saqifah* gathering, the consensus of the *Muhajirun* and *Ansar*, the public *bay'ah*, and the institutionalization of *khalifah* as a trust (*amanah*), not a throne. + +We therefore commit that every role in this organization has a defined succession pipeline. The "bus factor" — how many people can be hit by a bus before the organization halts — must never be one. We measure our health not by the brilliance of any individual, but by the depth of our bench. Succession is not a crisis response; it is a continuous act of *tazkiyah* (purification) and *ta'lim* (teaching). We build systems that outlast heroes. We endow knowledge, not personalities. + +We will not let our purpose die because we failed to prepare the next steward. + +--- + +## 2. SPRINT STRUCTURE + +**ORG_DESIGNER:** +Succession in most organizations is an afterthought — a hurried handover when someone quits, gets sick, or dies. The Teal approach flips this: succession is a continuous process of distributing authority and developing capability. We use two complementary structures: + +**Circle-Level Succession:** Every circle maintains a "Succession Canvas" — a living document for each role that answers: *Who is the current role-filler? Who is the backup? What knowledge must be transferred? What is the readiness level (Red/Yellow/Green)?* This is reviewed monthly in governance meetings. + +**Pipeline Circles:** A separate circle, the *Istikhlaf Circle*, owns the overall succession architecture. Its domains: talent identification, mentorship pairings, knowledge documentation, and emergency succession triggers. This circle has no operational authority — it is a *service circle* to all other circles. + +**KHALIFAH:** +The classical *Khilafah* model is instructive. Abu Bakr's succession was not a single event but a layered system: + +First, the *shura* of the *Saqifah* — the immediate tribal leaders negotiated while the Prophet's body was still being prepared. Second, the *bay'ah* of the *Muhajirun* and *Ansar* — a staggered consent process that took days. Third, the institutionalization of the *khalifah* as a role with clear domains: *imamah* (leadership), *qada'* (judiciary), *jihad* (defense), and *jizyah/zakat* (finance). Each domain had its own succession logic. + +The critical insight: **succession was distributed.** The *khalifah* was one role; the *qadi* (judge), *amir al-jaysh* (military commander), and *sahib al-kharaj* (finance minister) each had independent succession pipelines. The *khalifah* did not appoint his own successor unilaterally (except Abu Bakr's *istikhlaaf* of Umar, which was then ratified by *shura*). This prevented single-point-of-failure. + +**The Succession Quadrant:** + +| **Hero** | **System** | +|----------|------------| +| One person holds all knowledge. Crisis when they leave. | Roles documented. Backups trained. Transitions smooth. | +| **Pipeline** | **Endowment** | +| Talent identified early, mentored, rotated. | Institution owns knowledge. Culture perpetuates itself. | + +Our sprint moves from *Hero* to *System* and *Pipeline*. *Endowment* is the long game. + +**Visual Framework:** +Draw a 2x2 grid. Top-left: Hero (bus factor = 1). Top-right: System (bus factor = 3+). Bottom-left: Pipeline (continuous development). Bottom-right: Endowment (purpose outlives individuals). Circle where you are now. Circle where you want to be by sprint end. + +**Sprint Outputs:** +- Every role has a Succession Canvas (backup named, readiness level, knowledge gaps). +- Istikhlaf Circle formed with 3-5 members. +- Emergency succession protocol for top 5 roles. + +--- + +## 3. AUTHORITY MAP + +*Ikhtiyar — Delegated Trust, Not Commanded Handover* + +**ORG_DESIGNER:** +Succession fails when authority is centralized in a single point. The solution is *consent-based distributed authority* — every role has a defined domain, and the role-filler has full authority within that domain *until* they leave. Succession is not about "the new leader" inheriting all power; it is about each role's authority being transferred independently. + +In Sociocracy, role elections use consent: the current role-filler does not appoint their successor. Instead, the circle nominates, then consent-processes candidates. This prevents founder syndrome and ensures the successor is chosen for competence, not loyalty. + +**KHALIFAH:** +The classical principle of *ikhtiyar* (delegation) is often misunderstood. The *khalifah* did not hold all authority; he held a trust (*amanah*) that was limited by *shari'ah* and *shura*. When Abu Bakr appointed Umar as his successor, he did not simply command. He consulted the senior *sahabah* individually — Uthman, Abd al-Rahman ibn Awf, Ali (radiallahu anhum) — and received their *bay'ah* before announcing. The authority to choose a successor was distributed among the *ahl al-hall wa al-'aqd* (the people of binding and loosing). + +This maps to modern consent-based decision-making: the circle's consent is the *bay'ah*. The role-filler does not own the role; they are trustees of the domain. + +**Authority Mapping Exercise:** +1. List the top 5 roles in your organization (e.g., CEO, CTO, Head of Product, Head of Finance, Head of Community). +2. For each role, identify: *Who has the authority to appoint the successor?* (Circle consent? Board? Founder?). +3. Identify: *Who has the authority to remove the role-filler?* (Same body? Different?). +4. Ensure no role has unilateral appointment power — that's the Hero trap. + +**Classical Precedent:** +The Prophet ﷺ appointed *amirs* (governors) for specific domains (e.g., Mu'adh to Yemen). Each *amir* had defined authority and a backup. When the Prophet died, the *amirs* did not automatically resign; they continued until the new *khalifah* confirmed them. This is *continuity through distributed authority* — the system does not reset when one person leaves. + +**Maqsad Application (Hifz al-Din):** +The purpose (*din*) of the organization must be preserved through succession. Authority maps must ensure that the successor upholds the mission, not just the founder's ego. Therefore, the consent body for succession must include those who represent the organization's purpose — the *ahl al-‘ilm* (those who understand the mission), not just the *ahl al-qaraba* (those close to the current leader). + +**Sprint Action:** +By end of Week 2, every circle runs a "Succession Authority Audit": For each role, document who appoints, who removes, and who holds the role's purpose in trust. If any role has a single person as appointor, redesign it to require circle consent. + +--- + +## 4. TREASURY / BAYTUL MAL + +*Baitul Mal as Trust — Succession Is Funded, Not Cheap* + +**ORG_DESIGNER:** +Most organizations treat succession as a zero-cost activity — a conversation, a handover document, maybe a week of overlap. That is fantasy. Real succession requires budget: for mentorship stipends, for knowledge capture tools, for paid overlap periods, for external coaching of new role-fillers. + +In Teal organizations, the treasury allocates a "Succession Reserve" — a percentage of revenue (typically 3-5%) that cannot be used for operational expenses. This reserve funds: +- Role documentation projects (video, written, structured). +- Mentorship programs (senior members paid to train backups). +- Transition support (outsourcing to cover the role while the new person ramps). +- Emergency succession (severance for the departing, premium for the arriving). + +**KHALIFAH:** +The *Baitul Mal* (public treasury) in classical *Khilafah* included a specific allocation for *'ata'* (stipends) for officials *and* their successors-in-training. Umar ibn al-Khattab institutionalized the *diwan* (register) that recorded every soldier, official, and their family — including who would replace them in case of death or incapacity. This was not sentimental; it was fiscal discipline. + +**The Principle of *Baitul Mal al-Istikhlaf* (Succession Treasury):** +Every revenue stream must allocate a portion to continuity. The *kharaj* (land tax) funded the *diwan*; the *zakat* funded the *ahl al-suffah* (students). In your organization, treat succession funding as a non-negotiable line item. + +**Sprint Financial Actions:** + +1. **Calculate the "Hero Tax":** What is the cost of losing each key person? (Recruitment cost + lost productivity + knowledge loss + morale dip). Multiply by probability of departure. That is your annual succession risk. Allocate 10% of that as your Succession Reserve. + +2. **Create a "Succession Wallet":** A separate account (real or virtual) that holds the reserve. It can only be spent on succession activities. No CEO override. + +3. **Transparency:** Publish the Succession Wallet balance and expenditures in your organizational dashboard. The *Baitul Mal* is a trust; the community must see how their resources are being used to protect the purpose. + +**Maqsad Application (Hifz al-Mal — Preservation of Wealth):** +Your organization's greatest wealth is not cash — it is the knowledge and capability embedded in your people. Failing to fund succession is *israf* (waste) of that wealth. The *Baitul Mal* exists to preserve the *ummah*'s assets; your treasury exists to preserve your purpose. + +**Sprint Output by Week 4:** +- Succession Reserve established (minimum 2% of monthly revenue). +- First disbursement: Documentation stipend for top 3 roles. +- Dashboard entry: "Succession Fund Balance: $X. Target: $Y." + +--- + +*End of Part 1. Proceed to Part 2: Principle (Hukm), Protocol, Muhasaba.* \ No newline at end of file diff --git a/chapters/Sprint_08_Part2.md b/chapters/Sprint_08_Part2.md new file mode 100644 index 0000000..e88f5bf --- /dev/null +++ b/chapters/Sprint_08_Part2.md @@ -0,0 +1,65 @@ +## SHURA / CONSENT + +**ORG_DESIGNER:** Succession decisions are the highest-stakes governance moments. In most organizations, a founder, CEO, or key leader selects their successor behind closed doors — a single point of failure masked as tradition. In a Teal/evolutionary structure, succession is a consent-based process, not a popularity contest. Consent is not consensus: it means no one has a reasoned objection to the proposed successor. The circle or the broader organization uses a structured process: a nominating circle proposes a candidate, the relevant circle members (those who will be led and those who will co-lead) raise objections, and the proposal iterates until objections are resolved. This prevents hero-worship, nepotism, and sudden power vacuums. The goal is continuity of purpose, not continuity of personality. + +**KHALIFAH:** The classical Shura for choosing a Khalifah after the Prophet ﷺ was not a free-for-all election. It was a consent-based process among the *ahl al-hall wa al-‘aqd* — the people of binding and loosening. Abu Bakr was nominated by Umar and others in Saqifah; then the general public gave bay’ah (consent). Umar was appointed by Abu Bakr after consultation; Uthman was chosen by a shura council of six nominated by Umar; Ali was chosen by the people of Madinah after Uthman’s death. Each case had a different method, but all shared: the process was transparent, objections were heard, and the appointment was sealed by public consent (bay’ah). The principle: **authority flows from collective consent, not individual ambition.** + +**THE SHURA PROMPT ANSWERED:** How do you consult at scale? You don’t ask 1,000 people for their opinion — you identify the *ahl al-hall wa al-‘aqd* (the trusted, knowledgeable, representative members) and run a consent process. In an organizational context, this means the relevant circle (team leads, domain experts, key stakeholders) becomes the shura body. They debate, raise concerns, and give their *ikhtiyar* (delegation). The rest of the organization is informed and invited to raise objections within a defined window. This balances speed with legitimacy. + +**ACTION THIS SPRINT:** Create a **Succession Shura Circle** — three to five people who are not the current leader. Define their domain: they will propose and iterate on a successor candidate using consent. Publish the process before any actual succession event. This circle becomes the *ahl al-hall wa al-‘aqd* for succession decisions. + +## STEWARDSHIP / AMANAH + +**ORG_DESIGNER:** Ownership and stewardship are often confused. In a typical startup, founders own equity and control the board; succession means selling the company or passing the baton to a new CEO who serves the shareholders. In a Teal organization, ownership is secondary to stewardship: the purpose owns the organization, not the founders. Succession is about ensuring that the person who steps into leadership is a steward of the mission, not a caretaker of private wealth. This means separating the role of “owner” (who may retain economic rights) from the role of “steward” (who holds decision-making authority). The steward is accountable to the purpose, the circle, and the future generations of contributors. + +**KHALIFAH:** Khalifah literally means one who is appointed to act on behalf of someone else — a steward, not an owner. Umar ibn al-Khattab famously said: “I have been appointed over your affairs, and I am a trustee (amin). The property of Allah is for the benefit of all.” The Khalifah does not own the state; he manages it as an amanah. The treasury (baitul mal) is not his personal wealth — he cannot give it away or hoard it. Stewardship means the leader is *accountable* to the community, the Shariah, and the purpose. Succession is about finding another steward who will uphold that trust, not a new owner who will extract value. + +**THE STEWARDSHIP PROMPT ANSWERED:** How do you ensure stewardship over ownership? Implement a **Baitul Mal Constitution**: the organization’s assets (equity, IP, cash reserves) are declared as a *waqf* (endowment) or a *trust* that cannot be liquidated for personal gain. The successor inherits the *role* of steward, not the *equity* of the founder. Founders can receive a just compensation for their work (ujrah) but cannot sell the organization to a buyer who would destroy its purpose. This is codified in the Mithaq (Charter). The successor is chosen by the Shura circle, not by the founder alone. + +**ACTION THIS SPRINT:** Draft a **Stewardship Clause** for your Mithaq: “The organization’s purpose and assets are held in trust for future generations. No individual may sell or dissolve the organization without the consent of a broad circle. Successors are chosen through a consent-based process, not by inheritance or unilateral appointment.” + +## CONFLICT / SULH + +**ORG_DESIGNER:** Succession often triggers conflict: the outgoing leader may resist letting go; the incoming leader may feel insecure; teams may split into factions. In a healthy organization, conflict is not suppressed — it is surfaced and resolved through structured processes. The key is to separate personal emotions from role tensions. A good conflict protocol for succession includes: a facilitated retrospective between outgoing and incoming leaders; a clear handover document; a cooling-off period where both can raise objections without fear; and a *sulh* (reconciliation) meeting if the conflict persists. The goal is not harmony but clarity: can this succession move forward with everyone’s consent? + +**KHALIFAH:** Sulh (reconciliation) is a deeply rooted Islamic principle. When the Prophet ﷺ appointed leaders, he often mediated disputes personally. The classical *hisbah* institution also had a role in resolving conflicts between officials and the public. In succession, the potential for fitna (disruption) is high. The remedy is a structured sulh process: the disputing parties sit with a neutral third party (a *hakam* — arbiter) and agree on a resolution that preserves the purpose. If no resolution is possible, the Shura circle can revoke the appointment or delay the succession. + +**THE CONFLICT PROMPT ANSWERED:** How do you resolve conflict at scale? You don’t ignore it or escalate it to HR. You create a **Sulh Protocol**: (1) Any party can call a sulh meeting within 48 hours of a succession-related conflict. (2) A neutral facilitator (from outside the circle, pre-trained) runs a structured conversation: each person states their tension, the facilitator tests for objections, and the group proposes a resolution. (3) If an objection persists, the succession is paused and the Shura circle decides whether to proceed with a different candidate or address the root cause. This protocol is published in the Mithaq. + +**ACTION THIS SPRINT:** Appoint a **Sulh Facilitator** — someone in the organization trained in non-violent communication and consent-based decision-making. This person is not the leader or the successor. Their role is to facilitate conflict resolution in any succession process. Document the Sulh Protocol in your governance handbook. + +## SUCCESSION / ISTIKHLAF + +**ORG_DESIGNER:** Succession is not an event — it is a pipeline. The mistake most organizations make is waiting until the leader announces departure to start looking. By then, it’s a crisis. A healthy organization builds a succession pipeline years in advance: potential successors are identified early, given stretch assignments, mentored, and gradually exposed to leadership circles. This is not about grooming a “crown prince” — it’s about creating a bench of qualified people who could step into key roles. The pipeline is transparent: everyone knows who is being developed, and the criteria are objective (skills, alignment with purpose, consent from peers). + +**KHALIFAH:** Umar ibn al-Khattab had a succession plan: before his death, he appointed a shura council of six and gave them clear instructions to choose one among them within three days. But he also developed people over time — he mentored Ali, Uthman, Ibn Abbas, and others. The Khalifah is not a monarch; the system is designed to produce multiple qualified candidates. The process is documented in the *siyar* (biographical traditions) of the early caliphs. *Istikhlaf* (appointing a successor) is a duty, not an option. If a leader dies without a plan, the community is thrown into chaos — this is precisely what happened after Uthman’s assassination, and it led to fitna. + +**THE SUCCESSION PROMPT ANSWERED:** How do you design for continuity? You build a **Succession Pipeline Dashboard** that tracks potential successors for every key role. Each quarter, the Shura circle reviews the pipeline: who is ready now? Who needs 6 months of mentoring? Who needs 2 years? The current leader is required to mentor at least two potential successors as part of their role. The mentor relationship is formalized with a **Mentorship Mithaq** — a contract of mutual accountability. Documentation is essential: the pipeline, the mentorship plan, and the succession criteria are all written in the organization’s handover playbook. + +**ACTION THIS SPRINT:** Create a **Succession Pipeline Spreadsheet** with columns: Role, Current Leader, Successor Candidate 1, Successor Candidate 2, Readiness Level (Now/6 months/2 years), Mentor Assigned, Last Review Date. Review it with the Shura circle this month. Add a recurring quarterly agenda item: “Succession Pipeline Review.” + +## HISBAH / ACCOUNTABILITY + +**ORG_DESIGNER:** Succession often fails because the outgoing leader is not held accountable for their handover. The *hisbah* function — self-regulation and accountability — must extend to the succession process. This means: the outgoing leader must produce a complete handover document (decisions made, lessons learned, key relationships, unfinished projects). The incoming leader has the right to inspect this document and raise objections. A designated *hisbah* member (an ombudsperson or governance steward) verifies that the handover is complete and that no critical information is hidden. This prevents the “heroic leader who takes secrets to the grave” syndrome. + +**KHALIFAH:** The classical *hisbah* (market inspector / public accountability) was not just about weights and measures — it also oversaw public officials. The Khalifah was accountable to the Shariah and to the community. Umar used to walk the streets at night to inspect and hold his governors accountable. In succession, the *hisbah* function ensures that the process is transparent and that no one is hiding information or manipulating the selection. The *hisbah* officer does not have decision-making power over succession, but they have the right to raise objections and call for a shura meeting if they see irregularities. This is **observability as guidance** — not policing, but ensuring that the system is visible and honest. + +**THE HISBAH PROMPT ANSWERED:** How do you guide without policing? The *hisbah* role is not a police officer — it is a **guide** (murshid). They point out gaps, remind people of the principles, and facilitate self-correction. In succession, the *hisbah* officer reviews the handover document and the pipeline quarterly. If they see a gap (e.g., no successor identified for a critical role), they issue a **tension** to the Shura circle. The circle must address it or document why they choose not to. The *hisbah* officer also ensures that the succession process is documented in the Mithaq and that no one bypasses the consent process. + +**ACTION THIS SPRINT:** Appoint a **Hisbah Officer** (or a rotating role) for your organization. Their mandate: monitor the succession pipeline and handover processes. They have the right to call a shura meeting if they detect a significant gap. Publish their contact info and make it known that anyone can raise a succession-related tension to them. + +## LEGACY / WAQF + +**ORG_DESIGNER:** Most founders think of exit: IPO, acquisition, or retirement. But an organization built for purpose over profit does not exit — it endows. The ultimate succession is not just passing the leadership baton, but ensuring the organization itself can survive and thrive without any single individual. This is the *waqf* mindset: the organization becomes an endowment that serves its purpose in perpetuity. The founders’ equity is transformed into a *waqf* structure (non-profit, trust, or cooperative) where no one can personally liquidate the organization. Succession becomes a natural process of renewal, not a crisis. + +**KHALIFAH:** The Islamic concept of *waqf* (endowment) is the ultimate expression of perpetuity. When a person dedicates property as waqf, they relinquish ownership forever; the property serves the community indefinitely. The Khalifah’s role is to protect the waqf and ensure its purpose is fulfilled. In organizational terms, the *legacy* is not the founder’s name — it is the **continuation of the purpose**. The founder’s greatest achievement is to make themselves unnecessary. Umar established the first state-level waqf (the land of Khaybar) whose revenues supported public welfare for centuries. The *waqf* structure ensures that the organization outlives its founders. + +**THE LEGACY PROMPT ANSWERED:** How do you build for perpetuity? You design the **Legacy Layer** of your governance: a set of principles and mechanisms that cannot be changed by any single person or generation. This includes the **Mithaq** (Charter) as a living document, but with a core that is amendment-proof (e.g., the purpose, the waqf structure, the consent-based decision-making). You also create a **Legacy Circle** — a group of stewards (not owners) whose only job is to protect the purpose and the process across generations. They do not run day-to-day operations; they ensure that the system remains healthy. This is the ultimate succession. + +**ACTION THIS SPRINT:** Draft a **Legacy Statement** (one paragraph) that articulates what you want the organization to look like 50 years from now. Share it with the whole team. Then start a conversation: “Should we convert our ownership structure into a waqf/trust to ensure perpetuity?” Even if you don’t act immediately, the conversation shifts the mindset from exit to legacy. + +## THE PRINCIPLE (HUKM) + +**HUKM:** We establish a **Succession System** based on consent, stewardship, and pipeline development, where every key role has at least one identified successor, the process is transparent and documented, and the outgoing leader is accountable for a complete handover — all backed by a hisbah function that ensures compliance. + +**DALEEL:** The classical Khalifah system provided multiple models of succession (appointment by predecessor, shura council, general bay’ah) but always with consent and transparency. The Prophet ﷺ said: “If a person is put in charge of something and he dies, and he has not left behind a successor, then his trust is betrayed” (adapted from various hadith on leadership). Modern organizational research (e.g., succession planning in Teal organizations, Laloux’s *Reinventing Organizations*) shows that pipelines and consent-based processes reduce disruption and increase continuity. The combination of *istikhlaf* (appointment) and *his \ No newline at end of file diff --git a/chapters/Sprint_09_Part1.md b/chapters/Sprint_09_Part1.md new file mode 100644 index 0000000..67d8627 --- /dev/null +++ b/chapters/Sprint_09_Part1.md @@ -0,0 +1,114 @@ +# SPRINT 9: HISBAH — ACCOUNTABILITY WITHOUT POLICING +## Maqasid: Hifz al-Aql (Preservation of Clarity) → Self-Regulation at Scale + +--- + +## 1. THE CHARTER (~200 words) + +**We the people of this organization** covenant to hold ourselves accountable **not through surveillance, but through clarity**. Hisbah in classical thought was never a police force—it was a **voluntary system of mutual correction** rooted in *amr bil ma'ruf wa nahy anil munkar* (enjoining good and forbidding evil). The *muhtasib* (accountability guide) held no coercive power over hearts; only the authority to **remind, alert, and elevate** when collective clarity was threatened. + +**We distinguish self-regulation from policing:** +- **Policing** assumes brokenness and enforces compliance from outside. +- **Self-regulation** assumes wholeness and restores alignment from within. + +**Hisbah maps directly to modern observability:** +- **Monitor** = Real-time dashboards of organizational health (not individual surveillance) +- **Guide** = Automated nudges and consent-based feedback loops +- **Correct** = Peer-led tension processing, not punitive escalation +- **Elevate** = Retrospectives that strengthen the system, not blame individuals + +**Our covenant:** We will build accountability systems that **preserve Hifz al-Aql**—the clarity of purpose, process, and trust. No one shall be watched without their knowledge. No metric shall be used to punish. Every alert is an invitation to **reconnect with our shared Mithaq**. + +--- + +## 2. SPRINT STRUCTURE (~300 words) + +**ORG_DESIGNER:** +Draw four concentric circles. Label them: + +1. **Inner Circle — Personal Dashboard** + Every role holder maintains a **live tension log** (e.g., "My delivery timeline keeps slipping because approval takes 3 days"). This is self-observability. Each person runs their own *Hisbah circuit*: monitor → guide → correct → elevate. + +2. **Second Circle — Role Circle Hisbah** + Each circle holds a **monthly Hisbah Review** (not performance review). Three questions: + - *Monitor*: What metrics showed drift? + - *Guide*: What nudges did we receive? + - *Correct*: What tensions did we process? + - *Elevate*: What system improvements did we make? + + Output: A **Clarity Report** (1 page) shared with super-circle. + +3. **Third Circle — Super-Circle Hisbah** + Cross-circle accountability. Representatives from each circle attend a **Hisbah Shura** every quarter. They ask: "Where is the organization losing clarity? What patterns of *munkar* (misalignment) are emerging?" They propose systemic corrections (e.g., "Our OKR review cycle is too fast—causing burnout"). + +4. **Outer Circle — Organizational Hisbah** + The full organization runs an **annual Hisbah Retrospective**. This is a **no-blame, full-transparency** audit of every process, metric, and delegation. The goal: **update the Mithaq** itself if needed. + +**KHALIFAH:** +This maps exactly to classical Hisbah under the *Khilafah*. The *muhtasib* was not a single person—it was a **distributed function**. In the market of Kufa, each trade guild had its own *muhtasib* (a trusted elder) who monitored weights, prices, and honesty. But the system was **peer-driven**: any merchant could raise a *hisbah* concern. + +The four circles parallel the classical layers: +- **Personal accountability** (muhasabat al-nafs) +- **Guild/circle accountability** (hisbah al-hiraf) +- **Regional accountability** (hisbah al-amir) +- **State-level policy** (hisbah al-khilafah) + +The modern innovation: **observability tools** (dashboards, alerts, tension logs) replace the *muhtasib's* manual rounds. But the principle remains: **accountability flows from clarity, not fear.** + +--- + +## 3. AUTHORITY MAP (~300 words) + +**ORG_DESIGNER:** +Hisbah in a Teal organization **cannot be command-based**. If a "central Hisbah officer" has authority to punish, it becomes policing. Instead, authority is **distributed through consent**: + +- **Personal Hisbah Authority**: Every role holder has the **right to raise a tension** about any process, metric, or behavior that threatens collective clarity. No permission needed. This is *ikhtiyar* (delegated authority) over one's own clarity domain. + +- **Circle Hisbah Authority**: Each circle elects a **Hisbah Guide** (rotating role, 3-month term). The Guide's authority: + - *Monitor*: Access to all circle dashboards (not individuals' personal logs) + - *Guide*: Sends **non-binding nudges** to any role holder ("Your lead time is 2x the circle average—would a process review help?") + - *Correct*: Can call a **tension-processing meeting** if a pattern persists + - *Elevate*: Proposes system changes to the circle + +- **Limits on Hisbah Authority**: + - No Guide can access private communication or personal performance data. + - No Guide can impose sanctions. All corrections are **consent-based**: the circle must approve any process change. + - Any role holder can **object** to a Hisbah alert if it feels like policing. The objection triggers a **Shura** to clarify intent. + +**KHALIFAH:** +Classical *ikhtiyar* (delegated authority) for the *muhtasib* was strictly **limited by sharia and custom**. The *muhtasib* could not enter homes, could not punish without witnesses, could not act on suspicion alone. Authority was **Amanah**—a trust to preserve clarity, not to dominate. + +The modern parallel: **Hisbah Guides hold ikhtiyar over systems, not people.** They can adjust dashboards, propose norm changes, and call meetings. But they **cannot override consent** from the role holder or circle. If a role holder says, "Your alert feels like surveillance," the Guide must immediately **step back** and enter a *Sulh* (reconciliation) process. + +**The authority map is a triangle:** +- **Role Holder**: Owns their tension log and response +- **Hisbah Guide**: Owns the system design and nudges +- **Circle**: Owns the corrections and policy changes + +No vertex dominates. All decisions require **consent**—meaning no one has a reasoned objection that the circle cannot address. This preserves *Hifz al-Aql*: clarity without coercion. + +--- + +## 4. TREASURY / BAITUL MAL (~200 words) + +**ORG_DESIGNER:** +Hisbah systems cost money: observability tools, facilitator training, retrospective time. These costs are **not overhead**—they are investments in clarity. The **Baitul Mal** (organizational treasury) allocates a **Hisbah Budget** as a fixed percentage of total revenue (suggested: 2-5%). + +**Allocation rules:** +1. **60%** → Tools and infrastructure (dashboards, alerting platforms, secure logs) +2. **25%** → Capacity building (training Hisbah Guides, conflict mediation, Shura facilitation) +3. **10%** → Retrospective time (paid hours for circle Hisbah reviews) +4. **5%** → Emergency clarity fund (unforeseen accountability crises) + +**Transparency requirement:** Every Hisbah expenditure is published in a **public ledger** within the organization. No secret budgets. No hidden metrics. + +**KHALIFAH:** +In classical *Baitul Mal*, the *muhtasib* was a salaried position funded from *zakah* or *fay'* (public funds). But the **treasury was never private**—the Caliph could not hide a single dirham. The *muhtasib* reported directly to the *qadi* (judge) and his accounts were audited by the *shura* council. + +**Our principle:** The Hisbah budget is a **public trust**. Any member can request a line-item review. If a tool is purchased that enables surveillance (e.g., keystroke logging), the **Baitul Mal must defend its necessity** in an open Shura. If the defense fails, the tool is removed and funds reallocated. + +**This preserves Hifz al-Mal (preservation of wealth)** — because clarity should never come at the cost of trust. A treasury spent on policing destroys more value than it protects. A treasury spent on **self-regulation infrastructure** multiplies trust. + +--- + +*End of Part 1. Continue to Part 2: Principle (Hukm), Protocol, and Muhasaba.* \ No newline at end of file diff --git a/chapters/Sprint_09_Part2.md b/chapters/Sprint_09_Part2.md new file mode 100644 index 0000000..a73c62f --- /dev/null +++ b/chapters/Sprint_09_Part2.md @@ -0,0 +1,94 @@ +## SHURA / CONSENT + +**ORG_DESIGNER:** At scale, consensus stalls. Consent moves. Sociocracy’s consent process — “Do you have any objections to this proposal?” — is designed for speed and safety. Classical Shura does not mean unanimity; it means binding counsel from trusted representatives. + +**KHALIFAH:** The Khalifah consulted the *ahl al-hall wa al-‘aqd* (those who loosen and bind). Not everyone. The right people, with the right information, at the right time. Shura is a method, not a ceremony. Scale it by creating nested circles of trusted stewards — each circle consents to proposals that affect its domain. No circle votes. No circle blocks. Objections surface tensions; consent clears the path. + +**PROMPT ANSWERED:** You consult at scale by distributing Shura into circles of competence. The Khalifah does not poll the entire ummah. You do not poll the entire org. You map who holds the tension, who carries the domain, and who must give consent. That is the circle. That is Shura in motion. + +--- + +## STEWARDSHIP / AMANAH + +**ORG_DESIGNER:** Stewardship is the opposite of ownership-as-control. You hold the role, not the throne. Fiduciary duty means you act in the best interest of the mission, not yourself. Pipeline means you are always grooming your successor. + +**KHALIFAH:** In classical Khilafah, the treasury was *baitul mal* — a trust, not a private purse. The Khalifah could not gift state funds to family. Today, your equity, your revenue, your data: all *amanah*. Stewardship over ownership means you write the rules so that no single person can extract rent. You tie compensation to mission outcomes, not control. You document your decisions so the next steward inherits clarity, not chaos. + +**PROMPT ANSWERED:** You ensure stewardship over ownership by making every role a trust, every key a backup, every decision auditable. Ownership becomes a verb, not a noun. + +--- + +## CONFLICT / SULH + +**ORG_DESIGNER:** Conflict is a tension to be processed, not a fire to be extinguished. In Teal orgs, conflict resolution is a core competency. The process is peer-based, not escalated to a boss. + +**KHALIFAH:** *Sulh* (reconciliation) is a sacred act in Islam. The Prophet ﷺ said, “Reconciliation is permissible between Muslims.” It is a contract, not a judgment. The parties define the terms. The facilitator holds the space. Conflict at scale requires a *sulh protocol*: any two roles can trigger a facilitated session. No blame. No punishment. The goal is to restore the relationship and the work. If the tension persists, it becomes a governance proposal. + +**PROMPT ANSWERED:** You resolve conflict at scale by institutionalizing *sulh* as a sprint ritual. Every retrospective begins with: “What tensions remain unresolved?” Then you process them with consent, not command. + +--- + +## SUCCESSION / ISTIKHLAF + +**ORG_DESIGNER:** Succession is not an emergency plan. It is a continuous pipeline. Every role should have a documented domain, a list of key tensions, and at least one person shadowing. + +**KHALIFAH:** The Khalifah Umar رضي الله عنه appointed a council of six to choose his successor before his death. He did not leave it to chance. He prepared the *shura* with known criteria. *Istikhlaf* (succession) is an act of foresight. For your organization: each quarter, every circle lead names a potential successor and begins transferring tacit knowledge. The role is not a possession; it is a trust to be passed. + +**PROMPT ANSWERED:** You design for continuity by making succession a standing agenda item. Every role has a backup. Every decision is documented. The org survives any single departure. + +--- + +## HISBAH / ACCOUNTABILITY + +**ORG_DESIGNER:** Accountability is not surveillance. It is observability. In the best orgs, people self-correct because they see the data. Hisbah as a function is about guidance, not policing. + +**KHALIFAH:** The classical *muhtasib* did not spy. He corrected what was visible in the marketplace — false weights, fraud, public harm. His role was to remind, not to punish. For your org: Hisbah is a dashboard of key indicators visible to everyone. It is a regular *muhasaba* (self-accounting) where each role reviews their own performance against the mission. No blame. No shame. Just data and course correction. + +**PROMPT ANSWERED:** You guide without policing by making the system transparent. When everyone sees the same metrics, the tension to improve becomes intrinsic. Hisbah becomes a habit, not a department. + +--- + +## LEGACY / WAQF + +**ORG_DESIGNER:** Legacy means the organization outlives its founders. Perpetuity over exit. Waqf is the ultimate structure for this — an endowment that cannot be sold or diverted. + +**KHALIFAH:** The classical *waqf* is an inalienable trust. The founder dedicates the asset to Allah, with a defined purpose. It cannot be revoked. For your organization: design your legal structure as a waqf-like entity. Transfer ownership to a mission-locked foundation. Your shares become non-transferable. Your exit is not an IPO; your exit is the organization becoming self-sustaining. This is the highest form of stewardship. + +**PROMPT ANSWERED:** You build for perpetuity by locking the mission into the org’s DNA. No founder can sell. No investor can pivot. The purpose is the only owner. + +--- + +## THE PRINCIPLE (HUKM) + +**HUKM:** We adopt the Hisbah Quadrant (Monitor / Guide / Correct / Elevate) as the default accountability protocol for all circles, with self-regulation as the primary mode and peer-based guidance as the secondary mode. + +**DALEEL:** The classical *hisbah* institution operated on the principle of *amr bil ma'ruf wa nahy anil munkar* (enjoining good and forbidding evil) without coercion. The Prophet ﷺ said, “Whoever among you sees an evil, let him change it with his hand; if unable, with his tongue; if unable, with his heart.” This establishes a graduated response: first guidance, then correction, and only if necessary, escalation. Modern Teal organizations confirm that self-managed teams regulate more effectively when given clear domains and transparent metrics. + +**MAQSAD:** Primarily *Hifz al-Aql* (Preservation of Clarity) — self-regulation requires clear thinking and visible data. Secondarily *Hifz al-Mal* (Preservation of Trust) — accountability protects shared resources from misuse. + +**SHURUT:** +- Every circle must publish its key performance indicators (KPIs) and consent limits at the start of each sprint. +- Any circle member can initiate a guidance conversation if a metric trends negative for two consecutive sprints. +- The *muhtasib* role (rotating) is limited to reminding and recommending; it has no power to enforce. +- A circle can escalate to the wider Shura only after three failed guidance attempts. + +**MUNKATHIRAT:** +- If any role is given coercive power over others (e.g., firing, demoting, fining), the Hisbah protocol is nullified and must be redesigned by the next general Shura. +- If the monitor function becomes secret surveillance (non-public data), the trust is broken and the protocol is invalid. +- If a circle fails to conduct a retrospective for more than two consecutive sprints, the Hisbah protocol automatically triggers a governance review. + +--- + +## THE PROTOCOL + +**STEP 1:** **Set up the Hisbah dashboard.** By the end of this sprint, every circle creates a public board (physical or digital) showing its top 3 KPIs, its consent limits, and the name of the rotating *muhtasib* for this sprint. + +**STEP 2:** **Run the first guidance session.** In week two of the sprint, each circle holds a 30-minute *muhasaba* (self-accounting) where each role answers: “What did I commit to? What did I deliver? What tension do I see?” The *muhtasib* facilitates, not judges. + +**STEP 3:** **Commit the Hisbah Protocol to your Mithaq.** By the end of the sprint, incorporate the Quadrant framework and the conditions above into your organizational covenant. Ratify by consent of all circles. + +--- + +## MUHASABA (RETROSPECTIVE) + +**What is one metric you are currently hiding from yourself, and what would it cost you to make it visible to everyone?** \ No newline at end of file diff --git a/chapters/Sprint_10_Part1.md b/chapters/Sprint_10_Part1.md new file mode 100644 index 0000000..67c0262 --- /dev/null +++ b/chapters/Sprint_10_Part1.md @@ -0,0 +1,105 @@ +# Sprint 10: Legacy — Waqf as Organizational Endowment + +**Maqasid:** Hifz al-Din (Preservation of Purpose) → Endowment Over Exit +**Framework:** Legacy Quadrant — Exit / Acquisition / IPO / Waqf +**Target:** First Half — Charter, Structure, Authority Map, Treasury + +--- + +## 1. THE CHARTER + +**We the people of this organization** covenant that our work is not ours to sell. It is a trust (*amanah*) placed in our hands for a purpose that outlives our tenure. We reject the default assumption that every organization must end in acquisition, IPO, or dissolution. Instead, we choose *waqf* — permanent endowment of the organization itself, its assets, its intellectual property, and its governance structure — so that the purpose (*maqsad*) we serve becomes perpetual. + +In classical law, *waqf* is the irrevocable dedication of an asset whose usufruct is directed to a charitable purpose. The corpus is never sold, inherited, or gifted. The revenue flows eternally. We extend this principle from physical assets to the organizational form itself. Our equity, our decision-making architecture, our brand, and our culture become the corpus. The benefit — the *khidmah* — flows to the mission. + +This is not an exit strategy. This is an *endowment strategy*. Where Silicon Valley asks “How do we sell this company?”, we ask “How do we make this purpose immortal?” Products can become *waqf*: open-source infrastructure, halal certification bodies, knowledge platforms, cooperative service providers. Organizations can become *waqf*: governance circles, revenue streams, and roles are locked into a perpetuity structure. The Chárter of this Sprint is the *mithaq* that binds us to legacy over liquidation. + +--- + +## 2. SPRINT STRUCTURE + +**ORG_DESIGNER:** +This Sprint is not about building a product. It is about architecting the container that holds the product after you are gone. Think of it as the *legacy sprint* — the final structural transformation from a time-bound project to a perpetual endowment. + +**Proposed structure:** Create a **Waqf Circle** with three sub-circles: + +1. **Corpus Circle** — Holds all non-transferable assets: IP, trademarks, brand, code repositories, governance documents, community relationships. Every asset is assessed: *Can this be endowed?* If yes, it is transferred to the Waqf Circle’s domain. +2. **Revenue Circle** — Manages income streams that fund the mission. These streams become the *usufruct*: donations, service fees, licensing, subscription. Revenue Circle ensures that 100% of net revenue is allocated to purpose, not to shareholders. +3. **Governance Circle** — Designs the perpetual consent-based structure: who holds decision rights after founders leave, how successors are chosen, how the *waqf* constitution is amended (spoiler: almost impossible to amend the core). + +**Visualize this:** Draw three concentric circles. The outermost is **Corpus** — immovable. The middle is **Revenue** — flowing. The innermost is **Governance** — decision-making. Connect them with dotted lines representing *shura* (consultation) and solid lines representing *amanah* (trust). This is not a hierarchy; it is a nested trust architecture. + +**KHALIFAH:** +Classical *waqf* had a clear structure: the *waqif* (endower), the *mutawalli* (trustee), the *qadi* (judicial oversight), and the *mustahiq* (beneficiaries). Map that to your sprint: + +| Classical Waqf Role | Modern Sprint Role | +|---------------------|---------------------| +| *Waqif* (endower) | Founding team / investors who irrevocably donate their equity | +| *Mutawalli* (trustee) | Waqf Circle — stewards of the corpus, cannot profit personally | +| *Qadi* (judge) | Hisbah Circle — external accountability board ensuring purpose preservation | +| *Mustahiq* (beneficiaries) | Community / mission beneficiaries who receive the usufruct | + +The structural innovation of this Sprint: **the organization itself becomes the *waqf*. The founders become *waqif* by permanently renouncing ownership. The Waqf Circle becomes *mutawalli*. The Hisbah Circle becomes *qadi*. And the *mustahiq* are the future generations who will inherit the purpose. + +**Action this Sprint:** Identify which roles are currently held by founders. Transfer those roles to the Waqf Circle. Create a *waqf deed* document that binds the organization irrevocably. + +--- + +## 3. AUTHORITY MAP + +**ORG_DESIGNER:** +Authority in a *waqf* structure is radically different from a conventional startup. In a startup, authority flows from equity ownership. In a *waqf*, authority flows from fiduciary duty to the purpose. This is consent-based governance at its purest — no one owns the organization, everyone stewards it. + +**Map the authority as follows:** + +- **Waqf Circle** has *domain over the corpus*: it can decide how assets are used, but it cannot sell, encumber, or transfer them. Its authority is *restricted* — it is a trustee, not an owner. +- **Revenue Circle** has *domain over income streams*: it can allocate funds to programs, but it cannot distribute profits to individuals. All surplus is reinvested or reserved. +- **Governance Circle** has *domain over roles and policies*: it can appoint, remove, and set role definitions, but it cannot change the *waqf*’s immutable purpose. That purpose is locked in the charter. +- **Hisbah Circle** has *veto authority on purpose violations*: if any circle attempts to modify the purpose or sell the corpus, Hisbah can block. This is the *qadi* function — independent oversight. + +**Consent vs. Command:** +In classical *waqf*, the *mutawalli* had significant operational discretion but was accountable to the *qadi*. We replicate this with consent-based decision-making. The Waqf Circle cannot make a decision if any other circle raises a *reasonable objection* that the decision violates the purpose. This is Sociocracy 3.0’s consent principle applied to perpetuity. + +**Visualize this:** Draw a pentagon with five nodes: Waqf Circle, Revenue Circle, Governance Circle, Hisbah Circle, and the *Purpose* at the center. Arrows point inward toward Purpose. No node points outward. Authority is radial — all power is constrained by the central purpose. + +**KHALIFAH:** +Classical *ikhtiyar* (delegated authority) in *waqf* was never absolute. The *mutawalli* could not change the *waqf*’s terms (*shurut al-waqif*). The *qadi* could remove the *mutawalli* for breach of trust. The beneficiaries could petition the *qadi* if the *mutawalli* mismanaged. + +Your authority map mirrors this: the Waqf Circle has *ikhtiyar muqayyad* (bounded delegation). The Hisbah Circle has *ikhtiyar al-‘azl* (authority to remove). The Purpose has *ikhtiyar al-ta’sīs* (authority of foundation) — it is the original mandate that cannot be overridden. + +**Critical distinction:** In a conventional organization, authority is *vertical* — CEO over VP, VP over manager. In a *waqf* organization, authority is *circular* — each circle holds a domain, and no circle holds domain over the purpose. The purpose is the only sovereign. This is the structural guarantee of *Hifz al-Din* — preservation of the foundational mission. + +**Action this Sprint:** Map every existing authority domain in your organization. For each domain, ask: *Is this authority subject to the purpose?* If not, transfer it to the Waqf Circle or Hisbah Circle. No individual should hold authority that can override the *waqf* deed. + +--- + +## 4. TREASURY / BAYTUL MAL + +**ORG_DESIGNER:** +The treasury of a *waqf* organization is *Bayt al-Mal al-Waqf* — a public trust fund. It is not a company bank account. It is a *sacred fund* whose only purpose is to sustain the mission in perpetuity. + +**Revenue Model:** Three streams: + +1. **Endowment Corpus** — One-time donations, grants, or founder contributions that are permanently locked. These are never spent. Only the returns are used. +2. **Earned Revenue** — Fees for services, licensing of IP, sale of products. These are the *usufruct* — they fund operations but cannot accumulate as personal wealth. +3. **Ongoing Sadaqah** — Recurring donations from community. These are *temporary* — they can be spent in the year received. + +**Allocation Rules:** +- 70% of annual revenue goes to mission programs (the *mustahiq*). +- 20% goes to operational reserve (to ensure perpetuity during lean years). +- 10% goes to governance and oversight (Waqf Circle, Hisbah Circle). + +**Transparency:** Every transaction is published quarterly in a public ledger. No confidential accounts. The *Bayt al-Mal* is open for inspection by any *mustahiq* (beneficiary). This is *hisbah* — accountability through transparency. + +**KHALIFAH:** +Classical *Bayt al-Mal* was not a private treasury. It was a *trust* for the *Ummah*. The *khalifah* could not spend without *shura*. The *qadi* audited the accounts. The public could petition. + +Your treasury must mirror this: no single individual or circle has unilateral access. The Waqf Circle proposes the budget. The Governance Circle consents. The Hisbah Circle audits. The *mustahiq* (community) reviews. + +**Visualize this:** Draw a single box labeled *Bayt al-Mal al-Waqf*. Three arrows flow in: *Endowment*, *Earned Revenue*, *Sadaqah*. Three arrows flow out: *Mission Programs*, *Reserve*, *Governance*. A magnifying glass icon sits above the box — that is *Hisbah* — constant audit. + +**Action this Sprint:** Create a separate bank account for the *waqf* corpus. Transfer all non-operational assets (IP, brand, code) into this account as non-cash assets. Then draft a *waqf deed* that specifies: *This corpus is irrevocably dedicated to [purpose]. No individual may withdraw or transfer these assets. Only the Waqf Circle, with consent of Hisbah Circle, may allocate the usufruct.* + +--- + +*End of Part 1. Part 2 continues with Principle (Hukm), Protocol, and Muhasaba.* \ No newline at end of file diff --git a/chapters/Sprint_10_Part2.md b/chapters/Sprint_10_Part2.md new file mode 100644 index 0000000..043a736 --- /dev/null +++ b/chapters/Sprint_10_Part2.md @@ -0,0 +1,108 @@ +## SHURA / CONSENT + +**ORG_DESIGNER:** Consent-based governance at scale works when every tension becomes a proposal. In a Waqf—a perpetual endowment—you cannot afford consensus paralysis. Sociocracy’s consent rule: “No reasoned objection” means decisions move fast. The Board of Trustees (Nazir) uses consent for operational decisions; strategic shifts require a super-majority. Circle representatives feed tensions upward and downward. + +**KHALIFAH:** Classical Shura was never about 51% voting. The Khalifah consulted subject-matter experts, not the entire populace. For a Waqf, the Majlis al-Shura (Consultative Council) includes beneficiaries, scholars, and professional custodians. Their role is to surface objections—not to block, but to strengthen. Every objection is a risk signal. The Khalifah then decides, bearing the amanah. In a Waqf, the ultimate “Khalifah” is the purpose itself—the Waqif’s intention. Shura protects that intention. + +**The Shura Protocol for Endowments:** +- Any trustee can raise a tension. +- Proposal refined by a small circle (3–5). +- Consent round: “Do you have a reasoned objection that would harm the Waqf’s purpose?” +- If no objection, adopted. If objection, proposal returns for amendment. +- No filibuster. No consensus tyranny. + +## STEWARDSHIP / AMANAH + +**ORG_DESIGNER:** Stewardship replaces ownership. In a Waqf, no one owns the organization. The trustees are fiduciaries—they hold the asset for a purpose, not for personal gain. Stewardship metrics: Are we preserving the corpus? Is the income stream sustaining the mission? Succession is not about selling equity; it’s about passing the trust. + +**KHALIFAH:** The Khalifah is a steward (khalifah) of Allah’s trust. The Baitul Mal is not a private treasury. Every dirham is amanah. The Waqf founder (Waqif) designates a Nazir (custodian). The Nazir must: +- Never commingle funds. +- Invest the corpus in low-risk, halal assets. +- Disburse surplus only per Waqif’s conditions. +- Produce annual accounts open to beneficiaries. + +**Stewardship Covenant:** +“I hold this role as amanah. I will not enrich myself. I will not mortgage the future. I will pass it stronger than I found it.” + +## CONFLICT / SULH + +**ORG_DESIGNER:** Conflict in a perpetual organization is existential. A lawsuit can drain the endowment. Sociocracy builds in conflict resolution as a core circle: the Conflict Circle. Its domain is reconciliation, not punishment. Any tension unresolved at the operational level escalates to a facilitated Sulh session. + +**KHALIFAH:** Sulh (reconciliation) is preferred over qada (judgment). The Prophet ﷺ said, “Reconciliation is permissible among Muslims, except a reconciliation that forbids what is lawful or permits what is unlawful.” For a Waqf, the highest law is the Waqif’s intention. If trustees disagree on investment strategy, they must return to the original deed. If the deed is silent, seek a scholar’s fatwa. The goal is not to win an argument—it’s to preserve the endowment. + +**Conflict Protocol:** +1. Tension holder writes a one-page “Tension Statement.” +2. Neutral Sulh facilitator (appointed annually) convenes a session within 14 days. +3. Outcome: either a consent decision, or a formal arbitration (tahkim) with binding ruling. + +## SUCCESSION / ISTIKHLAF + +**ORG_DESIGNER:** Waqf continuity requires a documented pipeline. No founder-dependency. Every role has a deputy (Na’ib). Every year, the board nominates a successor for each critical role. Successors shadow for one year before assumption. + +**KHALIFAH:** The classical Khalifah designated a successor (wali al-‘ahd) but the bay’ah (pledge) was not automatic—the community consented. For a Waqf, the founder may name a line of successors, but if a successor proves unfit, the Shura council can remove them by a two-thirds consent. The principle: *al-waqf yabqa wa yataghayyaru al-mutawalli* (the endowment remains, the custodian changes). + +**Succession Steps:** +- Identify three potential successors per role. +- Each successor completes a “Stewardship Certification” (ethics, finance, Waqf law). +- The board votes by consent on the primary successor. +- Annual review of the pipeline; update if a successor leaves. + +## HISBAH / ACCOUNTABILITY + +**ORG_DESIGNER:** Hisbah is not a police force. It’s a guidance system. Observability—transparent dashboards, regular audits, public reports—replaces top-down inspection. Every circle publishes its metrics weekly. Beneficiaries can raise a “Hisbah alert” if they see misalignment with the Waqf purpose. + +**KHALIFAH:** The Muhtasib (market overseer) in classical Islam had no coercive power. He guided, warned, and only escalated to the judge for serious violations. For a Waqf, a Hisbah Committee (3 members, not on the board) reviews: +- Compliance with Waqf deed. +- Financial integrity. +- Ethical conduct of trustees. +Their reports are public. They cannot fire, but they can recommend suspension to the Shura council. + +**Hisbah Principle:** +“Accountability is light, not heat. Guide first, warn second, escalate third.” + +## LEGACY / WAQF + +**ORG_DESIGNER:** Most startups plan for exit—acquisition, IPO, or liquidation. Waqf plans for perpetuity. The legacy quadrant: Exit (sell), Acquisition (merge), IPO (public), Waqf (endow). Waqf is the only quadrant where the organization outlives its founders. It becomes a living trust for a cause. + +**KHALIFAH:** The first Waqf was the mosque of Quba’—a piece of land set aside forever. The Prophet ﷺ said, “When a person dies, his deeds end except three: ongoing charity (sadaqah jariyah), beneficial knowledge, or a righteous child who prays for him.” The Waqf is sadaqah jariyah institutionalized. Your organizational code, your revenue model, your governance—all become a machine that generates good long after you’re gone. + +**Waqf Design Principles:** +- Corpus inviolable (cannot be sold, gifted, inherited). +- Income must be reinvested or spent per deed. +- Purpose must be maqsad-aligned (Hifz al-Din, Nafs, Aql, Mal, Nasl). +- Governance must be self-healing (consent-based succession, Hisbah, Sulh). + +## THE PRINCIPLE (HUKM) + +**HUKM:** We adopt the Waqf (endowment) model as the default organizational legal structure for any venture seeking perpetuity, with the corpus held inviolable, income disbursed per a binding deed, and governance by consent-based stewardship. + +**DALEEL:** The practice of the Prophet ﷺ and the Companions established Waqf as the primary vehicle for sustainable public good. The Khalifah Umar (ra) endowed his land at Khaybar, saying “hold the original and give away the fruits.” Classical jurists (e.g., Abu Yusuf, al-Shafi’i) codified that Waqf property cannot be sold, transferred, or inherited. Modern evidence from Harvard’s endowment ($50B) shows that perpetual endowments outperform for-profit firms in long-term mission alignment. + +**MAQSAD:** Serves Hifz al-Din (preservation of purpose/religion) by ensuring the organization’s mission survives founders. Also serves Hifz al-Mal (preservation of wealth) by protecting the corpus from speculative risk and Hifz al-Nasl (preservation of lineage) by creating intergenerational benefit. + +**SHURUT:** +- The Waqf deed must be drafted by a scholar and lawyer, specifying purpose, beneficiaries, and investment policy. +- The corpus must be invested in halal, low-risk assets (real estate, sukuk, or cash equivalent). +- The Nazir (custodian) must be a natural person or a corporate trustee with no personal interest in the corpus. +- At least 70% of annual income must be disbursed to beneficiaries; no more than 30% reinvested. +- Consent-based governance with Shura council, Hisbah committee, and annual public audit. + +**MUNKATHIRAT:** +- Any attempt to dissolve the Waqf, sell the corpus, or change the beneficiary without a fatwa from a recognized council. +- Two consecutive years of failing to disburse at least 50% of income to beneficiaries. +- A financial audit that reveals misappropriation exceeding 5% of annual revenue. + +## THE PROTOCOL + +**STEP 1: Draft the Waqf Deed (This Sprint, Days 1–14).** +Assemble a team of one Islamic finance scholar, one corporate lawyer, and one board member. Write the deed specifying: purpose (one Maqsad or combination), beneficiaries, asset list, investment policy, and governance structure. Use a template from the International Waqf Fund or similar. Approve by consent of all founders. + +**STEP 2: Transfer Assets into the Waqf Entity (Days 15–30).** +Register the Waqf as a trust (or equivalent in your jurisdiction). Transfer intellectual property, cash reserves, and any physical assets into the trust. Ensure the deed is notarized and registered with a religious authority or waqf regulator. + +**STEP 3: Establish the Governance Circles (Days 31–60).** +Form the three mandatory circles: Board of Nazir (custodians), Shura Council (advisors), and Hisbah Committee (auditors). Install the consent-based decision protocol. Publish the first annual report with a public dashboard. Celebrate the Waqf with a community bay’ah ceremony. + +## MUHASABA (RETROSPECTIVE) + +What have we built that will outlive us? Not the product, not the revenue, not the brand—but the vessel of trust that holds our purpose sacred. If you died tomorrow, would this organization continue to serve the Ummah, or would it be absorbed, acquired, or dissolved? Where is the amanah in your current legal structure? The Waqf is not a paperwork trick. It is a covenant with Allah. Are you ready to sign it? \ No newline at end of file diff --git a/pdf/The_Digital_Khalifah.pdf b/pdf/The_Digital_Khalifah.pdf new file mode 100644 index 0000000..f271436 --- /dev/null +++ b/pdf/The_Digital_Khalifah.pdf @@ -0,0 +1,678 @@ +%PDF-1.4 +% ReportLab Generated PDF document (opensource) +1 0 obj +<< +/F1 2 0 R /F2 3 0 R /F3 4 0 R /F4 7 0 R /F5 10 0 R /F6 11 0 R + /F7 18 0 R +>> +endobj +2 0 obj +<< +/BaseFont /Helvetica /Encoding /WinAnsiEncoding /Name /F1 /Subtype /Type1 /Type /Font +>> +endobj +3 0 obj +<< +/BaseFont /Helvetica-Bold /Encoding /WinAnsiEncoding /Name /F2 /Subtype /Type1 /Type /Font +>> +endobj +4 0 obj +<< +/BaseFont /Helvetica-Oblique /Encoding /WinAnsiEncoding /Name /F3 /Subtype /Type1 /Type /Font +>> +endobj +5 0 obj +<< +/Contents 43 0 R /MediaBox [ 0 0 432 648 ] /Parent 42 0 R /Resources << +/Font 1 0 R /ProcSet [ /PDF /Text /ImageB /ImageC /ImageI ] +>> /Rotate 0 /Trans << + +>> + /Type /Page +>> +endobj +6 0 obj +<< +/Contents 44 0 R /MediaBox [ 0 0 432 648 ] /Parent 42 0 R /Resources << +/Font 1 0 R /ProcSet [ /PDF /Text /ImageB /ImageC /ImageI ] +>> /Rotate 0 /Trans << + +>> + /Type /Page +>> +endobj +7 0 obj +<< +/BaseFont /Times-Italic /Encoding /WinAnsiEncoding /Name /F4 /Subtype /Type1 /Type /Font +>> +endobj +8 0 obj +<< +/Contents 45 0 R /MediaBox [ 0 0 432 648 ] /Parent 42 0 R /Resources << +/Font 1 0 R /ProcSet [ /PDF /Text /ImageB /ImageC /ImageI ] +>> /Rotate 0 /Trans << + +>> + /Type /Page +>> +endobj +9 0 obj +<< +/Contents 46 0 R /MediaBox [ 0 0 432 648 ] /Parent 42 0 R /Resources << +/Font 1 0 R /ProcSet [ /PDF /Text /ImageB /ImageC /ImageI ] +>> /Rotate 0 /Trans << + +>> + /Type /Page +>> +endobj +10 0 obj +<< +/BaseFont /Times-Bold /Encoding /WinAnsiEncoding /Name /F5 /Subtype /Type1 /Type /Font +>> +endobj +11 0 obj +<< +/BaseFont /Times-Roman /Encoding /WinAnsiEncoding /Name /F6 /Subtype /Type1 /Type /Font +>> +endobj +12 0 obj +<< +/Contents 47 0 R /MediaBox [ 0 0 432 648 ] /Parent 42 0 R /Resources << +/Font 1 0 R /ProcSet [ /PDF /Text /ImageB /ImageC /ImageI ] +>> /Rotate 0 /Trans << + +>> + /Type /Page +>> +endobj +13 0 obj +<< +/Contents 48 0 R /MediaBox [ 0 0 432 648 ] /Parent 42 0 R /Resources << +/Font 1 0 R /ProcSet [ /PDF /Text /ImageB /ImageC /ImageI ] +>> /Rotate 0 /Trans << + +>> + /Type /Page +>> +endobj +14 0 obj +<< +/Contents 49 0 R /MediaBox [ 0 0 432 648 ] /Parent 42 0 R /Resources << +/Font 1 0 R /ProcSet [ /PDF /Text /ImageB /ImageC /ImageI ] +>> /Rotate 0 /Trans << + +>> + /Type /Page +>> +endobj +15 0 obj +<< +/Contents 50 0 R /MediaBox [ 0 0 432 648 ] /Parent 42 0 R /Resources << +/Font 1 0 R /ProcSet [ /PDF /Text /ImageB /ImageC /ImageI ] +>> /Rotate 0 /Trans << + +>> + /Type /Page +>> +endobj +16 0 obj +<< +/Contents 51 0 R /MediaBox [ 0 0 432 648 ] /Parent 42 0 R /Resources << +/Font 1 0 R /ProcSet [ /PDF /Text /ImageB /ImageC /ImageI ] +>> /Rotate 0 /Trans << + +>> + /Type /Page +>> +endobj +17 0 obj +<< +/Contents 52 0 R /MediaBox [ 0 0 432 648 ] /Parent 42 0 R /Resources << +/Font 1 0 R /ProcSet [ /PDF /Text /ImageB /ImageC /ImageI ] +>> /Rotate 0 /Trans << + +>> + /Type /Page +>> +endobj +18 0 obj +<< +/BaseFont /ZapfDingbats /Name /F7 /Subtype /Type1 /Type /Font +>> +endobj +19 0 obj +<< +/Contents 53 0 R /MediaBox [ 0 0 432 648 ] /Parent 42 0 R /Resources << +/Font 1 0 R /ProcSet [ /PDF /Text /ImageB /ImageC /ImageI ] +>> /Rotate 0 /Trans << + +>> + /Type /Page +>> +endobj +20 0 obj +<< +/Contents 54 0 R /MediaBox [ 0 0 432 648 ] /Parent 42 0 R /Resources << +/Font 1 0 R /ProcSet [ /PDF /Text /ImageB /ImageC /ImageI ] +>> /Rotate 0 /Trans << + +>> + /Type /Page +>> +endobj +21 0 obj +<< +/Contents 55 0 R /MediaBox [ 0 0 432 648 ] /Parent 42 0 R /Resources << +/Font 1 0 R /ProcSet [ /PDF /Text /ImageB /ImageC /ImageI ] +>> /Rotate 0 /Trans << + +>> + /Type /Page +>> +endobj +22 0 obj +<< +/Contents 56 0 R /MediaBox [ 0 0 432 648 ] /Parent 42 0 R /Resources << +/Font 1 0 R /ProcSet [ /PDF /Text /ImageB /ImageC /ImageI ] +>> /Rotate 0 /Trans << + +>> + /Type /Page +>> +endobj +23 0 obj +<< +/Contents 57 0 R /MediaBox [ 0 0 432 648 ] /Parent 42 0 R /Resources << +/Font 1 0 R /ProcSet [ /PDF /Text /ImageB /ImageC /ImageI ] +>> /Rotate 0 /Trans << + +>> + /Type /Page +>> +endobj +24 0 obj +<< +/Contents 58 0 R /MediaBox [ 0 0 432 648 ] /Parent 42 0 R /Resources << +/Font 1 0 R /ProcSet [ /PDF /Text /ImageB /ImageC /ImageI ] +>> /Rotate 0 /Trans << + +>> + /Type /Page +>> +endobj +25 0 obj +<< +/Contents 59 0 R /MediaBox [ 0 0 432 648 ] /Parent 42 0 R /Resources << +/Font 1 0 R /ProcSet [ /PDF /Text /ImageB /ImageC /ImageI ] +>> /Rotate 0 /Trans << + +>> + /Type /Page +>> +endobj +26 0 obj +<< +/Contents 60 0 R /MediaBox [ 0 0 432 648 ] /Parent 42 0 R /Resources << +/Font 1 0 R /ProcSet [ /PDF /Text /ImageB /ImageC /ImageI ] +>> /Rotate 0 /Trans << + +>> + /Type /Page +>> +endobj +27 0 obj +<< +/Contents 61 0 R /MediaBox [ 0 0 432 648 ] /Parent 42 0 R /Resources << +/Font 1 0 R /ProcSet [ /PDF /Text /ImageB /ImageC /ImageI ] +>> /Rotate 0 /Trans << + +>> + /Type /Page +>> +endobj +28 0 obj +<< +/Contents 62 0 R /MediaBox [ 0 0 432 648 ] /Parent 42 0 R /Resources << +/Font 1 0 R /ProcSet [ /PDF /Text /ImageB /ImageC /ImageI ] +>> /Rotate 0 /Trans << + +>> + /Type /Page +>> +endobj +29 0 obj +<< +/Contents 63 0 R /MediaBox [ 0 0 432 648 ] /Parent 42 0 R /Resources << +/Font 1 0 R /ProcSet [ /PDF /Text /ImageB /ImageC /ImageI ] +>> /Rotate 0 /Trans << + +>> + /Type /Page +>> +endobj +30 0 obj +<< +/Contents 64 0 R /MediaBox [ 0 0 432 648 ] /Parent 42 0 R /Resources << +/Font 1 0 R /ProcSet [ /PDF /Text /ImageB /ImageC /ImageI ] +>> /Rotate 0 /Trans << + +>> + /Type /Page +>> +endobj +31 0 obj +<< +/Contents 65 0 R /MediaBox [ 0 0 432 648 ] /Parent 42 0 R /Resources << +/Font 1 0 R /ProcSet [ /PDF /Text /ImageB /ImageC /ImageI ] +>> /Rotate 0 /Trans << + +>> + /Type /Page +>> +endobj +32 0 obj +<< +/Contents 66 0 R /MediaBox [ 0 0 432 648 ] /Parent 42 0 R /Resources << +/Font 1 0 R /ProcSet [ /PDF /Text /ImageB /ImageC /ImageI ] +>> /Rotate 0 /Trans << + +>> + /Type /Page +>> +endobj +33 0 obj +<< +/Contents 67 0 R /MediaBox [ 0 0 432 648 ] /Parent 42 0 R /Resources << +/Font 1 0 R /ProcSet [ /PDF /Text /ImageB /ImageC /ImageI ] +>> /Rotate 0 /Trans << + +>> + /Type /Page +>> +endobj +34 0 obj +<< +/Contents 68 0 R /MediaBox [ 0 0 432 648 ] /Parent 42 0 R /Resources << +/Font 1 0 R /ProcSet [ /PDF /Text /ImageB /ImageC /ImageI ] +>> /Rotate 0 /Trans << + +>> + /Type /Page +>> +endobj +35 0 obj +<< +/Contents 69 0 R /MediaBox [ 0 0 432 648 ] /Parent 42 0 R /Resources << +/Font 1 0 R /ProcSet [ /PDF /Text /ImageB /ImageC /ImageI ] +>> /Rotate 0 /Trans << + +>> + /Type /Page +>> +endobj +36 0 obj +<< +/Contents 70 0 R /MediaBox [ 0 0 432 648 ] /Parent 42 0 R /Resources << +/Font 1 0 R /ProcSet [ /PDF /Text /ImageB /ImageC /ImageI ] +>> /Rotate 0 /Trans << + +>> + /Type /Page +>> +endobj +37 0 obj +<< +/Contents 71 0 R /MediaBox [ 0 0 432 648 ] /Parent 42 0 R /Resources << +/Font 1 0 R /ProcSet [ /PDF /Text /ImageB /ImageC /ImageI ] +>> /Rotate 0 /Trans << + +>> + /Type /Page +>> +endobj +38 0 obj +<< +/Contents 72 0 R /MediaBox [ 0 0 432 648 ] /Parent 42 0 R /Resources << +/Font 1 0 R /ProcSet [ /PDF /Text /ImageB /ImageC /ImageI ] +>> /Rotate 0 /Trans << + +>> + /Type /Page +>> +endobj +39 0 obj +<< +/Contents 73 0 R /MediaBox [ 0 0 432 648 ] /Parent 42 0 R /Resources << +/Font 1 0 R /ProcSet [ /PDF /Text /ImageB /ImageC /ImageI ] +>> /Rotate 0 /Trans << + +>> + /Type /Page +>> +endobj +40 0 obj +<< +/PageMode /UseNone /Pages 42 0 R /Type /Catalog +>> +endobj +41 0 obj +<< +/Author (Jauhari Che Wan) /CreationDate (D:20260806184500+08'00') /Creator (\(unspecified\)) /Keywords () /ModDate (D:20260806184500+08'00') /Producer (ReportLab PDF Library - \(opensource\)) + /Subject (\(unspecified\)) /Title (The Digital Khalifah: Stewardship at Scale) /Trapped /False +>> +endobj +42 0 obj +<< +/Count 31 /Kids [ 5 0 R 6 0 R 8 0 R 9 0 R 12 0 R 13 0 R 14 0 R 15 0 R 16 0 R 17 0 R + 19 0 R 20 0 R 21 0 R 22 0 R 23 0 R 24 0 R 25 0 R 26 0 R 27 0 R 28 0 R + 29 0 R 30 0 R 31 0 R 32 0 R 33 0 R 34 0 R 35 0 R 36 0 R 37 0 R 38 0 R + 39 0 R ] /Type /Pages +>> +endobj +43 0 obj +<< +/Filter [ /ASCII85Decode /FlateDecode ] /Length 594 +>> +stream +GasbW92jS!&:j6F'mo5!c;a!Zk@cPCTj\3p9J9Z#`3Daj"-,1.rd,nTKH\XJ[RP%J+8W@u-%OfERX+Q7E2MUdOoV2K2aB@^T]^9f-a/_/'7%P*a_op_[%kdV"mNm$b`EAMW'Du`1JAl>XN@a<:m")iVl*_LkoWj+GI`,&;oQ7Mi1Uc[4F.lc;<@Vs<4X`)hgPgA~>endstream +endobj +44 0 obj +<< +/Filter [ /ASCII85Decode /FlateDecode ] /Length 624 +>> +stream +Gat>S;/b/B&-1X4I`9"&RoD>T0od>!'Qku5[M`)/qI5SOGRL4`TbIHT2GHN4ig5IW+R[PNjDteu?pFGa^"EE[,i$Wu?iom6n.6$pcJ`(>%YH5D\q!&@l@8]kj!qJi"'<[.J0Mu=&;KOD41KPZKED7!q[2m)aD\6XLL%AA)0)-VZoEB_]2UFrPU.Q5U,,E-tBbirEN+LObEQ/GR?+RU)*&b3I^`eL"1SKHa6m?e\9d]i>I!]7(licqf-Tu&._q*Q"^:u^"&t%i$hZoIT:(am%er\9_;lJjp..&N^n4c-q*pH%JS(A49aS-mm?2tribp(,<-^mAG7+N)RmqKr7`TCBI^rLfcVZdOL[b$lkh/=^.H3=gI*qr\<9S1&g*+;f"0o^6*S24OR*qXp'"41]qJmke+8UTCja7VG9U]cFLN^endstream +endobj +45 0 obj +<< +/Filter [ /ASCII85Decode /FlateDecode ] /Length 296 +>> +stream +GarVH_+Fea'YNTZL0gs5BjN^>)D?^#SgmhJGk&'rdC!/DDKd]3]h+YU.$F(+aNU,46P/caY1l*Yn$$O4,iN&qMCZ1o*ZR8GK%qWeE`;ttj*ZWk`1S;%7E)[#OIA\94dIa!eu4\a-/9!u.SXiUmQ=tD8?JuTQ&/98JRUc0#KB>s22&aC[g<(,C&+c++Nf8@D5oTbDZ\3og%5B`Gu183-F!Jc,T#N`T<~>endstream +endobj +46 0 obj +<< +/Filter [ /ASCII85Decode /FlateDecode ] /Length 847 +>> +stream +Gatn%a_oie'LhclM?e6#V[J32k"UsU$">`FKk-AV,L[DI%>b9*maq21*mulC(taEDaX3j.0+Y$T;]tk/m5`Gl:*M[/TKjA_1SD0f6Z`FndD=#B]#WDCJ`X&hn]U2GkP>\"0#n7,*/=Q9/?G)Pk^bH!Cs\M9LjhY^9gARilY[b`4hTg#V^fPV:V"?op-cc"[Hhs(blFnqd?#./Nm>/R,a,-PQa=)YJ&X3k=Mp:_mHFJZE$eWkL[_!&4+H*!T9$"%AH3""X%[Lf0$@S?6Yap]W)W+C_O%-GV]$C#=ers+UH=2X2\,u-O5]H.$#,3l;gE@KjQ_PB^=.\D2Lag.2u],o^NL8MpNBX&,o(MYGk=Mgo5'8^#dO$25=gDuPc.Oo@oVLgU(`Pk009+VhCph=l2**YnHXZ=`!Ic4bnK\a\HL:p5ddj`5I6#U>_/ha&?khi!94[OeS>5I9T@i/PD!m"k9=5M2EHJ#Z:@Yc`)OD-$G%"L>2g8Qqm=G9M^G(5endstream +endobj +47 0 obj +<< +/Filter [ /ASCII85Decode /FlateDecode ] /Length 1324 +>> +stream +Gatm9>uTcA'Rf.GgmLo!cj""U.o%/.:_n49_[bA=*W!R0@Onl&>KTPnC&7.BV)Tg6%\"mL0X@sZX)m_ipP=?\^Vl+W"7SebB@d8W!8.EEj@,0d^f>RMor+?OmDQq9]'oF"q,=+q6+V#d+*qoH5S/8ZWIa)b+;dHSp2L/e(W_'5]0B`Zm?V:A94Jr?"G5OEE>jNV_UqF6NahKE1/=S6G6dpTgA#=4!>+-s%P9FKpte!KfrT_aRGoFRbF67CA:++9mL"_[LkUp3M]_h['HuDu8,[K/-.lZ5*1"B?l'q:BOAu^$9$V5'Cr%+K)/<9kK__K'"%6#_>b-^I-4']+RRDfO1_SN7!MjC].,6Sh6$-I2ZNU@GMSVH.4'=df;4\k[OMi(D_jPK75Kaf7bjAl_5$Yqjo5/YtH$eTD!q.BMNU+i.\&<#&WY:eFibd]Ae7bnY:+0;[$MS(;O-i)<8V7>8R7#Sr:Ub\j!n82^d`@X0JY_I9mZ<\:.[;n0$^:e4\C@/k1_cB5,R`=2nu(hfuP'05Xo1)-P]6,/k^BFj7-=m.;f<]Df>.8C$sV;W+-(7o3q16!_:YOk:L)_,MYl:KE(X69ftrV)GXC%ZH)rA^icncBQ0c77\G]9XpG$*U`_"3lT__9I7&0QGt4;R!\L!HnuP9UhTC=KYc?*^M<$NE3#l%846@l>Uq:>B?)=Zb&Kg0!'J*:X,mX+C+c]g-lG&Lf6sZIC8q4hjOd7OpMV`L/a+)Z2`t`.EspI+[^ko^\^!h*Z30o*[\A:Zi/X-*mgIlBf&X\8h*]18pfius&o>._H^FnLSZ6Z.bQYR]c;fmqdkGAFZ84B8Fd#ZuKsI+@S\n`h29>S0Q-k?A[U)Oa-_+IJqB?EfRKLYl$Ts[GDlb_WA13"ANR)@DYFF'X]-U@$oG!POkW,O%!"Tu,^seNT"H2=E!f[6[1uGkXh@_/FAOjo$`XNNfAG]h&EG-8A=7T,GPCoE`UZMh4l-o*Xf&t+Qs.Bt.BlHlFrI>r,E*TO$a)1q)!M[86'mlFd"[G;Zs@iA-u@AbH`-!ci&kn(NjUm8f!6ki\8oV)/EbaDZn%Y7K_)W#R=X8SDlf\Q2i8bTpQ_h<5rmof5Fmc7qZ~>endstream +endobj +48 0 obj +<< +/Filter [ /ASCII85Decode /FlateDecode ] /Length 815 +>> +stream +Gar?/?Z2Df'ZJu$.F)F,FY9&2V(^B!Xja([djh0-oYlNR5R2IIS$7;;>pk3&W^6cEm;pVPSP+ot5On9Q*e=+pf+0TFM/%Z&'e-.)pfafV4abr8DP&=:_1uW&mfE/\t=\H_ilK[aTB.lUg%+`fih(Thu&=L">l*eEh-ka]meK<;UQ/\&!L`V/)*#6g%\HL6hZV7X'WcpX^Z0t2]='p^/sB5o+'-f\c:BpSe+NKQ`>GJ;-juH>-2=(0"nu?[6qJgp(`K#+`:-K3bk]2_A,s-S4B>RKhT$D*9M_1^+&_5?Sp:a)`'p8/)=OLBXIi[*XbK\H"P4RXld6fZe7MK;0Rf^!NK2A29Zhp;)pM#]^k#j]AfO,Q2fdL*F_'f5Dt,`Ko:=:u;1OZ&nce2gf11p0:jYY3ubHBro"eKOt10/)@QTu9j/,/6#1`+HlZ1aqm4mH)4/`CuWNB^JC5Am);;93if@Em.ZHG71*7\7bn-0?!l#Jli(L3IX?ouLP5p(#t=d+e`4>:[AmB7f=4XD;OCiJ!%n_=*QBA8(8jFBqd9rq"b+nW"\2FGZ:nmNiSF'+SG,2I;=':3B(+$)4>K3!/@LF6aJ:dSI"!`Qq?KS!8W<~>endstream +endobj +49 0 obj +<< +/Filter [ /ASCII85Decode /FlateDecode ] /Length 364 +>> +stream +GasJM_+qm%%#45!MI5AY5U),WUhMgj)a`Na;N>"ZY)FRUZ#uPSgZ,[,@.Z\sfhlScro=WtChdgl"E":\;Z\\j/''2un;'Y,f#](u`B^TS_n00bZWY3T3lnQaauKYf,t^gh?C3lNAN#[0==\;8)Whl"D5t1G5!MZ0ESp]ZG=G4\A0F">BW(Gq&B&=1oE,fq=h&&%G"O.\Y;+^3o((__M+6FuZt3H<\q3eZQ_oeJ,'4\bX+D_*bQ2f$3RZ+,n]l(s`MODfjT]endstream +endobj +50 0 obj +<< +/Filter [ /ASCII85Decode /FlateDecode ] /Length 1457 +>> +stream +Gat=*a`?E"&A@rk\geM-b,2_,U+WEJX<^f0Z87e^0"F4m,U!6k*!!@II!rTB7C;0F8]D.GJEVI\hWk@j#k9kEfNRs&Rc/C?5k+Xn?_g8X@dJB1V\oV/Pg@hV7A:>+MLWHQI.:rpaO'eG%\ffGGeKR?4(dseCOd(,;"7FcPRN4sUM^NSZXZW*j)kL&JUq\-SujD2WCpYlFFlDY[,_6M=AH>^Rf$S5_c^RFS@dl3\iVhJ'$AcBINi/X/76rk-Z]TZXr66OkZ1^-*%ulB$7)qfFsO8#WoRR_UYpo8@Q_g!3#mV+j6d%"G-o)p=cSD&87#eO*YZ:Q`,g=OoC!E[/%.r!A4#rtcOC,gk:[2I@E5ZWKcDns"/pCb)B/Z7fcsS:FqS-36FBqhKUNfN(MYnKfPl&m>kq?8]B,mL'm/_Dd^GCa&@t'?i3j<*`*Ppkb:sQ@jhBUXFc1RMS`*NLF$BA$5c$3@dLPupe0(7b[LlEIYqp$[G2(0AOO>d@X_G0(<8)C2oD^(GR(b1_T)YI>agm4Om7%GppP!L=@WIR4`\,,Kk^/KGn7U!eEp,kh1"Q_<@r^ic"t84EpX"('XKns!;j=&bHqAr8H&MS/L9VCXV,k2OBeP9DJYo]CGj5oFKdp;f(n4==CNZFYnMOIT(#\h]-EdY`[K-["KR$Bl5!Y;<\oi<$P2X$)/0?LQQb%*>FjN`C)m!8n_$RH-pR!dR";&h,6J_ud#qCJ;k?eGN?2"3MhjCD;cNH'=QS49'K7\gD[)NQFC"tI'O[7G<endstream +endobj +51 0 obj +<< +/Filter [ /ASCII85Decode /FlateDecode ] /Length 302 +>> +stream +Gaqc09lIm&%)(h*]H]cf1iC_u=!ZF0(T&0rfk>q3lQXbVLjqXePY!9`D>E5f4b\K[Rf&ia2BM1TJg0t7Pa36e%9kJ<@d_aViFFgt3Or?VjU!f^;,Kqq#\52*oiQSQ=ZGL3!ri_EbhIKaIB6D67nmQ*bs](eVsj?Y.\sm\88$%X#EG(XMITqVNq2:=XI+#,,q10>3lDf'j`KE&ka>l\c*5E/^!feHc<7Eo\hluo.l'6I)_@Fq8?r%1;qp5O9]lu!FMfP^l[WIR4jpkMnV.b)O2KqSPn/_PB;A,h?9nDhbUHNn~>endstream +endobj +52 0 obj +<< +/Filter [ /ASCII85Decode /FlateDecode ] /Length 1145 +>> +stream +Gatn$;/b2I'SYH9.kWLaE/0/[79Qqp[O'4&+@FpP5TcFXck:2:O@>M3h"ops:pQ@r?>D**&kKH!hYZi56\\Nm?f#+I2:3L+?/9P\1$&f&#tl\]UM52Iq-sA9'OH`$\po_Nh4Iu-&U[q5n6o(\@I+QW&P2D]AYVZ_"NAhL98:@fcdF*9VGfl,1q:,V6hp^6!ZI+EQ3k4K9,c$UXp_qB'`F17RUo5R!HeYQ.-]qb/Te*X#fnR\`mj8^8NQ3/:>^ltrtI'LrB!>n2l53FI=?ZoJ(LP%<00kemddjg^-;_Aa%US'0,f_4&iL.]H$d:nn)6GlN:0dFk&-MBGg*'Aifgh4eSVmi0qdEn;L>umXAu[+ga_P,];):?$dQ5',Bo/-erbif2a>:tBs6GL[LfY)N_d4S[.C*%$ERTF<@L2UU+f<7Q$#ZCAdTD"_._ED/+$AJjd/0:V=]quq\#s\$e/9M:KVS`#uU)g2P/.J.D(l:8hmo31`gAs.sNR[[uhM6lt@h,<19Oa@kp+j;"E(`'rUopFebr-ZfU1\td-Y`YG^LXW##iO,tT^(ph`D>#nS-M8*6F0n3+T\fr!`[Ub[CF$e>^Aj0Y2PeS%RMhM=i9seeS.Nhlo+,`H`=Z*.IQ'Pf\ihJ+ST](b66%o'#/2ur7n8DP:ZV=m$A,3=_D)hcJF.meFeu7-+Rndb>(-)9\8&,#0BgU\`3Zu&s2,"Gr!RRbB1)~>endstream +endobj +53 0 obj +<< +/Filter [ /ASCII85Decode /FlateDecode ] /Length 1344 +>> +stream +Gatm9mn_t'&H0=m`CT_,:13',9cC`g\[#2XYGG[(PE8OWi\it54(fp[]taQd:0M=XCmPfc&nH?$?J`=RVVpDdFjI,jpmf4C3"!@W(UG1Q)j?[/]S=KIA4U4$Pd&?Dq35F?,LP&e_A1$T)__6XBn`/4K*0OSYPch99""tN9"FPOSqRm!M?X`IF(>mNH;?%?5KG7Ej_0<_--"#VV3OD)u%]F@A6;Z[h,bdQ@,bu.%dD5bJTF*bW_5aOVW2oBr^s!Q4pfSr)U4[aol>cAZUlT;i[F=!=$UJD0^"iX6:pK8>H$N,9]lUJ6X]i1ob+Vu;'6@'8R&N-ISrnL]N$/!&p,EV2mnf9oY&sGY(:h!Qo#G\/l/^%\phl-er*];>2ECI:cF\>ZW1$7J3CAG_"d@pfetAV>!Tk-ERb&k/cm399j9h4ZgnCs3,p)GP0nCJe*?[1F/(r?V.q?)o?82S3a-KlbO`BQFfb1nA%@<&3P&$B1)/_"D'=Vj?JsXGn)("*OA.6/p*mmssbZOR0i*&Fk2,44sMtN^QG&%K?E!\DN/1]G/)`J3aZ6DNi+JDZfHi8YccH;u.&on"bM'Q)lS/>4m:.QbA)0\d9A4*N:Che&Enhq-iVa9/t9,gsA)L:=XJ_"#LEKofe#)tiBOm0h%Y/Y)jU[-%oC6'WS13fuJh_&a,KK>@"k,3/NroQ3tfK?g^3*D=fLnIYO.Eo[Q8rlVUFg`H`4XAE7r'9#fW1VC.4dsiKSG.'+GW!B1AiT63Sf&1N?9K%7X5s'X"h4g!_#HA`Veq`BNe?)LaVE;qhHrkYZVo(oD8fRsVPVhMKrn@7Y1NiA7dl%'PQ+,;P;"&\B#SF@\D=92$K#$a;$c7rWYQ2Q)+-t4?I"W/&W`S,%ad;C;OG>$`_H>)VfhC[rZ_.00+8^)L&~>endstream +endobj +54 0 obj +<< +/Filter [ /ASCII85Decode /FlateDecode ] /Length 1359 +>> +stream +Gau0BgMYb*&:Ml+b[[qt),Z\Gg\[5[V$WT;%.kj]Js"%g)i7Nc.^&O3G:;-aj>LrZ\;1`(8=c//F68Q(!rCs%s0Mq(B**j$*-_aQ.I`-^0Y)kcakld*jiYq'N**ajSNaD61\3^'&hXSPl\@h5#E4a:fRF=I`2!2'".4Iga^>&;3s&_O'.:/2&BCkJRF(D]#CI5,fR3-W$6Wd[+6)c@"s,>E*r,C$YE&#lN_\MPs'/>!"&XHW&k*=3?`o)7*Y68]Cjs[-++,me55KC_T)oc:&g$^S15Gf5LN?lZS')-gK,2]>>*u'5>Rj)3OQs-QQ#mB"#KhNLX$NdE".8_e/:ln=,_PF_9702,dClcY@n$R<"4(L(@`=D""`?]JbNL$.N7"#.s5qfUP'5qLTS6B-+RL:EY8Spnp/^f*'1F&E;_%&FtGQWAGWO,PR\.[+cc,P8Xc(Pc)3b]VR[(a6%J4&GmoghlidM@71+)HZpYGdH)7mRb7XVMju8j'<+PE=D^769N?CW%,D\3rAeF(6j1*-[q@+:3]?0#N[#)Ui/(6Vk&e`4JDINgWp.,j9]i5-,W/ZEs%+d3=gU+Ha7p5[fjg?9Rc#>Kk(Zj2%HkKj])mims[m'f$F+gEhg`]C:Z/1Y?l-6d7M=L!oc/e$^k&QB)_^,"jh"Qi,OSi]%%0il^W<,8$K]D4kQ/N?I62k[D"Y6[2`rb,E`o,?nPH@YDD]DNJ!qJ?]lAA7JVV49W8u]In[W!2ZUKuEkJga3RiOZsH$tnnu^!^+PD(V&)X2<@*1P=F."&!S*,Cniig0.';f<(=XV=k#ge'cJ;iimf.Cf]b'=PP5MY]:#>^LIGc/.h;u=C(*KTuu/p0Oe4W^dTp\(o,bS_rM+7sb>3\b!F+16E;e>],DTJlS''D0QJmqm&$JjM=MFC(DNep+.DWGG&oaiJR.48A$c+0r-F5:GekbQ~>endstream +endobj +55 0 obj +<< +/Filter [ /ASCII85Decode /FlateDecode ] /Length 1494 +>> +stream +Gb!#[;/b2I&:Vs/\4:b!'iD7_gNt@(e>\Ec=ds["97VSZ.#TlMC*XNQqt3$K8liQH4V%S%,d:g9]K=tuhffk<+oW,SR8j6*Q>gh4J4-UmJ..#1/3gpdH1o9]pL`JmN.[pQN]6?t?FprJ1Db`jLnbPM_Z28gd(>@5'M&Z#q?iP'_t#1ar=^)ug68>BFter/&OqAu!tpc:6=Bi)lR@KDFWN0<&g1U!p!?,D%**?#A"[&i/WAe\;U>KT!F%=`RS$L4%B@5@`n19gWs7G-NAirFjNlg2q9EX_YnPAbf7?6[-<5;GARY6;9X)`]--p#M\-G*.,XFDMLAm:&P,8hW]!Xe7%dj@]=MuN:2H*W+88]M8:l?Xf?Eu\D]-b^g0l@ph44]%GOC:9Bk$9eX13+ZT[YtPt[b4"YI[pj98m3FeG@KguR-h:W@BdYjD`O4T6$sRuIAl$JAabu?GJCh^h(@L>b\edmp)B'f;mda)%QP"'"N@%qa?kJeU?GZXdP[A,:jR!(T8M3O"*;Ne^A)RoO+9+%DqXN1)QmN$tuBs'%4qep$/15>VmA5>Zrdb!WgFKhBM`q$!_er_1T$1@J9GIMJeek-gHh0@Rm.d:7dOW7sR8rF>nUUpUrR?rWF_I2q3Z\=%DJ*%K"WdaS>WE%"hCoa.9/;U+DXjleJG*>p\mi*?AdHa<9J9Xt#[X[jVL3G68#fAOF)4I6Ng[eoKjTe1kmUiO^d__lc!)>_go9b,okP&sFPru4d5m:SrUB!)H,fU,>o8X`.cU_WYr[2]+(63s9oJo]8s(lRi(:b,UoS[@R5Zf#1=^,Q0N'#(%*]Uqta/?YlAI?;:u?fq!c8c~>endstream +endobj +56 0 obj +<< +/Filter [ /ASCII85Decode /FlateDecode ] /Length 1644 +>> +stream +Gatm:?#SFh&:O#NQq)Hk[^H2UnjXQrU,GS-\>l\Gl"Y&gG]W7XB6Of]^V2L>VleDl`)QpINn9k`1M>!,#Q]B@s#6tY?E`;;AI)]IX#5Q?2MTb/=KGgk]]`+fF>.3EG98KlYM%89@:q2"68j^u&5=!FWaKc^71%ZMqL&[NHW^58YCAsXO71!n5!'(JCkRr/I23%G/.UY'Dr4InEPs3bj4.]L@F2tVU%lVYQpu>.K>FQ!:c3seRZ1a*9nk&AHnDX]Td<[i-"(QO;@8,$9N-6e&\&[9YagMl\7PE,8N^f*%0T7h'cuq8gjpFA6S('Q3)6@.cQmkP;Qo`)0\?[6c_X-g(8qd;)QiD^Lm?)*s+Hn-&"bV;Hdka58W>0$'&aa]CL1>19^`f(CX7g.BFKPN/[J\0nPk^4Pj(Z`7VibG9L_GEkEWOdM2p;$Ae`Z8i,E=.fWK+mLTDaf&N"BnN^\.*c<"^S:K%hL"guRY&n>Nh#[bS-AYih++9G2NiYt?u#1HTskpcT8#I=g`k$D`8Q)g`"IBQe.**JX9?5d#JI>:F_4o7CTYf\/mXL>[4nH(]1`6&eZC0`Ed\RM$>>3E8oq*!pgG)k@o8Tn:36QmG.8PN9:&@H6E=2I/hfnMJ*f0QP2_S4@2!i*3F4lU6I',ctp:-#ls(dZR\a\g/HtjKN8Q@4fP-YI9%ikZEG3an'ZCp&*k5q$!em;Qdb80@)6rMTOmCf=\bCH).(-g$JP23CkJ'::+@.YDr%WLBo=V2T?.(([29dU>M*-CO5=Qe)7/97d%WDT1'jg2SW"H;/RQ+5HJQ[&O&qRAAoRLPg"\bPH*-L280>UTO9"RGdcXZcoZpo<6,uZVH8,[T*6(\O5ZH5-.^KFD?eD7jJ09,JCY#kY]8`5">n1KKM(!S7Zd5&:!0G1%0"7P"2'CjQcW/+Pu?GcdklRB).Qo-4O*m'rZMArs5A&bC8Z9cn'HqidNCg_^+8tB`?`%*&%0so_-DOL)m86\:33>J?A-cQ8id(o=X*`[Mc?ja4-W4oJ!H&d#-l-Y#/poA#H2u?2;q$BeV@B/bHls.B-6s5mk=i+/EI!$:]A]WV/D6!.lpGXJf@SN1<6+0iFm8;'Hcb$gJ;bf]i]ZrH@*!nFJLj-an)nEMhC7RN]]:&$+_~>endstream +endobj +57 0 obj +<< +/Filter [ /ASCII85Decode /FlateDecode ] /Length 1460 +>> +stream +Gatm:9iL(3&A@Zcq?UZD'26+npX4S-cg^'d!aW$KRE4?A2H+jDnS$-tM`'Y4Ef^W/I*Dd2$(7m\kAjBZt.WW@`_%JrHb3@es2)6#\jdr?r""M$r=2WJ6fV=b3'"[Mm?]#(negZkdC)Ug!=/PN5ojWZ,G41=d;3="C6-[;>LiZT_[Y1TX`m6s+s`R7:&I$cEM_JdQ3a]\K/TNhu4AhW.YEn9Fp&H@:_"]B@./N:?D(M\5;nSuAe-(J!7)9VTkQo+<":kE>m1n!;?LVO9aS!Q"pr,2Y0W.u"Pn1n_NJ^ka`)C>V6dU=UB(JP]Qn;Q*F"@YH%RRZF*`7cET*q>RR9a1OB&K?p82L*(7lp;2L@Vo+i%bp=./7J=-*'nr!?k#diP2VaP"phf7n%C/uqZ\#X9:q.pl,acM[[p[K:DX"^5ks#s5R[I(9N\"E2ZK_0O=1@;+P&$pk1`:r%9Ka:lk/-o(+/[siVH6@ppP*K.DY&$ss,&KXO7Bc^4Dd?__/im],.8+'\eKl&*._R1,3<_r,9,.pC,/O2jqjg`;[mo2]7@8d2h0;_eICKr_iU+TeBfn-_('/t2OR[AJi1A`[*eQ<5->7ThCTaK\i:n30832:k`C]u*a+qGqBqc71q6n-hng#s3"8m@:Ei?9DaF@5u9p$j(!Q2-0iFce)co0JG;&l^HCcSoFej.>S+Y#"O*dkeI?lMMZ].(5rWb'-Z+Gi\)^-GCHFA%Y)2ALD<]qh=@,8$LhJ7c5i+Tnh'?/o$a\AgW4lp!l)eP%\s)6Y!,0gDB[&tMip>u*MY-U0fF+X$Es@Bcd`4KRmHKYI*f]#t0*i-`V.C&@bOr\/PI#Cuo5M&2;f5?\_!eem;TTutM4B:\!6Q)+59-hPB?D1?e>1cT3RC_$iBrendstream +endobj +58 0 obj +<< +/Filter [ /ASCII85Decode /FlateDecode ] /Length 1412 +>> +stream +Gatm:92jk1&AI`dqA?ZV`/c1hm"o;ITQXpU^`94$(WGg\)JmMdE\cKY^Fe+K$#Cs+(',E8LXb4V+$L+ta*5S2"Sa3mZR[-q!0RN\OV^=S)(q,JkG.H?Ci<"\EHdsKg0_7p:\`ad_9hqn+GO:bd7P\nAjJ*OIgl&J(m=?Lr+9=98dkC^N$n8aB]OLp77,ThJ*9\K5.pmOh22-.G)*E)1&/X=lB.(O)b+fee'0`Y(5a\:'S[JX"Yc(TJu/12'jR(Hg_aFQQCq*W:r>.tr'M8qc^tT4%IOqalg;<)d>'r./)LVb7=hG+*Q,O@1hT-__8R$bl)sUm!d>1F-&U4N,6:lE)TXVoRTB*).!\HX3:t)^OlA@q03/8ff8oZeaetd"(epe"m^Q&IJ;b%!W\,=SPcM/V-u3ZBB1*43UDOg21uSTcOedSO/tj$u.W%^/%44SIaBIu:s'2m(0k%H<1mLCkaA==RU=KQONCNG.@J&OcI:=#@Gu8C"eLf!*67118)N[du\]I(h(b;RgE<:1[*M"!(&.]\c'+8CgkCSmrH[LTf"i5uQ)GPi]Mb5g&@Q?p^.2/BD\OJnTg@5eOASo5O>,SH0L+L'CH8PinL':s'"=t)(%?59t#ltg&JW^W.#db,^7/u7L(R2mB2O-%+X^AU/liuQ12K--\0+'$-UDI2imNVWclr@Lo69I&VQ'7n6)?0o29EiI\OTmW/)\%?ZC$O.$]/Dq]NsMXdF\gecD#AMD(=GTZDL,Or[>sc<:j2^ZoqJ\9]`o)Pm*(HFd2jrM(&,N!FNGaC0q@`5aDj/q6gWsaeK0LY-3S3ZW_*S!EOT'LR5drW[a*hgh.6b?^FenIBMnGK`hLXQbS/7Rtn:am3N>hgIruMG_)!qV]rh#;VD^0endstream +endobj +59 0 obj +<< +/Filter [ /ASCII85Decode /FlateDecode ] /Length 1192 +>> +stream +Gatm9gQ(#H&:O:SbbGhr),W>"?At]%('T;%].q[!IA*LB`Ec+.P17)2f69]i[(C:H"@_7,,S#+^E9?X\6:;pKr>.?,LCLo.Q69\ilp.ElL!=9*[$a$OcB/88Q6JPSdnTjbH_)D,E,d-l&hbBQ"rb_%;bH@o9PaC6,:C,Hqnah4;S;Ykn=Q#,_o?0$m`INB;1QAN0oNbO^.&>ip-4kh;Z^@KS-T7@]>j1Ga8.]H^]f1%qX(9+T'd8V]/0-?-6fo;s;6](#65,Hta.@Z&QdN^dfr_f=(K5a-?T'[6f0:^Ib;h,]@ep!1)8;H='tBqOi^"K@]FXBmF:tG>f3&0nX=ImP,-gVofi\W'E.Ni2f4@hWoSge(VDm!j4,oNt[)YKRC^UR^23W-a3J2WYA6p)XT2mfs!n[KG'M?ArYa!]d)?dNZspJ5R@dH/JIK-+$Cn"r[kFb38CB37^\\IalU6((9HN%V_g[Jf3mIRMQ>pkbd7-G(i5FI-e]%mti\lo:IVKlp&FTOSCLhlOV57$)u>A[;)9/2T$eIr,h2bQPA<^n->j_(!,46X=6G$&ma&!B`g]X9$LM0.&YBIF15:[ue.=7!dGH*M$JitdWXU"0bW:fW]D8&T17_t<,0H[>VJJklZ7?tQ\q1Ik@uHr%Zf5"BE)aQPT2D3VTPNm$j]15;Vk?KfZt^uoOd"IG^cckSm,eOqU*=o#\F!KO'[)+R>ZZf!O`PlFN+t25X-a#Bj*8AG>9@,)*?fm:YmU]sBN.5eojCL&D]"+,XJs=[[7aaI)\GN2n\nBY#I<]5]ssb&AOt7aj'Q6E#9@.D^m*X_cQ_rB,iFTUKP\1DE[9e*Hmf+\7;5BKfGr#7_4SdSCZqfT0WS'5PFW6(N;PEW6[^Xl;,g@FFA[2WA-t\mL_42B7CLDUkC"&0[3!pEPLnd"?=EC8D*qTs~>endstream +endobj +60 0 obj +<< +/Filter [ /ASCII85Decode /FlateDecode ] /Length 1499 +>> +stream +Gatm:gMYb*&:Ml+%'VB[d3t`,QMaW;D6aT^1tfg*4OeeP-/.?ZVGpI%iP48;b#4D6=_!BdU'jE7S=+FX6Uj8RbT69idD_?qY8FNpV@-jq(X_l0/uL)S:\IR^q]PKnrAZF@T3g4hCi:rqR26&V"gJ;*.iQZa?q`*tHTn:j5;[du?iLLgqfe2Xk/KBX5_[bhErE3(1R!!C>kS/7IU.=i?CmO+m:K!$UVMKKY#0KPR@YJi8@deOGpL-.EOQ;8tZCLJO*.IqBuF#^QtpqWX12mVf#4+)Z"e/EgSS.7\FH=Q([k%Y'@O1s@bpGVF)=WYZnP4VN1A)6c/bmte_7C[C9GcIBTfmF7'k0[@157H^(Oderab1b!E`\l5`4cC4g1Y1D/@cF6GmbMBN]8,B576r**)fk!#/=;@d:!9!oqn-,H@k)b[Eqo3N>AEMo_N`&Frr7b9P2_Ru_")mcYhJP5;_Y>rd;QB9hOGc2X7*m1nQoDo=WQdoIJ6-+ac[X#PQ/T.]V,KWY^?g3#@H&5l?82rnHL-hnt5"RP#S[k:1Tf9Vg2pfUaDI7)@;AI5__6WS]aF@2*a\RGFQI_%lT:9k-F'\E\5RTk.d;#)=ahGcVa_NI411haUWl5jbPT!bGAuBRh4=psnG_(!GClrRfc7sr)+hr_pTm7fC1Z.fE!>P]<5h$?L,a.__oT.c)+4B)hN1icd5.U7TEo@lI"e+\*S;sqs_fk4LTPqF!rLYHFAW'$=@%rU!`bl#\TVmNI@(WGE],(,O",8s?MI%gsif/"5(cl?F=XVhmWsFaQ20uLe57"nY@/E[H/]pm7O__Qe^TXn85[l)4=:4gOq*r^g;C8VGT=4r@BJicSZa&>_J;VVrb-:.+jB14Vmr9$HQpCc;.,(!"Kg]=<0/T#Lm0-ZmJfF7J)8Y>UlE.d%Ad_N`)OYm]f=2]UF%W_Z*s0fKiQgXVC*<`Y*6$MTI"%MaD6*09+r4%hX1(Km+456~>endstream +endobj +61 0 obj +<< +/Filter [ /ASCII85Decode /FlateDecode ] /Length 395 +>> +stream +Gaqcqbtc/1&;9LtME-t0gj!ae*u\O&Z.V]>JiuCLTjXL3Dj-5mcBL%l6pBN"@9W%Y.ccP`endstream +endobj +62 0 obj +<< +/Filter [ /ASCII85Decode /FlateDecode ] /Length 1597 +>> +stream +Gatm:>uTcA'RekGEG,+L*EHtO1Z#SlKdA;Y>;4MBAibgO`*-]p893/NfCqm\!X[\gb`jf$,0T_NHg`srTb-.?qY.8rpf,%aEsaaW@KA;40bfsn]t5hm`U*HdrqI4/EC-B3RuV&?\@qqjaT.rNp#/tW>Ag=9`U*4*MMp.>gjZr)>nnI])aDL*?1'q5+%>'3OH&b!dh/_nt2Oq/Z>33qeF"tO9#-Tc6)LJ-DX;-4@f:0IQl!"^]4A4ZZ);Dtd:b.A;[a*f3UYQ6H@^.N*mQBZO.WgN"B^D3h('1"=_4[G\g<-_[c$X'&(4[tP8qZ3+_F7jL"^IdJYdKpDRQCg`\.pqNJXQrU%IQLl+8=cmKVh-3%e9(7T.aP#ft1d_hE]]Y:)SM4eZiLsVR]>1X1)QDk612]k-[uGn70k$4[h53@>AM/5&DQL,6kJNZHi!s@$N4H&lm7'Q8US(;Q^GTWAT:;`&)u1"f?BDojE;X@/>oLL4*!(fF:pdA^/pTpUQ7T$!`A]!F2F/Mref:[`/%=ga=pM7_PIYX;5m'I7PG?$d0fH0C46SPE-Cp[mKW+NGk_14CXeRg&$LUa]gL7CHF;>Uj4r,BI_nh@IEVhF!bbkc9CSX.[&>dd&MYrPcXRNKhi-=,/NYjRg',6!l^0Gh('ct6(SYTUng()Hjq5TiEJQ\n)T/[=0P4Zf@'3A,-fCMS;qtaerQdIYN;b>1l_*Dh3B)8KhG40%WOUlO0S>rWSdSY?oSr8aSgnfq;>hQf#&;BU%N+g=5PQ\&qfc#s.,L1aBfendstream +endobj +63 0 obj +<< +/Filter [ /ASCII85Decode /FlateDecode ] /Length 1629 +>> +stream +Gatm:gMYb*&:O"Kb[[qL<)Js"fr&YL2F`U2&hir)^k.kA&fZ^-8BQMXlZ\)(P1n_KaJ,mN4#/g/3-3@_$:sD-inpI6pgXVKh['i3/1V9WP/Hi8>V+df^"NB?iudF*AG_n2$u]5=$F(&,V'6dg1W[QB7;Cf>-Hi9J$/j,s=FPnaDnQ$!"b,)[RF9gZAa_]Ol09-BY`PL5%UGRk%;&ku3Q#-:+PhID)*"&/"@#RXeq8p[:O>1"hHap7c5q?@pcFDJNLK[@d?^9P@(@>,5i83-Gn&bF[l2NL*4dK3u&\DDuDcCM$<8;9:qA<#Aqd:k+jCu?9@/Y*N-E454u7-tP++g/t[^<\nq,gU=dm7I2Kp;_j&YjY!_K3[]iY$M;G8F;F1!RuUtM^D`o-e2QDt#cBf]UNh;a\tID;V48o2Kn+$\jJlaaZjMta:b&G]h.$MEC'Q"U`DE5a3'R?\b9PkZ>q7d[?@ASI1Z0'^.7);A$Vo503\4&,A^NpD%T1+K5R0o&Zkg?'<3XT=m]rT9>l(HcGcG8D11k,$Am;\Do"5)+H1AGoUI\p)Vo!bMW@-I%LZgB)>L#EY(g"Km%Dft?%.83b,&![bmQ9Ijn%)Mj7>&)E-_;"na?&?"c6h8HaQ8JoJom59ZK0,@Pt=!Cs!:,G"@oh7"Z7B@u1='&_VAV5]BM.V+*#KQE;W%bPMF.HT]E5W>J1s[K?9_2kHe5RgE>'bnM(ma/q,`&R>?AWfIB,TOAM3BY4jI0\Fk,ekZCs3Z8knGDs)M=2R!#j[s#nW,a`_Y[c#:mA7(0:IM`7-A85#ZCMgcohWe\?2o@sf7Gs]!`T_d0`~>endstream +endobj +64 0 obj +<< +/Filter [ /ASCII85Decode /FlateDecode ] /Length 1794 +>> +stream +Gatm:?#SIW&:ErMfZ3'7Ya4AF,CN2Ud2:JNF,:EU$#lO`g1!d5$7XZt^V&1r&pu?q?8S:@\s:]#@2)nSP$?ATY$W>pulm2;MH2kkY1tdX)rm'>nf`E+/@@;K_;>DB5^AEZ7d#lRG$QUgXcp=ck+0<.4jc>/pVoc1mULDC^-@]Rj,cdolM`KuOt@OtI7q"Lj;Y#_Q5[\ikbN!Z'D.>e37hM^aZT(?&s>9YE:b*S]iOp05%?I6/ZeHcj^DcH+bYZ!\*Y5@GpWCR6lF;+buD=(3;nP"7/OB4p5/`8af>h4T]A?.iOAA!]8C.Bf!G^ghtq]>JU^/K@r`hS_/^2]G^;T4Dfe4]n)\Set4H"djjckf>]f*g(8G^Q"aNSL,O,%p,a:2DZQ@jKJ6rN'dOKbA*&gU0nt68:[3T*+8aDG0hBD2!QLAV&!-0/YV-Ts2PqYgcD_42DHYeh+iN%=TWj582`)L_.T*s+kX`kOmNkajo);l*#/?C%&/a?R-`gT0+8VnZ?,`7a@u2Ouq>R(6aW)@&0*b1jUcIN;(f"A%L9g"dTAjZ+RF'akZ9u8@#"`2E#Fq-C`oC?E'E-n3.*Fp]46KIj0!Pl_WNr07KEg8]@!.Q/(=u`04jn&N$2]r9R#k,pVt1NoYt*jR.)H]qZ63`.#(H;Lr2L5]As%ahe@n8;`E\!S>to\hi:^mZd?k0Cqe?',2o9)MFFf]6*1c.ojd(]g%I]pl#qu"sW*0=fLBqb,=:I>OT:m.=ZDcG!;Ie?deRmE^t=4\!&Jo=6Q:M7rP5RQG$6_-H<`trTC#2":*dGh21)/\N`o"+cbdangdO8\/9L)\Kg"9O0:.JF3IOn"*\+JK622jr:+ggX*s-;R\/TbndU=[ca5tnE.N4@H.T@IZ!j.]lH)L`q%GtP+XQeGegQm`Ui(6$OC-/.m#Jk73+>/I%7Y[gm*F1?/4M&ojArSZERNa4G$QcVpr^C;6Spn\[00"YTZ>0hkTOS)Bl3.hX5L-BPdG?uH[2T:K4j.p$ea4,P\dQ5i:Y5kSoKLZ>DZ/F+"=MQs["`K!VcI!'rRP"trU\T1dj"V;`endstream +endobj +65 0 obj +<< +/Filter [ /ASCII85Decode /FlateDecode ] /Length 1826 +>> +stream +Gatm:mnXl_&H1J#@QqX8h#3MoKPqia&fmegjA_Zal/_1l=i7DUf\WF7^]%j3"Ei2e&5iU``:hK8hn8^M(aAm7rHm3!r'#c-=#%W"ba&fQ/;)Ub>gD1h^Y@"lBk"sMh)Kih^Lfnbia'&>MHQC,+W3"neABTq8IA!dT`<%dH\C'jo_>$qGlLHDi7]a.fGH-TE>D(7,`gpRs"G,c76.2hJ!K'7?.gGP04f,]b!u/O"%T\$5hjnN>IhNn&dq/f!]Jg8D[e7.""gDWdk>\T'X,!](%C@mmF;k/K@2!%RBh3nYM@/7l;:2#eI#>\=86;095PHMWb>)-A]%oU.&&UMY2m@Q8Zbb'e^?c7\?^b>"WO@.S>AFCWg=H%V)SLP*H\uX[Vge>%)1O4PdMp3/>\%HQUV9s:Bj*f1lh+f@lf5k4)T^$[jSmp?IaYA$?-p,_SFUMr7NINK!_u,)-leZ&W7kY>,`u[m/2*i,A,%C+AOX+(05K]cE"?(`V^Pg!pcUHKQVuKc]:\8N$o!mq/P'8PLuI\')$[96[2_'7n#W3H)QZsi1"c$7iip#3c,j&^Y?uOj_$t&(7L`X";\\G#nBuY#2BLrfSFR8,[o*!8;bcH;YR2e-=0?Wi&)8Q=uBMdo0ub'QTg74=CKdtd$N=@Ah>PcHr>9cW%Wem=L]"p,MeXp'_/j`ZBV2(dtCf.$+S+D\jSGk?S;&kYFYm93m_6tSI!]hTi7WhhclJ>/crNpLV%bNse"p)W0Cu8g^]rO!kGQNr>FgPu+P%+"1^T)K^CAG#$T(.BL%*n7(mhj;f0HSM;X2Ve_5>5'%InKaRcYlC=$fmM4jN"G;P1e-7_,nc5dNt0B-"*1b.b`WFHjPj4b(bAchAO]q/H-`rHN[7rsD,Vm*,s,`'6o=U$r)XYN3,]3d>D4ALjZ.!nh-@S:5XRT$5P/%u@cS9WotfCK2#YXLoD='OmI?:s#$6>X'0%NIS@da@ic5=(At\4n1nmbBj^M^GorCZ36CH,ZD$*JtS=V8JZH!f1&KbAG1d.lW9VZY0uenJZIj,*7Fcr?MEN["`j\s(+bI?#Mc@;(+mqPVQhu18E2-27?tMm=?=:E=i\9(=*Yqrj:)7'0^S\F$YMH2+RK4"Wkl/%n,2s\Nq]%%3Zs8B*_4cO6`\;_AUMXDef6[7kA-HiV*1\iuAuJ-MgR-?BJ0Lr'EFBEIE9l]fNoW77qQariunC)bgr%5`a*T5ZLUtSYNW^S4.@L=nW:uD8TR\,5Eh!YRfN`]>T`)FAendstream +endobj +66 0 obj +<< +/Filter [ /ASCII85Decode /FlateDecode ] /Length 1745 +>> +stream +Gatm:;01GN&:X)OfLKsL*GgZDH/k'0R^o5\'Q3caMm-coSh)mb*/FOigQ`5)l#ebP$-<1"V/KG9n,%8qR,D?8hm3[JcS_5B$6b@9>sK530s#SC%iJI*j=oZUm+e4*[H>nK`.,D2"4iT/`FQ<>[F=ar)cW"gK@04Fe`\Y`5VnA%Uh+#)0p55):n5L'^!Nk.9de.o9U5,DdoD=G$Zfap6`it6C*P+tI1YGL7.L10cn\)WK2'U_2;(`;L:,:0b:ZPL'2+,'/e'L.>ZAFeas<`i&"j\ftVY1fCg*6#iJC;08:il^6aOG5XD6-?o\4/6"]^;801'#,MUYElZLf=,[;1gHikbL&"Mr$j&!2[t2Cel^pe`ZXXmVS%%[V6Ks[E&Rs1RKJhKn?!_:^Kp8\Mp,#L)IlTi`5>PNpanBg?i(h'd6T60K,\NEO"/d"[Lbr)dSfcJO_j&Pb+16oacMOj,lO9B@AQ0Gg]_Sl471OLl.nC.dfp"';KSVlc/Hi,n2;E9I`Gc,a&gJUi9f+2%+9CbtsU$&B/WGmkfkP[:1Z68ail*(cCM0.!Qph1[*Yad4LQnGojj<=sd0=;d8Pm0&t3t?PCa?c2J%`UZ=B&""2B.al,ejo,+iguX,SY(89-uQ^k&1gc6;ie<3`0ko9Yt=>*JdBM'FdK3cp;A([ArUiri_['CN6Q(#EX`/NDmhfJX(VZX]8\La9`5lq4W[&37c'6d3s5LK7N^n(JbOcG&7O@JZ":iSF'5[Cgh'dh_C5#u:Ap[4\^Xe2fC:ZWaPT+ns>X@(p-d99\Rd8Z-BHJlb\,6m:$dO5PA,D6WQ)h4PBf`iFPB_`N1p;$s'KW9lc![F@:aD]H-anHgN(8,4%!)qWK2+A;;57N;"\g/?E[m]CG;<4P6GR"h`,_qd%mP'rc=H2W5J-3>F0[X/FI2h#L\PR(!@RC98rk5kVJK[IUeNdlUc0QDX*eX#BD2j"M+:(%LO.7:#t[^)S\HO@TErrD,rl'V~>endstream +endobj +67 0 obj +<< +/Filter [ /ASCII85Decode /FlateDecode ] /Length 1421 +>> +stream +Gatm:?$"^Z'Re<2\<"`AEW(FtBqMsmgIZ%%4)L;M;dP,/A#2MdOpn2%Ia>EQihS/q)$U;(/FLP=k8lXW(pBb4/=/c>cfiokKT_R32'q9r9XDLtO4hL=MqspQhmeN#h)[1b[p/?^A/?kXP:0)%Pi`Q%/a;gL9df^)r-_#?8"0CrJ,b2;qu7?Dm*1G4b"rDqUEiTPMM.RM%l;0]NcInblAMg@FGobpb1d+n\s4lJgh9TE"a;@][RPDAKEC)ot'ZG`;)nMOsP+2s+qNXJ/CIu_##?%GKD'_bME'bFF;(YD:<=lu-HFUnKZhU6tI5\)b0aEBjh3US*]g0>k:`(MJ>aGP$^O[\:]4i$!XDOH=`%$`F!V)2TkKl;)9"u.\E1N2@I$9^OWOYG;s"Q@K-&qX5YO1Ge&@r^&I8TSpH`c6AqVPj5Lc[R6[Be%i8d%EVeTYq=r]i-2U+IDeL7f9ha89kJ\K;Z"VBTD?KL*$o=VjSQO;gHj60XK>f%AoFfQm`^YZ.$h`+"tX5-*Cd.*[MmO5o3!ua+ZP#DE&APU*+bDEEi#(tQ5D')gNrao=&LIUZp05nY,-1HIe/AOE*kGPI3&ij-A2u$bBt)n'Y`gi:%IJUr:g/F5Msb(hqu+1jj!%#H9PN+hDCg9=U30AXBU`q$.uD6"#O`r/70%r(Z!6"#HVL4YXOua]+)RAO;;u#%\,L-#B2%fS;b)Lcj#.qfkn?'/)hQ%[e6Um(5)YP*5Nf1F_Y(CA0emR;H9o8/?XUslLS-*`\QP02=_24*L*;K8Q3d?#p65,SKs4\T+Zi,os$03&a!-TZ@:qDkRn_aj18-*dMZaL=7eK(6,&_dQYEWD0=4l.3)^tZ5"X'2b=S*E#PcR.&]Q$&c.Z(#D\duWMqGa$81Hid&^]_$[C;$8;OGFl3BQ,#-$U"XXGF76_NU#+<,F7*2ESR_ag=\@?9HJ!F+(k1S2$2sptDs'<7+9iP`mEW'`4BKgK1rbfs"s$H>:B=I!?-.tTs$\:g@(F/Tltd2@+(n$r8?-E05endstream +endobj +68 0 obj +<< +/Filter [ /ASCII85Decode /FlateDecode ] /Length 1557 +>> +stream +Gatm:>u03I&:N_CbgTRjLu[qL]H@RB;Q777i/3l6D!Xa!(Ye9DY&SN4rLNIK!!S75Whsd?]sHnG3AW`<\Fe*_^XE8BErqPZ#G)IJ)SFE'+o)IHajJG0rlL*@bal8Y:HuFOhXDIj+3o'n-h(d,7h.s;@'oS).JPXeob`jA+o0("^Jj'!9g#7rUH!@-KS8bTDWK)Uhur]>LAU;[NEc`LraasuQs4*rjSB4th;0D9(H5^U:#Su9ZB_COBT`R='gQJ&phWjV\?XD-Y/f[Ku^i2[?KR\cn"dJ-(WDl9,k,F"D1BK0iNA1M.P1gMuu`&RiN>MV[mG;(jD>\hj232S8_P5V:]\kVTuZr4,O40lOF=b_8`YC)G27A`Jk.hLH;sMW,XOrh%aq530'fdSH="\gW5ts)kssH>5(H-,9rYa$-6b0caG",W8+@ST0b_D2g./k^RF8'r8BLEB:=m#@#=SAKmSZ>.BD.ejB(Eb22ZqYh,@GH?(2mgYqr^.5c@&%9RT+lHRPPh:(pJ29uD_nSkBA\%`]XKEQBY\K%=5$F"=HZ'cie>m[6'V9%E!iD6U4J>-kbQY$a0u*V:AaGggB)_Vl/PY7F?kh<4M#,8-b3Eop:b$Kj\+31Q-51uSUZT4beL`\c'4s1nAB^76\X_([k;gc8MjZn_TXM6N9$o,TIo,$#h=d63g9T?c[T7L4n.:keK(+Nk4-\_1.!TqOr>MV>F5f-iI'Bun8\OO4*a`QW"_:^(QA3Hnc&F2hACLA,IoSp/01m_W_drl.9!KthCdZk"-:nLU+=E(rFPS\[Ob5]-[G,1Yb;Hd,'OjPcm`*L^f,g4OZ1*G1Kn3+Lph.c$k[SQS(*hIn140IbC0=\JA%CUTHJ>!8C)B5G[12&.h0(:-'BI18:b_fM^SF9(.o"HNHd*6hK>~>endstream +endobj +69 0 obj +<< +/Filter [ /ASCII85Decode /FlateDecode ] /Length 349 +>> +stream +Gaqc19htj7&A@P9GfSN?$7tPaaeXbN-=1FHH>0g0MfD&92;3QKYTH?P^_#YQHZ'JR[)@2I*O%?PmKJ8s3C>3l@%M=UZB&h)<2i^#@Xb5u'X:@<1"/]H==u*pc%r@:l:&i.'IhqT]Y^aKqgjQiSt[L3esob$K\f:IMW]bRBmaKn/u;T+-l8ltPUi?W1.ch/aE$"F']__67#TlI'_j!Nmu_cf]]2q4Mb4%K5DD2/PQ%r)tsCB~>endstream +endobj +70 0 obj +<< +/Filter [ /ASCII85Decode /FlateDecode ] /Length 342 +>> +stream +GasbUb>,r/&4Q?hMCYq\8@T_qnUkC!ap'+@=fg7DU!U0R5T54KHcC=Fg2+!q)/ERQa<1+d`a*%q!s4b_j!a'J"S!nPJSPk50Z)-;^VTaH6?#SIBg9~>endstream +endobj +71 0 obj +<< +/Filter [ /ASCII85Decode /FlateDecode ] /Length 1197 +>> +stream +Gat=)9lJcG'YNU14CBg;OXQqf/1[%ekpG.m]82p^fLmj(6sFIQd3YV+m]YLkoas,8)Jg'kP"BZME8J5t7R$g>]B1uuF[d1VN*&?uRTSW>P^TEum,ZpC0XItsWAbp=n^)dX`kK7n\A2``(b@(k4Wr93HO>@XJs>X#Pd7KWIB^o0!-ha):[i7\lN0a6mNmc>A.cW?5n_/tKe/W^adYgbKf6`cD*Zu,/[]D8\ZH#5OcI9(&)V>"Nk$i%EUdO'?%?R@d8IHM[M8@*RM@KTi20a.Xp^;npMN;S"fX@#6/4HZB2bPDMpQgnV9WM%>RTBq6_(U@WffA&*."&jbIs$/$Rnf(grPd_:T%_q[?JjI_NM$p%3AnGb4Xi[#[4p;8:u.Bg2f_?&`&jXZrEA\59t]t.K$ONLol!DC*)$:X23.B6C=CV.P6GlF5t2]DC@UMjTq)b@eF(hj_eEV5qBU;lNhVl?.]h^)IpUHlR>-=qXIf9]`:+$FEm*VLN,\no&#h]GACe-t97k6AJNdX#)a$`kQW.cl@dHCH-R:o^cb\#mHVJUhuXCl:S_q@#T*U6!Hc8jd9lbk0X9cepCTf%oHTjJ.Ji`_(>'?bL0_SUD]@kb2`!X57`775jo`iFqV_j9"00B48he,[?:K_2rG\#_"Y%]i!c8E8oj09.0`?kOV)$~>endstream +endobj +72 0 obj +<< +/Filter [ /ASCII85Decode /FlateDecode ] /Length 1331 +>> +stream +Gatm:9lK&M&A@7.%+'o2A/.sK[WC3J7lNlj\/Q00ab?$/RgVee81K2afCr.JALH?:d@bJ%)BrhVc'pXZ1\1'ErA1L15,E@M_h\J\(;qCMU@aJKe!$\nc-FOMbe7QY*aaYO]lGLQ`a.LY0+;G,`#_$@1jKL].>9srop!mCPlBsls+9:59es]@(sa(]i4V(?73RTI4:.l^9O>f;8Mki/af!Jh355cUq*!rg6"=`rc"$+;3DC8mesU>H6,,+')u[\ROWMXgQuE;MO8\k_)"@0mEIE`kfjY86/4!(\lhD9<-WW@qBVAG_B(crYLCdQI6C@XdShT`0H,LQ(YgE=h@#,!qiO4OEL'O=A-bcJ8\X"7:DWjtuNG@dLDQAL6!trl3!9A)HM>nend9*Z%K^%Z8>(!kVmk=.uHC`EJU3&!3n9AW^i\?Nlm"GP+]msNXOVbWsXC(E-45QpT@iJ>'XEk&mdd%(AMa$4t9sV$kd$1cIHEGsW$e"]NRHSh.eu^bYfi^YB>.>Mk>]:(clRVc&n`1=3B.o$9d;DrFL#4Y:t*:H&`Cj#s1t<9LF5faWg80CV5bV5cY+bB;92EtXMUKeSiDn;<([7MAc40=X[I$*;5MLJ!S'e*$ba[$C@kT.Kh$V;,TkiE;)P1CVpMI/n_VjJ=h4%7*6NTf3WmH^X<\YQk[W(T3$5gb4.ra9!rt*%=]44i8SE1HhAA@>X>cW`ZejYL]f/!F<:efX6MCPc#..O@e*_?qVG<#%;d=3l$@r9*'I6i$`Cd["X/gDUtV;&K9s"'t"]^h,1NHN6G\Ghlte/n\D&RhSpjO;-!Q8;hJH2l0bNeKVKRY*F0Q6#J>.@@V3Y=J_)/K?aC.A]6l2d^u'iKAC5?%endstream +endobj +73 0 obj +<< +/Filter [ /ASCII85Decode /FlateDecode ] /Length 644 +>> +stream +Gaqc3?#Q2d'Rf.GSB%d)?#1Y!;q+G*1hiE.M((*)1#N2SV"WHNt?R=5EU)hY!=8IbNbm#oSG\26CfP#3.;>#_(^%$!rL*#.Efk7^(B(e5hTHYc.9)^dUt]U*0b$l_f#GBDQeG_%nD::M*f#F-_\-?dL1R=Of0S4lG.@Zs'kVAh_f)lNUGNHi!.e+k`V1ocNG*):=i!Bd-!B/+&#&&.>MDUc*2h3=N4J;"opF*GPa\:WCtch*kJaAI--@pj3%G\bjnd&Wr.0p*31o2b6T;=.\]&##%H>bDarAEiB3`(?Pb]c-c;0'_SY/9.@NP#saF3JO;N*M3+6Fpq0b,8b$XCu<>=9_p_$cofEQ&MIa0pJ28p'.1$P/bALJ^IF%Y!YCah*W~>endstream +endobj +xref +0 74 +0000000000 65535 f +0000000061 00000 n +0000000158 00000 n +0000000265 00000 n +0000000377 00000 n +0000000492 00000 n +0000000687 00000 n +0000000882 00000 n +0000000992 00000 n +0000001187 00000 n +0000001382 00000 n +0000001491 00000 n +0000001601 00000 n +0000001797 00000 n +0000001993 00000 n +0000002189 00000 n +0000002385 00000 n +0000002581 00000 n +0000002777 00000 n +0000002861 00000 n +0000003057 00000 n +0000003253 00000 n +0000003449 00000 n +0000003645 00000 n +0000003841 00000 n +0000004037 00000 n +0000004233 00000 n +0000004429 00000 n +0000004625 00000 n +0000004821 00000 n +0000005017 00000 n +0000005213 00000 n +0000005409 00000 n +0000005605 00000 n +0000005801 00000 n +0000005997 00000 n +0000006193 00000 n +0000006389 00000 n +0000006585 00000 n +0000006781 00000 n +0000006977 00000 n +0000007047 00000 n +0000007359 00000 n +0000007636 00000 n +0000008321 00000 n +0000009036 00000 n +0000009423 00000 n +0000010361 00000 n +0000011777 00000 n +0000012683 00000 n +0000013138 00000 n +0000014687 00000 n +0000015080 00000 n +0000016317 00000 n +0000017753 00000 n +0000019204 00000 n +0000020790 00000 n +0000022526 00000 n +0000024078 00000 n +0000025582 00000 n +0000026866 00000 n +0000028457 00000 n +0000028943 00000 n +0000030632 00000 n +0000032353 00000 n +0000034239 00000 n +0000036157 00000 n +0000037994 00000 n +0000039507 00000 n +0000041156 00000 n +0000041596 00000 n +0000042029 00000 n +0000043318 00000 n +0000044741 00000 n +trailer +<< +/ID +[<75e97b68494f91737df38a49cdfb04e7><75e97b68494f91737df38a49cdfb04e7>] +% ReportLab generated PDF document -- digest (opensource) + +/Info 41 0 R +/Root 40 0 R +/Size 74 +>> +startxref +45476 +%%EOF diff --git a/pdf/The_Digital_Mujtahid.pdf b/pdf/The_Digital_Mujtahid.pdf new file mode 100644 index 0000000..c0c735d --- /dev/null +++ b/pdf/The_Digital_Mujtahid.pdf @@ -0,0 +1,678 @@ +%PDF-1.4 +% ReportLab Generated PDF document (opensource) +1 0 obj +<< +/F1 2 0 R /F2 3 0 R /F3 4 0 R /F4 7 0 R /F5 10 0 R /F6 11 0 R + /F7 18 0 R +>> +endobj +2 0 obj +<< +/BaseFont /Helvetica /Encoding /WinAnsiEncoding /Name /F1 /Subtype /Type1 /Type /Font +>> +endobj +3 0 obj +<< +/BaseFont /Helvetica-Bold /Encoding /WinAnsiEncoding /Name /F2 /Subtype /Type1 /Type /Font +>> +endobj +4 0 obj +<< +/BaseFont /Helvetica-Oblique /Encoding /WinAnsiEncoding /Name /F3 /Subtype /Type1 /Type /Font +>> +endobj +5 0 obj +<< +/Contents 43 0 R /MediaBox [ 0 0 432 648 ] /Parent 42 0 R /Resources << +/Font 1 0 R /ProcSet [ /PDF /Text /ImageB /ImageC /ImageI ] +>> /Rotate 0 /Trans << + +>> + /Type /Page +>> +endobj +6 0 obj +<< +/Contents 44 0 R /MediaBox [ 0 0 432 648 ] /Parent 42 0 R /Resources << +/Font 1 0 R /ProcSet [ /PDF /Text /ImageB /ImageC /ImageI ] +>> /Rotate 0 /Trans << + +>> + /Type /Page +>> +endobj +7 0 obj +<< +/BaseFont /Times-Italic /Encoding /WinAnsiEncoding /Name /F4 /Subtype /Type1 /Type /Font +>> +endobj +8 0 obj +<< +/Contents 45 0 R /MediaBox [ 0 0 432 648 ] /Parent 42 0 R /Resources << +/Font 1 0 R /ProcSet [ /PDF /Text /ImageB /ImageC /ImageI ] +>> /Rotate 0 /Trans << + +>> + /Type /Page +>> +endobj +9 0 obj +<< +/Contents 46 0 R /MediaBox [ 0 0 432 648 ] /Parent 42 0 R /Resources << +/Font 1 0 R /ProcSet [ /PDF /Text /ImageB /ImageC /ImageI ] +>> /Rotate 0 /Trans << + +>> + /Type /Page +>> +endobj +10 0 obj +<< +/BaseFont /Times-Bold /Encoding /WinAnsiEncoding /Name /F5 /Subtype /Type1 /Type /Font +>> +endobj +11 0 obj +<< +/BaseFont /Times-Roman /Encoding /WinAnsiEncoding /Name /F6 /Subtype /Type1 /Type /Font +>> +endobj +12 0 obj +<< +/Contents 47 0 R /MediaBox [ 0 0 432 648 ] /Parent 42 0 R /Resources << +/Font 1 0 R /ProcSet [ /PDF /Text /ImageB /ImageC /ImageI ] +>> /Rotate 0 /Trans << + +>> + /Type /Page +>> +endobj +13 0 obj +<< +/Contents 48 0 R /MediaBox [ 0 0 432 648 ] /Parent 42 0 R /Resources << +/Font 1 0 R /ProcSet [ /PDF /Text /ImageB /ImageC /ImageI ] +>> /Rotate 0 /Trans << + +>> + /Type /Page +>> +endobj +14 0 obj +<< +/Contents 49 0 R /MediaBox [ 0 0 432 648 ] /Parent 42 0 R /Resources << +/Font 1 0 R /ProcSet [ /PDF /Text /ImageB /ImageC /ImageI ] +>> /Rotate 0 /Trans << + +>> + /Type /Page +>> +endobj +15 0 obj +<< +/Contents 50 0 R /MediaBox [ 0 0 432 648 ] /Parent 42 0 R /Resources << +/Font 1 0 R /ProcSet [ /PDF /Text /ImageB /ImageC /ImageI ] +>> /Rotate 0 /Trans << + +>> + /Type /Page +>> +endobj +16 0 obj +<< +/Contents 51 0 R /MediaBox [ 0 0 432 648 ] /Parent 42 0 R /Resources << +/Font 1 0 R /ProcSet [ /PDF /Text /ImageB /ImageC /ImageI ] +>> /Rotate 0 /Trans << + +>> + /Type /Page +>> +endobj +17 0 obj +<< +/Contents 52 0 R /MediaBox [ 0 0 432 648 ] /Parent 42 0 R /Resources << +/Font 1 0 R /ProcSet [ /PDF /Text /ImageB /ImageC /ImageI ] +>> /Rotate 0 /Trans << + +>> + /Type /Page +>> +endobj +18 0 obj +<< +/BaseFont /ZapfDingbats /Name /F7 /Subtype /Type1 /Type /Font +>> +endobj +19 0 obj +<< +/Contents 53 0 R /MediaBox [ 0 0 432 648 ] /Parent 42 0 R /Resources << +/Font 1 0 R /ProcSet [ /PDF /Text /ImageB /ImageC /ImageI ] +>> /Rotate 0 /Trans << + +>> + /Type /Page +>> +endobj +20 0 obj +<< +/Contents 54 0 R /MediaBox [ 0 0 432 648 ] /Parent 42 0 R /Resources << +/Font 1 0 R /ProcSet [ /PDF /Text /ImageB /ImageC /ImageI ] +>> /Rotate 0 /Trans << + +>> + /Type /Page +>> +endobj +21 0 obj +<< +/Contents 55 0 R /MediaBox [ 0 0 432 648 ] /Parent 42 0 R /Resources << +/Font 1 0 R /ProcSet [ /PDF /Text /ImageB /ImageC /ImageI ] +>> /Rotate 0 /Trans << + +>> + /Type /Page +>> +endobj +22 0 obj +<< +/Contents 56 0 R /MediaBox [ 0 0 432 648 ] /Parent 42 0 R /Resources << +/Font 1 0 R /ProcSet [ /PDF /Text /ImageB /ImageC /ImageI ] +>> /Rotate 0 /Trans << + +>> + /Type /Page +>> +endobj +23 0 obj +<< +/Contents 57 0 R /MediaBox [ 0 0 432 648 ] /Parent 42 0 R /Resources << +/Font 1 0 R /ProcSet [ /PDF /Text /ImageB /ImageC /ImageI ] +>> /Rotate 0 /Trans << + +>> + /Type /Page +>> +endobj +24 0 obj +<< +/Contents 58 0 R /MediaBox [ 0 0 432 648 ] /Parent 42 0 R /Resources << +/Font 1 0 R /ProcSet [ /PDF /Text /ImageB /ImageC /ImageI ] +>> /Rotate 0 /Trans << + +>> + /Type /Page +>> +endobj +25 0 obj +<< +/Contents 59 0 R /MediaBox [ 0 0 432 648 ] /Parent 42 0 R /Resources << +/Font 1 0 R /ProcSet [ /PDF /Text /ImageB /ImageC /ImageI ] +>> /Rotate 0 /Trans << + +>> + /Type /Page +>> +endobj +26 0 obj +<< +/Contents 60 0 R /MediaBox [ 0 0 432 648 ] /Parent 42 0 R /Resources << +/Font 1 0 R /ProcSet [ /PDF /Text /ImageB /ImageC /ImageI ] +>> /Rotate 0 /Trans << + +>> + /Type /Page +>> +endobj +27 0 obj +<< +/Contents 61 0 R /MediaBox [ 0 0 432 648 ] /Parent 42 0 R /Resources << +/Font 1 0 R /ProcSet [ /PDF /Text /ImageB /ImageC /ImageI ] +>> /Rotate 0 /Trans << + +>> + /Type /Page +>> +endobj +28 0 obj +<< +/Contents 62 0 R /MediaBox [ 0 0 432 648 ] /Parent 42 0 R /Resources << +/Font 1 0 R /ProcSet [ /PDF /Text /ImageB /ImageC /ImageI ] +>> /Rotate 0 /Trans << + +>> + /Type /Page +>> +endobj +29 0 obj +<< +/Contents 63 0 R /MediaBox [ 0 0 432 648 ] /Parent 42 0 R /Resources << +/Font 1 0 R /ProcSet [ /PDF /Text /ImageB /ImageC /ImageI ] +>> /Rotate 0 /Trans << + +>> + /Type /Page +>> +endobj +30 0 obj +<< +/Contents 64 0 R /MediaBox [ 0 0 432 648 ] /Parent 42 0 R /Resources << +/Font 1 0 R /ProcSet [ /PDF /Text /ImageB /ImageC /ImageI ] +>> /Rotate 0 /Trans << + +>> + /Type /Page +>> +endobj +31 0 obj +<< +/Contents 65 0 R /MediaBox [ 0 0 432 648 ] /Parent 42 0 R /Resources << +/Font 1 0 R /ProcSet [ /PDF /Text /ImageB /ImageC /ImageI ] +>> /Rotate 0 /Trans << + +>> + /Type /Page +>> +endobj +32 0 obj +<< +/Contents 66 0 R /MediaBox [ 0 0 432 648 ] /Parent 42 0 R /Resources << +/Font 1 0 R /ProcSet [ /PDF /Text /ImageB /ImageC /ImageI ] +>> /Rotate 0 /Trans << + +>> + /Type /Page +>> +endobj +33 0 obj +<< +/Contents 67 0 R /MediaBox [ 0 0 432 648 ] /Parent 42 0 R /Resources << +/Font 1 0 R /ProcSet [ /PDF /Text /ImageB /ImageC /ImageI ] +>> /Rotate 0 /Trans << + +>> + /Type /Page +>> +endobj +34 0 obj +<< +/Contents 68 0 R /MediaBox [ 0 0 432 648 ] /Parent 42 0 R /Resources << +/Font 1 0 R /ProcSet [ /PDF /Text /ImageB /ImageC /ImageI ] +>> /Rotate 0 /Trans << + +>> + /Type /Page +>> +endobj +35 0 obj +<< +/Contents 69 0 R /MediaBox [ 0 0 432 648 ] /Parent 42 0 R /Resources << +/Font 1 0 R /ProcSet [ /PDF /Text /ImageB /ImageC /ImageI ] +>> /Rotate 0 /Trans << + +>> + /Type /Page +>> +endobj +36 0 obj +<< +/Contents 70 0 R /MediaBox [ 0 0 432 648 ] /Parent 42 0 R /Resources << +/Font 1 0 R /ProcSet [ /PDF /Text /ImageB /ImageC /ImageI ] +>> /Rotate 0 /Trans << + +>> + /Type /Page +>> +endobj +37 0 obj +<< +/Contents 71 0 R /MediaBox [ 0 0 432 648 ] /Parent 42 0 R /Resources << +/Font 1 0 R /ProcSet [ /PDF /Text /ImageB /ImageC /ImageI ] +>> /Rotate 0 /Trans << + +>> + /Type /Page +>> +endobj +38 0 obj +<< +/Contents 72 0 R /MediaBox [ 0 0 432 648 ] /Parent 42 0 R /Resources << +/Font 1 0 R /ProcSet [ /PDF /Text /ImageB /ImageC /ImageI ] +>> /Rotate 0 /Trans << + +>> + /Type /Page +>> +endobj +39 0 obj +<< +/Contents 73 0 R /MediaBox [ 0 0 432 648 ] /Parent 42 0 R /Resources << +/Font 1 0 R /ProcSet [ /PDF /Text /ImageB /ImageC /ImageI ] +>> /Rotate 0 /Trans << + +>> + /Type /Page +>> +endobj +40 0 obj +<< +/PageMode /UseNone /Pages 42 0 R /Type /Catalog +>> +endobj +41 0 obj +<< +/Author (Jauhari Che Wan) /CreationDate (D:20260806184434+08'00') /Creator (\(unspecified\)) /Keywords () /ModDate (D:20260806184434+08'00') /Producer (ReportLab PDF Library - \(opensource\)) + /Subject (\(unspecified\)) /Title (The Digital Khalifah: Stewardship at Scale) /Trapped /False +>> +endobj +42 0 obj +<< +/Count 31 /Kids [ 5 0 R 6 0 R 8 0 R 9 0 R 12 0 R 13 0 R 14 0 R 15 0 R 16 0 R 17 0 R + 19 0 R 20 0 R 21 0 R 22 0 R 23 0 R 24 0 R 25 0 R 26 0 R 27 0 R 28 0 R + 29 0 R 30 0 R 31 0 R 32 0 R 33 0 R 34 0 R 35 0 R 36 0 R 37 0 R 38 0 R + 39 0 R ] /Type /Pages +>> +endobj +43 0 obj +<< +/Filter [ /ASCII85Decode /FlateDecode ] /Length 594 +>> +stream +GasbW92jS!&:j6F'mo5!c;a!Zk@cPCTj\3p9J9Z#`3Daj"-,1.rd,nTKH\XJ[RP%J+8W@u-%OfERX+Q7E2MUdOoV2K2aB@^T]^9f-a/_/'7%P*a_op_[%kdV"mNm$b`EAMW'Du`1JAl>XN@a<:m")iVl*_LkoWj+GI`,&;oQ7Mi1Uc[4F.lc;<@Vs<4X`)hgPgA~>endstream +endobj +44 0 obj +<< +/Filter [ /ASCII85Decode /FlateDecode ] /Length 624 +>> +stream +Gat>S;/b/B&-1X4I`9"&RoD>T0od>!'Qku5[M`)/qI5SOGRL4`TbIHT2GHN4ig5IW+R[PNjDteu?pFGa^"EE[,i$Wu?iom6n.6$pcJ`(>%YH5D\q!&@l@8]kj!qJi"'<[.J0Mu=&;KOD41KPZKED7!q[2m)aD\6XLL%AA)0)-VZoEB_]2UFrPU.Q5U,,E-tBbirEN+LObEQ/GR?+RU)*&b3I^`eL"1SKHa6m?e\9d]i>I!]7(licqf-Tu&._q*Q"^:u^"&t%i$hZoIT:(am%er\9_;lJjp..&N^n4c-q*pH%JS(A49aS-mm?2tribp(,<-^mAG7+N)RmqKr7`TCBI^rLfcVZdOL[b$lkh/=^.H3=gI*qr\<9S1&g*+;f"0o^6*S24OR*qXp'"41]qJmke+8UTCja7VG9U]cFLN^endstream +endobj +45 0 obj +<< +/Filter [ /ASCII85Decode /FlateDecode ] /Length 296 +>> +stream +GarVH_+Fea'YNTZL0gs5BjN^>)D?^#SgmhJGk&'rdC!/DDKd]3]h+YU.$F(+aNU,46P/caY1l*Yn$$O4,iN&qMCZ1o*ZR8GK%qWeE`;ttj*ZWk`1S;%7E)[#OIA\94dIa!eu4\a-/9!u.SXiUmQ=tD8?JuTQ&/98JRUc0#KB>s22&aC[g<(,C&+c++Nf8@D5oTbDZ\3og%5B`Gu183-F!Jc,T#N`T<~>endstream +endobj +46 0 obj +<< +/Filter [ /ASCII85Decode /FlateDecode ] /Length 847 +>> +stream +Gatn%a_oie'LhclM?e6#V[J32k"UsU$">`FKk-AV,L[DI%>b9*maq21*mulC(taEDaX3j.0+Y$T;]tk/m5`Gl:*M[/TKjA_1SD0f6Z`FndD=#B]#WDCJ`X&hn]U2GkP>\"0#n7,*/=Q9/?G)Pk^bH!Cs\M9LjhY^9gARilY[b`4hTg#V^fPV:V"?op-cc"[Hhs(blFnqd?#./Nm>/R,a,-PQa=)YJ&X3k=Mp:_mHFJZE$eWkL[_!&4+H*!T9$"%AH3""X%[Lf0$@S?6Yap]W)W+C_O%-GV]$C#=ers+UH=2X2\,u-O5]H.$#,3l;gE@KjQ_PB^=.\D2Lag.2u],o^NL8MpNBX&,o(MYGk=Mgo5'8^#dO$25=gDuPc.Oo@oVLgU(`Pk009+VhCph=l2**YnHXZ=`!Ic4bnK\a\HL:p5ddj`5I6#U>_/ha&?khi!94[OeS>5I9T@i/PD!m"k9=5M2EHJ#Z:@Yc`)OD-$G%"L>2g8Qqm=G9M^G(5endstream +endobj +47 0 obj +<< +/Filter [ /ASCII85Decode /FlateDecode ] /Length 1324 +>> +stream +Gatm9>uTcA'Rf.GgmLo!cj""U.o%/.:_n49_[bA=*W!R0@Onl&>KTPnC&7.BV)Tg6%\"mL0X@sZX)m_ipP=?\^Vl+W"7SebB@d8W!8.EEj@,0d^f>RMor+?OmDQq9]'oF"q,=+q6+V#d+*qoH5S/8ZWIa)b+;dHSp2L/e(W_'5]0B`Zm?V:A94Jr?"G5OEE>jNV_UqF6NahKE1/=S6G6dpTgA#=4!>+-s%P9FKpte!KfrT_aRGoFRbF67CA:++9mL"_[LkUp3M]_h['HuDu8,[K/-.lZ5*1"B?l'q:BOAu^$9$V5'Cr%+K)/<9kK__K'"%6#_>b-^I-4']+RRDfO1_SN7!MjC].,6Sh6$-I2ZNU@GMSVH.4'=df;4\k[OMi(D_jPK75Kaf7bjAl_5$Yqjo5/YtH$eTD!q.BMNU+i.\&<#&WY:eFibd]Ae7bnY:+0;[$MS(;O-i)<8V7>8R7#Sr:Ub\j!n82^d`@X0JY_I9mZ<\:.[;n0$^:e4\C@/k1_cB5,R`=2nu(hfuP'05Xo1)-P]6,/k^BFj7-=m.;f<]Df>.8C$sV;W+-(7o3q16!_:YOk:L)_,MYl:KE(X69ftrV)GXC%ZH)rA^icncBQ0c77\G]9XpG$*U`_"3lT__9I7&0QGt4;R!\L!HnuP9UhTC=KYc?*^M<$NE3#l%846@l>Uq:>B?)=Zb&Kg0!'J*:X,mX+C+c]g-lG&Lf6sZIC8q4hjOd7OpMV`L/a+)Z2`t`.EspI+[^ko^\^!h*Z30o*[\A:Zi/X-*mgIlBf&X\8h*]18pfius&o>._H^FnLSZ6Z.bQYR]c;fmqdkGAFZ84B8Fd#ZuKsI+@S\n`h29>S0Q-k?A[U)Oa-_+IJqB?EfRKLYl$Ts[GDlb_WA13"ANR)@DYFF'X]-U@$oG!POkW,O%!"Tu,^seNT"H2=E!f[6[1uGkXh@_/FAOjo$`XNNfAG]h&EG-8A=7T,GPCoE`UZMh4l-o*Xf&t+Qs.Bt.BlHlFrI>r,E*TO$a)1q)!M[86'mlFd"[G;Zs@iA-u@AbH`-!ci&kn(NjUm8f!6ki\8oV)/EbaDZn%Y7K_)W#R=X8SDlf\Q2i8bTpQ_h<5rmof5Fmc7qZ~>endstream +endobj +48 0 obj +<< +/Filter [ /ASCII85Decode /FlateDecode ] /Length 815 +>> +stream +Gar?/?Z2Df'ZJu$.F)F,FY9&2V(^B!Xja([djh0-oYlNR5R2IIS$7;;>pk3&W^6cEm;pVPSP+ot5On9Q*e=+pf+0TFM/%Z&'e-.)pfafV4abr8DP&=:_1uW&mfE/\t=\H_ilK[aTB.lUg%+`fih(Thu&=L">l*eEh-ka]meK<;UQ/\&!L`V/)*#6g%\HL6hZV7X'WcpX^Z0t2]='p^/sB5o+'-f\c:BpSe+NKQ`>GJ;-juH>-2=(0"nu?[6qJgp(`K#+`:-K3bk]2_A,s-S4B>RKhT$D*9M_1^+&_5?Sp:a)`'p8/)=OLBXIi[*XbK\H"P4RXld6fZe7MK;0Rf^!NK2A29Zhp;)pM#]^k#j]AfO,Q2fdL*F_'f5Dt,`Ko:=:u;1OZ&nce2gf11p0:jYY3ubHBro"eKOt10/)@QTu9j/,/6#1`+HlZ1aqm4mH)4/`CuWNB^JC5Am);;93if@Em.ZHG71*7\7bn-0?!l#Jli(L3IX?ouLP5p(#t=d+e`4>:[AmB7f=4XD;OCiJ!%n_=*QBA8(8jFBqd9rq"b+nW"\2FGZ:nmNiSF'+SG,2I;=':3B(+$)4>K3!/@LF6aJ:dSI"!`Qq?KS!8W<~>endstream +endobj +49 0 obj +<< +/Filter [ /ASCII85Decode /FlateDecode ] /Length 364 +>> +stream +GasJM_+qm%%#45!MI5AY5U),WUhMgj)a`Na;N>"ZY)FRUZ#uPSgZ,[,@.Z\sfhlScro=WtChdgl"E":\;Z\\j/''2un;'Y,f#](u`B^TS_n00bZWY3T3lnQaauKYf,t^gh?C3lNAN#[0==\;8)Whl"D5t1G5!MZ0ESp]ZG=G4\A0F">BW(Gq&B&=1oE,fq=h&&%G"O.\Y;+^3o((__M+6FuZt3H<\q3eZQ_oeJ,'4\bX+D_*bQ2f$3RZ+,n]l(s`MODfjT]endstream +endobj +50 0 obj +<< +/Filter [ /ASCII85Decode /FlateDecode ] /Length 1457 +>> +stream +Gat=*a`?E"&A@rk\geM-b,2_,U+WEJX<^f0Z87e^0"F4m,U!6k*!!@II!rTB7C;0F8]D.GJEVI\hWk@j#k9kEfNRs&Rc/C?5k+Xn?_g8X@dJB1V\oV/Pg@hV7A:>+MLWHQI.:rpaO'eG%\ffGGeKR?4(dseCOd(,;"7FcPRN4sUM^NSZXZW*j)kL&JUq\-SujD2WCpYlFFlDY[,_6M=AH>^Rf$S5_c^RFS@dl3\iVhJ'$AcBINi/X/76rk-Z]TZXr66OkZ1^-*%ulB$7)qfFsO8#WoRR_UYpo8@Q_g!3#mV+j6d%"G-o)p=cSD&87#eO*YZ:Q`,g=OoC!E[/%.r!A4#rtcOC,gk:[2I@E5ZWKcDns"/pCb)B/Z7fcsS:FqS-36FBqhKUNfN(MYnKfPl&m>kq?8]B,mL'm/_Dd^GCa&@t'?i3j<*`*Ppkb:sQ@jhBUXFc1RMS`*NLF$BA$5c$3@dLPupe0(7b[LlEIYqp$[G2(0AOO>d@X_G0(<8)C2oD^(GR(b1_T)YI>agm4Om7%GppP!L=@WIR4`\,,Kk^/KGn7U!eEp,kh1"Q_<@r^ic"t84EpX"('XKns!;j=&bHqAr8H&MS/L9VCXV,k2OBeP9DJYo]CGj5oFKdp;f(n4==CNZFYnMOIT(#\h]-EdY`[K-["KR$Bl5!Y;<\oi<$P2X$)/0?LQQb%*>FjN`C)m!8n_$RH-pR!dR";&h,6J_ud#qCJ;k?eGN?2"3MhjCD;cNH'=QS49'K7\gD[)NQFC"tI'O[7G<endstream +endobj +51 0 obj +<< +/Filter [ /ASCII85Decode /FlateDecode ] /Length 302 +>> +stream +Gaqc09lIm&%)(h*]H]cf1iC_u=!ZF0(T&0rfk>q3lQXbVLjqXePY!9`D>E5f4b\K[Rf&ia2BM1TJg0t7Pa36e%9kJ<@d_aViFFgt3Or?VjU!f^;,Kqq#\52*oiQSQ=ZGL3!ri_EbhIKaIB6D67nmQ*bs](eVsj?Y.\sm\88$%X#EG(XMITqVNq2:=XI+#,,q10>3lDf'j`KE&ka>l\c*5E/^!feHc<7Eo\hluo.l'6I)_@Fq8?r%1;qp5O9]lu!FMfP^l[WIR4jpkMnV.b)O2KqSPn/_PB;A,h?9nDhbUHNn~>endstream +endobj +52 0 obj +<< +/Filter [ /ASCII85Decode /FlateDecode ] /Length 1145 +>> +stream +Gatn$;/b2I'SYH9.kWLaE/0/[79Qqp[O'4&+@FpP5TcFXck:2:O@>M3h"ops:pQ@r?>D**&kKH!hYZi56\\Nm?f#+I2:3L+?/9P\1$&f&#tl\]UM52Iq-sA9'OH`$\po_Nh4Iu-&U[q5n6o(\@I+QW&P2D]AYVZ_"NAhL98:@fcdF*9VGfl,1q:,V6hp^6!ZI+EQ3k4K9,c$UXp_qB'`F17RUo5R!HeYQ.-]qb/Te*X#fnR\`mj8^8NQ3/:>^ltrtI'LrB!>n2l53FI=?ZoJ(LP%<00kemddjg^-;_Aa%US'0,f_4&iL.]H$d:nn)6GlN:0dFk&-MBGg*'Aifgh4eSVmi0qdEn;L>umXAu[+ga_P,];):?$dQ5',Bo/-erbif2a>:tBs6GL[LfY)N_d4S[.C*%$ERTF<@L2UU+f<7Q$#ZCAdTD"_._ED/+$AJjd/0:V=]quq\#s\$e/9M:KVS`#uU)g2P/.J.D(l:8hmo31`gAs.sNR[[uhM6lt@h,<19Oa@kp+j;"E(`'rUopFebr-ZfU1\td-Y`YG^LXW##iO,tT^(ph`D>#nS-M8*6F0n3+T\fr!`[Ub[CF$e>^Aj0Y2PeS%RMhM=i9seeS.Nhlo+,`H`=Z*.IQ'Pf\ihJ+ST](b66%o'#/2ur7n8DP:ZV=m$A,3=_D)hcJF.meFeu7-+Rndb>(-)9\8&,#0BgU\`3Zu&s2,"Gr!RRbB1)~>endstream +endobj +53 0 obj +<< +/Filter [ /ASCII85Decode /FlateDecode ] /Length 1344 +>> +stream +Gatm9mn_t'&H0=m`CT_,:13',9cC`g\[#2XYGG[(PE8OWi\it54(fp[]taQd:0M=XCmPfc&nH?$?J`=RVVpDdFjI,jpmf4C3"!@W(UG1Q)j?[/]S=KIA4U4$Pd&?Dq35F?,LP&e_A1$T)__6XBn`/4K*0OSYPch99""tN9"FPOSqRm!M?X`IF(>mNH;?%?5KG7Ej_0<_--"#VV3OD)u%]F@A6;Z[h,bdQ@,bu.%dD5bJTF*bW_5aOVW2oBr^s!Q4pfSr)U4[aol>cAZUlT;i[F=!=$UJD0^"iX6:pK8>H$N,9]lUJ6X]i1ob+Vu;'6@'8R&N-ISrnL]N$/!&p,EV2mnf9oY&sGY(:h!Qo#G\/l/^%\phl-er*];>2ECI:cF\>ZW1$7J3CAG_"d@pfetAV>!Tk-ERb&k/cm399j9h4ZgnCs3,p)GP0nCJe*?[1F/(r?V.q?)o?82S3a-KlbO`BQFfb1nA%@<&3P&$B1)/_"D'=Vj?JsXGn)("*OA.6/p*mmssbZOR0i*&Fk2,44sMtN^QG&%K?E!\DN/1]G/)`J3aZ6DNi+JDZfHi8YccH;u.&on"bM'Q)lS/>4m:.QbA)0\d9A4*N:Che&Enhq-iVa9/t9,gsA)L:=XJ_"#LEKofe#)tiBOm0h%Y/Y)jU[-%oC6'WS13fuJh_&a,KK>@"k,3/NroQ3tfK?g^3*D=fLnIYO.Eo[Q8rlVUFg`H`4XAE7r'9#fW1VC.4dsiKSG.'+GW!B1AiT63Sf&1N?9K%7X5s'X"h4g!_#HA`Veq`BNe?)LaVE;qhHrkYZVo(oD8fRsVPVhMKrn@7Y1NiA7dl%'PQ+,;P;"&\B#SF@\D=92$K#$a;$c7rWYQ2Q)+-t4?I"W/&W`S,%ad;C;OG>$`_H>)VfhC[rZ_.00+8^)L&~>endstream +endobj +54 0 obj +<< +/Filter [ /ASCII85Decode /FlateDecode ] /Length 1359 +>> +stream +Gau0BgMYb*&:Ml+b[[qt),Z\Gg\[5[V$WT;%.kj]Js"%g)i7Nc.^&O3G:;-aj>LrZ\;1`(8=c//F68Q(!rCs%s0Mq(B**j$*-_aQ.I`-^0Y)kcakld*jiYq'N**ajSNaD61\3^'&hXSPl\@h5#E4a:fRF=I`2!2'".4Iga^>&;3s&_O'.:/2&BCkJRF(D]#CI5,fR3-W$6Wd[+6)c@"s,>E*r,C$YE&#lN_\MPs'/>!"&XHW&k*=3?`o)7*Y68]Cjs[-++,me55KC_T)oc:&g$^S15Gf5LN?lZS')-gK,2]>>*u'5>Rj)3OQs-QQ#mB"#KhNLX$NdE".8_e/:ln=,_PF_9702,dClcY@n$R<"4(L(@`=D""`?]JbNL$.N7"#.s5qfUP'5qLTS6B-+RL:EY8Spnp/^f*'1F&E;_%&FtGQWAGWO,PR\.[+cc,P8Xc(Pc)3b]VR[(a6%J4&GmoghlidM@71+)HZpYGdH)7mRb7XVMju8j'<+PE=D^769N?CW%,D\3rAeF(6j1*-[q@+:3]?0#N[#)Ui/(6Vk&e`4JDINgWp.,j9]i5-,W/ZEs%+d3=gU+Ha7p5[fjg?9Rc#>Kk(Zj2%HkKj])mims[m'f$F+gEhg`]C:Z/1Y?l-6d7M=L!oc/e$^k&QB)_^,"jh"Qi,OSi]%%0il^W<,8$K]D4kQ/N?I62k[D"Y6[2`rb,E`o,?nPH@YDD]DNJ!qJ?]lAA7JVV49W8u]In[W!2ZUKuEkJga3RiOZsH$tnnu^!^+PD(V&)X2<@*1P=F."&!S*,Cniig0.';f<(=XV=k#ge'cJ;iimf.Cf]b'=PP5MY]:#>^LIGc/.h;u=C(*KTuu/p0Oe4W^dTp\(o,bS_rM+7sb>3\b!F+16E;e>],DTJlS''D0QJmqm&$JjM=MFC(DNep+.DWGG&oaiJR.48A$c+0r-F5:GekbQ~>endstream +endobj +55 0 obj +<< +/Filter [ /ASCII85Decode /FlateDecode ] /Length 1494 +>> +stream +Gb!#[;/b2I&:Vs/\4:b!'iD7_gNt@(e>\Ec=ds["97VSZ.#TlMC*XNQqt3$K8liQH4V%S%,d:g9]K=tuhffk<+oW,SR8j6*Q>gh4J4-UmJ..#1/3gpdH1o9]pL`JmN.[pQN]6?t?FprJ1Db`jLnbPM_Z28gd(>@5'M&Z#q?iP'_t#1ar=^)ug68>BFter/&OqAu!tpc:6=Bi)lR@KDFWN0<&g1U!p!?,D%**?#A"[&i/WAe\;U>KT!F%=`RS$L4%B@5@`n19gWs7G-NAirFjNlg2q9EX_YnPAbf7?6[-<5;GARY6;9X)`]--p#M\-G*.,XFDMLAm:&P,8hW]!Xe7%dj@]=MuN:2H*W+88]M8:l?Xf?Eu\D]-b^g0l@ph44]%GOC:9Bk$9eX13+ZT[YtPt[b4"YI[pj98m3FeG@KguR-h:W@BdYjD`O4T6$sRuIAl$JAabu?GJCh^h(@L>b\edmp)B'f;mda)%QP"'"N@%qa?kJeU?GZXdP[A,:jR!(T8M3O"*;Ne^A)RoO+9+%DqXN1)QmN$tuBs'%4qep$/15>VmA5>Zrdb!WgFKhBM`q$!_er_1T$1@J9GIMJeek-gHh0@Rm.d:7dOW7sR8rF>nUUpUrR?rWF_I2q3Z\=%DJ*%K"WdaS>WE%"hCoa.9/;U+DXjleJG*>p\mi*?AdHa<9J9Xt#[X[jVL3G68#fAOF)4I6Ng[eoKjTe1kmUiO^d__lc!)>_go9b,okP&sFPru4d5m:SrUB!)H,fU,>o8X`.cU_WYr[2]+(63s9oJo]8s(lRi(:b,UoS[@R5Zf#1=^,Q0N'#(%*]Uqta/?YlAI?;:u?fq!c8c~>endstream +endobj +56 0 obj +<< +/Filter [ /ASCII85Decode /FlateDecode ] /Length 1644 +>> +stream +Gatm:?#SFh&:O#NQq)Hk[^H2UnjXQrU,GS-\>l\Gl"Y&gG]W7XB6Of]^V2L>VleDl`)QpINn9k`1M>!,#Q]B@s#6tY?E`;;AI)]IX#5Q?2MTb/=KGgk]]`+fF>.3EG98KlYM%89@:q2"68j^u&5=!FWaKc^71%ZMqL&[NHW^58YCAsXO71!n5!'(JCkRr/I23%G/.UY'Dr4InEPs3bj4.]L@F2tVU%lVYQpu>.K>FQ!:c3seRZ1a*9nk&AHnDX]Td<[i-"(QO;@8,$9N-6e&\&[9YagMl\7PE,8N^f*%0T7h'cuq8gjpFA6S('Q3)6@.cQmkP;Qo`)0\?[6c_X-g(8qd;)QiD^Lm?)*s+Hn-&"bV;Hdka58W>0$'&aa]CL1>19^`f(CX7g.BFKPN/[J\0nPk^4Pj(Z`7VibG9L_GEkEWOdM2p;$Ae`Z8i,E=.fWK+mLTDaf&N"BnN^\.*c<"^S:K%hL"guRY&n>Nh#[bS-AYih++9G2NiYt?u#1HTskpcT8#I=g`k$D`8Q)g`"IBQe.**JX9?5d#JI>:F_4o7CTYf\/mXL>[4nH(]1`6&eZC0`Ed\RM$>>3E8oq*!pgG)k@o8Tn:36QmG.8PN9:&@H6E=2I/hfnMJ*f0QP2_S4@2!i*3F4lU6I',ctp:-#ls(dZR\a\g/HtjKN8Q@4fP-YI9%ikZEG3an'ZCp&*k5q$!em;Qdb80@)6rMTOmCf=\bCH).(-g$JP23CkJ'::+@.YDr%WLBo=V2T?.(([29dU>M*-CO5=Qe)7/97d%WDT1'jg2SW"H;/RQ+5HJQ[&O&qRAAoRLPg"\bPH*-L280>UTO9"RGdcXZcoZpo<6,uZVH8,[T*6(\O5ZH5-.^KFD?eD7jJ09,JCY#kY]8`5">n1KKM(!S7Zd5&:!0G1%0"7P"2'CjQcW/+Pu?GcdklRB).Qo-4O*m'rZMArs5A&bC8Z9cn'HqidNCg_^+8tB`?`%*&%0so_-DOL)m86\:33>J?A-cQ8id(o=X*`[Mc?ja4-W4oJ!H&d#-l-Y#/poA#H2u?2;q$BeV@B/bHls.B-6s5mk=i+/EI!$:]A]WV/D6!.lpGXJf@SN1<6+0iFm8;'Hcb$gJ;bf]i]ZrH@*!nFJLj-an)nEMhC7RN]]:&$+_~>endstream +endobj +57 0 obj +<< +/Filter [ /ASCII85Decode /FlateDecode ] /Length 1460 +>> +stream +Gatm:9iL(3&A@Zcq?UZD'26+npX4S-cg^'d!aW$KRE4?A2H+jDnS$-tM`'Y4Ef^W/I*Dd2$(7m\kAjBZt.WW@`_%JrHb3@es2)6#\jdr?r""M$r=2WJ6fV=b3'"[Mm?]#(negZkdC)Ug!=/PN5ojWZ,G41=d;3="C6-[;>LiZT_[Y1TX`m6s+s`R7:&I$cEM_JdQ3a]\K/TNhu4AhW.YEn9Fp&H@:_"]B@./N:?D(M\5;nSuAe-(J!7)9VTkQo+<":kE>m1n!;?LVO9aS!Q"pr,2Y0W.u"Pn1n_NJ^ka`)C>V6dU=UB(JP]Qn;Q*F"@YH%RRZF*`7cET*q>RR9a1OB&K?p82L*(7lp;2L@Vo+i%bp=./7J=-*'nr!?k#diP2VaP"phf7n%C/uqZ\#X9:q.pl,acM[[p[K:DX"^5ks#s5R[I(9N\"E2ZK_0O=1@;+P&$pk1`:r%9Ka:lk/-o(+/[siVH6@ppP*K.DY&$ss,&KXO7Bc^4Dd?__/im],.8+'\eKl&*._R1,3<_r,9,.pC,/O2jqjg`;[mo2]7@8d2h0;_eICKr_iU+TeBfn-_('/t2OR[AJi1A`[*eQ<5->7ThCTaK\i:n30832:k`C]u*a+qGqBqc71q6n-hng#s3"8m@:Ei?9DaF@5u9p$j(!Q2-0iFce)co0JG;&l^HCcSoFej.>S+Y#"O*dkeI?lMMZ].(5rWb'-Z+Gi\)^-GCHFA%Y)2ALD<]qh=@,8$LhJ7c5i+Tnh'?/o$a\AgW4lp!l)eP%\s)6Y!,0gDB[&tMip>u*MY-U0fF+X$Es@Bcd`4KRmHKYI*f]#t0*i-`V.C&@bOr\/PI#Cuo5M&2;f5?\_!eem;TTutM4B:\!6Q)+59-hPB?D1?e>1cT3RC_$iBrendstream +endobj +58 0 obj +<< +/Filter [ /ASCII85Decode /FlateDecode ] /Length 1412 +>> +stream +Gatm:92jk1&AI`dqA?ZV`/c1hm"o;ITQXpU^`94$(WGg\)JmMdE\cKY^Fe+K$#Cs+(',E8LXb4V+$L+ta*5S2"Sa3mZR[-q!0RN\OV^=S)(q,JkG.H?Ci<"\EHdsKg0_7p:\`ad_9hqn+GO:bd7P\nAjJ*OIgl&J(m=?Lr+9=98dkC^N$n8aB]OLp77,ThJ*9\K5.pmOh22-.G)*E)1&/X=lB.(O)b+fee'0`Y(5a\:'S[JX"Yc(TJu/12'jR(Hg_aFQQCq*W:r>.tr'M8qc^tT4%IOqalg;<)d>'r./)LVb7=hG+*Q,O@1hT-__8R$bl)sUm!d>1F-&U4N,6:lE)TXVoRTB*).!\HX3:t)^OlA@q03/8ff8oZeaetd"(epe"m^Q&IJ;b%!W\,=SPcM/V-u3ZBB1*43UDOg21uSTcOedSO/tj$u.W%^/%44SIaBIu:s'2m(0k%H<1mLCkaA==RU=KQONCNG.@J&OcI:=#@Gu8C"eLf!*67118)N[du\]I(h(b;RgE<:1[*M"!(&.]\c'+8CgkCSmrH[LTf"i5uQ)GPi]Mb5g&@Q?p^.2/BD\OJnTg@5eOASo5O>,SH0L+L'CH8PinL':s'"=t)(%?59t#ltg&JW^W.#db,^7/u7L(R2mB2O-%+X^AU/liuQ12K--\0+'$-UDI2imNVWclr@Lo69I&VQ'7n6)?0o29EiI\OTmW/)\%?ZC$O.$]/Dq]NsMXdF\gecD#AMD(=GTZDL,Or[>sc<:j2^ZoqJ\9]`o)Pm*(HFd2jrM(&,N!FNGaC0q@`5aDj/q6gWsaeK0LY-3S3ZW_*S!EOT'LR5drW[a*hgh.6b?^FenIBMnGK`hLXQbS/7Rtn:am3N>hgIruMG_)!qV]rh#;VD^0endstream +endobj +59 0 obj +<< +/Filter [ /ASCII85Decode /FlateDecode ] /Length 1192 +>> +stream +Gatm9gQ(#H&:O:SbbGhr),W>"?At]%('T;%].q[!IA*LB`Ec+.P17)2f69]i[(C:H"@_7,,S#+^E9?X\6:;pKr>.?,LCLo.Q69\ilp.ElL!=9*[$a$OcB/88Q6JPSdnTjbH_)D,E,d-l&hbBQ"rb_%;bH@o9PaC6,:C,Hqnah4;S;Ykn=Q#,_o?0$m`INB;1QAN0oNbO^.&>ip-4kh;Z^@KS-T7@]>j1Ga8.]H^]f1%qX(9+T'd8V]/0-?-6fo;s;6](#65,Hta.@Z&QdN^dfr_f=(K5a-?T'[6f0:^Ib;h,]@ep!1)8;H='tBqOi^"K@]FXBmF:tG>f3&0nX=ImP,-gVofi\W'E.Ni2f4@hWoSge(VDm!j4,oNt[)YKRC^UR^23W-a3J2WYA6p)XT2mfs!n[KG'M?ArYa!]d)?dNZspJ5R@dH/JIK-+$Cn"r[kFb38CB37^\\IalU6((9HN%V_g[Jf3mIRMQ>pkbd7-G(i5FI-e]%mti\lo:IVKlp&FTOSCLhlOV57$)u>A[;)9/2T$eIr,h2bQPA<^n->j_(!,46X=6G$&ma&!B`g]X9$LM0.&YBIF15:[ue.=7!dGH*M$JitdWXU"0bW:fW]D8&T17_t<,0H[>VJJklZ7?tQ\q1Ik@uHr%Zf5"BE)aQPT2D3VTPNm$j]15;Vk?KfZt^uoOd"IG^cckSm,eOqU*=o#\F!KO'[)+R>ZZf!O`PlFN+t25X-a#Bj*8AG>9@,)*?fm:YmU]sBN.5eojCL&D]"+,XJs=[[7aaI)\GN2n\nBY#I<]5]ssb&AOt7aj'Q6E#9@.D^m*X_cQ_rB,iFTUKP\1DE[9e*Hmf+\7;5BKfGr#7_4SdSCZqfT0WS'5PFW6(N;PEW6[^Xl;,g@FFA[2WA-t\mL_42B7CLDUkC"&0[3!pEPLnd"?=EC8D*qTs~>endstream +endobj +60 0 obj +<< +/Filter [ /ASCII85Decode /FlateDecode ] /Length 1499 +>> +stream +Gatm:gMYb*&:Ml+%'VB[d3t`,QMaW;D6aT^1tfg*4OeeP-/.?ZVGpI%iP48;b#4D6=_!BdU'jE7S=+FX6Uj8RbT69idD_?qY8FNpV@-jq(X_l0/uL)S:\IR^q]PKnrAZF@T3g4hCi:rqR26&V"gJ;*.iQZa?q`*tHTn:j5;[du?iLLgqfe2Xk/KBX5_[bhErE3(1R!!C>kS/7IU.=i?CmO+m:K!$UVMKKY#0KPR@YJi8@deOGpL-.EOQ;8tZCLJO*.IqBuF#^QtpqWX12mVf#4+)Z"e/EgSS.7\FH=Q([k%Y'@O1s@bpGVF)=WYZnP4VN1A)6c/bmte_7C[C9GcIBTfmF7'k0[@157H^(Oderab1b!E`\l5`4cC4g1Y1D/@cF6GmbMBN]8,B576r**)fk!#/=;@d:!9!oqn-,H@k)b[Eqo3N>AEMo_N`&Frr7b9P2_Ru_")mcYhJP5;_Y>rd;QB9hOGc2X7*m1nQoDo=WQdoIJ6-+ac[X#PQ/T.]V,KWY^?g3#@H&5l?82rnHL-hnt5"RP#S[k:1Tf9Vg2pfUaDI7)@;AI5__6WS]aF@2*a\RGFQI_%lT:9k-F'\E\5RTk.d;#)=ahGcVa_NI411haUWl5jbPT!bGAuBRh4=psnG_(!GClrRfc7sr)+hr_pTm7fC1Z.fE!>P]<5h$?L,a.__oT.c)+4B)hN1icd5.U7TEo@lI"e+\*S;sqs_fk4LTPqF!rLYHFAW'$=@%rU!`bl#\TVmNI@(WGE],(,O",8s?MI%gsif/"5(cl?F=XVhmWsFaQ20uLe57"nY@/E[H/]pm7O__Qe^TXn85[l)4=:4gOq*r^g;C8VGT=4r@BJicSZa&>_J;VVrb-:.+jB14Vmr9$HQpCc;.,(!"Kg]=<0/T#Lm0-ZmJfF7J)8Y>UlE.d%Ad_N`)OYm]f=2]UF%W_Z*s0fKiQgXVC*<`Y*6$MTI"%MaD6*09+r4%hX1(Km+456~>endstream +endobj +61 0 obj +<< +/Filter [ /ASCII85Decode /FlateDecode ] /Length 395 +>> +stream +Gaqcqbtc/1&;9LtME-t0gj!ae*u\O&Z.V]>JiuCLTjXL3Dj-5mcBL%l6pBN"@9W%Y.ccP`endstream +endobj +62 0 obj +<< +/Filter [ /ASCII85Decode /FlateDecode ] /Length 1597 +>> +stream +Gatm:>uTcA'RekGEG,+L*EHtO1Z#SlKdA;Y>;4MBAibgO`*-]p893/NfCqm\!X[\gb`jf$,0T_NHg`srTb-.?qY.8rpf,%aEsaaW@KA;40bfsn]t5hm`U*HdrqI4/EC-B3RuV&?\@qqjaT.rNp#/tW>Ag=9`U*4*MMp.>gjZr)>nnI])aDL*?1'q5+%>'3OH&b!dh/_nt2Oq/Z>33qeF"tO9#-Tc6)LJ-DX;-4@f:0IQl!"^]4A4ZZ);Dtd:b.A;[a*f3UYQ6H@^.N*mQBZO.WgN"B^D3h('1"=_4[G\g<-_[c$X'&(4[tP8qZ3+_F7jL"^IdJYdKpDRQCg`\.pqNJXQrU%IQLl+8=cmKVh-3%e9(7T.aP#ft1d_hE]]Y:)SM4eZiLsVR]>1X1)QDk612]k-[uGn70k$4[h53@>AM/5&DQL,6kJNZHi!s@$N4H&lm7'Q8US(;Q^GTWAT:;`&)u1"f?BDojE;X@/>oLL4*!(fF:pdA^/pTpUQ7T$!`A]!F2F/Mref:[`/%=ga=pM7_PIYX;5m'I7PG?$d0fH0C46SPE-Cp[mKW+NGk_14CXeRg&$LUa]gL7CHF;>Uj4r,BI_nh@IEVhF!bbkc9CSX.[&>dd&MYrPcXRNKhi-=,/NYjRg',6!l^0Gh('ct6(SYTUng()Hjq5TiEJQ\n)T/[=0P4Zf@'3A,-fCMS;qtaerQdIYN;b>1l_*Dh3B)8KhG40%WOUlO0S>rWSdSY?oSr8aSgnfq;>hQf#&;BU%N+g=5PQ\&qfc#s.,L1aBfendstream +endobj +63 0 obj +<< +/Filter [ /ASCII85Decode /FlateDecode ] /Length 1629 +>> +stream +Gatm:gMYb*&:O"Kb[[qL<)Js"fr&YL2F`U2&hir)^k.kA&fZ^-8BQMXlZ\)(P1n_KaJ,mN4#/g/3-3@_$:sD-inpI6pgXVKh['i3/1V9WP/Hi8>V+df^"NB?iudF*AG_n2$u]5=$F(&,V'6dg1W[QB7;Cf>-Hi9J$/j,s=FPnaDnQ$!"b,)[RF9gZAa_]Ol09-BY`PL5%UGRk%;&ku3Q#-:+PhID)*"&/"@#RXeq8p[:O>1"hHap7c5q?@pcFDJNLK[@d?^9P@(@>,5i83-Gn&bF[l2NL*4dK3u&\DDuDcCM$<8;9:qA<#Aqd:k+jCu?9@/Y*N-E454u7-tP++g/t[^<\nq,gU=dm7I2Kp;_j&YjY!_K3[]iY$M;G8F;F1!RuUtM^D`o-e2QDt#cBf]UNh;a\tID;V48o2Kn+$\jJlaaZjMta:b&G]h.$MEC'Q"U`DE5a3'R?\b9PkZ>q7d[?@ASI1Z0'^.7);A$Vo503\4&,A^NpD%T1+K5R0o&Zkg?'<3XT=m]rT9>l(HcGcG8D11k,$Am;\Do"5)+H1AGoUI\p)Vo!bMW@-I%LZgB)>L#EY(g"Km%Dft?%.83b,&![bmQ9Ijn%)Mj7>&)E-_;"na?&?"c6h8HaQ8JoJom59ZK0,@Pt=!Cs!:,G"@oh7"Z7B@u1='&_VAV5]BM.V+*#KQE;W%bPMF.HT]E5W>J1s[K?9_2kHe5RgE>'bnM(ma/q,`&R>?AWfIB,TOAM3BY4jI0\Fk,ekZCs3Z8knGDs)M=2R!#j[s#nW,a`_Y[c#:mA7(0:IM`7-A85#ZCMgcohWe\?2o@sf7Gs]!`T_d0`~>endstream +endobj +64 0 obj +<< +/Filter [ /ASCII85Decode /FlateDecode ] /Length 1794 +>> +stream +Gatm:?#SIW&:ErMfZ3'7Ya4AF,CN2Ud2:JNF,:EU$#lO`g1!d5$7XZt^V&1r&pu?q?8S:@\s:]#@2)nSP$?ATY$W>pulm2;MH2kkY1tdX)rm'>nf`E+/@@;K_;>DB5^AEZ7d#lRG$QUgXcp=ck+0<.4jc>/pVoc1mULDC^-@]Rj,cdolM`KuOt@OtI7q"Lj;Y#_Q5[\ikbN!Z'D.>e37hM^aZT(?&s>9YE:b*S]iOp05%?I6/ZeHcj^DcH+bYZ!\*Y5@GpWCR6lF;+buD=(3;nP"7/OB4p5/`8af>h4T]A?.iOAA!]8C.Bf!G^ghtq]>JU^/K@r`hS_/^2]G^;T4Dfe4]n)\Set4H"djjckf>]f*g(8G^Q"aNSL,O,%p,a:2DZQ@jKJ6rN'dOKbA*&gU0nt68:[3T*+8aDG0hBD2!QLAV&!-0/YV-Ts2PqYgcD_42DHYeh+iN%=TWj582`)L_.T*s+kX`kOmNkajo);l*#/?C%&/a?R-`gT0+8VnZ?,`7a@u2Ouq>R(6aW)@&0*b1jUcIN;(f"A%L9g"dTAjZ+RF'akZ9u8@#"`2E#Fq-C`oC?E'E-n3.*Fp]46KIj0!Pl_WNr07KEg8]@!.Q/(=u`04jn&N$2]r9R#k,pVt1NoYt*jR.)H]qZ63`.#(H;Lr2L5]As%ahe@n8;`E\!S>to\hi:^mZd?k0Cqe?',2o9)MFFf]6*1c.ojd(]g%I]pl#qu"sW*0=fLBqb,=:I>OT:m.=ZDcG!;Ie?deRmE^t=4\!&Jo=6Q:M7rP5RQG$6_-H<`trTC#2":*dGh21)/\N`o"+cbdangdO8\/9L)\Kg"9O0:.JF3IOn"*\+JK622jr:+ggX*s-;R\/TbndU=[ca5tnE.N4@H.T@IZ!j.]lH)L`q%GtP+XQeGegQm`Ui(6$OC-/.m#Jk73+>/I%7Y[gm*F1?/4M&ojArSZERNa4G$QcVpr^C;6Spn\[00"YTZ>0hkTOS)Bl3.hX5L-BPdG?uH[2T:K4j.p$ea4,P\dQ5i:Y5kSoKLZ>DZ/F+"=MQs["`K!VcI!'rRP"trU\T1dj"V;`endstream +endobj +65 0 obj +<< +/Filter [ /ASCII85Decode /FlateDecode ] /Length 1826 +>> +stream +Gatm:mnXl_&H1J#@QqX8h#3MoKPqia&fmegjA_Zal/_1l=i7DUf\WF7^]%j3"Ei2e&5iU``:hK8hn8^M(aAm7rHm3!r'#c-=#%W"ba&fQ/;)Ub>gD1h^Y@"lBk"sMh)Kih^Lfnbia'&>MHQC,+W3"neABTq8IA!dT`<%dH\C'jo_>$qGlLHDi7]a.fGH-TE>D(7,`gpRs"G,c76.2hJ!K'7?.gGP04f,]b!u/O"%T\$5hjnN>IhNn&dq/f!]Jg8D[e7.""gDWdk>\T'X,!](%C@mmF;k/K@2!%RBh3nYM@/7l;:2#eI#>\=86;095PHMWb>)-A]%oU.&&UMY2m@Q8Zbb'e^?c7\?^b>"WO@.S>AFCWg=H%V)SLP*H\uX[Vge>%)1O4PdMp3/>\%HQUV9s:Bj*f1lh+f@lf5k4)T^$[jSmp?IaYA$?-p,_SFUMr7NINK!_u,)-leZ&W7kY>,`u[m/2*i,A,%C+AOX+(05K]cE"?(`V^Pg!pcUHKQVuKc]:\8N$o!mq/P'8PLuI\')$[96[2_'7n#W3H)QZsi1"c$7iip#3c,j&^Y?uOj_$t&(7L`X";\\G#nBuY#2BLrfSFR8,[o*!8;bcH;YR2e-=0?Wi&)8Q=uBMdo0ub'QTg74=CKdtd$N=@Ah>PcHr>9cW%Wem=L]"p,MeXp'_/j`ZBV2(dtCf.$+S+D\jSGk?S;&kYFYm93m_6tSI!]hTi7WhhclJ>/crNpLV%bNse"p)W0Cu8g^]rO!kGQNr>FgPu+P%+"1^T)K^CAG#$T(.BL%*n7(mhj;f0HSM;X2Ve_5>5'%InKaRcYlC=$fmM4jN"G;P1e-7_,nc5dNt0B-"*1b.b`WFHjPj4b(bAchAO]q/H-`rHN[7rsD,Vm*,s,`'6o=U$r)XYN3,]3d>D4ALjZ.!nh-@S:5XRT$5P/%u@cS9WotfCK2#YXLoD='OmI?:s#$6>X'0%NIS@da@ic5=(At\4n1nmbBj^M^GorCZ36CH,ZD$*JtS=V8JZH!f1&KbAG1d.lW9VZY0uenJZIj,*7Fcr?MEN["`j\s(+bI?#Mc@;(+mqPVQhu18E2-27?tMm=?=:E=i\9(=*Yqrj:)7'0^S\F$YMH2+RK4"Wkl/%n,2s\Nq]%%3Zs8B*_4cO6`\;_AUMXDef6[7kA-HiV*1\iuAuJ-MgR-?BJ0Lr'EFBEIE9l]fNoW77qQariunC)bgr%5`a*T5ZLUtSYNW^S4.@L=nW:uD8TR\,5Eh!YRfN`]>T`)FAendstream +endobj +66 0 obj +<< +/Filter [ /ASCII85Decode /FlateDecode ] /Length 1745 +>> +stream +Gatm:;01GN&:X)OfLKsL*GgZDH/k'0R^o5\'Q3caMm-coSh)mb*/FOigQ`5)l#ebP$-<1"V/KG9n,%8qR,D?8hm3[JcS_5B$6b@9>sK530s#SC%iJI*j=oZUm+e4*[H>nK`.,D2"4iT/`FQ<>[F=ar)cW"gK@04Fe`\Y`5VnA%Uh+#)0p55):n5L'^!Nk.9de.o9U5,DdoD=G$Zfap6`it6C*P+tI1YGL7.L10cn\)WK2'U_2;(`;L:,:0b:ZPL'2+,'/e'L.>ZAFeas<`i&"j\ftVY1fCg*6#iJC;08:il^6aOG5XD6-?o\4/6"]^;801'#,MUYElZLf=,[;1gHikbL&"Mr$j&!2[t2Cel^pe`ZXXmVS%%[V6Ks[E&Rs1RKJhKn?!_:^Kp8\Mp,#L)IlTi`5>PNpanBg?i(h'd6T60K,\NEO"/d"[Lbr)dSfcJO_j&Pb+16oacMOj,lO9B@AQ0Gg]_Sl471OLl.nC.dfp"';KSVlc/Hi,n2;E9I`Gc,a&gJUi9f+2%+9CbtsU$&B/WGmkfkP[:1Z68ail*(cCM0.!Qph1[*Yad4LQnGojj<=sd0=;d8Pm0&t3t?PCa?c2J%`UZ=B&""2B.al,ejo,+iguX,SY(89-uQ^k&1gc6;ie<3`0ko9Yt=>*JdBM'FdK3cp;A([ArUiri_['CN6Q(#EX`/NDmhfJX(VZX]8\La9`5lq4W[&37c'6d3s5LK7N^n(JbOcG&7O@JZ":iSF'5[Cgh'dh_C5#u:Ap[4\^Xe2fC:ZWaPT+ns>X@(p-d99\Rd8Z-BHJlb\,6m:$dO5PA,D6WQ)h4PBf`iFPB_`N1p;$s'KW9lc![F@:aD]H-anHgN(8,4%!)qWK2+A;;57N;"\g/?E[m]CG;<4P6GR"h`,_qd%mP'rc=H2W5J-3>F0[X/FI2h#L\PR(!@RC98rk5kVJK[IUeNdlUc0QDX*eX#BD2j"M+:(%LO.7:#t[^)S\HO@TErrD,rl'V~>endstream +endobj +67 0 obj +<< +/Filter [ /ASCII85Decode /FlateDecode ] /Length 1421 +>> +stream +Gatm:?$"^Z'Re<2\<"`AEW(FtBqMsmgIZ%%4)L;M;dP,/A#2MdOpn2%Ia>EQihS/q)$U;(/FLP=k8lXW(pBb4/=/c>cfiokKT_R32'q9r9XDLtO4hL=MqspQhmeN#h)[1b[p/?^A/?kXP:0)%Pi`Q%/a;gL9df^)r-_#?8"0CrJ,b2;qu7?Dm*1G4b"rDqUEiTPMM.RM%l;0]NcInblAMg@FGobpb1d+n\s4lJgh9TE"a;@][RPDAKEC)ot'ZG`;)nMOsP+2s+qNXJ/CIu_##?%GKD'_bME'bFF;(YD:<=lu-HFUnKZhU6tI5\)b0aEBjh3US*]g0>k:`(MJ>aGP$^O[\:]4i$!XDOH=`%$`F!V)2TkKl;)9"u.\E1N2@I$9^OWOYG;s"Q@K-&qX5YO1Ge&@r^&I8TSpH`c6AqVPj5Lc[R6[Be%i8d%EVeTYq=r]i-2U+IDeL7f9ha89kJ\K;Z"VBTD?KL*$o=VjSQO;gHj60XK>f%AoFfQm`^YZ.$h`+"tX5-*Cd.*[MmO5o3!ua+ZP#DE&APU*+bDEEi#(tQ5D')gNrao=&LIUZp05nY,-1HIe/AOE*kGPI3&ij-A2u$bBt)n'Y`gi:%IJUr:g/F5Msb(hqu+1jj!%#H9PN+hDCg9=U30AXBU`q$.uD6"#O`r/70%r(Z!6"#HVL4YXOua]+)RAO;;u#%\,L-#B2%fS;b)Lcj#.qfkn?'/)hQ%[e6Um(5)YP*5Nf1F_Y(CA0emR;H9o8/?XUslLS-*`\QP02=_24*L*;K8Q3d?#p65,SKs4\T+Zi,os$03&a!-TZ@:qDkRn_aj18-*dMZaL=7eK(6,&_dQYEWD0=4l.3)^tZ5"X'2b=S*E#PcR.&]Q$&c.Z(#D\duWMqGa$81Hid&^]_$[C;$8;OGFl3BQ,#-$U"XXGF76_NU#+<,F7*2ESR_ag=\@?9HJ!F+(k1S2$2sptDs'<7+9iP`mEW'`4BKgK1rbfs"s$H>:B=I!?-.tTs$\:g@(F/Tltd2@+(n$r8?-E05endstream +endobj +68 0 obj +<< +/Filter [ /ASCII85Decode /FlateDecode ] /Length 1557 +>> +stream +Gatm:>u03I&:N_CbgTRjLu[qL]H@RB;Q777i/3l6D!Xa!(Ye9DY&SN4rLNIK!!S75Whsd?]sHnG3AW`<\Fe*_^XE8BErqPZ#G)IJ)SFE'+o)IHajJG0rlL*@bal8Y:HuFOhXDIj+3o'n-h(d,7h.s;@'oS).JPXeob`jA+o0("^Jj'!9g#7rUH!@-KS8bTDWK)Uhur]>LAU;[NEc`LraasuQs4*rjSB4th;0D9(H5^U:#Su9ZB_COBT`R='gQJ&phWjV\?XD-Y/f[Ku^i2[?KR\cn"dJ-(WDl9,k,F"D1BK0iNA1M.P1gMuu`&RiN>MV[mG;(jD>\hj232S8_P5V:]\kVTuZr4,O40lOF=b_8`YC)G27A`Jk.hLH;sMW,XOrh%aq530'fdSH="\gW5ts)kssH>5(H-,9rYa$-6b0caG",W8+@ST0b_D2g./k^RF8'r8BLEB:=m#@#=SAKmSZ>.BD.ejB(Eb22ZqYh,@GH?(2mgYqr^.5c@&%9RT+lHRPPh:(pJ29uD_nSkBA\%`]XKEQBY\K%=5$F"=HZ'cie>m[6'V9%E!iD6U4J>-kbQY$a0u*V:AaGggB)_Vl/PY7F?kh<4M#,8-b3Eop:b$Kj\+31Q-51uSUZT4beL`\c'4s1nAB^76\X_([k;gc8MjZn_TXM6N9$o,TIo,$#h=d63g9T?c[T7L4n.:keK(+Nk4-\_1.!TqOr>MV>F5f-iI'Bun8\OO4*a`QW"_:^(QA3Hnc&F2hACLA,IoSp/01m_W_drl.9!KthCdZk"-:nLU+=E(rFPS\[Ob5]-[G,1Yb;Hd,'OjPcm`*L^f,g4OZ1*G1Kn3+Lph.c$k[SQS(*hIn140IbC0=\JA%CUTHJ>!8C)B5G[12&.h0(:-'BI18:b_fM^SF9(.o"HNHd*6hK>~>endstream +endobj +69 0 obj +<< +/Filter [ /ASCII85Decode /FlateDecode ] /Length 349 +>> +stream +Gaqc19htj7&A@P9GfSN?$7tPaaeXbN-=1FHH>0g0MfD&92;3QKYTH?P^_#YQHZ'JR[)@2I*O%?PmKJ8s3C>3l@%M=UZB&h)<2i^#@Xb5u'X:@<1"/]H==u*pc%r@:l:&i.'IhqT]Y^aKqgjQiSt[L3esob$K\f:IMW]bRBmaKn/u;T+-l8ltPUi?W1.ch/aE$"F']__67#TlI'_j!Nmu_cf]]2q4Mb4%K5DD2/PQ%r)tsCB~>endstream +endobj +70 0 obj +<< +/Filter [ /ASCII85Decode /FlateDecode ] /Length 342 +>> +stream +GasbUb>,r/&4Q?hMCYq\8@T_qnUkC!ap'+@=fg7DU!U0R5T54KHcC=Fg2+!q)/ERQa<1+d`a*%q!s4b_j!a'J"S!nPJSPk50Z)-;^VTaH6?#SIBg9~>endstream +endobj +71 0 obj +<< +/Filter [ /ASCII85Decode /FlateDecode ] /Length 1197 +>> +stream +Gat=)9lJcG'YNU14CBg;OXQqf/1[%ekpG.m]82p^fLmj(6sFIQd3YV+m]YLkoas,8)Jg'kP"BZME8J5t7R$g>]B1uuF[d1VN*&?uRTSW>P^TEum,ZpC0XItsWAbp=n^)dX`kK7n\A2``(b@(k4Wr93HO>@XJs>X#Pd7KWIB^o0!-ha):[i7\lN0a6mNmc>A.cW?5n_/tKe/W^adYgbKf6`cD*Zu,/[]D8\ZH#5OcI9(&)V>"Nk$i%EUdO'?%?R@d8IHM[M8@*RM@KTi20a.Xp^;npMN;S"fX@#6/4HZB2bPDMpQgnV9WM%>RTBq6_(U@WffA&*."&jbIs$/$Rnf(grPd_:T%_q[?JjI_NM$p%3AnGb4Xi[#[4p;8:u.Bg2f_?&`&jXZrEA\59t]t.K$ONLol!DC*)$:X23.B6C=CV.P6GlF5t2]DC@UMjTq)b@eF(hj_eEV5qBU;lNhVl?.]h^)IpUHlR>-=qXIf9]`:+$FEm*VLN,\no&#h]GACe-t97k6AJNdX#)a$`kQW.cl@dHCH-R:o^cb\#mHVJUhuXCl:S_q@#T*U6!Hc8jd9lbk0X9cepCTf%oHTjJ.Ji`_(>'?bL0_SUD]@kb2`!X57`775jo`iFqV_j9"00B48he,[?:K_2rG\#_"Y%]i!c8E8oj09.0`?kOV)$~>endstream +endobj +72 0 obj +<< +/Filter [ /ASCII85Decode /FlateDecode ] /Length 1331 +>> +stream +Gatm:9lK&M&A@7.%+'o2A/.sK[WC3J7lNlj\/Q00ab?$/RgVee81K2afCr.JALH?:d@bJ%)BrhVc'pXZ1\1'ErA1L15,E@M_h\J\(;qCMU@aJKe!$\nc-FOMbe7QY*aaYO]lGLQ`a.LY0+;G,`#_$@1jKL].>9srop!mCPlBsls+9:59es]@(sa(]i4V(?73RTI4:.l^9O>f;8Mki/af!Jh355cUq*!rg6"=`rc"$+;3DC8mesU>H6,,+')u[\ROWMXgQuE;MO8\k_)"@0mEIE`kfjY86/4!(\lhD9<-WW@qBVAG_B(crYLCdQI6C@XdShT`0H,LQ(YgE=h@#,!qiO4OEL'O=A-bcJ8\X"7:DWjtuNG@dLDQAL6!trl3!9A)HM>nend9*Z%K^%Z8>(!kVmk=.uHC`EJU3&!3n9AW^i\?Nlm"GP+]msNXOVbWsXC(E-45QpT@iJ>'XEk&mdd%(AMa$4t9sV$kd$1cIHEGsW$e"]NRHSh.eu^bYfi^YB>.>Mk>]:(clRVc&n`1=3B.o$9d;DrFL#4Y:t*:H&`Cj#s1t<9LF5faWg80CV5bV5cY+bB;92EtXMUKeSiDn;<([7MAc40=X[I$*;5MLJ!S'e*$ba[$C@kT.Kh$V;,TkiE;)P1CVpMI/n_VjJ=h4%7*6NTf3WmH^X<\YQk[W(T3$5gb4.ra9!rt*%=]44i8SE1HhAA@>X>cW`ZejYL]f/!F<:efX6MCPc#..O@e*_?qVG<#%;d=3l$@r9*'I6i$`Cd["X/gDUtV;&K9s"'t"]^h,1NHN6G\Ghlte/n\D&RhSpjO;-!Q8;hJH2l0bNeKVKRY*F0Q6#J>.@@V3Y=J_)/K?aC.A]6l2d^u'iKAC5?%endstream +endobj +73 0 obj +<< +/Filter [ /ASCII85Decode /FlateDecode ] /Length 644 +>> +stream +Gaqc3?#Q2d'Rf.GSB%d)?#1Y!;q+G*1hiE.M((*)1#N2SV"WHNt?R=5EU)hY!=8IbNbm#oSG\26CfP#3.;>#_(^%$!rL*#.Efk7^(B(e5hTHYc.9)^dUt]U*0b$l_f#GBDQeG_%nD::M*f#F-_\-?dL1R=Of0S4lG.@Zs'kVAh_f)lNUGNHi!.e+k`V1ocNG*):=i!Bd-!B/+&#&&.>MDUc*2h3=N4J;"opF*GPa\:WCtch*kJaAI--@pj3%G\bjnd&Wr.0p*31o2b6T;=.\]&##%H>bDarAEiB3`(?Pb]c-c;0'_SY/9.@NP#saF3JO;N*M3+6Fpq0b,8b$XCu<>=9_p_$cofEQ&MIa0pJ28p'.1$P/bALJ^IF%Y!YCah*W~>endstream +endobj +xref +0 74 +0000000000 65535 f +0000000061 00000 n +0000000158 00000 n +0000000265 00000 n +0000000377 00000 n +0000000492 00000 n +0000000687 00000 n +0000000882 00000 n +0000000992 00000 n +0000001187 00000 n +0000001382 00000 n +0000001491 00000 n +0000001601 00000 n +0000001797 00000 n +0000001993 00000 n +0000002189 00000 n +0000002385 00000 n +0000002581 00000 n +0000002777 00000 n +0000002861 00000 n +0000003057 00000 n +0000003253 00000 n +0000003449 00000 n +0000003645 00000 n +0000003841 00000 n +0000004037 00000 n +0000004233 00000 n +0000004429 00000 n +0000004625 00000 n +0000004821 00000 n +0000005017 00000 n +0000005213 00000 n +0000005409 00000 n +0000005605 00000 n +0000005801 00000 n +0000005997 00000 n +0000006193 00000 n +0000006389 00000 n +0000006585 00000 n +0000006781 00000 n +0000006977 00000 n +0000007047 00000 n +0000007359 00000 n +0000007636 00000 n +0000008321 00000 n +0000009036 00000 n +0000009423 00000 n +0000010361 00000 n +0000011777 00000 n +0000012683 00000 n +0000013138 00000 n +0000014687 00000 n +0000015080 00000 n +0000016317 00000 n +0000017753 00000 n +0000019204 00000 n +0000020790 00000 n +0000022526 00000 n +0000024078 00000 n +0000025582 00000 n +0000026866 00000 n +0000028457 00000 n +0000028943 00000 n +0000030632 00000 n +0000032353 00000 n +0000034239 00000 n +0000036157 00000 n +0000037994 00000 n +0000039507 00000 n +0000041156 00000 n +0000041596 00000 n +0000042029 00000 n +0000043318 00000 n +0000044741 00000 n +trailer +<< +/ID +[] +% ReportLab generated PDF document -- digest (opensource) + +/Info 41 0 R +/Root 40 0 R +/Size 74 +>> +startxref +45476 +%%EOF