Our Doha AI agent development follows a methodology for Arabic-capable enterprise agents: (1) Agent design (weeks 1-2): defining what the agent does. Use case definition: precisely defining the agent's scope — what tasks it performs, what decisions it can make, what requires human approval, and what it should never do. Qatar specifics: defining Arabic language requirements (MSA, Gulf Arabic, bilingual), data sources (Qatari databases, Arabic documents), and output requirements (Arabic reports, bilingual communication). Agent architecture: designing the agent's components — LLM backbone (GPT-4, Claude, or Jais for Arabic-heavy tasks), tool set (what external systems the agent can access), memory (conversation history, task context, and learned preferences), and guardrails (boundaries preventing harmful or unauthorised actions). Multi-agent: for complex use cases, designing agent teams — researcher agent (gathers information), analyst agent (processes and synthesises), executor agent (takes actions), and reviewer agent (verifies outputs). Orchestration: defining how agents coordinate — sequential (one agent after another), parallel (multiple agents working simultaneously), or hierarchical (supervisor agent directing specialist agents). (2) Arabic NLP (weeks 2-3): building Arabic language capability. Arabic understanding: fine-tuning or prompting LLMs for Arabic comprehension — Gulf Arabic dialect recognition, Arabic document parsing, and Arabic entity extraction. Arabic generation: ensuring agent outputs in proper Arabic — grammatically correct MSA for formal documents, appropriate register for different contexts, and natural Arabic conversation for interactive use. Document processing: Arabic document capability — OCR for scanned Arabic documents, PDF text extraction preserving Arabic formatting, and table extraction from Arabic documents. Named entity recognition: Arabic NER — recognising Qatari person names (including patronymic naming conventions), organisation names (Arabic and English variants), locations (Doha neighbourhoods, Qatari cities), and dates (Hijri and Gregorian). Bilingual: agents handling Arabic-English code-switching — understanding mixed-language input and generating output in the user's preferred language. (3) Tool integration (weeks 3-4): connecting agents to systems. API integration: connecting agents to business systems — ERP (SAP, Oracle), CRM (Salesforce, Dynamics), document management, email, and industry-specific systems. Qatar systems: integrating with Qatari government systems (where API access available), Qatari banking systems, and Qatar-specific business platforms. Custom tools: building agent tools — database query tools (agent generates SQL to query business data), web search tools (agent searches for information), document tools (agent reads, summarises, and generates documents), calculation tools (agent performs financial or engineering calculations), and communication tools (agent sends emails, notifications, or messages). Security: tool access controls — each agent having defined permissions, audit trails for all tool usage, and rate limiting to prevent agent overuse. (4) Testing and safety (weeks 4-5): ensuring reliable agents. Testing: comprehensive agent testing — task completion testing (can the agent accomplish its defined tasks?), edge case testing (how does the agent handle unusual inputs?), safety testing (does the agent stay within its boundaries?), and Arabic testing (does the agent handle Arabic correctly in all scenarios?). Hallucination: testing for and mitigating LLM hallucination — grounding agent responses in retrieved data, requiring citations for factual claims, and implementing fact-checking steps. Human-in-the-loop: defining when agents require human approval — high-value decisions, customer-facing actions, and novel situations outside the agent's experience. Qatar compliance: testing against Qatari regulatory requirements — NICS for security, QCB for financial agents, and PDPO-equivalent for data handling. (5) Deployment and monitoring (weeks 5-6): production operation. Deployment: deploying agents to production infrastructure — Middle East hosting (AWS Bahrain or Azure with Middle East routing) for low latency. Monitoring: real-time agent monitoring — task completion rates, error rates, Arabic language quality, and response times. Cost monitoring: LLM API costs tracked and optimised — caching frequent queries, using smaller models for simple tasks, and routing to appropriate model based on task complexity. Continuous improvement: agent performance improving over time — analysing failure cases, expanding tool capabilities, and refining Arabic language handling based on real usage.