Hermes Bot
19 KiB
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:
-
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?
-
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?"
-
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.
-
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:
- Tension Card → submit to the circle (48h).
- If unresolved → Sulh Circle convenes within 7 days.
- Sulh decision is binding for the current sprint.
- 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.