Chain of Custody: Data Provenance and Fidelity Boundaries in AyatFlow

When institutions, educators, or creators use a tool to generate Quranic content, typography is secondary to one critical requirement: trust.

The first trust question is simple: who is the source of truth?

For AyatFlow, Quranic text authority is upstream. We do not claim to verify or authenticate revelation ourselves. We claim something narrower and operationally testable: transparent provenance and faithful rendering.

First Principle: Verification vs Fidelity

Quranic textual verification belongs to canonical scholarship, publishers, and the data source itself. In AyatFlow's current stack, that source is Quran.com via its API.

AyatFlow's responsibility is different:

1. Provenance clarity: state exactly where the text comes from.
2. Fidelity in transit: avoid manual rewriting/paraphrasing in the pipeline.
3. Deterministic rendering: preserve correct shaping and layout at export time.

Source of Record in AyatFlow

1. Arabic Quran text

AyatFlow consumes Quranic Arabic text from the Quran.com API and stores it for recall-first search and rendering. We do not manually type, rewrite, or "improve" verse text.

2. English translation (current default)

AyatFlow currently uses the Saheeh International translation from Quran.com for consistency across search and exports.

3. The 99 Names dataset

For Asma-ul-Husna outputs, AyatFlow provides a curated, widely transmitted enumeration for creator workflows. We explicitly label this boundary in-product: "A widely transmitted enumeration of the 99 Names."

This is presented as a practical reference artifact, not a claim of definitive theological adjudication.

Chain of Custody in Practice

From query to downloadable image, the flow is intentionally constrained:

1. Intent routing in the Omnibox (citation, Surah, topic, or name).
2. Retrieval from sourced data already ingested from Quran.com.
3. Rendering through browser-grade shaping in the generator engine.
4. Export as a deterministic artifact with no manual glyph editing.

You can inspect that output path directly by opening a render state such as 2:255 in dark story format.

What AyatFlow Does Not Claim

• We do not issue fatwa, tafsir, or theological rulings.
• We do not claim to replace a Mushaf or qualified scholarship.
• We do not claim independent authentication of revelation sources.

AyatFlow's promise is narrower and deliberate: preserve trusted source provenance and deliver typography that remains faithful at the point of sharing.