A traditional Meccan or Medinan classification. It is not presented as an exact day or year.
Read the words.
Follow the context.
Move from the verified Arabic text to reviewed historical context and precise Bukhārī or Muslim references—without asking AI to invent the bridge.
What the metadata can safely say.
Traditional revelation order metadata, distinct from the Sūrah’s position in the Muṣḥaf.
24 rukūʿ divisions in the current metadata record.
Why there is no automatic “revelation date.” A Sūrah may include passages revealed across more than one event, and reports can differ. Exact timing and reasons appear only inside claim-level, human-reviewed records below.
Context is a record, not a generated tale.
Every published claim carries its own source locator, reviewer, and correction path.
The reader remains open, but Quraan Journey will not fill this space with model memory, folklore, or a simplified “reason” that the evidence does not support.
Two collections. A deliberate order.
Ṣaḥīḥ al-Bukhārī is checked first, followed by Ṣaḥīḥ Muslim. A connection publishes only with exact reference metadata and an approved source-access record.
Ṣaḥīḥ al-Bukhārī
No licensed, human-reviewed connection for this Sūrah is public yet.
Ṣaḥīḥ Muslim
Checked after Bukhārī, with the same exact-numbering and review requirements.
Guide the journey. Never author the religion.
AI may route a question to an exact ayah or an approved record. It does not compose Qur’an, Hadith, tafsīr, revelation stories, or rulings.