Share Economy

Every contribution is a transaction on an open ledger. Every task carries a rate. Every reward is provable from git history. No off-ledger work, no shadow contribution, no opaque allocation.

This page is the contract between Databayt and its parties. The doctrine is the lineage. The CU spec is the measurement.

Every form of contribution is measurable, owned, and compensated; the value of the company is the sum of those contributions — never extracted from them.

The operational primitives

The contract executes on seven primitives that already exist in our toolchain — none invented for this purpose:

You don't need an employer, a salary negotiation, or permission to start. You need a GitHub account, a clean PR, and patience to refine through review. The toolchain — git, GitHub, CI — is the smart-contract VM.

Akbar (Ummatics 2024) names exactly what this contract is for: "The Umma can only be created through ḥuqūq — revival requires that its members understand and exercise their rights." Where neoliberalism centers economy and leaves a vacuum over the role of governance, Qaṣ al-Ḥaq fills that vacuum with ḥuqūq as the centerpiece. The primitives above are the rights structure that fills the same vacuum at the company scale.

The smart-contract framing

A smart contract — in the structural sense, not the blockchain sense — has three properties. Databayt's share-economy has the same three:

What this is not: not on-chain, not a token, no blockchain, no NFTs, not autonomous-agent governance. The contract is enforced by license, ledger, and custody — not by a Turing-complete VM.

Akbar (Ummatics 2024) names three concrete failures of capitalism that the contract structurally prevents: exploitation → prevented by Clause 1 (Shirkat al-A'mal — contributor-as-owner); worker–owner separation → prevented by Clause 1 (the same — contributor is the owner, not labor); supply-chain pollution / harm to commons → prevented by Clause 5 (anti-darar, anti-dirar).

The five parties — Akbar's three claims × five forms of submission

Akbar's framework (MIT 1984; Crisis in the Built Environment 1988) names three claims any party can hold over a productive resource — ownership, control, use — combining into five forms of submission. All five exist across the databayt org today:

A sponsor, contributor, customer, or partner is always operating in one of these five forms. The contract attaches different clauses to each.

The contract — five clauses

Each clause names what is agreed, how it is enforced, and which Islamic primitive grounds it.

Clause 1 — Contribution is measured, owned, compensated. (Shirkat al-A'mal — شِركة الأعمال — partnership of labor.) Every contribution accrues Contribution Units by a public formula across hogwarts, mkan, souq, shifa, and future databayt products. CU is the contract's accounting unit. Honest divergence from the classical structure: contributor downside is capped — operational losses are absorbed by the operating reserve, not redistributed pro-rata. Enforced by: the CU ledger in the hogwarts CU spec, generalised per-product as products graduate from R&D.

Clause 2 — Sponsored builds split profit by pre-agreed ratio. (Mudaraba — مضاربة — silent partnership.) A sponsor (rabb al-mal) commissions a custom build; Databayt (mudarib) executes; profit shares by a ratio fixed at contract formation. Loss falls on the capital provider unless the mudarib acted in negligence. Applies to custom builds across all databayt products — not to SaaS subscriptions, per-student / per-vendor pricing, or free pilots. Enforced by: standard Mudaraba contract template (Samia, Q3 2026 → databayt/revenue).

Clause 3 — 5% of revenue is custodied for the commons. (Waqf — وقف — perpetual endowment.) 5% of revenue across all databayt products is administratively segregated into a Community Pool (waqf-track) the moment MRR exists. The pool matures into a formal waqf when three triggers fire: (1) MRR ≥ $10K/month sustained 12 months; (2) legal-entity registration in a waqf-compatible jurisdiction; (3) external counsel on the nazir arrangement. Purposes: open infrastructure, contributor scholarships, emergency support, education in Arabic-speaking regions. Quranic anchor: al-Hashr 59:7 — كَيْ لَا يَكُونَ دُولَةً بَيْنَ الْأَغْنِيَاءِ مِنكُمْ — wealth must not circulate only among the wealthy. Enforced by: bookkeeping segregation today; legal instrument when triggers fire.

Clause 4 — 2.5% of net profits funds contributors in need. (Zakat-aligned — صندوق العون / Needs Fund.) We adopt the 2.5% rate, the redistribution intent, and the structural-obligation principle — but we call it the Needs Fund, not zakat, because zakat in classical fiqh is an obligation on individual Muslims, not on corporations. Recipients: contributors in conflict zones (Sudan, Yemen, Gaza-region) whose work is disrupted; medical / displacement emergencies; new contributors below the pay-floor; education-cause grants. Quranic anchor: at-Tawbah 9:60 — the eight categories of zakat recipients; the Needs Fund draws from but does not exhaust these categories. Enforced by: published beneficiary policy + audit trail.

Clause 5 — No extractive use; no gratuitous harm. (Darar / dirar — ضرر / ضرار — Akbar 1999.) The Prophetic tradition "لا ضرر ولا ضرار" names two distinct harm patterns; the contract enforces them with two distinct mechanisms:

• Darar — extractive harm (actor benefits at others' expense). SSPL prevents this — a closed competitor cannot resell databayt code commercially without contributing back or paying a commercial license.
• Dirar — gratuitous harm (actor harms without even benefiting). Trademark policy prevents this — a bad-faith fork cannot misuse the "Hogwarts" / "Souq" / "Mkan" / "Shifa" / "Databayt" names to mislead users.

Two harm categories, two policies, two mechanisms.

The five Khedr clauses — partnership formation

د. محمد حسام خضر (Cairo University engineer; MBA Universitat Autònoma de Barcelona 2017; DBA 2025) is a practitioner, not a theorist — ~28 years of operating MENA companies including Internet Plus (founded, still operating), ألعاب شمس (Sun Games, acquired by a larger firm), Managing Partner at Endure Capital, active angel investor in MENA startups. His book رائد الأعمال Inside Out (2019) names five operational requirements that every Databayt partnership pre-commits to before the first commit. The five clauses below are the patterns he has seen prevent the most common failure modes:

The first Databayt contributor agreement — triggered when MRR ≥ $3K and the hiring phase opens — follows this five-clause shape.

How the contract executes — Akbar's three mechanisms

The contract is not a static document; it executes through three Akbar-named mechanisms (Rationality, 1999) that map 1-to-1 onto open-source practice:

• Collective solution-seeking → pull requests, RFCs, issue discussions across all databayt repos
• Action precedes permission → fork-then-PR culture; the OSS "show, don't ask" norm
• Refinement through conflict → code review iterations as productive friction

The codebase is the open laboratory; conventions evolve through use, not by decree. "Conventions cannot be made, they evolve" — Akbar, 1999.

Hard core, protective belt — what's immutable, what evolves

Akbar's Lakatosian framing (Rights and Civilizations, 2019) treats Huquq as a research program with a hard core and a protective belt. The Databayt contract has the same shape:

• Hard core (immutable across versions): justice = fair access by evidence of contribution. The contributor-as-owner posture. The four primitives. The two-harm distinction. The five-form taxonomy of parties.
• Protective belt (mutable; evolves through use): the CU formula weights, the $45/hr floor, the anti-gaming controls, supermajority governance, vote caps, founder-power decay, pool sizing percentages.

The hard core is the smart-contract constant. The protective belt is the parameters the parties re-tune through proposal, simulation, public discussion, and supermajority vote.

Where each clause is enforced

The "today" rows operate at company scale. The "Q3 2026" rows are the operational templates Samia is formalising in the (not-yet-created) databayt/revenue repo. This contract does not pre-commit those templates; it names the slots they fill.

What this contract is NOT

• Not on-chain. No blockchain, no tokens, no NFTs, no smart-contract VM. The "smart contract" framing is structural — public rules, self-execution, code enforcement — not technological.
• Not autonomous. Disputes go to humans: three-maintainer review within 7 days, 67% supermajority for core-valuation changes, external arbitration for major disputes.
• Not a Sharia-compliance certification. We name the Islamic primitives as posture and vocabulary. Formal Sharia review of specific products and contracts is a separate professional process.
• Not a fatwa. We are a software company, not a religious authority.
• Not a political program. NMBD references are economic-philosophical only.
• Not the operational spec. CU formulas, contribution matrix, founder reserve %, conversion-to-cash mechanics — those live in the hogwarts CU spec (measurement layer) and in Samia's Q3 2026 framework (operational layer). This page is the contract that names what is enforced; the operational documents say how.

References

Akbar, J. — جميل عبد القادر أكبر. Responsibility and the Traditional Muslim Built Environment (MIT PhD, 1984; the three-claims framework). Crisis in the Built Environment (1988; five forms of submission). Rationality: Blight of the Muslim Built Environment (1999; three mechanisms; darar/dirar). قص الحق (Qas al-Haq, 1st ed 2014, 2nd ed 2022, 1,800pp). Rights and Civilizations (2019; Lakatosian hard-core / protective-belt framing). Property Rights (Ḥuquq) and Civilizations (2023; most accessible English summary). Ummatics colloquium 2024 — Umma-through-Huquq, neoliberalism vacuum, three concrete capitalism critiques (exploitation / worker–owner separation / supply-chain pollution), Quranic anchors (al-Hashr 59:7 · at-Tawbah 9:60 · al-Anfal 8:41).

Khedr, M.H. — د. محمد حسام خضر. رائد الأعمال Inside Out (Dar Don, 2019; ISBN 9789778061598). إضاءات review · YouTube خضر و بزنس · ratteb.com.

NMBD — الحركة الوطنية للبناء والتنمية. ورقة الاقتصاد التشاركي (Participatory Economy Paper). Bennabi, M. — شروط النهضة (1949); وجهة العالم الإسلامي (1954). Hajj Hammad, A.Q. — المنهجية القرآنية.

Islamic-finance primitives. Iqbal & Mirakhor, An Introduction to Islamic Finance (Wiley, 2011). AAOIFI standards. Cizakca, A History of Philanthropic Foundations (2000).

See also

• Doctrine — kun/docs/SHARE-ECONOMY-MODEL.md (the full 579-line lineage and references)
• Measurement layer — hogwarts/content/docs-en/shared-economy.mdx (CU formula, contribution matrix, anti-gaming, governance)
• Captain — /docs/captain (the CEO brain that grounds share-economy decisions in this contract)
• Team — /docs/team (Samia owns the Q3 2026 operational framework)
• العقد بالعربية — /docs/share-economy.ar — Arabic mirror, synced to the smart-contract framing