Islamic AI challenge puts working products and their handover records to the test

The deadline concerns a product

The AI Challenge Serving Islamic Content has set October 6 at 11:59 p.m. Riyadh time, or 20:59 UTC, as its submission deadline. Its published program places the remote camp on October 4–6. Entries must perform their complete use case and explain their operating limits; an idea or unfinished prototype does not meet the stated requirement. Source: islamicaich.org

Bathel Foundation’s September 15 announcement describes the competition as a collaboration with the Saudi Data and AI Authority, with 200,000 Saudi riyals in prizes. Its five tracks cover dialogue, multilingual content, learning experiences, verification tools and other Islamic outreach applications. Source: bathel.sa

What reviewers should be able to inspect

The Arabic participant guide requires a working demonstration link, a public GitHub repository containing publishable code, operating documentation, a presentation and a video lasting at most two minutes. Religious and knowledge sources must be documented, including how they were used and checked.

The final rubric gives 25% to technical quality and AI use, 20% to demonstrated benefit within the chosen track, and 15% to reliability and scholarly soundness. Another 10% concerns realistic continued operation: costs, dependencies, maintenance and content review. The rubric links stronger reliability ratings to handling varied cases and feasible human review. The guide recommends a religious or subject specialist on the team but does not make that team composition compulsory. These are announced judging standards, not evidence that any entry has satisfied them. Source: islamicaich.org

A public repository does not settle every right

The organizer’s Arabic terms require a register recording sources, intended uses and the permission or licence relied upon. Participants must disclose outside models, services and pre-existing components. Existing projects are eligible, but competitive assessment concerns additions made during October 4–6.

For demonstrations and testing, the terms require synthetic or irreversibly anonymized data. Replacing names with codes does not satisfy the challenge’s prohibition on uploading real beneficiary conversations or records.

Ownership remains with the rights holders. Winning can activate a broader, non-exclusive licence for the foundation’s nonprofit use, subject to the specified acceptance and prize conditions; that is distinct from permission to release code under an open-source licence. Non-winners need a separate support-and-licence agreement for that broader use. These are the competition’s stated arrangements, not general advice about Saudi copyright law. Source: islamicaich.org

The question after the demonstration

For a religious institution considering a similar project, the useful question is who can sustain it after the showcase. Ask for a named maintainer, a realistic operating budget and an account of which materials can travel with the software. A compelling demonstration cannot answer those questions by itself.

Christian readers can approach that responsibility through Luke 14:28–33, where Jesus uses the cost of completing a building within teaching about the demands of discipleship. Applying the passage to institutional planning is our analogy, not an endorsement of this competition or its religious claims. Luke 14:28-33 (NIV)