Bilingual AI for Diplomatic Correspondence

A foreign ministry desk officer drafting a note verbale at 21:00 on a Thursday has the same problem as a treaty negotiator at the United Nations and a protocol officer at a presidential palace: the text has to be flawless in two languages, has to match the receiving mission's expectations of register and form, and has to ship before the diplomatic bag closes. Bilingual on-premise AI is the only architecture that compresses this drafting load without exposing draft state secrets to a foreign cloud. This piece walks through the four pieces a credible deployment needs, framed for a MoFA-class secretariat working in Arabic and English.

The MoFA-class drafting workload

The volume is steady and the genres are well defined. A typical week at a foreign ministry combines notes verbale to and from accredited missions, demarche talking points for envoys delivering a position to a host capital, condolence and congratulatory cables on national days and bereavements, accreditation and recall letters for ambassadors, third-person aides-memoire summarising bilateral conversations, and substantive bilateral letters on cooperation, consular cases, and treaty matters. Wikipedia's overview of diplomatic correspondence categorises the genre cleanly into letters, notes, memoranda, and aides-memoire, each with its own protocol. The Geneva-based DiploFoundation training programme on diplomatic correspondence goes further and treats it as a discipline distinct from general professional writing, with its own conventions for opening salutations, third-person reference, complimentary closes, and signature blocks.

The bilingual pressure is the load multiplier. An Arab-Gulf foreign ministry routinely issues a single envelope containing the Arabic original and the English translation, both of which must be protocol-correct, both of which must be perfectly equivalent in substance. A drafting assistant that handles one language well and the other passably is no better than a monolingual assistant. The bar is both bars at once.

The register problem

Three things make this drafting harder than ordinary government writing. First, the Arabic register sits at the top end of formal Modern Standard Arabic, with prayer formulae, archaic adjectives, careful agent-passive choices, and a tight protocol vocabulary cluster around sovereignty, friendship, and respect. Second, the English register has its own conventions: third-person address in notes verbale ("The Ministry of Foreign Affairs presents its compliments..."), avoidance of contracted forms, careful titulature, and a complimentary close ("...avails itself of this opportunity to renew the assurances of its highest consideration") that is fixed by long usage. Third, both languages have to use protocol-correct titles for the receiving party (Excellency, Highness, Eminence, Honourable, depending on the addressee) and the right calendar pair, with Hijri and Gregorian dates rendered in the order the ministry's house style requires. A general-purpose model that has not been tuned on diplomatic corpora will get one or two of these wrong on every draft, and a wrong honorific on a head-of-mission letter is a small diplomatic incident.

The on-premise stack

The architecture is straightforward, and every piece runs inside the ministry's own perimeter. This is the same posture argued in the pillar reference on defence AI Arabic triage, applied here to the diplomatic side of the same sovereignty problem.

• Falcon Arabic for the Arabic side. The Technology Innovation Institute's Falcon Arabic family, including the more recent Falcon-H1 Arabic hybrid release, was trained on fluent MSA with strong Gulf coverage and ships under terms that allow on-premise deployment with full control of the weights. It is the strongest open-weight Arabic baseline available in 2026.
• Gemma 4 for the English side and long-context retrieval. Google DeepMind's Apache-2.0 release covers English ceremonial drafting and handles the long-context reads needed when a draft has to reconcile against decades of past notes, prior bilateral correspondence, and treaty text in a single pass.
• RAG over historical correspondence. The ministry's archive of past notes, demarches, and bilateral letters is indexed and retrieved at draft time, so the model writes in the precedent the ministry actually uses, not what a generic model imagines diplomatic prose to look like.
• An authority file for protected fields. Names, titles, mission numbers, treaty references, and Hijri-Gregorian date pairs are pulled from a ministry-owned authority file at draft time. The model never invents a title or a treaty number.

A light LoRA fine-tune on a few thousand internal documents, run on the same air-gapped hardware that serves the model, teaches the system to open with the right invocation, address with the right honorific, and close with the right complimentary formula in both languages. The corpus never leaves the enclave.

Operational guardrails

The model is the easy part. The guardrails are what make the system safe to put in front of a desk that drafts text other states will read. Four are non-negotiable.

• No auto-send. The system has no outbound capability, no diplomatic-bag interface, no SMTP path. Drafts arrive in a queue. The dispatch path is the existing protocol office, unchanged.
• Two-eyes review. Every draft destined for an external mission passes through a designated bilingual desk officer and a senior reviewer. The system enforces the two-signature gate before a draft can be marked ready for dispatch.
• Audit log. Every prompt, every retrieval, every model version, every editor change, and every sign-off is recorded with timestamp and operator identity. The log is immutable and survives operator turnover. Retention aligns with the ministry's existing classification regime.
• Authority-file primacy. If a draft cites a treaty number, a date, or a quoted prior text that does not match the authority file, the system flags the draft and refuses to advance it until a human resolves the discrepancy.

If your foreign ministry or sovereign-affairs office is sizing a bilingual diplomatic drafting assistant against this shape of brief, the next step is a one-hour briefing on architecture, models, and the security posture. Email [email protected] or message +968 9889 9100. Pricing is by quotation, sized to the volume and the air-gap requirement.