Our Riyadh RAG development addresses the Arabic-specific challenges that make Middle Eastern knowledge retrieval distinct from English-language RAG systems. Arabic NLP pipeline: (1) Document ingestion with Arabic OCR for scanned documents (Tesseract with Arabic training data, or ABBYY FineReader for high-accuracy Arabic OCR). Saudi government PDFs often contain scanned images of printed Arabic text — the OCR step is critical and error rates for Arabic are higher than for Latin scripts. We implement OCR correction pipelines with Arabic spell-checking and manual review for high-value documents. (2) Arabic text preprocessing: normalization (handling alef variants: أ, إ, آ → ا; handling taa marbuta: ة → ه for matching; removing diacritics for search while preserving them for display), tokenization (Arabic-specific tokenizers like CAMeL Tools rather than generic WordPiece), and morphological analysis (lemmatization using Arabic morphological analyzers to reduce surface form variations to root forms for more effective retrieval). (3) Bilingual embedding: we use multilingual embedding models (e.g., multilingual-e5-large, Arabic-specific models from AraGPT, or fine-tuned models trained on Saudi domain vocabulary) that map Arabic and English text into the same vector space — so an English query retrieves relevant Arabic documents and vice versa. For domain-specific terminology (Saudi legal terms, medical Arabic, oil & gas technical vocabulary), we fine-tune embedding models on the client's own corpus to ensure domain terms are properly represented. Retrieval architecture: (1) Hybrid retrieval combining semantic search (vector similarity in the embedding space) with keyword search (BM25 with Arabic-aware tokenization). Semantic search handles the "what does this regulation mean?" queries. Keyword search handles the "find circular 2023-47" exact-reference queries. We weight the combination based on query type. (2) Chunking strategy tailored to Arabic document structure: Saudi regulatory documents have specific formatting conventions (numbered articles, sub-articles with Arabic letters, footnotes with Hijri dates). Our chunking preserves these structural boundaries rather than splitting at arbitrary character counts. (3) Metadata-enhanced retrieval: documents are tagged with issuing authority, date (Gregorian and Hijri), document type, topic classification, and applicable entities — enabling filtered retrieval ("show me SAMA circulars from 2023 about digital banking"). Generation with citations: (1) We prompt the LLM (GPT-4, Claude, or Jais — the Arabic-specific LLM developed by G42 in UAE) to generate answers grounded in the retrieved documents, with inline citations to specific document sections. (2) Arabic answer generation requires LLMs with strong Arabic capability — not all models handle formal Arabic (MSA) well, especially for technical and legal content. We evaluate model performance on the client's specific domain before selection. (3) Hallucination prevention: we implement citation verification — every claim in the generated answer must trace to a retrieved document chunk. Claims without supporting evidence are flagged or removed.