Write the fiqh basis document: what rulings are encoded, and their sources

[eaitbrahim]

This is the document that converts "someone's trading bot" into something a Muslim developer will trust, and it does not exist. Right now the fiqh reasoning is spread across code comments (guards.py rail 17 on §65.4 qabd, screen.py on sector and backing, the DOGE issuance discussion in the run log). A reader cannot assess the basis without reading the source.

What it must contain

• Which rulings are encoded, each with its source — §65.4 qabd / constructive possession behind rail 17, the riba screen, the sector and backing axes, why pays_yield is about a bare holder rather than "staking exists"
• What is attested versus what is derived. Nothing about sector, backing or yield is derived from price data — that is the core claim and it should be provable from the document
• What keel deliberately does not decide — the boundary from the Phase 6 positioning issue
• Known open questions, stated rather than hidden. The uncapped-inflation-accruing-only-to-stakers question raised against ATOM is a live example with no settled answer here
• How to disagree: local attestation and documented exceptions, and what that means in practice

Standard

Cite sources the way the codebase already does — verbatim quotes with a fetchable reference, and "not stated" where a source is silent. Do not paper over disagreement between schools; name it.