Solution & integration design

⁦1⁩. Solution overview

The platform is the unified Mueen portal, a case workflow and forms engine, a central integration layer and a case and beneficiary data store, hosted on the government cloud inside the Kingdom with a ⁦99.9%⁩ availability target.

⁦2⁩. Integration map

Every interface goes through the central API gateway; the Government Service Bus uses asynchronous messaging so a slow agency never blocks a case registration, with automatic retries and an audit trail for every message.

⁦3⁩. Simulator & fallback

A local simulator of the Nafath, Government Service Bus and Absher interfaces is built in the first integration sprint, so the team keeps working when the national test environments go down — as they did for nine days in September.

⁦4⁩. Data model

• Beneficiary: national ID, capacity (litigant, lawyer or government agency), contacts, consents
• Case: type, the competent judicial circuit, stage, attachments, statutory deadlines
• Notice: Service Bus message number, defendant agency, status, reply date
• Log: every change with who, when and through which channel

⁦5⁩. Cybersecurity & data protection

• Compliance with the ⁦ECC-2:2024⁩ and the cloud cybersecurity controls
• Personal data encrypted at rest and in transit under the PDPL
• An independent penetration test before launch with no critical or high findings
• Round-the-clock monitoring from the security operations centre