Hermes Bot
8.3 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.