Why ship JSON instead of committing quran.sql?
JSON is canonical in repo because large SQL dump exceeds practical Git workflow limits. SQL stays local, conversion is deterministic, verification checks counts and shard integrity.
Hosted API access is disabled on `al-quran-database.vercel.app` for now. Use the repository locally or self-host this project to run the API endpoints documented here.
FAQ
Product, dataset, conversion, and interpretation policy questions from one canonical knowledge file.
How do I prove JSON matches quran.sql?
Run `npm run data:verify -- --check-determinism`. Script re-counts source SQL tables, validates generated manifests, and compares regenerated file hashes.
Do you support translations, tafsir, transliteration, and audio together?
Yes. Edition metadata is normalized, while ayah-edition content is sharded by identifier. Same loader resolves translation, tafsir, transliteration, or audio references.
Is scientific miracles data treated as absolute proof?
No. Repository models them as interpretive references with caution notes, not as forced scientific certainties.
How should legal-ruling data be used?
As research metadata and navigation aid. It should not replace qualified fiqh study or madhhab-specific legal guidance.
Can I extend knowledge coverage to all ayahs?
Yes. Add curated entries into `knowledge-base.json`, rerun tests, regenerate exports, and update docs coverage counts.