DG council

Person #2: Can you all hear me? Hello? I think we're live. Person #34: Yes, we hear you. Good morning, everyone. Person #2: Good morning, good morning. And I believe the Chairman is joining us shortly. He said he had a quick thing with the Executive Council office first. Person #9: Morning. I'm here. Coffee's on. Whoever— okay, we're good. Person #24: Good morning. Saadat, good morning. Yes, we're all here. Person #2: So the agenda today is the World Governments Summit narrative. February is coming, and the Chairman has asked for a consolidated story around AI-native government. We have about forty-five minutes, we'll go around and then we'll see if he wants to jump in. I know he has to step out by quarter to eleven. Person #34: That's fine. I've got a hard stop at 10:40 anyway for the cloud steering committee. Person #35: You mean the one we moved from Wednesday? Person #34: Yes, the one we moved. Because of the— anyway. Fine. Person #2: Shall we start with framing? I'll take the first minute. Look, we've been reporting to ADEC every quarter on the Digital Strategy, and the feedback has been— honestly, it's been good. But the Chairman wants the World Governments Summit to be the moment where the world sees Abu Dhabi not as a government that uses AI, but as a government that thinks AI-native, operates AI-native, and— this is his word— Person #9: Embeds. Person #2: Embeds" AI into the operating model. Yes. Not just services. So the narrative we bring to February needs to show the full continuum. From the sovereign cloud, to the data platform, to the common applications, to TAMM, to workforce enablement and talent. And we need to frame it as a coherent story, not as a collection of sector achievements. Which is, as you know, a challenge. Person #24: If I can make a comment, Saadat. The risk is we go to the Summit and we talk about infrastructure and platforms, and the audience— the heads of state, the ministers, the CEOs— they want to see what it feels like. They download TAMM. They type in something. They see a journey that works. That's the story. Person #34: And they will. We're demoing TAMM 4.0 at the Summit. We're doing the AI assistant, the journeys with DoH and ADEK and DMT. But I agree with you, we need the connective tissue. The cloud story alone is not something you lead with in a five-minute keynote. Person #35: If I can add— and I know I'm biased— but the sovereign cloud story is actually more important than the app demo when it comes to the international audience. The GCC, the Europeans, they all want to know: where does the data live? Who has access? What's your sovereignty framework? We have a real answer there, and it's not something most governments can say. We've exited two legacy data centers, we're on track for the third wave by March, and we're running forty-two percent of entity workloads on the sovereign platform as of last week. That's a number. Person #2: That's a good number. We should use it. But let's hold the content discussion for a moment. I want to first agree on the structure of the narrative, and then we can fill it with the numbers and the demos. Person #10: Let me challenge you, Saadat. Do we need a structure? Or do we need a sensation? The World Governments Summit is about emotion. It's about the moment where someone says, "I didn't know a government could do that." If we go with a clean, logical structure, we lose them. We need a moment. A world-first moment. Person #2: I agree, we need a moment. But the moment has to sit inside a structure, or it's just a firework. The Chairman wants last year's message to be different. And I'll be honest, last year was— fine. But it was fragmented. Person #9: I wasn't there last year, but I've seen the footage. It was very— sectoral. Each of you had your booth, your panel, your pitch. The Chairman watched the opening and said, "This is not one government. This is six governments. Person #34: That's exactly right. And we didn't even have six booths, we had about twenty. Everyone wanted their own shelf. No— we've talked about this internally, but I'll say it here: we need to kill the sector booths. Person #10: No, no. Not kill. Curate. We can't have the whole government in one booth. It gets cluttered. But we can have a journey. The human journey. Someone walks in, they see a life event, they experience the journey, and behind it they see the platform that makes it possible. That's the structure. Person #24: And TAMM can be the front door for that. The journey— from a new parent to a new business owner to a visitor— TAMM is the front door. Person #35: But the front door has to open. We had— look, we had two incidents last week. I don't want to be the guy who kills the vibe, but between the GITEX demo and now, we had a four-hour partial outage on the payment gateway last Tuesday. The media didn't pick it up, but the app rating dropped to four point two. Person #24: It was not a TAMM issue. It was the DoF sandbox integration. We were— the test environment was not properly synced, and the payment gateway in production picked up the test configuration. It was an entity-side change. We had it resolved in three hours fifty minutes. Person #35: It was unplanned. That's my point. It was an unplanned change by a vendor with access to the integration layer. And we've been trying to get a change freeze for the last month, but we keep getting overruled because of "business urgency". I'm not saying it's TAMM's fault. I'm saying the story we tell at the Summit has to be true, and if we have another incident like that in February, the story dies. Person #2: That's a fair risk. And we'll address it. But let's not get stuck in the operational weeds right now. We have time for that later. We have about— we have the Chairman coming. Let's use this time to get everyone aligned on the narrative shape. I want to propose something. Person #9: Propose. We're listening. Person #2: Three acts. Act one: the "Why." Why Abu Dhabi, why now. The strategy, the ambition, the AI-native vision. Act two: the "How." The platform, the cloud, the data, the common systems, the workforce capabilities. Act three: the "What," which is the live experience. TAMM, the journeys, the AI assistant, the Copilot deployment. And we weave the outcomes through all three. Not as a separate section, but as the throughline. Person #10: I would add a fourth act: the future. The "What's next." Because the Summit audience is not buying the present, they're buying the trajectory. If we can show them where we're going— the 200-plus use cases, the frontier models, the workforce of the future— that's the hook. Person #2: I love that. Acts one, two, three, and a coda for the future. That's the structure. Good. Person #34: And who writes the narrative? Who owns the words? Because I've seen this before, six sectors, six drafts, and the final document is a Frankenstein. We had that with the Digital Strategy last year. It took three rounds of harmonization. Person #2: Don't remind me. Okay. I'll set up a narrative working group with one representative from each sector. Communications will have the pen. And I'll chair the group personally. Friday afternoons, starting next week. Person #9: Friday afternoons? Saadat, Ramadan is coming. Person #2: No, not for another— Ramadan is in February this year. It starts around the seventeenth, if I'm not mistaken. And the Summit is on the ninth, tenth, eleventh. So we have until the Summit, then we have Ramadan. Friday afternoons are fine until then. Person #9: Oh, that's right. I keep forgetting the calendar. My team is still planning for "Q1 deliverables" like it's a normal quarter. Person #11: It's in the ADEC planning calendar. The Summit, then Ramadan, then Q2 planning starts. We sent it out in June. Person #9: Did we? Good. I'll tell them. Person #2: Okay. So the working group. Each sector sends one senior person. GovDigital, TAMM, Talent, GovAcademy, Strategic Affairs. And I want someone from the Chairman's office as a link. I'll confirm with him. Person #10: Before you set the group, can I make a suggestion? The narrative should not be written by us. It should be written by the audience. We should be asking: what does a minister from Latin America, or a deputy minister from Southeast Asia, or a CEO from Silicon Valley need to hear to walk away thinking Abu Dhabi is the place? Person #2: That's the empathy question, and I agree. We'll do persona mapping in the working group. Who are the five key personas at the Summit? We build the narrative around their questions. Person #24: And their problems. Because I think the biggest mistake governments make at these summits is they present success stories without the problem. The audience wants to know: what was the pain? What was the friction? And then, how did you get from the pain to the solution? That's what makes it human. Person #34: One hundred percent. The problem story is the beginning. And for Abu Dhabi, the problem was fragmentation. 53 entities, each doing their own IT, their own HR systems, their own data centers. And we consolidated. We went from three hundred-ish data centers to— what are we at now? Person #35: Seventeen. We're at seventeen active data centers, with a target of eight by the end of 2027. And those seventeen include the sovereign platform nodes. Person #34: Seventeen. And the entity IT consolidation— we've brought, what, twenty-three entities onto the common infrastructure? Person #35: Twenty-six. Twenty-six entities are fully on the common infrastructure, with nine more in migration. And the ADERP finance and HR rollout— that's Person #37's domain. Person #37: We're at thirty-one of fifty-three entities live on ADERP. The next wave is eight entities going live in October. We had a bit of a slippage on the Ministry of Energy– I mean, the Department of Energy integration, because they had a legacy payroll issue. But we're back on track, and we'll hit the target of forty-two by year-end. Person #2: And what's the number when we're done? Fifty-three by when? Person #37: All fifty-three by Q3 2027. That's the plan. But if you're asking for the Summit narrative, I don't want to say "fifty-three entities" because it's not complete. I'd rather say "the largest public sector ERP consolidation in the region" and let them ask for details. Person #34: I'd say the number is more credible than the superlative. Every government in the room has heard "largest in the region" from someone else. The number is real. Thirty-one of fifty-three is a concrete fact. Person #35: And we can say "on track" to complete by Q3 2027. That shows a plan, not a boast. Person #11: Can I ask a question, Saadat? Person #2: Yes, of course. Person #11: The narrative we're building— the AI-native government, the sovereign cloud, the TAMM journeys— it's a government-to-government story. But the World Governments Summit also has a business audience. The G42s, the Microsofts, the Oracies of the world are there. Are we telling them a procurement story, or a partnership story? Person #2: Good question. And I think the answer is: both. The G2G audience wants to see the model. The industry audience wants to see the opportunity. And we should be explicit about both. We're not hiding the fact that we work with partners. The sovereign cloud is built with partners. The ERP runs on Oracle. The AI assistant runs on a mix of open-source and commercial models. The point is not "we did it alone," the point is "we know how to orchestrate. Person #10: That's a beautiful framing. Orchestration. The government as the platform that enables the ecosystem. I love it. Person #34: It's also honest. Because if the industry audience hears us pretending we built everything from scratch, they'll know it's not true. They know who the vendors are. They see the logos on the booth. Person #2: Exactly. And we'll have a partner area at the Summit— we're inviting G42, Core42, Oracle, Microsoft, ServiceNow, a couple of others— and we're positioning them as "the Abu Dhabi government's technology partners," not as "our sponsors." That's a deliberate message. Person #9: Saadat, can I ask— the workforce angle. Where does that fit in the three acts plus coda? Because you mentioned the Copilot rollout, but the broader story— the HR law, the Emiratisation targets, the Tomouh platform, the Mawaheb hub— that's a whole different audience. The people leaders at the Summit care about that. Person #2: I haven't forgotten the workforce. It's act two. The "How" includes the human capital. You can't have an AI-native government with a workforce that's still doing 20th-century workflows. The HR law is the enabling framework. The Copilot rollout is the tool. Tomouh and Mawaheb are the pipeline. And the training, the upskilling, the Academy programs— that's part of the "How" too. Person #10: And I would argue the Academy programs are also part of the "What." Because we're not just talking about capabilities; we're doing it. Al Jadaara has 1,500 graduates. The Drive has its third cohort starting in November. We're partnering with MBZUAI for the executive AI program. These are live programs, with real numbers. Person #9: And the HR law— when does that go to the Executive Council? I know we've had delays. Person #11: It's in the final review. We're aiming for approval by the end of September. That gives us— okay, the Summit is February. We'll have had it in force for four months. We can talk about early results. The first performance management cycle under the new framework closes in December. So we'll have data. Person #2: Good. And the Emiratisation targets— can we share numbers yet? Person #9: We can share the framework. The targets per entity are confidential until the Council approves the thresholds. But we can say the government sector is on track for the 2026 targets. The private sector is a different story, and I know the Chairman wants to speak to that at the Summit. Person #11: The private sector placement numbers are actually— the data is mixed. Mawaheb has placed 2,800 Emiratis in the last twelve months. But the retention at the nine-month mark is 71 percent. That's not where we want it. Person #9: 71 percent? I thought it was 76. Person #11: The 76 percent figure was for the 2024 cohorts. The 2025 cohorts have a lower retention, mostly in the defense industry roles. We think it's a training-to-role mismatch in some of the technical tracks. We're analyzing. Person #2: That's a good— it's a good honest number. But for the Summit, we want to lead with the positive. The 2,800 placements, the new Tomouh modules, the AI-powered talent matching. And if someone asks about retention, we'll have the trend line, not just the point. Person #11: Understood, Saadat. But I'd caution against presenting a trend line that goes the wrong way. Person #2: Then we show the trajectory after the fix. If we're analyzing it now, we should have the fix by February. Person #11: We'll see. Person #2: Fair. Okay. Let's— I want to move us to the next item. The Chairman mentioned he wants everyone to have a "one-liner" ready. The message each of you would deliver if you had sixty seconds on the main stage. Has anyone drafted theirs? Person #24: I have something. "At the end of the day, the success of a government is not measured by the number of laws it passes, but by the number of tasks a citizen can complete without visiting an office." That's my line. Person #2: I like that. It's punchy. Who's heard it already? Person #10: I've heard you rehearse it in your office. It is good. Though I would add a future-focus: "without visiting an office, and without waiting for a human to approve it. Person #2: Hmm. That's a bit long. But the sentiment is right. Person #34: My line is: "We used to manage infrastructure. Now we manage intelligence." It's a bit— it's a bit grand, but it captures the shift. Person #35: That's good. Though the infrastructure people in the room will say, "you still need to manage infrastructure." Which is true. The cloud doesn't run itself. Person #34: That's why I said "we used to manage" and "now we manage." It's a shift, not a replacement. Person #35: I know. I'm just being— I'm being the infrastructure guy. Person #2: Okay, you're the infrastructure guy. What's your line? Person #35: I don't have one. I'm not the one giving the keynote. I'm the one who keeps the lights on so the keynote works. Person #9: That's humble. You don't want a line? Person #35: I'll have a line if the Chairman asks. But my line is about trust: "Sovereignty is not a feature. It's a promise." Something like that. Person #2: That's actually strong. "Sovereignty is a promise." We might use that in the Act Two materials. Person #35: Take it. It's yours. Person #2: What about you, Person #9? You've been quiet on the narratives. Person #9: I've been taking notes, actually. I'm still learning the rhythm of these meetings. But I have a line: "The best AI strategy in the world is nothing without people who can use it. Person #2: Good. Direct. Person #10: I love it. Person #9: It's a bit— it's the HR answer. But it's true. And the Chairman knows it. He's been pushing on the digital literacy program for the civil service. We have 35,000 people getting Copilot, but we also have 35,000 people who need to learn what to ask it. Person #34: And they will. The rollout is staged. We've done the first 8,000. The second wave is another 12,000 starting in October. And the training modules go out with the license. We learned from last time— the first wave, people got the tool and then just— they opened it, they typed one question, and then they went back to their old ways. So now we're doing the change management differently. Person #2: How so? Person #34: We don't give the license until the person completes the first two modules on Tomouh. And we have a "prompt of the week" campaign. And each entity has a champion who's responsible for adoption metrics. It's not perfect, but the usage is up. Daily active users went from 14% to 31% in the last two months. Person #2: That's a metric we can use. 31 percent, and climbing. Person #35: If you share that, be ready for the question: "What's your target?" Because 31 percent sounds low. Person #34: Target is 70 percent by the end of 2027. That's ambitious, but it's the plan. And we can be honest about the journey. Person #2: Good. Honest journey. That's the theme. Okay. I want to do a quick check-in on the GITEX feedback, because the Chairman will ask. What did we learn, what do we repeat, what do we drop? Person #24: GITEX was good for us. The TAMM 4.0 demo went well. We had a queue at the booth every day. The AI assistant handled about 4,000 live interactions during the event. The feedback from the entities was positive. But we had— the DoH integration in the demo had a moment where it took eight seconds to respond. Which is not— it's not acceptable. Person #35: It was the network. The GITEX network was saturated. We had a dedicated line, but the DoH side was going through their own— it was a mess. Person #24: Whatever the cause, it's a lesson. For the Summit, we need a rehearsal with the actual network, the actual devices, the actual accounts. Not a dry run three days before. A full simulation. Person #34: Agreed. And we'll have a different setup. The Summit is a bigger stage. More scrutiny. We need to be surgical. Person #2: What did we drop? What didn't work? Person #10: The panel format. We did two panels at GITEX— one on the future of public services, one on sovereign AI. The attendance was okay, but the format was tired. The moderator asked the same questions we've all heard. I'd rather we do keynote-style presentations with visuals, not talking heads. Person #34: I disagree. The panels at GITEX were fine. They're not for the walk-through crowd; they're for the press. The press writes about panels. They don't write about demos. We need panels at the Summit for the media narrative. Person #10: The press writes about panels, but they write about the participants, not the content. "Director General X said the future is AI." That's not a story. At the Summit, we should be creating moments, not moments of boredom. Person #2: Let's not fight. We'll have both. A keynote and a panel. And the demos. And the experience. That's the answer. Person #9: Saadat, can I ask about the Chairman's role at the Summit? Is he speaking on the main stage? Person #2: Yes. He's confirmed for a main stage session— a conversation, not a keynote. The moderator will be— we're in talks with a well-known international journalist. The session is titled "From Citizens to Copilots: The AI-Native Government." That's the working title. Person #9: From Citizens to Copilots." I like it. Though it's a bit— it's a bit cute. Person #2: It's catchy. And the Chairman has approved it. So we're keeping it. Person #24: And what's the throughline? Is he going to talk about TAMM? The cloud? The HR law? Person #2: He wants to talk about the whole thing. But the moderator will guide. We're preparing a briefing document for him— three pages, not thirty— and we'll have a prep session with him two weeks before. Person #10: I can help draft that. I've done similar briefing notes for the Prime Minister's Office. Person #2: I know. You'll be in the working group. Everyone will contribute. But the coordination is through my office. Person #35: If I can ask something. The Chairman's session— is it going to be in Arabic or English? Or both? Person #2: The Summit is bilingual. He'll do the opening in English, and then he can switch to Arabic if the moderator asks. We'll have simultaneous interpretation for the audience. Person #35: And are we doing any Arabic-first messaging for the regional audience? Because the summit has a big GCC presence, and the Arabic media will cover it differently than the English media. Person #2: Good point. We'll have a separate Arabic press package. And the Chairman's office has a communications person who will handle the Arabic outlets. But we should coordinate so the message is consistent. Person #35: I can make sure the technical terms are consistent. We've had issues before where the Arabic translation of "sovereign cloud" doesn't match what we use in official documents. Person #2: That's a good catch. We'll add that to the working group's list. Person #11: Saadat, I have a question about the "coda" you mentioned. The future. What's the specific message? Are we announcing something new at the Summit, or are we just describing the trajectory? Person #2: That's a good question. Let me think. The Chairman has been talking about a potential announcement— but it's still in the early stages. I don't want to share details until I've confirmed with him. But let's say the coda will have at least one "piece of news" that gives the press something to write about. Person #11: Okay. I won't ask more. But the workforce side would need to be involved if it's a talent-related announcement. Person #2: It's not. But I'll keep you in the loop. Person #10: Saadat, can I propose something for the coda? We've been talking about a "government as a platform" manifesto. Something we can publish— not just at the Summit, but as a living document. The world needs a framework for what an AI-native government looks like. We have the experience, we have the data, we have the results. We should be the ones to define it. Person #2: I like that. A manifesto. A framework. Something that positions Abu Dhabi as the thought leader, not just the case study. Person #34: We have the Digital Strategy 2025-2027. Is that not the manifesto? Person #10: It's a strategy document. It's internal-facing. It's about what we're doing. A manifesto is about what the world should do. It's aspirational, it's normative, it's— it's a point of view. It's different. Person #34: I'm not sure the Chairman wants us to be preachy. He wants us to be impressive. A manifesto risks being preachy. Person #2: Let's not decide now. We'll float it in the working group. If it's a five-page document, it could be a good add-on. If it becomes a debate, we drop it. Person #10: I'll draft a first pass. I'll have something by the first working group meeting. Person #2: Good. And I'll have the persona mapping ready by then as well. Person #24: Saadat, one more thing. The TAMM app rating. It's at four point two after the incident. The Chairman might be asked about it at the Summit. How do we frame it? Person #2: We need to get it back above four point five before February. That's the priority. And if we can't— frame it as "the app has four point two stars because we migrated to a new platform, and the migration is still settling." Which is true. Person #35: We can also push a few "rate us" prompts to the active users. The happy ones will rate. The unhappy ones already rated. We can balance it out. Person #24: We've done the prompts. We only send them to users who have completed a journey successfully. That's the policy. It's not gaming, it's just— it's asking the satisfied users to share their experience. Person #35: I'm not going to judge. It's a metric, and metrics have momentum. Person #2: Good. Let's— we have about twenty-five minutes left, and the Chairman should be joining soon. I want to do a quick go-around on readiness. Each of you, thirty seconds: what's the one thing you need to deliver your part of the Summit narrative? Person #9: I need the final approval on the HR law. Without it, I can't talk about the legal framework. And I need the final numbers on the Tomouh platform usage— we're at 240,000 active users, but I want to present the growth curve, not just the point. Person #2: Approval is in process. Numbers will come. Next. Person #10: I need a confirmed speaker for the Academy session. We're in talks with a former head of state— I can't say who— but if he confirms, we have a world-first moment. Person #2: That would be impressive. When will you know? Person #10: Two weeks. He's deciding after his— after his next visit to the region. Person #2: Keep me posted. Next. Person #11: I need the retention analysis to show a positive trend. If the fix works, we can present a compelling story. If not, we'll present the problem and the plan. Person #2: When will you know? Person #11: The fix is rolling out in the October cohort. We'll see the first data by December. That's the timeline. Person #35: I need the change freeze policy approved. If the Chairman signs it, we can guarantee a stable platform for the Summit. If not, we're at risk. Person #24: I need the TAMM 4.0 final release to be stable. We have a release candidate going out in November. And I need the DoH and ADEK teams to commit to the integration testing timeline. We've had slippage. Person #37: I need the ADERP wave nine go-live to be clean. If it's clean, we can showcase the fully integrated finance and HR system at the Summit. If there's an issue, I'll need to limit the scope of the showcase. Person #34: I need the Chairman to give us the go-ahead on the next cloud migration wave. We can't show a half-migrated platform. And I need the copilot adoption metrics to keep climbing. Person #2: Good. And I need— I need all of you to deliver those. And I need the narrative working group to start next week. I'll send the calendar invite. Friday at 2:00 PM. Person #10: Friday at 2:00? That's— that's the weekend start. People are tired. Person #2: It's forty-five minutes, and it's virtual. We can have a coffee. It's fine. Person #9: Friday at 2:00 works for me. Person #24: Fine. Person #35: I'll be there. But if there's an incident— I might need to step out. Person #2: Incidents happen. Just tell us— just step out and come back. Person #34: Saadat, before the Chairman joins, I want to raise one thing. The Summit narrative is well-constructed, but we have a risk. The "AI-native government" phrase— everyone is using it now. Singapore used it in their last national strategy. Saudi Arabia used it at LEAP. If we go to the Summit and say "AI-native," we're not differentiated. Person #2: So what's the differentiation? Person #34: The execution. Not the phrase. The phrase is table stakes. The differentiation is the scale and the speed. Fifty-three entities. 35,000 civil servants. 200-plus use cases. The sovereign cloud. The data platform. We're not the first to say it, but we might be the first to do it at this scale. Person #2: I agree. And the narrative should be "AI-native, delivered." That's the slogan we can use internally. "AI-native, delivered." For the Summit, the phrase can shift. Person #10: Delivered" is a bit— it's a bit corporate. But I get the concept. Person #2: We'll workshop the language. The point is the content. Person #35: Can I say something? We've been talking about the Summit narrative, but we haven't talked about the aftermath. The Summit is one thing, but the real test is what we do in the next 12 months. If we promise something at the Summit and don't deliver, the damage is worse than not going. Person #2: That's the undercurrent of everything we do. And I'm glad you raised it. The Summit is not the end. It's the launch. The narrative has to be backed by the reality. And we're building that reality. We're not there yet, but we have the plan. Person #35: And the plan has dates. I want to see the dates in the Summit materials. Not vague "we will" but "by Q3 2027, we will have done X. Person #2: Agreed. The materials will have a timeline. A public-facing roadmap. Which is a risk— it invites scrutiny— but it's also a commitment. We need to be careful. Person #24: I think the roadmap is a good idea. It shows confidence. And it's a way to hold ourselves accountable. Person #34: It's also a way for the media to write "Abu Dhabi sets 2027 deadline." Which is a headline we want. Person #2: Good. We'll include the roadmap. Now, let's— I think the Chairman is coming. Let me check my— yes, he's joining. Person #2: Good morning, Your Excellency. We've just started. We're at the go-around. I'll bring you up to speed. Person #2: Your Excellency, we’re discussing the World Governments Summit narrative. The core framing is "AI-native, delivered" — the execution at scale across 53 entities, 35,000 civil servants, the sovereign cloud. We’ve agreed to include a public-facing roadmap with concrete dates in the materials, to signal commitment. Person #34: And to give the media a headline. "Abu Dhabi sets 2027 deadline." That’s the kind of story that lands well. Person #9: Absolutely, Your Excellency. That’s where Government Talent comes in. The Copilot rollout is about empowering our people to serve better. We’re training 35,000 civil servants — not just on the tool, but on the mindset. Person #11: Forty-two percent of the training modules are already live on Tomouh. We expect full completion by end of Q4. Person #2: We have that. The "AI-native, delivered" story is three pillars: infrastructure, services, and talent. Each has its own section and KPIs. Person #10: And the leadership angle. The Al Jadaara graduates — they’re the ones driving this change. We could feature a few of them in the Summit video. Real stories, not just metrics. Person #35: If we do video, we need to start production by mid-September. The Summit is February, but the lead time for that kind of content is longer than people think. Person #2: Understood, Your Excellency. We’ll have it to you well before the deadline. Anything else? Person #24: Yes, Your Excellency. Root cause was a database migration issue. We’ve implemented a change freeze until the post-mortem is complete. Uptime is back to 99.98%. Person #2: Shukran, Your Excellency. We’ll send the summary. Yallah, team — let’s wrap this up. Emails by noon.