Skip to content

The epistemic boundary

One honest thing must be said, or the whole vision curdles into arrogance.

A machine does not issue a fatwa. It cannot tell you what is halal. That knowledge lives with scholars, with the long, breathing tradition of fiqh, with people — not programs. Fiqh is not a rigid code: it differs between madhāhib, it bends with circumstance and custom, and it holds room for mercy and for necessity. No compiler can replace that, and the serious version of this work does not pretend to.

What a machine can do is humbler, and still worth building: take the rules a qualified human has authored and cited, and guarantee — every single time, identically, for anyone to verify — that a contract is consistent with them.

Deducible proves consistency with a rule-base. It does not establish legitimacy.

It does not decide the law. It refuses to let the law be quietly broken between the signing and the running. It closes the gap between what was promised and what is delivered.

  • It does not declare any contract halal or haram. A green check means “consistent with the selected rule module” — nothing more.
  • It does not originate rulings. Citations in diagnostics are flagged for verification by a qualified scholar; they are pointers to the tradition, not pronouncements.
  • It does not resolve khilāf. Where schools differ, the difference lives in the rule module, chosen openly — not hidden inside the engine.
  • The natural-language drafter (deducible nl) proposes; the formal engine disposes. An LLM never has the last word on compliance.
Layer Who owns it
The rules, citations, and their soundness Qualified scholars / standards bodies
The faithful, mechanical enforcement of those rules Deducible
The legitimacy of an instrument for a given person A qualified local scholar

For anything weighty or actionable in worship, transactions, or family matters, take the question to a qualified scholar. A compiler’s checkmark is evidence of consistency, not a substitute for a ruling.

Allāhu aʿlam.