# Quality report: Pack A (Rotalume help center), English → Arabic, Gulf (Saudi Arabia)

Demonstration project on sample content written by Locstars for fictional companies, not client work. Service level: AI. Human review: None.

Updated on 2026-11-11 after round 2, a second checking round run by AI agents after the delivery review. Round-1 text is kept; round-2 additions are marked "Round 2". The corrections made to the round-1 report are listed in section 11.

Updated again on 2026-11-11 after round 3: a separate native-reader agent that saw only the target text re-read the round-2 file, a separate devil's advocate challenged each of its findings and a separate judge ruled. Round 3 changed no segment. Round-3 additions are marked "Round 3".


## 1. Job summary

| Field | Value |
|---|---|
| Human review | None |
| Service level | AI |
| Quality gate | Quality gate: passed<br>Which run passed: the round-1 file passed on gate run 2 (run 1 raised one flag, on S08, which was ruled a false alarm; the check was narrowed and the file was not changed). The round-2 file, which is the file now delivered and differs from the round-1 file in 6 segments, passed on gate run 3, the one gate run of round 2. Round 3 ordered no correction, so the final file is the round-2 file, byte for byte; the gate was run on it once more (gate run 4) and passed. |
| Job | Pack A (Rotalume help center), file prefix pack-a-gulf-sa. Source file: A-source.docx |
| Client | Fictional. Rotalume is a fictional product; the pack is demonstration content. |
| Direction | English → Arabic |
| Arabic variety | Gulf (Saudi Arabia) |
| Readers | Managers and owners of cafés, restaurants, and shops in Saudi Arabia. Women and men. They read on a phone and are not technical. |
| Content type | Help-center article (getting-started guide) for a staff-scheduling app, with UI labels and six quoted in-app messages |
| Scope | Whole file: 60 segments, 1,017 source words. No translation memory and no earlier batch were supplied; every word counts as new. |
| Steps run | 1. Intake and scoping: run as described. The agent counted the segments and words; an automatic count gave the same figures (60 segments, 1,017 words, 0 repeats).<br>2. Terminology with sources: run as described. 16 new terms, more than 10, so they were grouped: 4 term agents with 4 terms each. The agents used web search and opened pages; for some terms no page was opened (see the new-term list).<br>3. Calibrated AI translation, then automatic checks: run as described. Output frozen. Check 5 (length limit) not applicable: the style guide sets no limit.<br>4. Separate checks, each blind to the others: run as described, six separate agents. Each agent also received the paragraph type of each segment and the cycle's definitions of finding, category and severity.<br>5. The devil's advocate: run as described. The agent's reply had one malformed entry (S17) and gave the intended entry in a note in the same reply; that entry was used.<br>6. The judge, then the script: run as described. The script replaced 1 segment (S16).<br>7. Quality gate and report: run as described. Regression: 1 round, 1 segment re-read, no findings; the regression agent was also given the three rulings on S16, which it needs to confirm the correction. Gate: run 1 raised one flag (S08), which went to the devil's advocate and the judge as separate agents and was ruled Not a defect; the check rule was corrected and run 2 passed.<br>Round 2 (a second checking round, run after the delivery review, by AI agents, with a corrected judge rule): steps 4 to 7 were run again on the round-1 delivered text. Step 4: the six checking agents ran again; their independence from one another was not assured, and they had already seen the round-1 report and the delivery review, so they were not blind to these in fact. The six items of the delivery review that no agent raised were added as findings "Raised in delivery review". Step 5: the devil's advocate challenged all 14 round-2 findings. Step 6: the judge ruled on all 14 with this corrected rule: a native-reader finding counts as a defect when it names a concrete defect in the target text (a broken or ungrammatical construction, meaning added or lost against the source, an ambiguity that changes what the reader understands, a wrong tense or agreement, inconsistent wording for the same UI action), even if the only reference is the source segment or the grammar of the language; a finding that only says another wording would be nicer stays a Preference; where two corrections are possible, the one that changes least is chosen. A script replaced 6 segments (S16, S23, S44, S53, S59, S60). Step 7: regression, 1 round, 6 segments re-read with their neighbors, no findings; gate run 3 passed. No human took part in round 2.<br>Round 3: after round 2, a separate native-reader agent that saw only the target text re-read the file; a separate devil's advocate challenged each of its findings and a separate judge ruled. 13 findings were raised; the judge ruled none a Defect (5 Not a defect, 8 Preference), so no segment changed, there was nothing for the regression agent to re-read, and the delivered file is the round-2 file unchanged. No human took part in round 3. |
| Instructions used | Glossary: A-glossary.xlsx, 30 entries (approved terms, inflected as the sentence requires; forbidden forms in the notes). Style guide: A-style-guide.md. Rules that applied: variety and two register levels (standard wording for labels, headings and numbered steps; Saudi conversational wording for what the product says); second person singular; gender-neutral wording for messages to a named person, direct questions, and sentences about a person in a placeholder; Rotalume speaks as "we"; UI labels as in the glossary, in « », menu paths with >; placeholders copied exactly, %d sentence valid for every number; Rotalume in Latin letters, addresses unchanged, personal names in Arabic letters; Western digits; date, time, money, percent and duration formats; Arabic punctuation and « »; idioms translated by meaning. |
| Assumptions / open questions | 25 open questions, listed with the assumption used for each in section 8 (Q1 to Q25; Q22 and Q23 were added in round 2: whether the trial-end message to the Owner must be gender-neutral, and whether the client wants «مين» or a Najdi form for "who"; Q24 and Q25 were added in round 3: which wording level unnumbered body paragraphs with imperatives take, and how the sign ">" in menu paths is drawn in the client's right-to-left view). In short: source strings that cannot work as written with their placeholders (S25 %d and "tomorrow", S20 and S33 gendered verbs, S33 single date) were restructured or translated as written; unknown placeholder values were assumed to arrive in the style-guide format; the register of ordinary explanatory paragraphs is not assigned by the style guide (Q10: the delivered text uses Saudi conversational wording there); 16 new terms, including 9 UI labels missing from the glossary, are proposals not confirmed by the client; the glossary gives the role label Manager as indefinite «مدير» beside definite «المالك» and «عضو الفريق» (Q21); SOURCES.md was not supplied; automatic list numbers were left as the file draws them. |
| Who decided | The judge agent ruled on every finding, after the devil's advocate's challenge, within the client's instructions. No human reviewed or edited the file. Open items: 25. Round 2: the judge agent, run again with the corrected rule, ruled on 14 further findings after the devil's advocate's challenge and re-ruled five round-1 Preference rulings as Defect (S16-2, S23, S44-3, S53, S59-2). Locstars asked for the second round and set the corrected rule; no human ruled on any finding or edited the text. Round 3: a separate judge agent ruled on the 13 findings of the separate native-reader agent after a separate devil's advocate's challenge; it ruled no Defect, so nothing was changed. Limits stated by the round-3 judge: its rulings on findings R3-03, R3-04, R3-05, R3-06, R3-08 and R3-13 turn partly on whether a Saudi wording sounds natural, which it could not verify against usage evidence; those rulings rest on the client's rules and on the absence of a concrete error, and a Saudi reviewer's judgment would outrank the judge's on naturalness. It did not check how the sign ">" in menu paths is drawn in a right-to-left view. It noted that the style guide assigns unnumbered body paragraphs that contain imperatives to neither wording level. |
| Label | Assessment by Locstars. Demonstration run on fictional sample content. |

## 2. Run record

Not part of this copy.

## 3. Issue counts

Round 1: 40 findings were raised: 26 by the step-3 script, 13 by the checking agents (17 agent reports, 4 pairs of which were the same defect in the same words and share a row), and 1 by the quality gate. The judge ruled 1 Defect, 28 Not a defect (one of them "Not a defect in the translation", sent to the open questions as Q21) and 11 Preference. 1 was fixed. 33 of the 60 segments had no finding. The step-3 script matches letters: all 26 of its flags were inflected forms of an approved term (25) or the glossary's dual for the number 2 (1), and none was an error.

Round 2: 14 findings were raised: 8 by the checking agents (18 agent reports; 6 rows were reported by two or three agents) and 6 taken from the delivery review because no agent raised them. The judge, with the corrected rule, ruled 6 Defect, 2 Not a defect and 6 Preference. 6 were fixed. 5 of the 6 Defect rulings are on wording that a round-1 finding had already reported and that round 1 ruled Preference (S16-2, S23, S44-3, S53, S59-2); those round-1 rows are marked as re-ruled and each defect is counted once, on its round-2 row.

Round 3: 13 findings were raised by a separate native-reader agent that saw only the target text of the round-2 file. A separate devil's advocate challenged each one and a separate judge ruled 0 Defect, 5 Not a defect and 8 Preference. Nothing was fixed and no segment changed. Nine of the thirteen proposed corrections would themselves have broken the glossary, the style guide, a placeholder or the meaning, by the judge's count. Limits stated by the round-3 judge: its rulings on findings R3-03, R3-04, R3-05, R3-06, R3-08 and R3-13 turn partly on whether a Saudi wording sounds natural, which it could not verify against usage evidence; those rulings rest on the client's rules and on the absence of a concrete error, and a Saudi reviewer's judgment would outrank the judge's on naturalness. It did not check how the sign ">" in menu paths is drawn in a right-to-left view. It noted that the style guide assigns unnumbered body paragraphs that contain imperatives to neither wording level.

All three rounds together: 67 findings raised, 7 ruled Defect and fixed, 35 ruled Not a defect, and 20 standing as Preference (5 further round-1 Preference rows were re-ruled in round 2). 23 of the 60 segments had no finding in any round.

| Category | Critical | Major | Minor |
|---|---|---|---|
| Accuracy | 0 | 0 | 1 |
| Fluency | 0 | 0 | 1 |
| Terminology | 0 | 0 | 0 |
| Style | 0 | 0 | 5 |
| Locale | 0 | 0 | 0 |
| Tags and format | 0 | 0 | 0 |
| Client requirements | 0 | 0 | 0 |
| Total | 0 | 0 | 7 |

The table counts Defect rulings only, from all three rounds, each defect once. Round 3 added none. Round 1 alone: Style 1 Minor (S16-3).

## 4. Findings by agent

Round 1 (the rulings as they stood at the end of round 1; five of the Preference rulings were re-ruled in round 2):

| Raised by | Findings raised | Ruled Defect | Ruled Not a defect | Ruled Preference | Preferences logged |
|---|---|---|---|---|---|
| Step 3 automatic check | 26 | 0 | 26 | 0 | 0 |
| Native-reader agent | 11 | 0 | 1 | 10 | 9 |
| Accuracy agent | 0 | 0 | 0 | 0 | 2 |
| Grammar agent | 1 | 0 | 0 | 1 | 1 |
| Style agent | 1 | 1 | 0 | 0 | 5 |
| Terminology agent | 0 | 0 | 0 | 0 | 2 |
| Dialect-consistency agent | 4 | 0 | 0 | 4 | 3 |
| Quality gate | 1 | 0 | 1 | 0 | 0 |

A row found by two agents is counted under each of them, so the agent lines add up to 17 for 13 rows. S16-2, S23, S44-3 and S53 were each reported by two agents.

Round 2:

| Raised by | Findings raised | Ruled Defect | Ruled Not a defect | Ruled Preference | Preferences logged |
|---|---|---|---|---|---|
| Native-reader agent | 7 | 5 | 1 | 1 | 3 |
| Accuracy agent | 0 | 0 | 0 | 0 | 1 |
| Grammar agent | 1 | 1 | 0 | 0 | 0 |
| Style agent | 4 | 4 | 0 | 0 | 0 |
| Terminology agent | 1 | 1 | 0 | 0 | 0 |
| Dialect-consistency agent | 5 | 3 | 0 | 2 | 0 |
| Raised in delivery review (not an agent) | 6 | 1 | 1 | 4 | 0 |

A row found by more than one agent is counted under each of them, so the agent lines add up to 18 for 8 rows; with the 6 rows from the delivery review that makes 14. R2-S16-1 and R2-S22 were each reported by two agents; R2-S23, R2-S44, R2-S53 and R2-S59 by three. The step-3 script was not run again, because round 2 did not translate. The round-2 gate raised no finding.

Round 3:

| Raised by | Findings raised | Ruled Defect | Ruled Not a defect | Ruled Preference | Preferences logged |
|---|---|---|---|---|---|
| Native-reader agent (target only, separate agent) | 13 | 0 | 5 | 8 | 4 |

Only the native-reader agent ran at step 4 in round 3. Its findings were challenged by a separate devil's advocate and ruled on by a separate judge. The gate run on the final file raised no finding.

## 5. Top patterns

Round 1 wrote "No pattern: fewer than two related issues", which was true of its single Defect ruling. After round 2:

1. A verbal noun or noun phrase where the message needs a verb, in the product messages and tips (level 2): R2-S23 («عليك بس تعديل»), R2-S44 («ولازم اختيار باقة»), R2-S53 («أكيد حذف»), R2-S59 («دور نشر»). The translation avoided a verb, and with it a choice of gender, also where the style guide does not ask for a neutral structure.

No other pattern: the remaining Defect rulings (R2-S16-1 agreement, R2-S60 ambiguous word, S16-3 quotation marks) are unrelated.

Round 3 added no Defect ruling, so the pattern is unchanged.

## 6. Issue log

Rows S03 to S59-2 are round 1. Rows R2-… are round 2 and follow the round-1 rows. A round-1 row that round 2 ruled on again keeps its text; the round-2 ruling is added in the Judge cell after "Round 2:" and the Status is updated. In round-2 rows, "Target (AI translation)" is the segment as delivered after round 1, which is the text round 2 checked. Rows R3-… are round 3: the findings of the separate native-reader agent, numbered as in its own list, with the segments named in the "Found by" cell; "Target (AI translation)" there is the segment as delivered after round 2, and the challenge and the ruling are summarized from the separate agents' files.

| ID | Category | Severity | Source | Target (AI translation) | Correction | Found by | Devil's advocate | Judge | Decided by | Status |
|---|---|---|---|---|---|---|---|---|---|---|
| S03 | Terminology | Not a defect (not counted) | Welcome to Rotalume! This guide walks you through the basics, from signing in to publishing your first schedule. It takes about 10 minutes, and you don't need to be a tech expert to follow it. | حياك الله في Rotalume! هذا الدليل يمشي معك خطوة خطوة في الأساسيات، من تسجيل الدخول إلى نشر أول جدول لك. ياخذ منك حوالي 10 دقائق، وما يحتاج خبرة تقنية. | No change | Step 3 automatic check: Check 3 glossary terms: glossary term "Schedule" is in the source, but the approved term «الجدول» (or a form given in the glossary note) was not found in the target. | False positive from letter matching: the target has «نشر أول جدول لك», where «جدول» is the approved «الجدول» in its indefinite form, which the glossary-forms rule allows. No different word is used for 'schedule', so there is no defect and nothing to correct. | Not a defect. «جدول» in «نشر أول جدول لك» is the approved «الجدول» in its indefinite form, which the glossary-forms rule allows. No other word for 'schedule' is used. | Judge agent | Not applied |
| S04 | Terminology | Not a defect (not counted) | 1. Sign in and set up your workspace | 1. تسجيل الدخول وإعداد مساحة عملك | No change | Step 3 automatic check: Check 3 glossary terms: glossary term "workspace" is in the source, but the approved term «مساحة العمل» (or a form given in the glossary note) was not found in the target. | False positive: «مساحة عملك» is the approved «مساحة العمل» with an attached pronoun for 'your workspace', which the glossary-forms rule explicitly counts as the approved term. The script only missed it because the definite article is replaced by the pronoun. | Not a defect. «مساحة عملك» is the approved «مساحة العمل» with an attached pronoun for 'your workspace'. That is an allowed inflection. | Judge agent | Not applied |
| S05 | Terminology | Not a defect (not counted) | Open the Rotalume app on your mobile phone, or go to app.rotalume.example on your computer. | افتح تطبيق Rotalume على جوالك، أو انتقل إلى app.rotalume.example من الكمبيوتر. | No change | Step 3 automatic check: Check 3 glossary terms: glossary term "mobile phone" is in the source, but the approved term «الجوال» (or a form given in the glossary note) was not found in the target. | False positive: «على جوالك» is the approved «الجوال» with an attached pronoun for 'your mobile phone'. None of the forbidden words («موبايل», «هاتف محمول», «تليفون», «هاتف نقال») appears. | Not a defect. «جوالك» is the approved «الجوال» with an attached pronoun. None of the forbidden words appears. | Judge agent | Not applied |
| S06 | Terminology | Not a defect (not counted) | Tap **Sign in** and enter your mobile number. We'll text you a 6-digit verification code. The code expires after 5 minutes. | اضغط «**تسجيل الدخول**» واكتب رقم جوالك. نرسل لك رسالة نصية تحتوي على رمز التحقق المكوّن من 6 أرقام. تنتهي صلاحية الرمز بعد 5 دقائق. | No change | Step 3 automatic check: Check 3 glossary terms: glossary term "mobile number" is in the source, but the approved term «رقم الجوال» (or a form given in the glossary note) was not found in the target. | False positive: «رقم جوالك» is the approved «رقم الجوال» with an attached pronoun for 'your mobile number', an allowed inflection. No forbidden variant is used, so there is no terminology deviation. | Not a defect. «رقم جوالك» is the approved «رقم الجوال» with an attached pronoun for 'your mobile number'. No forbidden variant is used. | Judge agent | Not applied |
| S08 | Terminology | Not a defect (not counted) | Never share your verification code with anyone, including Rotalume support staff. We will never ask you for it by phone, by email, or in chat. | لا تعطي رمز التحقق لأي أحد، حتى موظفي الدعم في Rotalume. ما راح نطلبه منك أبداً، لا بالاتصال ولا بالبريد الإلكتروني ولا في المحادثة. | No change | Quality gate: Check G5 (glossary terms; no forbidden form anywhere in the file): form «موظفي» matches «موظف», which the glossary note for "team member" forbids. | The defect is not real: the glossary note says «عضو الفريق» must not be replaced with «موظف» when rendering "team member", but the source here says "Rotalume support staff", and "team member" does not appear in the segment at all. «موظفي الدعم» correctly translates "support staff" (Rotalume's own employees, not the customer's team members), so the letter match is a false positive. Changing it to «أعضاء الفريق» would introduce an Accuracy error by confusing Rotalume support with the customer's workspace team in a security warning, so no change and no severity should be applied. | Not a defect. The glossary note forbids «موظف» only as a replacement for "team member" («عضو الفريق»), and the source here says "Rotalume support staff", not "team member". «موظفي الدعم» correctly renders "support staff"; the gate's letter match is a false positive, and changing it to «أعضاء الفريق» would confuse Rotalume's support with the customer's own team in a security warning. | Judge agent | Not applied |
| S10 | Terminology | Not a defect (not counted) | Welcome, {first_name}! Your workspace "{workspace_name}" is ready. What do you want to do first? | هلا {first_name}! مساحة عملك «{workspace_name}» جاهزة. وش أول شي ودّك فيه؟ | No change | Step 3 automatic check: Check 3 glossary terms: glossary term "workspace" is in the source, but the approved term «مساحة العمل» (or a form given in the glossary note) was not found in the target. | False positive: «مساحة عملك» is «مساحة العمل» with an attached pronoun, matching the source 'Your workspace'. The glossary-forms rule treats this as the approved term. | Not a defect. «مساحة عملك» is the approved «مساحة العمل» with an attached pronoun, matching 'Your workspace'. | Judge agent | Not applied |
| S14-1 | Terminology | Not a defect (not counted) | To add people, open **Team** and tap **Invite team member**. Enter the person's name and mobile number, choose a role, and tap **Send invite**. Each new team member gets a text message with a link that is valid for 48 hours. | لإضافة أشخاص، افتح «**الفريق**» واضغط «**دعوة عضو للفريق**». اكتب اسم الشخص ورقم جواله، واختر الدور، ثم اضغط «**إرسال الدعوة**». كل عضو فريق جديد توصله رسالة نصية فيها رابط صالح لمدة 48 ساعة. | No change | Step 3 automatic check: Check 3 glossary terms: glossary term "mobile number" is in the source, but the approved term «رقم الجوال» (or a form given in the glossary note) was not found in the target. | False positive: «رقم جواله» is «رقم الجوال» with an attached pronoun that refers back to «الشخص» ('the person's ... mobile number'). This is an allowed inflection, not a different term. | Not a defect. «رقم جواله» is the approved «رقم الجوال» with a pronoun referring to «الشخص». It is an allowed inflection. | Judge agent | Not applied |
| S14-2 | Terminology | Not a defect (not counted) | To add people, open **Team** and tap **Invite team member**. Enter the person's name and mobile number, choose a role, and tap **Send invite**. Each new team member gets a text message with a link that is valid for 48 hours. | لإضافة أشخاص، افتح «**الفريق**» واضغط «**دعوة عضو للفريق**». اكتب اسم الشخص ورقم جواله، واختر الدور، ثم اضغط «**إرسال الدعوة**». كل عضو فريق جديد توصله رسالة نصية فيها رابط صالح لمدة 48 ساعة. | No change | Step 3 automatic check: Check 3 glossary terms: glossary term "team member" is in the source, but the approved term «عضو الفريق» (or a form given in the glossary note) was not found in the target. | False positive: «كل عضو فريق جديد» is «عضو الفريق» made indefinite, as 'Each new team member' requires after «كل», and the label «دعوة عضو للفريق» is exactly the glossary form. No «موظف» or other substitute appears. | Not a defect. «كل عضو فريق جديد» is the indefinite form of «عضو الفريق» required after «كل», and the label «دعوة عضو للفريق» matches the glossary exactly. | Judge agent | Not applied |
| S16-1 | Terminology | Not a defect (not counted) | **Owner**: can do everything, including billing. Each workspace has only one Owner. | «**المالك**»: يقدر يسوي كل شي، ومنها الفوترة. كل مساحة عمل لها مالك واحد بس. | No change | Step 3 automatic check: Check 3 glossary terms: glossary term "workspace" is in the source, but the approved term «مساحة العمل» (or a form given in the glossary note) was not found in the target. | False positive: «كل مساحة عمل» is the indefinite singular of «مساحة العمل», which Arabic requires after «كل» for 'Each workspace'. Indefinite forms are allowed by the glossary-forms rule. | Not a defect. «كل مساحة عمل» is the indefinite singular of «مساحة العمل», required after «كل» for 'Each workspace'. | Judge agent | Not applied |
| S16-2 | Fluency | Preference (not counted) | **Owner**: can do everything, including billing. Each workspace has only one Owner. | «**المالك**»: يقدر يسوي كل شي، ومنها الفوترة. كل مساحة عمل لها مالك واحد بس. | No change | Native-reader agent: Pronoun agreement: in "يقدر يسوي كل شي، ومنها الفوترة" the feminine pronoun in "ومنها" has no feminine antecedent; it refers back to "كل شي" (masculine). Reference: Reference: none visible to this agent (Arabic pronoun agreement within the segment itself: "كل شي، ومنها"). Proposed correction: «**المالك**»: يقدر يسوي كل شي، ومن ضمنه الفوترة. كل مساحة عمل لها مالك واحد بس.<br>Grammar agent: Pronoun agreement: in "كل شي، ومنها الفوترة" the feminine suffix in "ومنها" has no feminine or plural antecedent; the only antecedent is "كل شي", which is masculine singular. Borderline: some writers accept "منها" by attraction to "الفوترة" or to an implied plural ("things"), so the reviewer may downgrade this to a preference. Reference: Language rule (Arabic, including Gulf/Saudi usage): a resumptive pronoun agrees in gender and number with its antecedent; "شي" is masculine singular, so the pronoun should be "ـه" ("ومنه"). Proposed correction: «**المالك**»: يقدر يسوي كل شي، ومنه الفوترة. كل مساحة عمل لها مالك واحد بس. | This is a preference, not a defect: «كل شي» means 'all things', and Saudi conversational usage routinely takes a feminine singular pronoun for that non-human collective sense, so «ومنها الفوترة» reads naturally. The Grammar agent itself calls it borderline, the two agents propose different fixes («ومن ضمنه» against «ومنه»), and the only reference is a general rule, not the source, glossary or style guide. | Preference. The only reference is a general agreement rule, the Grammar agent itself calls it borderline, and «كل شي» in the sense 'all things' can take «ومنها» in Saudi conversational usage. The source meaning 'everything, including billing' is intact.<br>Round 2: Defect (Fluency, Minor). Re-ruled under the corrected rule: wrong agreement is a concrete defect even when the only reference is the grammar of the language. Corrected to «ومنه الفوترة». See R2-S16-1. | Judge agent | Re-ruled in round 2: Fixed (see R2-S16-1) |
| S16-3 | Style | Minor | **Owner**: can do everything, including billing. Each workspace has only one Owner. | «**المالك**»: يقدر يسوي كل شي، ومنها الفوترة. كل مساحة عمل لها مالك واحد بس. | «**المالك**»: يقدر يسوي كل شي، ومنها الفوترة. كل مساحة عمل لها «مالك» واحد بس. | Style agent: The second mention of the role name Owner (capitalized in the source: "Each workspace has only one Owner") is written as «مالك واحد»: indefinite and without Arabic quotation marks. The same role label is written «المالك» in quotation marks at the start of this segment and in S40, S43 and S45, so the label is not rendered the same way every time. Reference: Style guide, UI strings: "Translate every UI label exactly as the glossary gives it, every time, and put it in Arabic quotation marks: «الإعدادات»." Style guide, Variety and register, level 1: "Standard wording for everything the reader must find on screen: UI labels, button names, role names". Source: "Each workspace has only one Owner." Proposed correction: «**المالك**»: يقدر يسوي كل شي، ومنها الفوترة. ودور «المالك» في كل مساحة عمل لشخص واحد بس. | «مالك واحد» is the approved term in its indefinite form, which a counted phrase ('only one Owner') requires, so the 'exactly as the glossary gives it' rule is arguably met and only the quotation marks are in question. The proposed rewrite «ودور «المالك» في كل مساحة عمل لشخص واحد بس» adds 'role' and 'person', which the source does not have, and it keeps «ومنها», so it collides with whatever is decided for S16-2. The reader loses nothing here; weigh it as a preference or at most Minor. | Defect (Style, Minor). The source has the capitalized role name 'Owner', and the style guide requires every UI label 'every time' in Arabic quotation marks, as S43 and S45 do with «المالك». The indefinite «مالك» is an allowed glossary form, so only the quotation marks are added and the proposed rewrite is not adopted. | Judge agent | Fixed |
| S17 | Terminology | Not a defect (not counted) | **Manager**: can build schedules, approve requests, and export timesheets, but only for their own branches. | «**مدير**»: يقدر يبني الجداول ويوافق على الطلبات ويصدّر سجلات الدوام، لكن لفروعه بس. | No change | Native-reader agent: Role name is inconsistent in form with the other two in the same list: "«**مدير**»" is indefinite, while S16 has "«**المالك**»" and S18 has "«**عضو الفريق**»" (both definite). A native writer would list the three roles in the same form. If the label must match the app's UI string, the later steps should check which form the UI uses. Reference: Reference: none visible to this agent (internal inconsistency with S16 "«**المالك**»" and S18 "«**عضو الفريق**»"). Proposed correction: «**المدير**»: يقدر يبني الجداول ويوافق على الطلبات ويصدّر سجلات الدوام، لكن لفروعه بس. | The glossary settles this against the finding: Manager = «مدير», with the note 'Role name (label). Keep the label in this form.' The proposed «المدير» is therefore a form the glossary note rules out, the finding cites no reference, and the mismatch with «المالك» and «عضو الفريق» comes from the glossary itself, not from the translation. | Not a defect in the translation. The glossary gives Manager = «مدير» with the note 'Keep the label in this form', so the target follows the instruction and «المدير» is ruled out. The mismatch with «المالك» and «عضو الفريق» comes from the glossary itself.<br>Round 2: Not a defect upheld. Raised again by the round-2 native-reader agent. See R2-S17. | Judge agent | Not applied |
| S20-1 | Terminology | Not a defect (not counted) | {name} has accepted your invite and joined {branch_name}. | تم قبول دعوتك: {name} الحين ضمن {branch_name}. | No change | Step 3 automatic check: Check 3 glossary terms: glossary term "invite" is in the source, but the approved term «دعوة» (or a form given in the glossary note) was not found in the target. | False positive: «دعوتك» is the approved «دعوة» with an attached pronoun for 'your invite'. No other word for 'invite' is used. | Not a defect. «دعوتك» is the approved «دعوة» with an attached pronoun for 'your invite'. | Judge agent | Not applied |
| S20-2 | Style | Preference (not counted) | {name} has accepted your invite and joined {branch_name}. | تم قبول دعوتك: {name} الحين ضمن {branch_name}. | No change | Dialect-consistency agent: Notification message mixes levels in one sentence: the MSA passive «تم قبول دعوتك» and MSA «ضمن» sit beside Saudi conversational «الحين». Borderline: «تم …» is common in Saudi app notifications, but it is still standard wording inside a level-2 message. Reference: Style guide, Variety and register: "Saudi conversational wording for everything the product 'says' to the reader: … notification messages" and "Do not mix levels inside one sentence." Proposed correction: انقبلت دعوتك: {name} الحين في {branch_name}. | The agent admits this is borderline: «تم …» is standard in Saudi app notifications, and the passive is how the target obeys the rule that {name} must not force a masculine or feminine verb. The colon also splits the line into two clauses, so 'inside one sentence' is debatable, and «انقبلت دعوتك» may read as too slangy for a written notification. Changing «ضمن» to «في» is pure preference. | Preference. The agent admits it is borderline, and the style guide does not establish «تم قبول» as outside the light Saudi app register. The neutral structure also satisfies the rule that {name} must not force a gendered verb, and «ضمن» to «في» has no reference.<br>Round 2: Preference upheld. Raised again by the round-2 dialect-consistency agent; the text stays. See R2-S20. | Judge agent | Logged, not applied |
| S22 | Locale | Preference (not counted) | Open **Schedule** and pick a week. Tap any empty slot to add a shift, then choose a team member, a start time, and an end time. If you don't know yet who will work a shift, save it as an **Open shift**. Team members at that branch can then pick it up themselves. | افتح «**الجدول**» واختر الأسبوع. اضغط أي خانة فاضية لإضافة وردية، ثم اختر عضو الفريق ووقت البداية ووقت النهاية. وإذا ما تعرف للحين مين راح يشتغل في الوردية، احفظها كـ«**وردية مفتوحة**». وقتها أعضاء الفريق في هذا الفرع يقدرون ياخذونها بنفسهم. | No change | Native-reader agent: "مين" in "مين راح يشتغل في الوردية" is the Hejazi/Egyptian/Levantine form. The rest of the text is written in a Najdi-leaning Saudi register ("وش", "ودّك", "لين", "هالأسبوع"), where the word is "من". The mix reads as a slip from another variety. Reference: Brief: "Variety: Gulf (Saudi Arabia)"; internal inconsistency with S10 "وش أول شي ودّك فيه؟". Proposed correction: افتح «**الجدول**» واختر الأسبوع. اضغط أي خانة فاضية لإضافة وردية، ثم اختر عضو الفريق ووقت البداية ووقت النهاية. وإذا ما تعرف للحين من اللي راح يشتغل في الوردية، احفظها كـ«**وردية مفتوحة**». وقتها أعضاء الفريق في هذا الفرع يقدرون ياخذونها بنفسهم. | «مين» is Hejazi, which is a Saudi variety, and it is not in the style guide's list of forbidden words, so the cited reference ('Variety: Gulf (Saudi Arabia)') does not make it wrong; this is closer to a preference than a Locale error. The correction «ما تعرف للحين من اللي راح يشتغل» is also risky in unvowelled text, because «من اللي» can be read as the preposition 'from those who'. | Preference. «مين» is used in Saudi (Hejazi) speech and is not on the style guide's list of forbidden words, so 'Variety: Gulf (Saudi Arabia)' does not make it wrong. The proposed «من اللي» is also ambiguous in unvowelled text.<br>Round 2: Preference upheld. Raised again by two round-2 agents and ruled again; the text stays. See R2-S22 and open question Q23. | Judge agent | Logged, not applied |
| S23 | Style | Preference (not counted) | In a hurry? Tap **Copy last week** and let Rotalume do the heavy lifting. You only need to fix what has changed. | ما عندك وقت؟ اضغط «**نسخ الأسبوع الماضي**» وخلّ الباقي على Rotalume. عليك بس تعديل اللي تغيّر. | No change | Native-reader agent: "عليك بس تعديل اللي تغيّر" is a stiff nominal construction ("عليك" + verbal noun) dropped into a colloquial sentence; it reads like a word-for-word rendering. A Saudi writer would use a verb here. Reference: Reference: none visible to this agent. Proposed correction: ما عندك وقت؟ اضغط «**نسخ الأسبوع الماضي**» وخلّ الباقي على Rotalume. ما عليك إلا تعدّل اللي تغيّر.<br>Dialect-consistency agent: Tip mixes levels in one sentence: «عليك بس تعديل اللي تغيّر» uses the MSA construction «عليك» + verbal noun «تعديل» together with Saudi conversational «بس» and «اللي». Reference: Style guide, Variety and register: "Saudi conversational wording for everything the product 'says' to the reader: … short questions (… 'In a hurry?' …), tips" and "Do not mix levels inside one sentence." Proposed correction: ما عندك وقت؟ اضغط «**نسخ الأسبوع الماضي**» وخلّ الباقي على Rotalume. عليك بس تعدّل اللي تغيّر. | The defect is small and the meaning is intact, and the two agents disagree on the fix: «ما عليك إلا تعدّل» against «عليك بس تعدّل», the second of which is itself not idiomatic. The Native-reader agent cites no reference at all, so only the Dialect agent's 'do not mix levels' reading supports this; if applied, one correction must be chosen and it stays Minor. | Preference. The style guide itself endorses verbal nouns in conversational messages, so «عليك بس تعديل اللي تغيّر» is not shown to mix levels. The source meaning is intact, and the two agents disagree on the fix.<br>Round 2: Defect (Style, Minor). Re-ruled under the corrected rule: the neutral-structure rule does not cover a tip, and «عليك» + verbal noun with «بس» and «اللي» mixes levels in one sentence. Corrected to «وعدّل بس اللي تغيّر.» See R2-S23. | Judge agent | Re-ruled in round 2: Fixed (see R2-S23) |
| S26-1 | Terminology | Not a defect (not counted) | You can edit a published shift at any time, unless the team member has already clocked in. To change a shift that is in progress, ask the team member to clock out first. | تقدر تعدّل الوردية المنشورة في أي وقت، إلا إذا عضو الفريق سجّل حضوره. ولتعديل وردية جارية الحين، اطلب من عضو الفريق يسجّل انصرافه أول. | No change | Step 3 automatic check: Check 3 glossary terms: glossary term "clock in" is in the source, but the approved term «تسجيل الحضور» (or a form given in the glossary note) was not found in the target. | False positive: the glossary note says that in running text the form is «يسجّل حضوره», and the target has «سجّل حضوره», the same verb phrase in the past tense as 'has already clocked in' requires. This is the approved running-text form. | Not a defect. «سجّل حضوره» is the glossary's running-text form «يسجّل حضوره» in the past tense, as 'has already clocked in' requires. | Judge agent | Not applied |
| S26-2 | Terminology | Not a defect (not counted) | You can edit a published shift at any time, unless the team member has already clocked in. To change a shift that is in progress, ask the team member to clock out first. | تقدر تعدّل الوردية المنشورة في أي وقت، إلا إذا عضو الفريق سجّل حضوره. ولتعديل وردية جارية الحين، اطلب من عضو الفريق يسجّل انصرافه أول. | No change | Step 3 automatic check: Check 3 glossary terms: glossary term "Publish" is in the source, but the approved term «نشر» (or a form given in the glossary note) was not found in the target. | False positive: the source 'a published shift' is an adjective, not the Publish button label, and «الوردية المنشورة» uses the participle of the same approved word «نشر». No competing word for 'publish' appears, so there is no deviation. | Not a defect. 'Published' is an adjective here, not the button label, and «المنشورة» is the participle of the approved «نشر». No competing word is used. | Judge agent | Not applied |
| S27 | Style | Preference (not counted) | A shift can't be longer than 12 hours. Rotalume also warns you when someone has fewer than 8 hours of rest between two shifts. | الوردية ما تزيد عن 12 ساعة. ويحذّرك Rotalume إذا كانت الراحة بين ورديتين لأي شخص أقل من 8 ساعات. | No change | Native-reader agent: Unclear: "الوردية ما تزيد عن 12 ساعة" reads as a description of fact (shifts do not go over 12 hours), not clearly as a limit the app enforces. The reader cannot tell whether this is a rule, a block, or advice. Reference: Reference: none visible to this agent. Proposed correction: أقصى مدة للوردية 12 ساعة. ويحذّرك Rotalume إذا كانت الراحة بين ورديتين لأي شخص أقل من 8 ساعات. | No reference is cited, so by the pack's own definition this is a preference. The source 'A shift can't be longer than 12 hours' is itself a plain statement, and «الوردية ما تزيد عن 12 ساعة» mirrors it in the usual way Saudi policies state a limit. If the claim were that the modality is weakened, the category would be Accuracy, not Style, and the finding does not argue that. | Preference. No reference is cited. «الوردية ما تزيد عن 12 ساعة» conveys the source's plain statement 'A shift can't be longer than 12 hours' without changing the meaning. | Judge agent | Logged, not applied |
| S28 | Terminology | Not a defect (not counted) | 4. Requests: time off and shift swaps | 4. الطلبات: الإجازة وتبديل الورديات | No change | Step 3 automatic check: Check 3 glossary terms: glossary term "Shift swap" is in the source, but the approved term «تبديل وردية» (or a form given in the glossary note) was not found in the target. | False positive: «تبديل الورديات» is the approved «تبديل وردية» with the noun made definite and plural, matching the lower-case plural 'shift swaps' in a heading and standing parallel to «الإجازة». The glossary-forms rule allows definite and plural forms, and no forbidden word («مناوبة», «شفت», «دوام») is used. | Not a defect. «تبديل الورديات» is the approved «تبديل وردية» made definite and plural for the lower-case plural 'shift swaps' in a heading. No forbidden word for 'shift' is used. | Judge agent | Not applied |
| S34-1 | Terminology | Not a defect (not counted) | A swap does not take effect until a manager approves it, even if both team members have already agreed. Requests that nobody answers within 72 hours are marked **Expired**, and the team member is asked to send a new one. | التبديل ما يصير ساري إلا بعد ما يوافق عليه مدير، حتى لو كان الاثنين من أعضاء الفريق متفقين من قبل. والطلبات اللي ما أحد يرد عليها خلال 72 ساعة تتحول حالتها إلى «**منتهي الصلاحية**»، ونطلب من عضو الفريق يرسل طلب جديد. | No change | Step 3 automatic check: Check 3 glossary terms: glossary term "Approve" is in the source, but the approved term «موافقة» (or a form given in the glossary note) was not found in the target. | False positive: the glossary note says that in running text the verb is «يوافق على», and the target has exactly that in «يوافق عليه مدير». The verbal noun «موافقة» is for the button label, which this sentence is not. | Not a defect. «يوافق عليه مدير» uses the running-text verb «يوافق على» that the glossary note prescribes. The verbal noun «موافقة» is for the button only. | Judge agent | Not applied |
| S34-2 | Style | Preference (not counted) | A swap does not take effect until a manager approves it, even if both team members have already agreed. Requests that nobody answers within 72 hours are marked **Expired**, and the team member is asked to send a new one. | التبديل ما يصير ساري إلا بعد ما يوافق عليه مدير، حتى لو كان الاثنين من أعضاء الفريق متفقين من قبل. والطلبات اللي ما أحد يرد عليها خلال 72 ساعة تتحول حالتها إلى «**منتهي الصلاحية**»، ونطلب من عضو الفريق يرسل طلب جديد. | No change | Native-reader agent: "الاثنين من أعضاء الفريق" is a heavy, translated-sounding phrase for two people already identified in context; a native writer would say "العضوين" or "الطرفين". Reference: Reference: none visible to this agent. Proposed correction: التبديل ما يصير ساري إلا بعد ما يوافق عليه مدير، حتى لو كان العضوين متفقين من قبل. والطلبات اللي ما أحد يرد عليها خلال 72 ساعة تتحول حالتها إلى «**منتهي الصلاحية**»، ونطلب من عضو الفريق يرسل طلب جديد. | No reference is cited, so this is a preference. The correction also damages terminology: «العضوين» drops «الفريق» from the approved «أعضاء الفريق», and «الطرفين» is a different word, while the target «الاثنين من أعضاء الفريق» keeps the glossary plural intact. | Preference. No reference is cited. The proposed «العضوين» or «الطرفين» would drop or replace the approved «أعضاء الفريق», which the target keeps intact. | Judge agent | Logged, not applied |
| S36-1 | Terminology | Not a defect (not counted) | When team members clock in and clock out on their mobile phones, Rotalume records their hours for you. At the end of the month, open **Timesheets**, check the totals, and tap **Export** to download the file. | لما يسجّل أعضاء الفريق حضورهم ويسجّلون انصرافهم من جوالاتهم، Rotalume يسجّل ساعاتهم عنك. في نهاية الشهر، افتح «**سجل الدوام**» وراجع المجاميع، ثم اضغط «**تصدير**» لتنزيل الملف. | No change | Step 3 automatic check: Check 3 glossary terms: glossary term "mobile phone" is in the source, but the approved term «الجوال» (or a form given in the glossary note) was not found in the target. | False positive: «من جوالاتهم» is «الجوال» in the plural with an attached pronoun for 'their mobile phones'. Both inflections are allowed and no forbidden word appears. | Not a defect. «جوالاتهم» is the approved «الجوال» in the plural with an attached pronoun for 'their mobile phones'. | Judge agent | Not applied |
| S36-2 | Terminology | Not a defect (not counted) | When team members clock in and clock out on their mobile phones, Rotalume records their hours for you. At the end of the month, open **Timesheets**, check the totals, and tap **Export** to download the file. | لما يسجّل أعضاء الفريق حضورهم ويسجّلون انصرافهم من جوالاتهم، Rotalume يسجّل ساعاتهم عنك. في نهاية الشهر، افتح «**سجل الدوام**» وراجع المجاميع، ثم اضغط «**تصدير**» لتنزيل الملف. | No change | Step 3 automatic check: Check 3 glossary terms: glossary term "clock in" is in the source, but the approved term «تسجيل الحضور» (or a form given in the glossary note) was not found in the target. | False positive: «يسجّل أعضاء الفريق حضورهم» is the running-text form the glossary note prescribes («يسجّل حضوره»), with the pronoun made plural for 'team members'. The script was looking for the action name «تسجيل الحضور», which does not belong in this sentence. | Not a defect. «يسجّل أعضاء الفريق حضورهم» is the glossary's running-text form «يسجّل حضوره», inflected for a plural subject. | Judge agent | Not applied |
| S36-3 | Terminology | Not a defect (not counted) | When team members clock in and clock out on their mobile phones, Rotalume records their hours for you. At the end of the month, open **Timesheets**, check the totals, and tap **Export** to download the file. | لما يسجّل أعضاء الفريق حضورهم ويسجّلون انصرافهم من جوالاتهم، Rotalume يسجّل ساعاتهم عنك. في نهاية الشهر، افتح «**سجل الدوام**» وراجع المجاميع، ثم اضغط «**تصدير**» لتنزيل الملف. | No change | Step 3 automatic check: Check 3 glossary terms: glossary term "clock out" is in the source, but the approved term «تسجيل الانصراف» (or a form given in the glossary note) was not found in the target. | False positive: «يسجّلون انصرافهم» is the glossary's running-text form «يسجّل انصرافه», inflected for the plural subject. This is the approved term, not a deviation. | Not a defect. «يسجّلون انصرافهم» is the glossary's running-text form «يسجّل انصرافه», inflected for a plural subject. | Judge agent | Not applied |
| S39 | Accuracy | Not a defect (not counted) | Fahad: 2 shifts, 11 hours, no overtime | فهد: ورديتين، 11 ساعة، بدون ساعات إضافية | No change | Step 3 automatic check: Check 2 numbers: number "2" written in digits in the source is not in the target in digits. | Not an Accuracy error: the number 2 is fully expressed by the dual «ورديتين», and the glossary note prescribes exactly this counted form («وردية واحدة، ورديتين، 3 ورديات، 22 وردية»). Writing «2 وردية» or «2 ورديات» to satisfy the script would break the glossary and Arabic number rules. | Not a defect. The number 2 is fully expressed by the dual «ورديتين», which is exactly the counted form the glossary note prescribes. A digit here would break the glossary and Arabic number rules. | Judge agent | Not applied |
| S42-1 | Terminology | Not a defect (not counted) | Rotalume is free for workspaces with up to 5 team members, and there are no strings attached. The Team plan costs SAR 19 per team member per month. Prices do not include VAT (15%). | Rotalume مجاني لمساحات العمل اللي فيها 5 من أعضاء الفريق أو أقل، وبدون أي شروط مخفية. سعر باقة الفريق 19 ريال لكل عضو فريق في الشهر. الأسعار ما تشمل ضريبة القيمة المضافة (15%). | No change | Step 3 automatic check: Check 3 glossary terms: glossary term "workspace" is in the source, but the approved term «مساحة العمل» (or a form given in the glossary note) was not found in the target. | False positive: «لمساحات العمل» is the approved term in the plural with an attached preposition, as 'for workspaces' requires. The plural is an allowed form. | Not a defect. «لمساحات العمل» is the approved term in the plural with an attached preposition, as 'for workspaces' requires. | Judge agent | Not applied |
| S42-2 | Style | Preference (not counted) | Rotalume is free for workspaces with up to 5 team members, and there are no strings attached. The Team plan costs SAR 19 per team member per month. Prices do not include VAT (15%). | Rotalume مجاني لمساحات العمل اللي فيها 5 من أعضاء الفريق أو أقل، وبدون أي شروط مخفية. سعر باقة الفريق 19 ريال لكل عضو فريق في الشهر. الأسعار ما تشمل ضريبة القيمة المضافة (15%). | No change | Native-reader agent: "5 من أعضاء الفريق أو أقل" — number + "من أعضاء الفريق" is a calqued counting pattern; natural Arabic counts directly ("5 أعضاء أو أقل"). Reference: Reference: none visible to this agent. Proposed correction: Rotalume مجاني لمساحات العمل اللي فيها 5 أعضاء أو أقل، وبدون أي شروط مخفية. سعر باقة الفريق 19 ريال لكل عضو فريق في الشهر. الأسعار ما تشمل ضريبة القيمة المضافة (15%). | No reference is cited, so this is a preference. The correction «5 أعضاء أو أقل» cuts «الفريق» from the approved «أعضاء الفريق», while the target's «5 من أعضاء الفريق» is the grammatical way to keep the definite glossary plural after a number. | Preference. No reference is cited. The proposed «5 أعضاء أو أقل» would cut «الفريق» from the approved «أعضاء الفريق», which the target keeps whole. | Judge agent | Logged, not applied |
| S43 | Terminology | Not a defect (not counted) | Every new workspace starts with a 30-day free trial of the Team plan. When the trial is about to end, the Owner sees this message: | كل مساحة عمل جديدة تبدأ بفترة تجريبية مجانية لمدة 30 يوم على باقة الفريق. ولما تقرّب الفترة التجريبية من نهايتها، يشوف «المالك» هذي الرسالة: | No change | Step 3 automatic check: Check 3 glossary terms: glossary term "workspace" is in the source, but the approved term «مساحة العمل» (or a form given in the glossary note) was not found in the target. | False positive: «كل مساحة عمل جديدة» is «مساحة العمل» in the indefinite form that «كل» and the adjective require for 'Every new workspace'. Allowed inflection, no defect. | Not a defect. «كل مساحة عمل جديدة» is the indefinite form of «مساحة العمل» required after «كل» for 'Every new workspace'. | Judge agent | Not applied |
| S44-1 | Terminology | Not a defect (not counted) | Your free trial ends on {end_date}. Choose a plan to keep your schedules. | فترتك التجريبية المجانية تنتهي يوم {end_date}. ولازم اختيار باقة عشان تبقى جداولك محفوظة. | No change | Step 3 automatic check: Check 3 glossary terms: glossary term "Schedule" is in the source, but the approved term «الجدول» (or a form given in the glossary note) was not found in the target. | False positive: «جداولك» is the plural that the glossary note itself gives («الجداول»), with an attached pronoun for 'your schedules'. This is the approved term. | Not a defect. «جداولك» is the glossary's own plural «الجداول» with an attached pronoun for 'your schedules'. | Judge agent | Not applied |
| S44-2 | Terminology | Not a defect (not counted) | Your free trial ends on {end_date}. Choose a plan to keep your schedules. | فترتك التجريبية المجانية تنتهي يوم {end_date}. ولازم اختيار باقة عشان تبقى جداولك محفوظة. | No change | Step 3 automatic check: Check 3 glossary terms: glossary term "plan" is in the source, but the approved term «الباقة» (or a form given in the glossary note) was not found in the target. | False positive: «اختيار باقة» uses «الباقة» in the indefinite form for 'a plan'. The forbidden «خطة» does not appear. | Not a defect. «باقة» in «اختيار باقة» is the approved «الباقة» in the indefinite form for 'a plan'. The forbidden «خطة» does not appear. | Judge agent | Not applied |
| S44-3 | Style | Preference (not counted) | Your free trial ends on {end_date}. Choose a plan to keep your schedules. | فترتك التجريبية المجانية تنتهي يوم {end_date}. ولازم اختيار باقة عشان تبقى جداولك محفوظة. | No change | Native-reader agent: "ولازم اختيار باقة" is an impersonal verbal-noun construction that sounds stiff and translated in a message addressed directly to the owner (the first sentence says "فترتك" and "جداولك"). A native writer would address the reader with a verb. Reference: Reference: none visible to this agent. Proposed correction: فترتك التجريبية المجانية تنتهي يوم {end_date}. اختر باقة عشان تبقى جداولك محفوظة.<br>Dialect-consistency agent: Notification message mixes levels in one sentence: «ولازم اختيار باقة» uses an MSA verbal noun («اختيار») after «لازم», followed by Saudi conversational «عشان». Saudi conversational wording uses a conjugated verb here («لازم تختار»). Reference: Style guide, Variety and register: "Saudi conversational wording for everything the product 'says' to the reader: … notification messages" and "Do not mix levels inside one sentence." Proposed correction: فترتك التجريبية المجانية تنتهي يوم {end_date}. ولازم تختار باقة عشان تبقى جداولك محفوظة. | The verbal noun «اختيار» keeps this notification neutral for an Owner who may be a woman, in line with the Address section's preference for 'a verbal noun or a neutral structure to a gendered verb'; both corrections («اختر باقة», «لازم تختار باقة») make the message masculine. The two agents also propose different fixes and the Native-reader agent cites no reference, so the 'do not mix levels' reading has to be weighed against the gender rule before anything is changed. | Preference. The style guide endorses verbal nouns as a neutral structure in messages, so «ولازم اختيار باقة» is not shown to mix levels. Both proposed fixes («اختر باقة», «لازم تختار باقة») make a message to an Owner of either gender masculine, and the agents disagree on the fix.<br>Round 2: Defect (Style, Minor). Re-ruled under the corrected rule: the neutral-structure rule covers messages with {first_name} and direct questions, and this message is neither; «لازم» also states an obligation the source does not. Corrected to «اختر باقة عشان تبقى جداولك محفوظة.» See R2-S44. | Judge agent | Re-ruled in round 2: Fixed (see R2-S44) |
| S45-1 | Terminology | Not a defect (not counted) | We send an invoice to the Owner's email address on the 1st of each month. For example, a workspace with 14 team members pays SAR 266.00 before VAT. You can change or cancel your plan at any time under **Settings > Plan**. | نرسل فاتورة على بريد «المالك» الإلكتروني يوم 1 من كل شهر. مثلاً، مساحة عمل فيها 14 من أعضاء الفريق تدفع 266.00 ريال قبل ضريبة القيمة المضافة. تقدر تغيّر باقتك أو تلغيها في أي وقت من «**الإعدادات > الباقة**». | No change | Step 3 automatic check: Check 3 glossary terms: glossary term "workspace" is in the source, but the approved term «مساحة العمل» (or a form given in the glossary note) was not found in the target. | False positive: «مساحة عمل فيها 14 …» is the indefinite form of «مساحة العمل» for 'a workspace'. Allowed inflection. | Not a defect. «مساحة عمل فيها 14» is the indefinite form of «مساحة العمل» for 'a workspace'. | Judge agent | Not applied |
| S45-2 | Style | Preference (not counted) | We send an invoice to the Owner's email address on the 1st of each month. For example, a workspace with 14 team members pays SAR 266.00 before VAT. You can change or cancel your plan at any time under **Settings > Plan**. | نرسل فاتورة على بريد «المالك» الإلكتروني يوم 1 من كل شهر. مثلاً، مساحة عمل فيها 14 من أعضاء الفريق تدفع 266.00 ريال قبل ضريبة القيمة المضافة. تقدر تغيّر باقتك أو تلغيها في أي وقت من «**الإعدادات > الباقة**». | No change | Native-reader agent: "14 من أعضاء الفريق" — same calqued counting pattern as S42; natural wording is "14 عضو". Reference: Reference: none visible to this agent. Proposed correction: نرسل فاتورة على بريد «المالك» الإلكتروني يوم 1 من كل شهر. مثلاً، مساحة عمل فيها 14 عضو تدفع 266.00 ريال قبل ضريبة القيمة المضافة. تقدر تغيّر باقتك أو تلغيها في أي وقت من «**الإعدادات > الباقة**». | No reference is cited, so this is a preference. The correction «14 عضو» drops «الفريق» from the approved term «عضو الفريق», whereas the target «14 من أعضاء الفريق» keeps the glossary plural whole; any change here would also have to be made identically in S42. | Preference. No reference is cited. The proposed «14 عضو» drops «الفريق» from the approved term, which «14 من أعضاء الفريق» keeps whole. | Judge agent | Logged, not applied |
| S48 | Terminology | Not a defect (not counted) | Wait 60 seconds, then tap **Resend code**. Check that your mobile phone has a signal and that you typed the right number. Still nothing? Contact us and we'll sort it out. | انتظر 60 ثانية، ثم اضغط «**إعادة إرسال الرمز**». تأكد إن في جوالك شبكة وإنك كتبت الرقم الصحيح. للحين ما وصل شي؟ تواصل معنا ونحلّها لك. | No change | Step 3 automatic check: Check 3 glossary terms: glossary term "mobile phone" is in the source, but the approved term «الجوال» (or a form given in the glossary note) was not found in the target. | False positive: «في جوالك» is «الجوال» with an attached pronoun for 'your mobile phone'. No forbidden word is used. | Not a defect. «جوالك» is the approved «الجوال» with an attached pronoun for 'your mobile phone'. | Judge agent | Not applied |
| S49 | Terminology | Not a defect (not counted) | **A team member can't see their shifts.** | **عضو فريق ما يقدر يشوف وردياته.** | No change | Step 3 automatic check: Check 3 glossary terms: glossary term "team member" is in the source, but the approved term «عضو الفريق» (or a form given in the glossary note) was not found in the target. | False positive: «عضو فريق» is the indefinite form of «عضو الفريق», matching the source's indefinite 'A team member'. The role name is not replaced by «موظف» or any other word. | Not a defect. «عضو فريق» is the indefinite form of «عضو الفريق», matching the source's 'A team member'. | Judge agent | Not applied |
| S50 | Terminology | Not a defect (not counted) | First, make sure you have published the schedule. Then check that they signed in with the same mobile number you sent the invite to. | أول شي، تأكد إنك نشرت الجدول. بعدها تأكد إنه سجّل دخوله بنفس رقم الجوال اللي أرسلت عليه الدعوة. | No change | Step 3 automatic check: Check 3 glossary terms: glossary term "Sign in" is in the source, but the approved term «تسجيل الدخول» (or a form given in the glossary note) was not found in the target. | False positive: the glossary note gives the running-text verb «سجّل دخولك», and the target's «سجّل دخوله» is the same verb phrase with a third-person pronoun for 'they signed in'. The label «تسجيل الدخول» belongs on the button, not in this sentence. | Not a defect. «سجّل دخوله» is the glossary's running-text verb «سجّل دخولك» with a third-person pronoun for 'they signed in'. | Judge agent | Not applied |
| S53 | Style | Preference (not counted) | Are you sure you want to delete this shift? You can't undo this. | أكيد حذف هذي الوردية؟ ما فيه تراجع بعد الحذف. | No change | Native-reader agent: "أكيد حذف هذي الوردية؟" is telegraphic and not how a Saudi speaker asks for confirmation; "أكيد" followed by a bare verbal noun is not idiomatic. A verb is needed ("أكيد تبي تحذف..."). Reference: Brief: "Variety: Gulf (Saudi Arabia)". Proposed correction: أكيد تبي تحذف هذي الوردية؟ ما فيه تراجع بعد الحذف.<br>Dialect-consistency agent: Message shown by the app mixes levels in one sentence: «أكيد حذف هذي الوردية؟» puts the MSA verbal noun «حذف» between conversational «أكيد» and Saudi «هذي». Same pattern as S23 and S44. Saudi conversational wording uses a verb, and the guide's preferred word «تبي» fits. Reference: Style guide, Variety and register: "Saudi conversational wording for everything the product 'says' to the reader: … notification messages"; "Preferred everyday words at level 2: … «تبي» (you want)"; "Do not mix levels inside one sentence." Proposed correction: أكيد تبي تحذف هذي الوردية؟ ما فيه تراجع بعد الحذف. | This is a direct question, and the style guide says such wording must fit a woman and a man and should 'prefer a verbal noun or a neutral structure to a gendered verb'; «أكيد حذف هذي الوردية؟» does exactly that. The agreed correction «أكيد تبي تحذف» is masculine (a woman would be asked «تبين تحذفين»), so it breaks the Address rule to satisfy the register rule. If the wording is judged too telegraphic, any fix must stay gender-neutral, and this correction does not. | Preference. This is a direct question, where the style guide says to 'prefer a verbal noun or a neutral structure to a gendered verb', and «أكيد حذف هذي الوردية؟» does that. The proposed «أكيد تبي تحذف» is masculine, so the finding cannot answer its challenge.<br>Round 2: Defect (Style, Minor). Re-ruled under the corrected rule: a question without a verb is a concrete defect. The masculine «أكيد تبي تحذف» stays rejected; the neutral «أكيد نحذف هذي الوردية؟» is applied. See R2-S53. | Judge agent | Re-ruled in round 2: Fixed (see R2-S53) |
| S59-1 | Terminology | Not a defect (not counted) | That's it. You're all set, so go ahead and publish your first schedule! | بس كذا. كل شي جاهز عندك، والحين دور نشر أول جدول لك! | No change | Step 3 automatic check: Check 3 glossary terms: glossary term "Schedule" is in the source, but the approved term «الجدول» (or a form given in the glossary note) was not found in the target. | False positive: «أول جدول لك» is «الجدول» in the indefinite form that 'your first schedule' requires after «أول». No other word for 'schedule' is used. | Not a defect. «أول جدول لك» has the approved «الجدول» in the indefinite form required after «أول». | Judge agent | Not applied |
| S59-2 | Style | Preference (not counted) | That's it. You're all set, so go ahead and publish your first schedule! | بس كذا. كل شي جاهز عندك، والحين دور نشر أول جدول لك! | No change | Native-reader agent: "والحين دور نشر أول جدول لك" is awkward: "دور" + verbal noun is not a natural way to say that the next step is publishing, and "دور" can momentarily be read as "role", which is a term used elsewhere in the article (S14 "اختر الدور", S15 "ثلاثة أدوار"). Reference: Reference: none visible to this agent (possible confusion with "الدور" in S14 and "أدوار" in S15). Proposed correction: بس كذا. كل شي جاهز عندك، والحين جاء وقت نشر أول جدول لك! | The finding cites no source, glossary or style-guide reference, so under the pack's definition it is a preference and cannot be applied. The proposed «والحين جاء وقت نشر» also brings the MSA verb «جاء» into a level-2 closing line beside «الحين», which the 'do not mix levels inside one sentence' rule forbids. | Preference. No source, glossary or style-guide reference is cited. The proposed «جاء وقت نشر» would also put an MSA verb beside «الحين» in a level-2 closing line.<br>Round 2: Defect (Style, Minor). Re-ruled under the corrected rule: the clash with «دور» = role is an ambiguity and the instruction of the source is lost. Corrected to «والحين انشر أول جدول لك!» See R2-S59. | Judge agent | Re-ruled in round 2: Fixed (see R2-S59) |
| R2-S02 | Style | Preference (not counted) | Getting started: your first week as a manager | البداية: أسبوعك الأول بدور مدير | No change | Round 2 · Raised in delivery review: Review A4: «بدور مدير» in the heading is heavy; «كمدير» is lighter. The review itself lists it as a preference. Reference: Delivery review, A4. No source, glossary or style-guide rule quoted. Proposed correction: البداية: أسبوعك الأول كمدير | Round 2 · Devil's advocate: The review itself files this under "Not counted (preferences)". «بدور مدير» is grammatical and keeps the glossary label «مدير» intact; «كمدير» attaches a prefix to the label. No rule is quoted. Preference. | Round 2 · Preference. No rule supports a change; the heading is grammatical and keeps the glossary label «مدير» whole. | Judge agent (round 2) | Logged, not applied |
| R2-S11 | Style | Preference (not counted) | Not sure where to start? Add your branches first. Everything else builds on them. | مو واضح من وين البداية؟ أول شي إضافة فروعك، وكل شي ثاني ينبني عليها. | No change | Round 2 · Raised in delivery review: Review A2 item 6: «أول شي إضافة فروعك» uses a verbal noun where the rest of the text uses the imperative. Reference: Delivery review, A2 item 6, citing the style guide: tips are level 2; "Friendly and short". Source: "Add your branches first." Proposed correction: مو واضح من وين البداية؟ أول شي أضف فروعك، وكل شي ثاني ينبني عليها. | Round 2 · Devil's advocate: «أول شي إضافة فروعك» is a complete nominal sentence that answers the question before it («من وين البداية؟»): "the first thing is adding your branches". Nothing is ungrammatical, no meaning is added or lost, and «إضافة» is the word of the button «إضافة فرع» the reader is about to press. A verbal noun is not standard-only wording, so "mixed levels" does not apply. The finding says another wording would be livelier, which is a preference. | Round 2 · Preference. Under the corrected rule a finding must name a concrete defect. «أول شي إضافة فروعك» is a complete, grammatical sentence that answers the question before it, with the meaning of the source intact and no second reading. The review's point is that a verb would read better; that is "another wording would be nicer". The delivery review is not followed on this item and the text stays. | Judge agent (round 2) | Logged, not applied |
| R2-S16-1 | Fluency | Minor | **Owner**: can do everything, including billing. Each workspace has only one Owner. | «**المالك**»: يقدر يسوي كل شي، ومنها الفوترة. كل مساحة عمل لها «مالك» واحد بس. | «**المالك**»: يقدر يسوي كل شي، ومنه الفوترة. كل مساحة عمل لها «مالك» واحد بس. | Round 2 · Native-reader agent: Agreement: in «يقدر يسوي كل شي، ومنها الفوترة» the feminine pronoun in «ومنها» has no feminine antecedent; the only antecedent is «كل شي», masculine singular. Reference: The target language's grammar (a pronoun agrees with its antecedent); none other visible to this agent. Proposed correction: «**المالك**»: يقدر يسوي كل شي، حتى الفوترة. كل مساحة عمل لها «مالك» واحد بس.<br>Round 2 · Grammar agent: Pronoun agreement: «كل شي، ومنها الفوترة». The suffix «ـها» is feminine; its antecedent «كل شي» is masculine singular. Reference: Rule of the language: a pronoun agrees in gender and number with its antecedent («شي» is masculine singular, so «ومنه»). Proposed correction: «**المالك**»: يقدر يسوي كل شي، ومنه الفوترة. كل مساحة عمل لها «مالك» واحد بس. | Round 2 · Devil's advocate: The grammar point is real but small, and the two agents disagree on the fix. «حتى الفوترة» turns "including" into "even", which adds emphasis the source does not have. If anything is changed, «ومنه» is the smaller change and keeps the wording the file uses for "including" in S38 («منها»). Round 1 held that Saudi speech accepts «منها» after «كل شي»; no reference was given for that then and none is given now. | Round 2 · Defect (Fluency, Minor). Wrong agreement is a concrete defect under the corrected rule, with the grammar of the language as reference; round 1's claim that Saudi usage takes the feminine here had no reference. Of the two corrections, «ومنه» changes least and adds no emphasis, so it is chosen over «حتى». | Judge agent (round 2) | Fixed |
| R2-S16-2 | Style | Not a defect (not counted) | **Owner**: can do everything, including billing. Each workspace has only one Owner. | «**المالك**»: يقدر يسوي كل شي، ومنها الفوترة. كل مساحة عمل لها «مالك» واحد بس. | No change | Round 2 · Raised in delivery review: Review A5: after the round-1 fix the label is written two ways in one segment, «المالك» and «مالك» in quotation marks; «مالك» is not the label "exactly as the glossary gives it". Reference: Delivery review, A5, citing the style guide, UI strings: "Translate every UI label exactly as the glossary gives it, every time, and put it in Arabic quotation marks". Proposed correction: «**المالك**»: يقدر يسوي كل شي، ومنها الفوترة. ودور «المالك» في كل مساحة عمل لشخص واحد بس. | Round 2 · Devil's advocate: The cycle's rule on glossary forms says the approved term "may be inflected as the sentence requires: definite or indefinite"; "only one Owner" needs the indefinite. The review itself calls the round-1 fix "acceptable, harmless". The proposed rewrite adds "role" and "person", which the source does not have. Not a defect. | Round 2 · Not a defect. The indefinite «مالك» is an allowed form of the approved term (the cycle's rule on glossary forms), the source needs it ("only one Owner"), and it now carries the quotation marks the style guide asks for. The rewrite would add words the source does not have. | Judge agent (round 2) | Not applied |
| R2-S17 | Style | Not a defect (not counted) | **Manager**: can build schedules, approve requests, and export timesheets, but only for their own branches. | «**مدير**»: يقدر يبني الجداول ويوافق على الطلبات ويصدّر سجلات الدوام، لكن لفروعه بس. | No change | Round 2 · Native-reader agent: The three role names in the list are not in the same form: «**مدير**» is indefinite while «**المالك**» (S16) and «**عضو الفريق**» (S18) are definite. Reference: None visible to this agent (inconsistency inside the list S16 to S18). Proposed correction: «**المدير**»: يقدر يبني الجداول ويوافق على الطلبات ويصدّر سجلات الدوام، لكن لفروعه بس. | Round 2 · Devil's advocate: The glossary gives Manager = «مدير» with the note "Keep the label in this form". «المدير» is ruled out by the client's own instruction. Round 1 sent this to the client as Q21, and nothing has changed. | Round 2 · Not a defect in the translation. The glossary note says "Keep the label in this form". Open question Q21 stands. | Judge agent (round 2) | Not applied |
| R2-S20 | Style | Preference (not counted) | {name} has accepted your invite and joined {branch_name}. | تم قبول دعوتك: {name} الحين ضمن {branch_name}. | No change | Round 2 · Dialect-consistency agent: The notification mixes levels in one line: standard passive «تم قبول دعوتك» and «ضمن» beside Saudi «الحين». Borderline: «تم…» is usual in app notifications. Reference: Style guide, Variety and register: notification messages are level 2; "Do not mix levels inside one sentence." Proposed correction: انقبلت دعوتك: {name} الحين في {branch_name}. | Round 2 · Devil's advocate: The agent calls it borderline. «تم…» is the usual wording of app notifications, the colon splits the line into two clauses, and the passive is how the line avoids a gendered verb for {name}, which the style guide requires. «انقبلت» is very colloquial for a written notification. The delivery review counts the round-1 Preference ruling here as correct. | Round 2 · Preference. The agent calls it borderline, the neutral passive is what the style guide asks for around {name}, and no rule places «تم قبول» outside the light Saudi app register. | Judge agent (round 2) | Logged, not applied |
| R2-S22 | Locale | Preference (not counted) | Open **Schedule** and pick a week. Tap any empty slot to add a shift, then choose a team member, a start time, and an end time. If you don't know yet who will work a shift, save it as an **Open shift**. Team members at that branch can then pick it up themselves. | افتح «**الجدول**» واختر الأسبوع. اضغط أي خانة فاضية لإضافة وردية، ثم اختر عضو الفريق ووقت البداية ووقت النهاية. وإذا ما تعرف للحين مين راح يشتغل في الوردية، احفظها كـ«**وردية مفتوحة**». وقتها أعضاء الفريق في هذا الفرع يقدرون ياخذونها بنفسهم. | No change | Round 2 · Native-reader agent: «مين» in «مين راح يشتغل في الوردية» is the Hejazi form of "who"; the rest of the text uses Najdi-leaning forms («وش», «ودّك», «لين», «هالأسبوع»). Low confidence: «مين» is heard across Saudi Arabia. Reference: Brief line: variety Gulf (Saudi Arabia); S10 «وش أول شي ودّك فيه؟». Proposed correction: افتح «**الجدول**» واختر الأسبوع. اضغط أي خانة فاضية لإضافة وردية، ثم اختر عضو الفريق ووقت البداية ووقت النهاية. وإذا ما تعرف للحين من راح يشتغل في الوردية، احفظها كـ«**وردية مفتوحة**». وقتها أعضاء الفريق في هذا الفرع يقدرون ياخذونها بنفسهم.<br>Round 2 · Dialect-consistency agent: «مين» is the Hejazi form; the file otherwise uses Najdi-leaning forms («وش»). Two Saudi varieties in one file. Low confidence. Reference: Variety line: Gulf (Saudi Arabia); the agent's brief: "The target must be in one variety". Proposed correction: افتح «**الجدول**» واختر الأسبوع. اضغط أي خانة فاضية لإضافة وردية، ثم اختر عضو الفريق ووقت البداية ووقت النهاية. وإذا ما تعرف للحين من راح يشتغل في الوردية، احفظها كـ«**وردية مفتوحة**». وقتها أعضاء الفريق في هذا الفرع يقدرون ياخذونها بنفسهم. | Round 2 · Devil's advocate: «مين» is Saudi, it is not on the style guide's list of banned words, and the variety named by the client is "Gulf (Saudi Arabia)", not Najdi. Both agents mark low confidence. The fix «من راح يشتغل» is ambiguous without vowels («مِن» / «مَن»). No page that was opened in round 2 shows that Saudi "white" writing keeps «مين» out of a text that uses «وش». The delivery review calls the round-1 ruling defensible. | Round 2 · Preference. «مين» is in Saudi use, the client named the variety "Gulf (Saudi Arabia)" and banned no Saudi form, and the proposed «من» is ambiguous without vowels. The evidence found does not settle whether a Najdi-leaning text excludes «مين», so the text stays. Sent to the client as Q23. | Judge agent (round 2) | Logged, not applied |
| R2-S23 | Style | Minor | In a hurry? Tap **Copy last week** and let Rotalume do the heavy lifting. You only need to fix what has changed. | ما عندك وقت؟ اضغط «**نسخ الأسبوع الماضي**» وخلّ الباقي على Rotalume. عليك بس تعديل اللي تغيّر. | ما عندك وقت؟ اضغط «**نسخ الأسبوع الماضي**» وخلّ الباقي على Rotalume. وعدّل بس اللي تغيّر. | Round 2 · Native-reader agent: «عليك بس تعديل اللي تغيّر» is not a sentence a Saudi writer produces: the formal frame «عليك» + verbal noun is filled with the colloquial «بس» and «اللي». The same paragraph already speaks with verbs («اضغط», «خلّ»). Reference: None visible to this agent beyond the brief line (Saudi readers); the construction itself. Proposed correction: ما عندك وقت؟ اضغط «**نسخ الأسبوع الماضي**» وخلّ الباقي على Rotalume. ما عليك إلا تعدّل اللي تغيّر.<br>Round 2 · Style agent: The tip «عليك بس تعديل اللي تغيّر» mixes the two levels in one sentence: the standard frame «عليك» + verbal noun «تعديل» with level-2 «بس» and «اللي». Reference: Style guide, Variety and register: tips are level 2; "Do not mix levels inside one sentence."; "It must read as written by a Saudi". Source: "You only need to fix what has changed." Proposed correction: ما عندك وقت؟ اضغط «**نسخ الأسبوع الماضي**» وخلّ الباقي على Rotalume. وعدّل بس اللي تغيّر.<br>Round 2 · Dialect-consistency agent: «عليك بس تعديل اللي تغيّر»: standard «عليك» + verbal noun with Saudi «بس» and «اللي» in one sentence. Reference: Style guide: tips are level 2; "Do not mix levels inside one sentence." Proposed correction: ما عندك وقت؟ اضغط «**نسخ الأسبوع الماضي**» وخلّ الباقي على Rotalume. عليك بس تعدّل اللي تغيّر. | Round 2 · Devil's advocate: The three agents give three different fixes. «عليك بس تعدّل» keeps «عليك» before a verb and is still not something a Saudi says. «ما عليك إلا تعدّل» is idiomatic but no page was found for it in round 2. «وعدّل بس اللي تغيّر» drops "need to". All three use a masculine verb; that is allowed here, because a tip is not a message to a named person or a direct question, and the same segment already has «اضغط» and «خلّ». Minor at most. | Round 2 · Defect (Style, Minor). A concrete defect: the frame «عليك» + verbal noun with «بس» and «اللي» inside it mixes the two levels in one sentence of a level-2 tip, which the style guide forbids, and it is not a construction of the variety. The gender rule does not cover a tip, and the segment already uses «اضغط» and «خلّ». «عليك بس تعدّل» does not remove the defect. «وعدّل بس اللي تغيّر» is chosen: imperative followed by «اللي» is the pattern found in Saudi app copy opened in round 2, and "only" is kept by «بس». | Judge agent (round 2) | Fixed |
| R2-S30 | Tags and format | Preference (not counted) | **Time off**: for one day or more. A request must be sent at least 3 days in advance. | «**إجازة**»: ليوم واحد أو أكثر. لازم ينرسل الطلب قبلها بـ 3 أيام على الأقل. | No change | Round 2 · Raised in delivery review: Review A4: «بـ 3» is written with a space between the preposition and the number. Reference: Delivery review, A4. No style-guide spacing rule quoted. Proposed correction: «**إجازة**»: ليوم واحد أو أكثر. لازم ينرسل الطلب قبلها بـ3 أيام على الأقل. | Round 2 · Devil's advocate: The style guide has no rule on a space after «بـ». The gate check G7 (spacing) passes. The review lists it as a preference. Preference. | Round 2 · Preference. The style guide sets no spacing rule for «بـ» before a number. | Judge agent (round 2) | Logged, not applied |
| R2-S40 | Style | Preference (not counted) | You have until the 5th of the following month to correct a timesheet. After that date it is locked, and only the Owner can unlock it. | معك لين يوم 5 من الشهر اللي بعده عشان تصحّح سجل الدوام. بعد هذا التاريخ ينقفل السجل، وما يقدر يفتحه إلا «المالك». | No change | Round 2 · Raised in delivery review: Review A4: «معك لين يوم 5» for "You have until the 5th" is listed as a wording the delivery review would change. No replacement is given in the review. Reference: Delivery review, A4. No rule quoted. Proposed correction: No correction proposed in the review. | Round 2 · Devil's advocate: The review proposes no correction and quotes no rule. «معك لين يوم 5» gives the deadline correctly. Preference. | Round 2 · Preference. No rule and no correction are given; the deadline is stated correctly. | Judge agent (round 2) | Logged, not applied |
| R2-S44 | Style | Minor | Your free trial ends on {end_date}. Choose a plan to keep your schedules. | فترتك التجريبية المجانية تنتهي يوم {end_date}. ولازم اختيار باقة عشان تبقى جداولك محفوظة. | فترتك التجريبية المجانية تنتهي يوم {end_date}. اختر باقة عشان تبقى جداولك محفوظة. | Round 2 · Native-reader agent: «ولازم اختيار باقة» is an impersonal «لازم» + verbal noun in a message that speaks to the reader directly («فترتك», «جداولك»); it reads as translated. Reference: None visible to this agent beyond the brief line; the construction itself. Proposed correction: فترتك التجريبية المجانية تنتهي يوم {end_date}. اختر باقة عشان تبقى جداولك محفوظة.<br>Round 2 · Style agent: The notification «ولازم اختيار باقة عشان…» puts «لازم» + verbal noun «اختيار» beside level-2 «عشان». The Address rule that asks for a neutral structure covers messages to a named person and direct questions; this message is neither. Reference: Style guide, Variety and register: notification messages are level 2; "Do not mix levels inside one sentence." Address: "Where a message goes to a named person ({first_name}) or asks a direct question…". Source: "Choose a plan to keep your schedules." Proposed correction: فترتك التجريبية المجانية تنتهي يوم {end_date}. اختر باقة عشان تبقى جداولك محفوظة.<br>Round 2 · Dialect-consistency agent: «ولازم اختيار باقة»: verbal noun after «لازم», then Saudi «عشان», in one sentence. Reference: Style guide: notification messages are level 2; "Do not mix levels inside one sentence." Proposed correction: فترتك التجريبية المجانية تنتهي يوم {end_date}. ولازم تختار باقة عشان تبقى جداولك محفوظة. | Round 2 · Devil's advocate: The Owner who reads this message may be a woman, and «اختر» is a masculine imperative; the round-1 judge kept the verbal noun on that ground. Against that: the Address rule limits the neutral structure to messages with {first_name} and to direct questions, and this is neither; the file uses the masculine imperative with «عشان» elsewhere (S32). «ولازم تختار» keeps the added "must". If changed, the gender point should go to the client as an open question. | Round 2 · Defect (Style, Minor). A concrete defect: «لازم» + verbal noun beside «عشان» mixes levels in one sentence of a notification, and «لازم» states an obligation the source does not state. Round 1 applied the neutral-structure rule outside its stated scope: this message has no {first_name} and asks no question. «اختر باقة» removes both points with the smallest change and matches S14 and S22 («اختر»). Whether the Owner's message should be gender-neutral is sent to the client as Q22. | Judge agent (round 2) | Fixed |
| R2-S53 | Style | Minor | Are you sure you want to delete this shift? You can't undo this. | أكيد حذف هذي الوردية؟ ما فيه تراجع بعد الحذف. | أكيد نحذف هذي الوردية؟ ما فيه تراجع بعد الحذف. | Round 2 · Native-reader agent: «أكيد حذف هذي الوردية؟» is a broken question: «أكيد» followed by a bare verbal noun has no verb and is not how a Saudi speaker asks for confirmation. Reference: The target language's grammar and the brief line (Saudi readers). Proposed correction: أكيد تبي تحذف هذي الوردية؟ ما فيه تراجع بعد الحذف.<br>Round 2 · Style agent: The confirmation message «أكيد حذف هذي الوردية؟» is not Saudi conversational wording: a bare verbal noun after «أكيد». It is a direct question, so the fix must fit a woman and a man. Reference: Style guide: messages are level 2 and "must read as written by a Saudi"; Address: direct questions take "a verbal noun or a neutral structure"; "Rotalume speaks as 'we'". Proposed correction: أكيد نحذف هذي الوردية؟ ما فيه تراجع بعد الحذف.<br>Round 2 · Dialect-consistency agent: «أكيد حذف هذي الوردية؟»: verbal noun «حذف» between conversational «أكيد» and Saudi «هذي». Reference: Style guide: messages are level 2; preferred word «تبي»; "Do not mix levels inside one sentence." Proposed correction: أكيد تبي تحذف هذي الوردية؟ ما فيه تراجع بعد الحذف. | Round 2 · Devil's advocate: Two of the three fixes («أكيد تبي تحذف») are masculine, and this is a direct question, where the style guide requires wording that fits a woman and a man. They cannot be applied. «أكيد نحذف هذي الوردية؟» is neutral and changes one word, but it moves the action from "you" to "we"; the source says "you want to delete". No page with this exact dialog wording was found. Check that "we" does not mislead about who deletes. | Round 2 · Defect (Style, Minor). A concrete defect: «أكيد حذف هذي الوردية؟» is a question without a verb and is not a construction of the variety; three agents quote the same words. Round 1 was right to reject «أكيد تبي تحذف» (masculine in a direct question) and wrong to stop there. «أكيد نحذف هذي الوردية؟» is neutral, changes one word, and uses the "we" the style guide gives Rotalume; the reader has just pressed delete and S52 says Rotalume asks for confirmation, so "we delete" does not mislead. | Judge agent (round 2) | Fixed |
| R2-S59 | Style | Minor | That's it. You're all set, so go ahead and publish your first schedule! | بس كذا. كل شي جاهز عندك، والحين دور نشر أول جدول لك! | بس كذا. كل شي جاهز عندك، والحين انشر أول جدول لك! | Round 2 · Native-reader agent: «والحين دور نشر أول جدول لك» is ambiguous: «دور» is the word the text uses for "role" (S14 «اختر الدور», S15 «ثلاثة أدوار»), so the reader first takes it as "the publishing role". The sentence also has no verb telling the reader what to do. Reference: S14 and S15 of the same text. Proposed correction: بس كذا. كل شي جاهز عندك، والحين انشر أول جدول لك!<br>Round 2 · Style agent: "go ahead and publish" is rendered «والحين دور نشر أول جدول لك», a noun phrase that is not a natural Saudi equivalent and drops the instruction. Reference: Style guide, Idioms: "Translate the meaning, not the words… 'you're all set' need[s] a natural Saudi equivalent"; the closing line is level 2. Source: "so go ahead and publish your first schedule!" Proposed correction: بس كذا. كل شي جاهز عندك، والحين انشر أول جدول لك!<br>Round 2 · Terminology agent: «دور» in «والحين دور نشر» is the word used for the new term "role" (S14 «اختر الدور», S15 «ثلاثة أدوار»). Here it carries another sense ("turn"), so one word serves two meanings in the same article. Reference: New-term list: role = «دور»; S14 and S15 against S59. Proposed correction: بس كذا. كل شي جاهز عندك، والحين انشر أول جدول لك! | Round 2 · Devil's advocate: «انشر» is a masculine imperative, but the closing line is not a named-person message or a direct question, and the guide prescribes the short imperative. «انشر» is the verb of the glossary word «نشر» (S50 has «نشرت»), so the term is kept. The defect is real on two counts the finders name: the clash with «دور» = role, and the lost instruction. Only the severity is in question: Minor. | Round 2 · Defect (Style, Minor). Two concrete defects: an ambiguity («دور» is this text's word for "role", S14 and S15) and meaning lost against the source (the instruction "go ahead and publish"). «والحين انشر أول جدول لك!» removes both; «انشر» is the verb of the glossary word «نشر». The imperative with «الحين» is the pattern found in Saudi app copy opened in round 2. | Judge agent (round 2) | Fixed |
| R2-S60 | Accuracy | Minor | *Rotalume is a fictional product. This text was written as sample content for a translation demonstration.* | *Rotalume منتج خيالي. هذا النص مكتوب كمحتوى تجريبي لعرض توضيحي للترجمة.* | *Rotalume منتج غير حقيقي. هذا النص مكتوب كمحتوى تجريبي لعرض توضيحي للترجمة.* | Round 2 · Raised in delivery review: Review A2 item 7: «خيالي» in «Rotalume منتج خيالي» also means "fabulous, amazing" in everyday and advertising Arabic, so the one line that must say the product does not exist can be read as praise. Reference: Delivery review, A2 item 7. Source: "Rotalume is a fictional product." The line is gate item G9. Proposed correction: *Rotalume منتج غير حقيقي. هذا النص مكتوب كمحتوى تجريبي لعرض توضيحي للترجمة.* | Round 2 · Devil's advocate: «خيالي» is the dictionary word for "fictional", and the second sentence («هذا النص مكتوب كمحتوى تجريبي…») tells the reader what the text is. The "fabulous" sense was not confirmed on any page opened in round 2: the one dictionary page opened gives "imaginary" and "unrealistic, impractical" only. «غير حقيقي» could itself be read as "not genuine". The line is a gate item and must stay; any change must keep it plain and in place. | Round 2 · Defect (Accuracy, Minor). An ambiguity that changes what the reader understands, in the one line whose job is to say the product does not exist. The page opened gives a second sense, "unrealistic", for «خيالي»; the "fabulous" sense rests on model knowledge and was not confirmed on a page. Either second reading defeats the line. «غير حقيقي» says "not real" with no praise reading; the second sentence is untouched and the line stays last and in italic. | Judge agent (round 2) | Fixed |
| R3-01 | Style | Not a defect (not counted) | S14: To add people, open **Team** and tap **Invite team member**. Enter the person's name and mobile number, choose a role, and tap **Send invite**. Each new team member gets a text message with a link that is valid for 48 hours.<br>S22: Open **Schedule** and pick a week. Tap any empty slot to add a shift, then choose a team member, a start time, and an end time. If you don't know yet who will work a shift, save it as an **Open shift**. Team members at that branch can then pick it up themselves.<br>S32: You'll find them all under **Requests**. Open a request and tap **Approve** or **Decline**. If you decline, add a short note so the person knows why.<br>S36: When team members clock in and clock out on their mobile phones, Rotalume records their hours for you. At the end of the month, open **Timesheets**, check the totals, and tap **Export** to download the file. | S14: لإضافة أشخاص، افتح «**الفريق**» واضغط «**دعوة عضو للفريق**». اكتب اسم الشخص ورقم جواله، واختر الدور، ثم اضغط «**إرسال الدعوة**». كل عضو فريق جديد توصله رسالة نصية فيها رابط صالح لمدة 48 ساعة.<br>S22: افتح «**الجدول**» واختر الأسبوع. اضغط أي خانة فاضية لإضافة وردية، ثم اختر عضو الفريق ووقت البداية ووقت النهاية. وإذا ما تعرف للحين مين راح يشتغل في الوردية، احفظها كـ«**وردية مفتوحة**». وقتها أعضاء الفريق في هذا الفرع يقدرون ياخذونها بنفسهم.<br>S32: تلقاها كلها في «**الطلبات**». افتح الطلب واضغط «**موافقة**» أو «**رفض**». وإذا رفضت، اكتب ملاحظة قصيرة عشان يعرف الشخص السبب.<br>S36: لما يسجّل أعضاء الفريق حضورهم ويسجّلون انصرافهم من جوالاتهم، Rotalume يسجّل ساعاتهم عنك. في نهاية الشهر، افتح «**سجل الدوام**» وراجع المجاميع، ثم اضغط «**تصدير**» لتنزيل الملف. | No change | Round 3 · Native-reader agent (target only, separate agent): S14, S22, S32, S36 (category assigned when recording, from the agent's label) Colloquial wording inside instruction steps (label: register), for example S22 «وإذا ما تعرف للحين مين راح يشتغل… ياخذونها بنفسهم», S32 «تلقاها… عشان يعرف», S14 «توصله رسالة نصية فيها رابط», while S05 to S07 are standard. The agent assumed these four lines are instruction steps because the numbering is flattened in the text it was given, and said that assumption must be checked against the source and the style guide. Proposed severity: Major. Proposed correction: For S22: «وإذا لم تحدّد بعد من سيعمل في الوردية، احفظها كـ«وردية مفتوحة»». | Round 3 · Devil's advocate (separate agent): The premise is false. The source has one numbered list (S05 to S07); S14, S22, S32 and S36 are unnumbered body paragraphs and carry no list style in the delivered file. The style guide reserves standard wording for labels, headings and "the numbered steps", so Saudi wording here is what the guide requires and the contrast with S05 to S07 is its two-level design. The proposed S22 wording is plain MSA («لم», «سيعمل») and shifts "don't know yet" to "have not yet decided". UI labels in the four lines match the glossary and no banned word appears. What is left is a gap in the guide: unnumbered body paragraphs that contain imperatives are named under neither level. Does not survive, and not as Major. | Round 3 · Judge (separate agent): Not a defect. The premise is wrong: in the source these are unnumbered body paragraphs, and the only numbered steps are S05 to S07. The style guide reserves standard wording for labels, headings and "the numbered steps" and requires the rest to read "as written by a Saudi, not as Modern Standard Arabic". The Saudi wording follows the guide. The proposed S22 correction is MSA and changes the meaning, so it would create two defects. Note for the client, not a translation defect: the guide does not name unnumbered body paragraphs that contain imperatives under either level (open question Q24). | Judge agent (round 3, separate agent) | No change |
| R3-02 | Terminology | Not a defect (not counted) | **Manager**: can build schedules, approve requests, and export timesheets, but only for their own branches. | «**مدير**»: يقدر يبني الجداول ويوافق على الطلبات ويصدّر سجلات الدوام، لكن لفروعه بس. | No change | Round 3 · Native-reader agent (target only, separate agent): S17 (category assigned when recording, from the agent's label) «مدير» beside «المالك» (S16) and «عضو الفريق» (S18): inconsistent label form. Proposed severity: Minor. Proposed correction: «المدير» | Round 3 · Devil's advocate (separate agent): The glossary sets these forms: Manager = «مدير» with the note "Keep the label in this form", Owner = «المالك», team member = «عضو الفريق». The target copies all three. «المدير» is a glossary breach. The mismatch is feedback on the glossary for the client. Does not survive. | Round 3 · Judge (separate agent): Not a defect. The glossary gives the three labels in these forms and the target copies them. «المدير» would breach the glossary. The uneven definiteness is a point about the glossary itself (open question Q21 stands). | Judge agent (round 3, separate agent) | No change |
| R3-03 | Locale | Preference (not counted) | You have until the 5th of the following month to correct a timesheet. After that date it is locked, and only the Owner can unlock it. | معك لين يوم 5 من الشهر اللي بعده عشان تصحّح سجل الدوام. بعد هذا التاريخ ينقفل السجل، وما يقدر يفتحه إلا «المالك». | No change | Round 3 · Native-reader agent (target only, separate agent): S40 (category assigned when recording, from the agent's label) «معك لين يوم 5» sounds Levantine. Proposed severity: Minor. Proposed correction: «عندك لين يوم 5» | Round 3 · Devil's advocate (separate agent): No rule is cited. «لين» is a Gulf marker, so the phrase cannot read as Levantine as a whole; «معك» is not banned, and possession of time with «مع» is used in Saudi speech too. A web search for Saudi attestations of «معك لين» returned nothing usable either way, so both the finding and the counter-claim rest on native judgment only. The swap to «عندك» is harmless. A preference. | Round 3 · Judge (separate agent): Preference. No rule is cited and no concrete error is named. The meaning matches the source, «لين» is a Gulf form and «معك» is not on the banned list. The judge could not confirm whether «معك» or «عندك» is the more natural Saudi choice; neither side produced evidence. «عندك لين يوم 5» is a harmless optional swap. | Judge agent (round 3, separate agent) | No change |
| R3-04 | Style | Preference (not counted) | A swap does not take effect until a manager approves it, even if both team members have already agreed. Requests that nobody answers within 72 hours are marked **Expired**, and the team member is asked to send a new one. | التبديل ما يصير ساري إلا بعد ما يوافق عليه مدير، حتى لو كان الاثنين من أعضاء الفريق متفقين من قبل. والطلبات اللي ما أحد يرد عليها خلال 72 ساعة تتحول حالتها إلى «**منتهي الصلاحية**»، ونطلب من عضو الفريق يرسل طلب جديد. | No change | Round 3 · Native-reader agent (target only, separate agent): S34 (category assigned when recording, from the agent's label) «حتى لو كان الاثنين من أعضاء الفريق متفقين» has a translated feel. Proposed severity: Minor. Proposed correction: «حتى لو العضوين متفقين» | Round 3 · Devil's advocate (separate agent): The wording keeps the glossary term «أعضاء الفريق» (note: "Do not replace") and matches S31 «اثنين من أعضاء الفريق». It is grammatical in Saudi usage; "translated feel" is taste with no rule behind it. «العضوين» drops «الفريق» from an approved term and breaks consistency with S31, and the quoted correction leaves out «من قبل», so "already" could be lost. Preference; the correction carries risk. | Round 3 · Judge (separate agent): Preference. "Translated feel" is not a concrete defect. The clause is understandable, keeps "already" («من قبل»), keeps the glossary plural and matches S31. The proposed «العضوين» cuts the approved term and, as quoted, drops "already". | Judge agent (round 3, separate agent) | No change |
| R3-05 | Style | Preference (not counted) | S42: Rotalume is free for workspaces with up to 5 team members, and there are no strings attached. The Team plan costs SAR 19 per team member per month. Prices do not include VAT (15%).<br>S45: We send an invoice to the Owner's email address on the 1st of each month. For example, a workspace with 14 team members pays SAR 266.00 before VAT. You can change or cancel your plan at any time under **Settings > Plan**. | S42: Rotalume مجاني لمساحات العمل اللي فيها 5 من أعضاء الفريق أو أقل، وبدون أي شروط مخفية. سعر باقة الفريق 19 ريال لكل عضو فريق في الشهر. الأسعار ما تشمل ضريبة القيمة المضافة (15%).<br>S45: نرسل فاتورة على بريد «المالك» الإلكتروني يوم 1 من كل شهر. مثلاً، مساحة عمل فيها 14 من أعضاء الفريق تدفع 266.00 ريال قبل ضريبة القيمة المضافة. تقدر تغيّر باقتك أو تلغيها في أي وقت من «**الإعدادات > الباقة**». | No change | Round 3 · Native-reader agent (target only, separate agent): S42, S45 (category assigned when recording, from the agent's label) «5 من أعضاء الفريق أو أقل» (S42) and «14 من أعضاء الفريق» (S45): calque. Proposed severity: Minor. Proposed correction: «5 أعضاء أو أقل», «14 عضو» | Round 3 · Devil's advocate (separate agent): «5 أعضاء» and «14 عضو» drop «الفريق», so the approved term is cut; the correction should not be applied. The partitive form is grammatical and keeps the glossary plural. For fairness: «14 من أعضاء الفريق» can read as "14 out of the team's members" where the source means a headcount, and the glossary's counted forms for shift point to direct counting; «5 أعضاء فريق أو أقل» and «14 عضو فريق» would keep the term. The finding survives only in a weak form (naturalness, Minor); the proposed correction does not. | Round 3 · Judge (separate agent): Preference. The form is grammatical, keeps the glossary plural intact, and in context is read as a headcount, so the reader's understanding does not change. The style guide's number rule is stated for durations and the glossary gives counted forms only for shift, so no rule is breached. The proposed forms cut «الفريق» and must not be applied. If the client wants direct counting, the form that keeps the term is «5 أعضاء فريق أو أقل» and «14 عضو فريق»; the judge could not say with certainty that it reads more naturally. | Judge agent (round 3, separate agent) | No change |
| R3-06 | Style | Preference (not counted) | **Owner**: can do everything, including billing. Each workspace has only one Owner. | «**المالك**»: يقدر يسوي كل شي، ومنه الفوترة. كل مساحة عمل لها «مالك» واحد بس. | No change | Round 3 · Native-reader agent (target only, separate agent): S16 (category assigned when recording, from the agent's label) «ومنه الفوترة» is awkward. (This wording was itself a round-2 fix.) Proposed severity: Minor. Proposed correction: «بما فيه الفوترة» | Round 3 · Devil's advocate (separate agent): The meaning of the source ("including billing") is intact, the pronoun agrees with «كل شي», and no rule is broken; "awkward" is taste. «بما فيه» is closer to the MSA formula «بما في ذلك» and moves a Saudi-worded line toward mixed levels, which the style guide forbids. Reversing a round-2 fix on preference alone is churn. Preference. | Round 3 · Judge (separate agent): Preference. The meaning is kept and the pronoun agrees with «كل شي». "Awkward" names no error. «بما فيه» leans toward the MSA formula inside a Saudi-worded line. | Judge agent (round 3, separate agent) | No change |
| R3-07 | Style | Preference (not counted) | Getting started: your first week as a manager | البداية: أسبوعك الأول بدور مدير | No change | Round 3 · Native-reader agent (target only, separate agent): S02 (category assigned when recording, from the agent's label) «بدور مدير»: calque. Proposed severity: Minor. Proposed correction: «كمدير» | Round 3 · Devil's advocate (separate agent): S02 is a heading, so standard wording applies. «كـ» for English "as" is the textbook calque, so the correction replaces an alleged calque with a recognized one. «بدور مدير» ties the heading to the product's role concept (S14, S15) and keeps the glossary label unchanged. For fairness, the target uses «كـ» elsewhere (S22, S60), so «كمدير» would not be out of place; it is still only an alternative. Preference. | Round 3 · Judge (separate agent): Preference. S02 is a heading, so standard wording applies, and «بدور مدير» is correct standard Arabic that keeps the glossary label. «كمدير» is only an alternative, and «كـ» for "as" is itself the commonly criticized calque. | Judge agent (round 3, separate agent) | No change |
| R3-08 | Style | Preference (not counted) | Welcome, {first_name}! Your workspace "{workspace_name}" is ready. What do you want to do first? | هلا {first_name}! مساحة عملك «{workspace_name}» جاهزة. وش أول شي ودّك فيه؟ | No change | Round 3 · Native-reader agent (target only, separate agent): S10 (category assigned when recording, from the agent's label) «وش أول شي ودّك فيه؟» is unclear. Proposed severity: Minor. Proposed correction: «وش ودّك تبدأ فيه؟» | Round 3 · Devil's advocate (separate agent): S10 goes to a named person ({first_name}) and asks a direct question, so the style guide requires wording that fits a woman and a man. «تبدأ» is a masculine second-person verb, so the correction breaches the guide; the current wording has no gendered verb. «ودّك في شي» is ordinary Gulf usage. What is left: "do" in the source is implied, not stated, a small accuracy nuance and not the "unclear" the reader raised. The correction does not survive; the finding survives at most as a Minor nuance, and any fix must stay gender-neutral. | Round 3 · Judge (separate agent): Preference. The string goes to a named person and asks a direct question, so the wording must fit a woman and a man; the current wording has no gendered verb and the proposed one adds a masculine verb. The source's "do" is implied rather than stated; in a welcome prompt that does not change what the reader understands, so it is not a meaning loss. The judge could not confirm how natural «ودّك فيه» sounds to every Saudi reader. | Judge agent (round 3, separate agent) | No change |
| R3-09 | Style | Not a defect (not counted) | Fahad: 2 shifts, 11 hours, no overtime | فهد: ورديتين، 11 ساعة، بدون ساعات إضافية | No change | Round 3 · Native-reader agent (target only, separate agent): S39 (category assigned when recording, from the agent's label) «ورديتين» in a sample record row: colloquial in UI data. Proposed severity: Minor. Proposed correction: «ورديتان» | Round 3 · Devil's advocate (separate agent): The glossary prescribes it: "Counted forms: وردية واحدة، ورديتين، 3 ورديات، 22 وردية". «ورديتان» is a glossary breach and an MSA nominative form in a text that must not read as MSA. Does not survive. | Round 3 · Judge (separate agent): Not a defect. The glossary prescribes «ورديتين» among its counted forms. «ورديتان» would breach the glossary and is an MSA form. | Judge agent (round 3, separate agent) | No change |
| R3-10 | Style | Preference (not counted) | Go to **Settings > Branches** and tap **Add branch**. Give each branch a name and its opening hours, for example 7:00 AM to 11:30 PM. | ادخل على «**الإعدادات > الفروع**» واضغط «**إضافة فرع**». اكتب لكل فرع اسمه وساعات العمل فيه، مثلاً من 7:00 ص إلى 11:30 م. | No change | Round 3 · Native-reader agent (target only, separate agent): S13 (category assigned when recording, from the agent's label) «ادخل على» (S13) against «انتقل إلى» (S05): inconsistent, and colloquial in a step. Proposed severity: Minor. Proposed correction: «انتقل إلى» | Round 3 · Devil's advocate (separate agent): S05 is a numbered step and takes standard wording; S13 is an unnumbered body paragraph. Different wording across the two levels is what the style guide asks for; "colloquial in a step" is the same false premise as in finding 1. The objects differ (a web address, a menu path), and «ادخل على» for a settings screen is natural Saudi help-desk phrasing and is not banned. For fairness, the source verb is the same in both places ("go to") and «انتقل إلى» breaks no rule. At most optional. | Round 3 · Judge (separate agent): Preference. S05 is a numbered step and takes standard wording; S13 is an unnumbered body paragraph, so different wording across the two levels is what the guide asks for. Neither phrase is a UI label, so the glossary consistency rule does not apply, and the objects differ. «انتقل إلى» in S13 would break no rule, so it stays optional. | Judge agent (round 3, separate agent) | No change |
| R3-11 | Tags and format | Not a defect (not counted) | You have %d new shifts this week. Your first shift starts tomorrow at {start_time}. | ورديات جديدة لك هالأسبوع: %d. أول وردية لك تبدأ بكرة الساعة {start_time}. | No change | Round 3 · Native-reader agent (target only, separate agent): S25 (category assigned when recording, from the agent's label) «%d» beside {…} placeholders elsewhere: inconsistent. Proposed severity: Minor. Proposed correction: None given. | Round 3 · Devil's advocate (separate agent): The source string has %d and {start_time} together, and the style guide says to copy %d "and all others exactly". The mix of formats comes from the source; changing it would be a placeholder change and could break the string at run time. The sentence follows the %d rule (label, then the number). Does not survive; at most a note to the client about the source. | Round 3 · Judge (separate agent): Not a defect. The source string has %d and {start_time} together, and the style guide says to copy placeholders exactly. The sentence follows the %d rule (label, then the number), so it is correct for every count. Changing the format would be a placeholder change. | Judge agent (round 3, separate agent) | No change |
| R3-12 | Tags and format | Not a defect (not counted) | S13: Go to **Settings > Branches** and tap **Add branch**. Give each branch a name and its opening hours, for example 7:00 AM to 11:30 PM.<br>S45: We send an invoice to the Owner's email address on the 1st of each month. For example, a workspace with 14 team members pays SAR 266.00 before VAT. You can change or cancel your plan at any time under **Settings > Plan**.<br>S56: Rotalume uses the time zone of each branch, not the time zone of your phone. You can change it under **Settings > Branches**.<br>S58: Our support team is here from Sunday to Thursday, 9:00 AM to 6:00 PM, Riyadh time. In the app, tap **Help > Chat with us**, or write to help@rotalume.example. We usually reply right away during working hours. | S13: ادخل على «**الإعدادات > الفروع**» واضغط «**إضافة فرع**». اكتب لكل فرع اسمه وساعات العمل فيه، مثلاً من 7:00 ص إلى 11:30 م.<br>S45: نرسل فاتورة على بريد «المالك» الإلكتروني يوم 1 من كل شهر. مثلاً، مساحة عمل فيها 14 من أعضاء الفريق تدفع 266.00 ريال قبل ضريبة القيمة المضافة. تقدر تغيّر باقتك أو تلغيها في أي وقت من «**الإعدادات > الباقة**».<br>S56: Rotalume يستخدم المنطقة الزمنية لكل فرع، مو المنطقة الزمنية لجوالك. تقدر تغيّرها من «**الإعدادات > الفروع**».<br>S58: فريق الدعم عندنا موجود من الأحد إلى الخميس، من 9:00 ص إلى 6:00 م بتوقيت الرياض. في التطبيق، اضغط «**المساعدة > المحادثة معنا**»، أو راسلنا على help@rotalume.example. غالباً نرد عليك على طول في ساعات العمل. | No change | Round 3 · Native-reader agent (target only, separate agent): S13, S45, S56, S58 (category assigned when recording, from the agent's label) Menu paths such as «الإعدادات > الفروع»: the sign ">" points against the reading direction in right-to-left text. Proposed severity: Minor. Proposed correction: «‹» or «←» | Round 3 · Devil's advocate (separate agent): The style guide prescribes this exact form: "Menu paths keep their order with the sign > between the parts: «الإعدادات > الفروع»"; replacing it is a style-guide breach. ">" is a mirrored character in the Unicode bidirectional algorithm, so between two Arabic words in a right-to-left paragraph it is drawn pointing in the reading direction; the reader worked from a flat text extract, so the complaint may be an artefact of the extract and should be confirmed in the rendered file. A web search for how Saudi help centers write menu paths gave no usable result. Does not survive. | Round 3 · Judge (separate agent): Not a defect. The style guide prescribes this exact form, and «‹» or «←» would breach it. How the sign is drawn in a right-to-left line was not checked in a rendered view; that is a display question for the client, not a translation defect (open question Q25). | Judge agent (round 3, separate agent) | No change |
| R3-13 | Style | Preference (not counted) | {name} has accepted your invite and joined {branch_name}. | تم قبول دعوتك: {name} الحين ضمن {branch_name}. | No change | Round 3 · Native-reader agent (target only, separate agent): S20 (category assigned when recording, from the agent's label) «تم قبول دعوتك: {name} الحين…»: stiff standard opening in a notification. Proposed severity: Minor. Proposed correction: «{name} قبل دعوتك، والحين ضمن…» | Round 3 · Devil's advocate (separate agent): The style guide says a placeholder for a person must not force a masculine or feminine verb. «{name} قبل دعوتك» puts a masculine verb on {name}, so the correction breaches the guide; the current structure is the restructuring the guide asks for and keeps both placeholders. «تم» plus a verbal noun is the normal pattern in Saudi app notifications. For fairness: notifications are level 2 and «تم قبول» sits beside «الحين»; a gender-neutral Saudi alternative exists, for example «دعوتك انقبلت: {name} الحين ضمن {branch_name}.» The correction does not survive; the finding survives only weakly, and only with a gender-neutral fix. | Round 3 · Judge (separate agent): Preference. The current wording does what the style guide asks around {name}, keeps both placeholders and keeps the meaning. The proposed correction puts a masculine verb on {name} and would breach the guide. On level-mixing, the judge could not establish that «تم» plus a verbal noun falls outside the "white" Saudi register of app notifications, and could not confirm that the challenger's «دعوتك انقبلت» is natural, so it is not imposed. | Judge agent (round 3, separate agent) | No change |

## 7. Preferences

| ID | Source | Target (AI translation) | Suggested wording | Raised by | Reason | Origin | Status |
|---|---|---|---|---|---|---|---|
| P-S02-1 | Getting started: your first week as a manager | البداية: أسبوعك الأول بدور مدير | أسبوعك الأول بدور مدير  →  أسبوعك الأول كمدير | Native-reader agent | "بدور مدير" is understandable but slightly heavy for a heading; correct as it stands. | Logged as a preference by the agent | Logged, not applied |
| P-S05-1 | Open the Rotalume app on your mobile phone, or go to app.rotalume.example on your computer. | افتح تطبيق Rotalume على جوالك، أو انتقل إلى app.rotalume.example من الكمبيوتر. | أو انتقل إلى app.rotalume.example من الكمبيوتر  →  أو ادخل على app.rotalume.example من الكمبيوتر | Native-reader agent | "انتقل إلى" is formal MSA in an otherwise colloquial text; S13 already uses "ادخل على". Correct, only a register choice. | Logged as a preference by the agent | Logged, not applied |
| P-S06-1 | Tap **Sign in** and enter your mobile number. We'll text you a 6-digit verification code. The code expires after 5 minutes. | اضغط «**تسجيل الدخول**» واكتب رقم جوالك. نرسل لك رسالة نصية تحتوي على رمز التحقق المكوّن من 6 أرقام. تنتهي صلاحية الرمز بعد 5 دقائق. | نرسل لك رسالة نصية تحتوي على رمز التحقق المكوّن من 6 أرقام. تنتهي صلاحية الرمز بعد 5 دقائق.  →  نرسل لك رسالة نصية فيها رمز تحقق من 6 أرقام. الرمز تنتهي صلاحيته بعد 5 دقائق. | Native-reader agent | More formal than the surrounding segments (S14 uses "رسالة نصية فيها رابط"). Correct and clear; register smoothing only. | Logged as a preference by the agent | Logged, not applied |
| P-S13-1 | Go to **Settings > Branches** and tap **Add branch**. Give each branch a name and its opening hours, for example 7:00 AM to 11:30 PM. | ادخل على «**الإعدادات > الفروع**» واضغط «**إضافة فرع**». اكتب لكل فرع اسمه وساعات العمل فيه، مثلاً من 7:00 ص إلى 11:30 م. | اكتب لكل فرع اسمه وساعات العمل فيه  →  اكتب لكل فرع اسمه وساعات دوامه | Terminology agent | 'opening hours' (S13) and 'working hours' (S58) are both rendered «ساعات العمل». Neither is a glossary or new-term entry, and the meaning is clear in both places, so this is only a note that two source expressions share one target. | Logged as a preference by the agent | Logged, not applied |
| P-S14-1 | To add people, open **Team** and tap **Invite team member**. Enter the person's name and mobile number, choose a role, and tap **Send invite**. Each new team member gets a text message with a link that is valid for 48 hours. | لإضافة أشخاص، افتح «**الفريق**» واضغط «**دعوة عضو للفريق**». اكتب اسم الشخص ورقم جواله، واختر الدور، ثم اضغط «**إرسال الدعوة**». كل عضو فريق جديد توصله رسالة نصية فيها رابط صالح لمدة 48 ساعة. | لإضافة أشخاص  →  لإضافة موظفين | Native-reader agent | "أشخاص" is a little generic for staff; correct as it stands. | Logged as a preference by the agent | Logged, not applied |
| P-S16-1 | **Owner**: can do everything, including billing. Each workspace has only one Owner. | «**المالك**»: يقدر يسوي كل شي، ومنها الفوترة. كل مساحة عمل لها مالك واحد بس. | يقدر يسوي كل شي، ومنها الفوترة  →  يقدر يسوي كل شي، حتى الفوترة | Style agent | «ومنها» does not agree with «كل شي». This is a grammar point outside the style rules, noted here in case the fluency check does not pick it up. | Logged as a preference by the agent | Logged, not applied |
| P-S17-1 | **Manager**: can build schedules, approve requests, and export timesheets, but only for their own branches. | «**مدير**»: يقدر يبني الجداول ويوافق على الطلبات ويصدّر سجلات الدوام، لكن لفروعه بس. | «**مدير**»  →  «**المدير**» | Style agent | The other two role labels are definite («المالك», «عضو الفريق»); a definite form would be parallel. No glossary was supplied in this message, so the required label form cannot be verified and this is not a finding. The same limit applies to every UI label in the file: none could be checked against the glossary. | Logged as a preference by the agent | Logged, not applied |
| P-S18-1 | **Team member**: can see their own shifts, clock in and clock out, and send requests. | «**عضو الفريق**»: يقدر يشوف وردياته، ويسجّل حضوره ويسجّل انصرافه، ويرسل الطلبات. | ويسجّل حضوره ويسجّل انصرافه  →  ويسجّل حضوره وانصرافه | Native-reader agent | Repeated verb is heavier than needed; meaning is clear either way. | Logged as a preference by the agent | Logged, not applied |
| P-S21-1 | 3. Build and publish a schedule | 3. إنشاء الجدول ونشره | 3. إنشاء الجدول ونشره  →  3. بناء الجدول ونشره | Terminology agent | The verb 'build' (a schedule) is rendered «يبني الجداول» in S17 but «إنشاء الجدول» in S21. 'Build' is not in the glossary or the new-term list, so there is no reference to enforce; using one rendering would also keep «إنشاء» reserved for 'Create' as in «إنشاء مساحة العمل» (S07). | Logged as a preference by the agent | Logged, not applied |
| P-S22-1 | Open **Schedule** and pick a week. Tap any empty slot to add a shift, then choose a team member, a start time, and an end time. If you don't know yet who will work a shift, save it as an **Open shift**. Team members at that branch can then pick it up themselves. | افتح «**الجدول**» واختر الأسبوع. اضغط أي خانة فاضية لإضافة وردية، ثم اختر عضو الفريق ووقت البداية ووقت النهاية. وإذا ما تعرف للحين مين راح يشتغل في الوردية، احفظها كـ«**وردية مفتوحة**». وقتها أعضاء الفريق في هذا الفرع يقدرون ياخذونها بنفسهم. | اضغط أي خانة فاضية لإضافة وردية، ثم اختر عضو الفريق ووقت البداية ووقت النهاية.  →  اضغط أي خانة فارغة لإضافة وردية، ثم اختر عضو الفريق ووقت البداية ووقت النهاية. | Dialect-consistency agent | The sentence is otherwise standard («لإضافة», «ثم»), and conversational «فاضية» is the only dialect word in it. The paragraph is Normal, not a numbered step, so no rule is clearly broken. | Logged as a preference by the agent | Logged, not applied |
| P-S26-1 | You can edit a published shift at any time, unless the team member has already clocked in. To change a shift that is in progress, ask the team member to clock out first. | تقدر تعدّل الوردية المنشورة في أي وقت، إلا إذا عضو الفريق سجّل حضوره. ولتعديل وردية جارية الحين، اطلب من عضو الفريق يسجّل انصرافه أول. | ولتعديل وردية جارية الحين  →  ولتعديل وردية شغّالة الحين | Native-reader agent | "جارية" is a bit formal next to "الحين"; correct as it stands. | Logged as a preference by the agent | Logged, not applied |
| P-S26-2 | You can edit a published shift at any time, unless the team member has already clocked in. To change a shift that is in progress, ask the team member to clock out first. | تقدر تعدّل الوردية المنشورة في أي وقت، إلا إذا عضو الفريق سجّل حضوره. ولتعديل وردية جارية الحين، اطلب من عضو الفريق يسجّل انصرافه أول. | ولتعديل وردية جارية الحين، اطلب من عضو الفريق يسجّل انصرافه أول.  →  وإذا تبي تعدّل وردية شغّالة الحين، اطلب من عضو الفريق يسجّل انصرافه أول. | Dialect-consistency agent | «ولتعديل وردية جارية» is MSA phrasing next to Saudi «الحين» and «أول». The style guide does not assign body instructions to either level, so this is not a rule breach. | Logged as a preference by the agent | Logged, not applied |
| P-S27-1 | A shift can't be longer than 12 hours. Rotalume also warns you when someone has fewer than 8 hours of rest between two shifts. | الوردية ما تزيد عن 12 ساعة. ويحذّرك Rotalume إذا كانت الراحة بين ورديتين لأي شخص أقل من 8 ساعات. | الوردية ما تزيد عن 12 ساعة.  →  الوردية ما يمكن تزيد عن 12 ساعة. | Accuracy agent | Source says "A shift can't be longer than 12 hours" (a limit the system enforces). The target reads "a shift does not exceed 12 hours", which still reads as a rule, so the meaning is intact; an explicit "cannot" would mirror the source modality more closely. | Logged as a preference by the agent | Logged, not applied |
| P-S30-1 | **Time off**: for one day or more. A request must be sent at least 3 days in advance. | «**إجازة**»: ليوم واحد أو أكثر. لازم ينرسل الطلب قبلها بـ 3 أيام على الأقل. | قبلها بـ 3 أيام على الأقل  →  قبلها بـ3 أيام على الأقل | Grammar agent | The preposition "بـ" is a prefix and is normally written attached to what follows; the space before the numeral is a common typographic habit, not a clear error. | Logged as a preference by the agent | Logged, not applied |
| P-S36-1 | When team members clock in and clock out on their mobile phones, Rotalume records their hours for you. At the end of the month, open **Timesheets**, check the totals, and tap **Export** to download the file. | لما يسجّل أعضاء الفريق حضورهم ويسجّلون انصرافهم من جوالاتهم، Rotalume يسجّل ساعاتهم عنك. في نهاية الشهر، افتح «**سجل الدوام**» وراجع المجاميع، ثم اضغط «**تصدير**» لتنزيل الملف. | لما يسجّل أعضاء الفريق حضورهم ويسجّلون انصرافهم من جوالاتهم، Rotalume يسجّل ساعاتهم عنك  →  لما يسجّل أعضاء الفريق حضورهم وانصرافهم من جوالاتهم، Rotalume يحسب ساعاتهم عنك | Native-reader agent | "يسجّل" appears three times in one sentence; lighter with one fewer. Correct as it stands. | Logged as a preference by the agent | Logged, not applied |
| P-S39-1 | Fahad: 2 shifts, 11 hours, no overtime | فهد: ورديتين، 11 ساعة، بدون ساعات إضافية | فهد: ورديتين، 11 ساعة، بدون ساعات إضافية  →  فهد: 2 وردية، 11 ساعة، بدون ساعات إضافية | Style agent | The source has the digit "2" in a data line that parallels S38 («22 وردية»). The dual is correct Arabic and the guide says durations follow Arabic number rules, so no rule is broken; keeping a digit would only make the two timesheet lines look alike. | Logged as a preference by the agent | Logged, not applied |
| P-S40-1 | You have until the 5th of the following month to correct a timesheet. After that date it is locked, and only the Owner can unlock it. | معك لين يوم 5 من الشهر اللي بعده عشان تصحّح سجل الدوام. بعد هذا التاريخ ينقفل السجل، وما يقدر يفتحه إلا «المالك». | معك لين يوم 5 من الشهر اللي بعده  →  عندك مهلة لين يوم 5 من الشهر اللي بعده | Native-reader agent | "معك لين" is used colloquially and is understood; "عندك مهلة" is a touch clearer. | Logged as a preference by the agent | Logged, not applied |
| P-S42-1 | Rotalume is free for workspaces with up to 5 team members, and there are no strings attached. The Team plan costs SAR 19 per team member per month. Prices do not include VAT (15%). | Rotalume مجاني لمساحات العمل اللي فيها 5 من أعضاء الفريق أو أقل، وبدون أي شروط مخفية. سعر باقة الفريق 19 ريال لكل عضو فريق في الشهر. الأسعار ما تشمل ضريبة القيمة المضافة (15%). | وبدون أي شروط مخفية  →  وبدون أي التزام | Style agent | The guide asks for a natural Saudi equivalent of "no strings attached". The current wording carries the meaning and is not word-for-word, so it breaks no rule; the suggestion is shorter and closer to what Saudi apps write. | Logged as a preference by the agent | Logged, not applied |
| P-S44-1 | Your free trial ends on {end_date}. Choose a plan to keep your schedules. | فترتك التجريبية المجانية تنتهي يوم {end_date}. ولازم اختيار باقة عشان تبقى جداولك محفوظة. | ولازم اختيار باقة عشان تبقى جداولك محفوظة.  →  اختر باقة عشان تبقى جداولك محفوظة. | Accuracy agent | Source is a plain imperative: "Choose a plan to keep your schedules." The target adds "لازم" ("must"), a slightly stronger obligation than the source states. The consequence is the same, so this is not a meaning error. | Logged as a preference by the agent | Logged, not applied |
| P-S44-2 | Your free trial ends on {end_date}. Choose a plan to keep your schedules. | فترتك التجريبية المجانية تنتهي يوم {end_date}. ولازم اختيار باقة عشان تبقى جداولك محفوظة. | ولازم اختيار باقة عشان تبقى جداولك محفوظة.  →  اختيار باقة يحفظ لك جداولك. | Style agent | The gender-neutral verbal noun follows the guide, but «لازم» reads heavier than the source's "Choose a plan to keep your schedules". Tone only; no style rule is broken. Whether the added obligation is an accuracy issue is for the accuracy check. | Logged as a preference by the agent | Logged, not applied |
| P-S48-1 | Wait 60 seconds, then tap **Resend code**. Check that your mobile phone has a signal and that you typed the right number. Still nothing? Contact us and we'll sort it out. | انتظر 60 ثانية، ثم اضغط «**إعادة إرسال الرمز**». تأكد إن في جوالك شبكة وإنك كتبت الرقم الصحيح. للحين ما وصل شي؟ تواصل معنا ونحلّها لك. | تأكد إن في جوالك شبكة  →  تأكد إن جوالك فيه شبكة | Native-reader agent | Word order flows slightly better; both are natural. | Logged as a preference by the agent | Logged, not applied |
| P-S59-1 | That's it. You're all set, so go ahead and publish your first schedule! | بس كذا. كل شي جاهز عندك، والحين دور نشر أول جدول لك! | والحين دور نشر أول جدول لك!  →  والحين دورك تنشر أول جدول لك! | Dialect-consistency agent | The noun chain «دور نشر أول جدول» reads slightly formal for the closing line. A verb is more natural in Saudi conversational wording. Meaning and the exclamation mark are unchanged. | Logged as a preference by the agent | Logged, not applied |
| S16-2 | **Owner**: can do everything, including billing. Each workspace has only one Owner. | «**المالك**»: يقدر يسوي كل شي، ومنها الفوترة. كل مساحة عمل لها مالك واحد بس. | Native-reader agent: «**المالك**»: يقدر يسوي كل شي، ومن ضمنه الفوترة. كل مساحة عمل لها مالك واحد بس.<br>Grammar agent: «**المالك**»: يقدر يسوي كل شي، ومنه الفوترة. كل مساحة عمل لها مالك واحد بس. | Native-reader agent + Grammar agent | The only reference is a general agreement rule, the Grammar agent itself calls it borderline, and «كل شي» in the sense 'all things' can take «ومنها» in Saudi conversational usage. The source meaning 'everything, including billing' is intact. | Finding ruled a preference by the judge (see Issues) | Logged, not applied |
| S20-2 | {name} has accepted your invite and joined {branch_name}. | تم قبول دعوتك: {name} الحين ضمن {branch_name}. | Dialect-consistency agent: انقبلت دعوتك: {name} الحين في {branch_name}. | Dialect-consistency agent | The agent admits it is borderline, and the style guide does not establish «تم قبول» as outside the light Saudi app register. The neutral structure also satisfies the rule that {name} must not force a gendered verb, and «ضمن» to «في» has no reference. | Finding ruled a preference by the judge (see Issues) | Logged, not applied |
| S22 | Open **Schedule** and pick a week. Tap any empty slot to add a shift, then choose a team member, a start time, and an end time. If you don't know yet who will work a shift, save it as an **Open shift**. Team members at that branch can then pick it up themselves. | افتح «**الجدول**» واختر الأسبوع. اضغط أي خانة فاضية لإضافة وردية، ثم اختر عضو الفريق ووقت البداية ووقت النهاية. وإذا ما تعرف للحين مين راح يشتغل في الوردية، احفظها كـ«**وردية مفتوحة**». وقتها أعضاء الفريق في هذا الفرع يقدرون ياخذونها بنفسهم. | Native-reader agent: افتح «**الجدول**» واختر الأسبوع. اضغط أي خانة فاضية لإضافة وردية، ثم اختر عضو الفريق ووقت البداية ووقت النهاية. وإذا ما تعرف للحين من اللي راح يشتغل في الوردية، احفظها كـ«**وردية مفتوحة**». وقتها أعضاء الفريق في هذا الفرع يقدرون ياخذونها بنفسهم. | Native-reader agent | «مين» is used in Saudi (Hejazi) speech and is not on the style guide's list of forbidden words, so 'Variety: Gulf (Saudi Arabia)' does not make it wrong. The proposed «من اللي» is also ambiguous in unvowelled text. | Finding ruled a preference by the judge (see Issues) | Logged, not applied |
| S23 | In a hurry? Tap **Copy last week** and let Rotalume do the heavy lifting. You only need to fix what has changed. | ما عندك وقت؟ اضغط «**نسخ الأسبوع الماضي**» وخلّ الباقي على Rotalume. عليك بس تعديل اللي تغيّر. | Native-reader agent: ما عندك وقت؟ اضغط «**نسخ الأسبوع الماضي**» وخلّ الباقي على Rotalume. ما عليك إلا تعدّل اللي تغيّر.<br>Dialect-consistency agent: ما عندك وقت؟ اضغط «**نسخ الأسبوع الماضي**» وخلّ الباقي على Rotalume. عليك بس تعدّل اللي تغيّر. | Native-reader agent + Dialect-consistency agent | The style guide itself endorses verbal nouns in conversational messages, so «عليك بس تعديل اللي تغيّر» is not shown to mix levels. The source meaning is intact, and the two agents disagree on the fix. | Finding ruled a preference by the judge (see Issues) | Logged, not applied |
| S27 | A shift can't be longer than 12 hours. Rotalume also warns you when someone has fewer than 8 hours of rest between two shifts. | الوردية ما تزيد عن 12 ساعة. ويحذّرك Rotalume إذا كانت الراحة بين ورديتين لأي شخص أقل من 8 ساعات. | Native-reader agent: أقصى مدة للوردية 12 ساعة. ويحذّرك Rotalume إذا كانت الراحة بين ورديتين لأي شخص أقل من 8 ساعات. | Native-reader agent | No reference is cited. «الوردية ما تزيد عن 12 ساعة» conveys the source's plain statement 'A shift can't be longer than 12 hours' without changing the meaning. | Finding ruled a preference by the judge (see Issues) | Logged, not applied |
| S34-2 | A swap does not take effect until a manager approves it, even if both team members have already agreed. Requests that nobody answers within 72 hours are marked **Expired**, and the team member is asked to send a new one. | التبديل ما يصير ساري إلا بعد ما يوافق عليه مدير، حتى لو كان الاثنين من أعضاء الفريق متفقين من قبل. والطلبات اللي ما أحد يرد عليها خلال 72 ساعة تتحول حالتها إلى «**منتهي الصلاحية**»، ونطلب من عضو الفريق يرسل طلب جديد. | Native-reader agent: التبديل ما يصير ساري إلا بعد ما يوافق عليه مدير، حتى لو كان العضوين متفقين من قبل. والطلبات اللي ما أحد يرد عليها خلال 72 ساعة تتحول حالتها إلى «**منتهي الصلاحية**»، ونطلب من عضو الفريق يرسل طلب جديد. | Native-reader agent | No reference is cited. The proposed «العضوين» or «الطرفين» would drop or replace the approved «أعضاء الفريق», which the target keeps intact. | Finding ruled a preference by the judge (see Issues) | Logged, not applied |
| S42-2 | Rotalume is free for workspaces with up to 5 team members, and there are no strings attached. The Team plan costs SAR 19 per team member per month. Prices do not include VAT (15%). | Rotalume مجاني لمساحات العمل اللي فيها 5 من أعضاء الفريق أو أقل، وبدون أي شروط مخفية. سعر باقة الفريق 19 ريال لكل عضو فريق في الشهر. الأسعار ما تشمل ضريبة القيمة المضافة (15%). | Native-reader agent: Rotalume مجاني لمساحات العمل اللي فيها 5 أعضاء أو أقل، وبدون أي شروط مخفية. سعر باقة الفريق 19 ريال لكل عضو فريق في الشهر. الأسعار ما تشمل ضريبة القيمة المضافة (15%). | Native-reader agent | No reference is cited. The proposed «5 أعضاء أو أقل» would cut «الفريق» from the approved «أعضاء الفريق», which the target keeps whole. | Finding ruled a preference by the judge (see Issues) | Logged, not applied |
| S44-3 | Your free trial ends on {end_date}. Choose a plan to keep your schedules. | فترتك التجريبية المجانية تنتهي يوم {end_date}. ولازم اختيار باقة عشان تبقى جداولك محفوظة. | Native-reader agent: فترتك التجريبية المجانية تنتهي يوم {end_date}. اختر باقة عشان تبقى جداولك محفوظة.<br>Dialect-consistency agent: فترتك التجريبية المجانية تنتهي يوم {end_date}. ولازم تختار باقة عشان تبقى جداولك محفوظة. | Native-reader agent + Dialect-consistency agent | The style guide endorses verbal nouns as a neutral structure in messages, so «ولازم اختيار باقة» is not shown to mix levels. Both proposed fixes («اختر باقة», «لازم تختار باقة») make a message to an Owner of either gender masculine, and the agents disagree on the fix. | Finding ruled a preference by the judge (see Issues) | Logged, not applied |
| S45-2 | We send an invoice to the Owner's email address on the 1st of each month. For example, a workspace with 14 team members pays SAR 266.00 before VAT. You can change or cancel your plan at any time under **Settings > Plan**. | نرسل فاتورة على بريد «المالك» الإلكتروني يوم 1 من كل شهر. مثلاً، مساحة عمل فيها 14 من أعضاء الفريق تدفع 266.00 ريال قبل ضريبة القيمة المضافة. تقدر تغيّر باقتك أو تلغيها في أي وقت من «**الإعدادات > الباقة**». | Native-reader agent: نرسل فاتورة على بريد «المالك» الإلكتروني يوم 1 من كل شهر. مثلاً، مساحة عمل فيها 14 عضو تدفع 266.00 ريال قبل ضريبة القيمة المضافة. تقدر تغيّر باقتك أو تلغيها في أي وقت من «**الإعدادات > الباقة**». | Native-reader agent | No reference is cited. The proposed «14 عضو» drops «الفريق» from the approved term, which «14 من أعضاء الفريق» keeps whole. | Finding ruled a preference by the judge (see Issues) | Logged, not applied |
| S53 | Are you sure you want to delete this shift? You can't undo this. | أكيد حذف هذي الوردية؟ ما فيه تراجع بعد الحذف. | Native-reader agent: أكيد تبي تحذف هذي الوردية؟ ما فيه تراجع بعد الحذف.<br>Dialect-consistency agent: أكيد تبي تحذف هذي الوردية؟ ما فيه تراجع بعد الحذف. | Native-reader agent + Dialect-consistency agent | This is a direct question, where the style guide says to 'prefer a verbal noun or a neutral structure to a gendered verb', and «أكيد حذف هذي الوردية؟» does that. The proposed «أكيد تبي تحذف» is masculine, so the finding cannot answer its challenge. | Finding ruled a preference by the judge (see Issues) | Logged, not applied |
| S59-2 | That's it. You're all set, so go ahead and publish your first schedule! | بس كذا. كل شي جاهز عندك، والحين دور نشر أول جدول لك! | Native-reader agent: بس كذا. كل شي جاهز عندك، والحين جاء وقت نشر أول جدول لك! | Native-reader agent | No source, glossary or style-guide reference is cited. The proposed «جاء وقت نشر» would also put an MSA verb beside «الحين» in a level-2 closing line. | Finding ruled a preference by the judge (see Issues) | Logged, not applied |
| R2-P-S34-1 | A swap does not take effect until a manager approves it, even if both team members have already agreed. Requests that nobody answers within 72 hours are marked **Expired**, and the team member is asked to send a new one. | التبديل ما يصير ساري إلا بعد ما يوافق عليه مدير، حتى لو كان الاثنين من أعضاء الفريق متفقين من قبل. والطلبات اللي ما أحد يرد عليها خلال 72 ساعة تتحول حالتها إلى «**منتهي الصلاحية**»، ونطلب من عضو الفريق يرسل طلب جديد. | الاثنين من أعضاء الفريق  →  العضوين | Round 2 · Native-reader agent | Heavy phrase for two people already named; correct as it stands. | Logged as a preference by the agent | Logged, not applied |
| R2-P-S42-1 | Rotalume is free for workspaces with up to 5 team members, and there are no strings attached. The Team plan costs SAR 19 per team member per month. Prices do not include VAT (15%). | Rotalume مجاني لمساحات العمل اللي فيها 5 من أعضاء الفريق أو أقل، وبدون أي شروط مخفية. سعر باقة الفريق 19 ريال لكل عضو فريق في الشهر. الأسعار ما تشمل ضريبة القيمة المضافة (15%). | 5 من أعضاء الفريق أو أقل  →  5 أعضاء أو أقل | Round 2 · Native-reader agent | Number + «من أعضاء الفريق» is heavy; correct as it stands. | Logged as a preference by the agent | Logged, not applied |
| R2-P-S45-1 | We send an invoice to the Owner's email address on the 1st of each month. For example, a workspace with 14 team members pays SAR 266.00 before VAT. You can change or cancel your plan at any time under **Settings > Plan**. | نرسل فاتورة على بريد «المالك» الإلكتروني يوم 1 من كل شهر. مثلاً، مساحة عمل فيها 14 من أعضاء الفريق تدفع 266.00 ريال قبل ضريبة القيمة المضافة. تقدر تغيّر باقتك أو تلغيها في أي وقت من «**الإعدادات > الباقة**». | 14 من أعضاء الفريق  →  14 عضو | Round 2 · Native-reader agent | Same counting pattern as S42; correct as it stands. | Logged as a preference by the agent | Logged, not applied |
| R2-P-S44-1 | Your free trial ends on {end_date}. Choose a plan to keep your schedules. | فترتك التجريبية المجانية تنتهي يوم {end_date}. ولازم اختيار باقة عشان تبقى جداولك محفوظة. | ولازم اختيار باقة عشان تبقى جداولك محفوظة.  →  اختر باقة عشان تبقى جداولك محفوظة. | Round 2 · Accuracy agent | The source is an instruction ("Choose a plan"); «لازم» states an obligation in so many words. The meaning the reader acts on is the same, so this is logged as a preference. | Logged as a preference by the agent | Logged, not applied |
| R2-S02 | Getting started: your first week as a manager | البداية: أسبوعك الأول بدور مدير | Round 2 · Raised in delivery review: البداية: أسبوعك الأول كمدير | Round 2 · Raised in delivery review | Round 2 · Raised in delivery review: Review A4: «بدور مدير» in the heading is heavy; «كمدير» is lighter. The review itself lists it as a preference. | Finding ruled a preference by the judge (see Issues) | Logged, not applied |
| R2-S11 | Not sure where to start? Add your branches first. Everything else builds on them. | مو واضح من وين البداية؟ أول شي إضافة فروعك، وكل شي ثاني ينبني عليها. | Round 2 · Raised in delivery review: مو واضح من وين البداية؟ أول شي أضف فروعك، وكل شي ثاني ينبني عليها. | Round 2 · Raised in delivery review | Round 2 · Raised in delivery review: Review A2 item 6: «أول شي إضافة فروعك» uses a verbal noun where the rest of the text uses the imperative. | Finding ruled a preference by the judge (see Issues) | Logged, not applied |
| R2-S20 | {name} has accepted your invite and joined {branch_name}. | تم قبول دعوتك: {name} الحين ضمن {branch_name}. | Round 2 · Dialect-consistency agent: انقبلت دعوتك: {name} الحين في {branch_name}. | Round 2 · Dialect-consistency agent | Round 2 · Dialect-consistency agent: The notification mixes levels in one line: standard passive «تم قبول دعوتك» and «ضمن» beside Saudi «الحين». Borderline: «تم…» is usual in app notifications. | Finding ruled a preference by the judge (see Issues) | Logged, not applied |
| R2-S22 | Open **Schedule** and pick a week. Tap any empty slot to add a shift, then choose a team member, a start time, and an end time. If you don't know yet who will work a shift, save it as an **Open shift**. Team members at that branch can then pick it up themselves. | افتح «**الجدول**» واختر الأسبوع. اضغط أي خانة فاضية لإضافة وردية، ثم اختر عضو الفريق ووقت البداية ووقت النهاية. وإذا ما تعرف للحين مين راح يشتغل في الوردية، احفظها كـ«**وردية مفتوحة**». وقتها أعضاء الفريق في هذا الفرع يقدرون ياخذونها بنفسهم. | Round 2 · Native-reader agent: افتح «**الجدول**» واختر الأسبوع. اضغط أي خانة فاضية لإضافة وردية، ثم اختر عضو الفريق ووقت البداية ووقت النهاية. وإذا ما تعرف للحين من راح يشتغل في الوردية، احفظها كـ«**وردية مفتوحة**». وقتها أعضاء الفريق في هذا الفرع يقدرون ياخذونها بنفسهم.<br>Round 2 · Dialect-consistency agent: افتح «**الجدول**» واختر الأسبوع. اضغط أي خانة فاضية لإضافة وردية، ثم اختر عضو الفريق ووقت البداية ووقت النهاية. وإذا ما تعرف للحين من راح يشتغل في الوردية، احفظها كـ«**وردية مفتوحة**». وقتها أعضاء الفريق في هذا الفرع يقدرون ياخذونها بنفسهم. | Round 2 · Native-reader agent + Round 2 · Dialect-consistency agent | Round 2 · Native-reader agent: «مين» in «مين راح يشتغل في الوردية» is the Hejazi form of "who"; the rest of the text uses Najdi-leaning forms («وش», «ودّك», «لين», «هالأسبوع»). Low confidence: «مين» is heard across Saudi Arabia.<br>Round 2 · Dialect-consistency agent: «مين» is the Hejazi form; the file otherwise uses Najdi-leaning forms («وش»). Two Saudi varieties in one file. Low confidence. | Finding ruled a preference by the judge (see Issues) | Logged, not applied |
| R2-S30 | **Time off**: for one day or more. A request must be sent at least 3 days in advance. | «**إجازة**»: ليوم واحد أو أكثر. لازم ينرسل الطلب قبلها بـ 3 أيام على الأقل. | Round 2 · Raised in delivery review: «**إجازة**»: ليوم واحد أو أكثر. لازم ينرسل الطلب قبلها بـ3 أيام على الأقل. | Round 2 · Raised in delivery review | Round 2 · Raised in delivery review: Review A4: «بـ 3» is written with a space between the preposition and the number. | Finding ruled a preference by the judge (see Issues) | Logged, not applied |
| R2-S40 | You have until the 5th of the following month to correct a timesheet. After that date it is locked, and only the Owner can unlock it. | معك لين يوم 5 من الشهر اللي بعده عشان تصحّح سجل الدوام. بعد هذا التاريخ ينقفل السجل، وما يقدر يفتحه إلا «المالك». | Round 2 · Raised in delivery review: No correction proposed in the review. | Round 2 · Raised in delivery review | Round 2 · Raised in delivery review: Review A4: «معك لين يوم 5» for "You have until the 5th" is listed as a wording the delivery review would change. No replacement is given in the review. | Finding ruled a preference by the judge (see Issues) | Logged, not applied |
| R3-P-1 | S11: Not sure where to start? Add your branches first. Everything else builds on them.<br>S56: Rotalume uses the time zone of each branch, not the time zone of your phone. You can change it under **Settings > Branches**. | S11: مو واضح من وين البداية؟ أول شي إضافة فروعك، وكل شي ثاني ينبني عليها.<br>S56: Rotalume يستخدم المنطقة الزمنية لكل فرع، مو المنطقة الزمنية لجوالك. تقدر تغيّرها من «**الإعدادات > الفروع**». | «مو»  →  no wording suggested | Round 3 · Native-reader agent (target only, separate agent) | Listed by the agent under "Preferences only (not raised as defects)", without a reason. | Logged as a preference by the agent | Logged, not applied |
| R3-P-2 | Open **Schedule** and pick a week. Tap any empty slot to add a shift, then choose a team member, a start time, and an end time. If you don't know yet who will work a shift, save it as an **Open shift**. Team members at that branch can then pick it up themselves. | افتح «**الجدول**» واختر الأسبوع. اضغط أي خانة فاضية لإضافة وردية، ثم اختر عضو الفريق ووقت البداية ووقت النهاية. وإذا ما تعرف للحين مين راح يشتغل في الوردية، احفظها كـ«**وردية مفتوحة**». وقتها أعضاء الفريق في هذا الفرع يقدرون ياخذونها بنفسهم. | «مين»  →  no wording suggested | Round 3 · Native-reader agent (target only, separate agent) | Listed by the agent under "Preferences only (not raised as defects)", without a reason. | Logged as a preference by the agent | Logged, not applied |
| R3-P-3 | Rotalume is free for workspaces with up to 5 team members, and there are no strings attached. The Team plan costs SAR 19 per team member per month. Prices do not include VAT (15%). | Rotalume مجاني لمساحات العمل اللي فيها 5 من أعضاء الفريق أو أقل، وبدون أي شروط مخفية. سعر باقة الفريق 19 ريال لكل عضو فريق في الشهر. الأسعار ما تشمل ضريبة القيمة المضافة (15%). | «بدون أي شروط مخفية»  →  no wording suggested | Round 3 · Native-reader agent (target only, separate agent) | Listed by the agent under "Preferences only (not raised as defects)", without a reason. | Logged as a preference by the agent | Logged, not applied |
| R3-P-4 | We send an invoice to the Owner's email address on the 1st of each month. For example, a workspace with 14 team members pays SAR 266.00 before VAT. You can change or cancel your plan at any time under **Settings > Plan**. | نرسل فاتورة على بريد «المالك» الإلكتروني يوم 1 من كل شهر. مثلاً، مساحة عمل فيها 14 من أعضاء الفريق تدفع 266.00 ريال قبل ضريبة القيمة المضافة. تقدر تغيّر باقتك أو تلغيها في أي وقت من «**الإعدادات > الباقة**». | «بريد «المالك» الإلكتروني»  →  no wording suggested | Round 3 · Native-reader agent (target only, separate agent) | Listed by the agent under "Preferences only (not raised as defects)", without a reason. | Logged as a preference by the agent | Logged, not applied |
| R3-03 | You have until the 5th of the following month to correct a timesheet. After that date it is locked, and only the Owner can unlock it. | معك لين يوم 5 من الشهر اللي بعده عشان تصحّح سجل الدوام. بعد هذا التاريخ ينقفل السجل، وما يقدر يفتحه إلا «المالك». | «عندك لين يوم 5» | Round 3 · Native-reader agent (target only, separate agent) | «معك لين يوم 5» sounds Levantine. | Finding ruled a preference by the judge (see Issues) | Logged, not applied |
| R3-04 | A swap does not take effect until a manager approves it, even if both team members have already agreed. Requests that nobody answers within 72 hours are marked **Expired**, and the team member is asked to send a new one. | التبديل ما يصير ساري إلا بعد ما يوافق عليه مدير، حتى لو كان الاثنين من أعضاء الفريق متفقين من قبل. والطلبات اللي ما أحد يرد عليها خلال 72 ساعة تتحول حالتها إلى «**منتهي الصلاحية**»، ونطلب من عضو الفريق يرسل طلب جديد. | «حتى لو العضوين متفقين» | Round 3 · Native-reader agent (target only, separate agent) | «حتى لو كان الاثنين من أعضاء الفريق متفقين» has a translated feel. | Finding ruled a preference by the judge (see Issues) | Logged, not applied |
| R3-05 | S42: Rotalume is free for workspaces with up to 5 team members, and there are no strings attached. The Team plan costs SAR 19 per team member per month. Prices do not include VAT (15%).<br>S45: We send an invoice to the Owner's email address on the 1st of each month. For example, a workspace with 14 team members pays SAR 266.00 before VAT. You can change or cancel your plan at any time under **Settings > Plan**. | S42: Rotalume مجاني لمساحات العمل اللي فيها 5 من أعضاء الفريق أو أقل، وبدون أي شروط مخفية. سعر باقة الفريق 19 ريال لكل عضو فريق في الشهر. الأسعار ما تشمل ضريبة القيمة المضافة (15%).<br>S45: نرسل فاتورة على بريد «المالك» الإلكتروني يوم 1 من كل شهر. مثلاً، مساحة عمل فيها 14 من أعضاء الفريق تدفع 266.00 ريال قبل ضريبة القيمة المضافة. تقدر تغيّر باقتك أو تلغيها في أي وقت من «**الإعدادات > الباقة**». | «5 أعضاء أو أقل», «14 عضو» | Round 3 · Native-reader agent (target only, separate agent) | «5 من أعضاء الفريق أو أقل» (S42) and «14 من أعضاء الفريق» (S45): calque. | Finding ruled a preference by the judge (see Issues) | Logged, not applied |
| R3-06 | **Owner**: can do everything, including billing. Each workspace has only one Owner. | «**المالك**»: يقدر يسوي كل شي، ومنه الفوترة. كل مساحة عمل لها «مالك» واحد بس. | «بما فيه الفوترة» | Round 3 · Native-reader agent (target only, separate agent) | «ومنه الفوترة» is awkward. (This wording was itself a round-2 fix.) | Finding ruled a preference by the judge (see Issues) | Logged, not applied |
| R3-07 | Getting started: your first week as a manager | البداية: أسبوعك الأول بدور مدير | «كمدير» | Round 3 · Native-reader agent (target only, separate agent) | «بدور مدير»: calque. | Finding ruled a preference by the judge (see Issues) | Logged, not applied |
| R3-08 | Welcome, {first_name}! Your workspace "{workspace_name}" is ready. What do you want to do first? | هلا {first_name}! مساحة عملك «{workspace_name}» جاهزة. وش أول شي ودّك فيه؟ | «وش ودّك تبدأ فيه؟» | Round 3 · Native-reader agent (target only, separate agent) | «وش أول شي ودّك فيه؟» is unclear. | Finding ruled a preference by the judge (see Issues) | Logged, not applied |
| R3-10 | Go to **Settings > Branches** and tap **Add branch**. Give each branch a name and its opening hours, for example 7:00 AM to 11:30 PM. | ادخل على «**الإعدادات > الفروع**» واضغط «**إضافة فرع**». اكتب لكل فرع اسمه وساعات العمل فيه، مثلاً من 7:00 ص إلى 11:30 م. | «انتقل إلى» | Round 3 · Native-reader agent (target only, separate agent) | «ادخل على» (S13) against «انتقل إلى» (S05): inconsistent, and colloquial in a step. | Finding ruled a preference by the judge (see Issues) | Logged, not applied |
| R3-13 | {name} has accepted your invite and joined {branch_name}. | تم قبول دعوتك: {name} الحين ضمن {branch_name}. | «{name} قبل دعوتك، والحين ضمن…» | Round 3 · Native-reader agent (target only, separate agent) | «تم قبول دعوتك: {name} الحين…»: stiff standard opening in a notification. | Finding ruled a preference by the judge (see Issues) | Logged, not applied |

## 8. Glossary changes and open queries

No glossary entry was changed. New terms proposed by the term agents (not approved by anyone; the translator used them as candidates):

| Term | Proposed target | Source / evidence | Status |
|---|---|---|---|
| Help Center | مركز المساعدة | Glossary: no entry contains or defines 'Help Center' or 'Help'. \| Style guide: headings take the standard wording (level 1), and Rotalume stays in Latin letters, so in the S01 heading the brand sits next to the Arabic term (for example «مركز مساعدة Rotalume»). The style guide gives no Arabic form for the term itself. \| Source: S01 uses it as the page name (Heading 1); S58 has a related menu label 'Help' in 'Help > Chat with us', which should stay consistent with it («المساعدة»). \| Web source checked; not listed here. | Proposed, for the client to confirm (Candidate) |
| Create workspace | إنشاء مساحة العمل | Glossary: workspace = «مساحة العمل» (approved form, with the definite article). \| Glossary pattern for buttons: verbal noun, not imperative (Sign in = «تسجيل الدخول», Publish = «نشر», Approve = «موافقة»); 'Send invite' = «إرسال الدعوة» keeps the definite noun after the verbal noun. \| Style guide: UI labels use standard wording, and glossary terms are used exactly as given, every time. \| Source: S07 'Type a name for your workspace, then tap **Create workspace**' refers to the reader's one workspace, so the definite form fits. \| No page was checked for this term. The verbal noun «إنشاء» is my choice. The indefinite «إنشاء مساحة عمل» is the alternative if the client prefers it (compare 'Invite team member' = «دعوة عضو للفريق»). | Proposed, for the client to confirm |
| Add branch | إضافة فرع | Glossary: branch = «فرع» (masculine; plural «فروع»; 'Branches' = «الفروع»). \| Glossary pattern for buttons: verbal noun (Sign in = «تسجيل الدخول», Publish = «نشر»); indefinite object as in 'Invite team member' = «دعوة عضو للفريق». \| Style guide: UI labels use standard wording and go in « » in running text. \| Source: S13 'tap **Add branch**. Give each branch a name' is a repeatable action on any new branch, so the indefinite singular fits. \| No page was checked for this term; one search returned no usable page. The verbal noun «إضافة» is my choice. | Proposed, for the client to confirm |
| Team | الفريق | Glossary: team member = «عضو الفريق», plural «أعضاء الفريق»; 'Team plan' = «باقة الفريق»; 'Invite team member' = «دعوة عضو للفريق». All render 'team' as «الفريق». \| Glossary pattern for screen names: definite noun (Schedule = «الجدول», Requests = «الطلبات», Settings = «الإعدادات», Branches = «الفروع»). \| Style guide: UI labels use standard wording and go in « » in running text. \| Source: S14 'open **Team** and tap **Invite team member**' shows it is the screen that lists team members. \| No page was checked for this term. | Proposed, for the client to confirm |
| Copy last week | نسخ الأسبوع الماضي | Glossary: no entry for 'Copy last week' or for 'copy'. The pattern for button labels is a verbal noun (Sign in = «تسجيل الدخول», Publish = «نشر», Approve = «موافقة», Decline = «رفض», Send invite = «إرسال الدعوة»), so «نسخ» follows the same form. \| Style guide, 'Variety and register': UI labels and button names take standard wording (level 1), not Saudi conversational wording, so «الأسبوع الماضي» rather than a colloquial form. It sets no length limit for labels. \| Source S22-S23: the button sits on the Schedule screen after the manager picks a week, and copies the previous week's shifts into it ('You only need to fix what has changed'). \| No page opened for this term. | Proposed, for the client to confirm (Candidate) |
| Expired | منتهي الصلاحية | Glossary: no entry for 'Expired'. The noun it describes is Requests = «الطلبات», singular «طلب» (masculine), so the status takes the masculine singular form. \| Style guide, 'Variety and register': UI labels take standard wording (level 1). It sets no length limit for labels. \| Source S34: a status given to requests that nobody answers within 72 hours. Source S06 uses the verb 'expires' for the verification code, which is not a label; in running text that is «تنتهي صلاحية الرمز», and the two stay consistent. \| No page opened for this term: one search returned no usable Saudi page showing this status label. Model knowledge only for the wording itself. \| Shorter alternative for the client to consider if the status chip is narrow: «منتهي». | Proposed, for the client to confirm (Candidate) |
| Export | تصدير | Glossary: no entry for 'Export'. The pattern for button labels is a verbal noun (Publish = «نشر», Approve = «موافقة», Decline = «رفض»), so «تصدير» follows the same form. \| Style guide, 'Variety and register': UI labels and button names take standard wording (level 1). \| Source S36: a button on the Timesheets screen that downloads the file. Source S17 uses the verb in running text ('export timesheets'), which would be «يصدّر سجلات الدوام». \| Web source checked; not listed here. | Proposed, for the client to confirm |
| Resend code | إعادة إرسال الرمز | Glossary: verification code = «رمز التحقق», with the note 'Do not use «كود» or «رمز التفعيل»', so 'code' is «الرمز». Send invite = «إرسال الدعوة» gives «إرسال» for 'send' in a button label, in the verbal-noun form. \| Style guide, 'Variety and register': UI labels and button names take standard wording (level 1). It sets no length limit for labels. \| Source S48: the button is tapped after waiting 60 seconds when the verification code of S06 and S47 has not arrived. The source label says 'code', not 'verification code', so the short form «الرمز» mirrors it. \| Web source checked; not listed here. \| Longer alternative for the client to consider, matching the glossary term in full: «إعادة إرسال رمز التحقق». | Proposed, for the client to confirm |
| Help | «المساعدة» | Glossary: no entry for 'Help'. Nearest pattern: menu and screen names are definite nouns (Settings = «الإعدادات», Requests = «الطلبات», Schedule = «الجدول»), so the menu name takes the definite article. \| Style guide, UI strings: labels go in Arabic quotation marks and menu paths keep their order with '>', so S58 reads «المساعدة > المحادثة معنا». Style guide, Variety and register: UI labels use standard wording (level 1). \| Source: S58 uses 'Help' as a menu name in a path; S01 has 'Help Center', which should use the same noun («مركز المساعدة») for consistency. \| Web source checked; not listed here. | Proposed, for the client to confirm |
| Chat with us | «المحادثة معنا» | Glossary: no entry for 'Chat with us'. Nearest pattern: action labels are verbal nouns, not imperatives (Sign in = «تسجيل الدخول», Publish = «نشر», 'Send invite' = «إرسال الدعوة», 'Invite team member' = «دعوة عضو للفريق»). A verbal-noun label follows that pattern. \| Style guide, Address: prefer a verbal noun or neutral structure to a gendered verb; this rules out the masculine imperative «تحدّث معنا» as a label for an audience of women and men. Style guide, Variety and register: UI labels use standard wording, so not the colloquial «دردش معنا». No length limit for labels is stated in the style guide. \| Source: S58 uses it as the second part of a menu path ('Help > Chat with us'); S08 uses 'in chat' for the same channel, which should use the same noun («في المحادثة»). \| Web source checked; not listed here. \| The exact string «المحادثة معنا» was not found on any page opened. Alternative for the client to consider if an imperative label is acceptable: «تحدّث معنا». | Proposed, for the client to confirm (Candidate) |
| role | دور (definite «الدور»; plural «أدوار»; S14 'choose a role' = «اختر الدور»; S15 'three roles' = «ثلاثة أدوار») | Glossary: no entry for 'role', and no Arabic word for it. The notes for 'team member', 'Manager' and 'Owner' call each one a 'Role name', which confirms the sense: a named permission level in the workspace, not a job title. \| Style guide: no rule specific to this term. S14 is a numbered-step-style instruction, so the short imperative applies («اختر»), and standard wording applies to what the reader must find on screen. \| Source: S14 'choose a role' (a choice made when inviting a person); S15 'There are three roles', followed by Owner, Manager, Team member with their permissions (S16 to S18). 'role' is not bold in the source, so it is a domain noun, not a UI label, and takes no quotation marks. \| Web source checked; not listed here. \| The Arabic form is supported by one opened page only. Alternative seen in the same page for a related concept: «صلاحيات» (permissions), which is not the same as 'role' and is not proposed. | Proposed, for the client to confirm (Candidate) |
| free trial | فترة تجريبية مجانية (definite «الفترة التجريبية المجانية»; 'the trial' in S43 = «الفترة التجريبية»; S43 '30-day free trial of the Team plan' = «فترة تجريبية مجانية لمدة 30 يوم على باقة الفريق») | Glossary: no entry for 'free trial' or 'trial'. Related entry that must be kept inside the phrase: plan = «الباقة», 'Team plan' = «باقة الفريق» (do not use «خطة»). \| Style guide: Western digits and Arabic number rules for durations, so «30 يوم». S44 is a product message (level 2, Saudi conversational wording) with the placeholder {end_date} copied exactly; the term itself stays the same at both levels. \| Source: S43 '30-day free trial of the Team plan' and 'When the trial is about to end'; S44 'Your free trial ends on {end_date}'. The term is a period with a start and an end date, which fits «فترة» better than the bare «تجربة». \| Web source checked; not listed here. \| Web source checked; not listed here. So the proposed form is supported by one opened page; «تجربة مجانية» is the alternative for the client to consider. | Proposed, for the client to confirm (Candidate) |
| billing | الفوترة | Glossary: no entry for 'billing'. Related entries only: invoice = «فاتورة» (same root as «الفوترة»), plan = «الباقة» (so S41 'Plans and billing' would read «الباقات والفوترة»). \| Style guide: S41 is a heading and S16 is a role description, so level 1 (standard wording) applies; no length limit is stated. \| Source usage: S16 ('can do everything, including billing') and S41 ('Plans and billing', a section about plans, prices, VAT and the monthly invoice) use it as the subscription-payment area of the product, not as a single invoice. \| Web source checked; not listed here. | Proposed, for the client to confirm (Candidate) |
| time zone | المنطقة الزمنية | Glossary: no entry for 'time zone' or any part of it. \| Style guide: no rule for 'time zone' itself. The only related rule is 'Riyadh time' = «بتوقيت الرياض» (S58), which is a different expression and should stay as the guide gives it. \| Source usage: S56 uses it twice as a setting of each branch ('the time zone of each branch, not the time zone of your phone'), changed under «الإعدادات > الفروع»; a plain noun, not a UI label in bold. \| Web source checked; not listed here. | Proposed, for the client to confirm (Candidate) |
| support (support staff, support team) | الدعم — 'support team' = «فريق الدعم» (S58); 'support staff' = «موظفو الدعم» (S08, in the sentence: «موظفي الدعم في Rotalume») | Glossary: no entry for 'support'. Note on a neighboring entry: 'team member' = «عضو الفريق», 'Do not replace with «موظف»'. That restriction is about the customer's team members; Rotalume's own support staff are a different referent, so «موظفو الدعم» does not break it, but the client should confirm. If the client wants to avoid «موظف» altogether, «فريق الدعم» can serve in S08 as well. \| Style guide: Rotalume stays in Latin letters next to the term (S08). Rotalume speaks as 'we', so S58 'Our support team' = «فريق الدعم عندنا» / «فريق الدعم» with a first-person plural verb. No length limit applies (running text, not a UI label). \| Source usage: S08 'Rotalume support staff' (the people who might contact the reader) and S58 'Our support team is here from Sunday to Thursday' both mean customer support, not technical support specifically, so «الدعم» without «الفني» matches the source. \| Web source checked; not listed here. \| «موظفو الدعم» itself: Model knowledge only; no page checked. | Proposed, for the client to confirm (Candidate) |
| app | التطبيق (S05 'the Rotalume app' = «تطبيق Rotalume») | Glossary: no entry for 'app'. Brand entry applies in S05: Rotalume stays in Latin letters, so «تطبيق Rotalume». \| Style guide: the register is described as the one 'Saudi apps use'; the web address app.rotalume.example in S05 stays exactly as in the source and is not translated. 'App' is not a UI label, so no quotation marks and no length limit. \| Source usage: S05 (open the app on the mobile phone, as opposed to the web address on a computer), S29, S55, S56 context and S58 ('In the app, tap ...') all mean the mobile application; one target form fits all five. \| Web source checked; not listed here. | Proposed, for the client to confirm (Candidate) |

Open questions. Q1 to Q20 come from the intake agent (step 1), each with the assumption it stated. The translator agent did not receive the intake report, because it is not among the inputs listed for it; after the run each assumption was compared with the delivered text and the 'In the delivered text' remark was added. Q21 comes from the judge (step 6). Q22 and Q23 come from the round-2 judge, Q24 and Q25 from the round-3 judge. Round 3 raised the form of the Manager label again (R3-02); Q21 already asks it. Nobody answered any question.

- **Q1.** S25, %d with a fixed plural: "You have %d new shifts" is already wrong in English for 1, and Arabic needs different noun forms for 1, 2, 3 to 10 and 11 or more. (Source defect.) *Assumption used:* Restructure as a label followed by the number, as the style guide allows. *In the delivered text:* Follows the assumption: «ورديات جديدة لك هالأسبوع: %d».
- **Q2.** S25, "Your first shift starts tomorrow" is hard-coded, and {start_time} carries only a time. The sentence is false whenever the first shift is not the next day, and reads oddly when %d is 1. (Source defect.) *Assumption used:* Translate as written, with «بكرة», and report it as a source defect. *In the delivered text:* Follows the assumption.
- **Q3.** S20 and S33: the placeholder {name} is the subject of a gendered verb in Arabic. (Source defect.) *Assumption used:* Restructure around verbal nouns, as the style guide instructs. *In the delivered text:* Follows the assumption: «تم قبول دعوتك: {name} …», «طلب تبديل وردية من {name}: …».
- **Q4.** S33: one {date} for a two-way swap. The string does not say whose shift the date refers to, or whether both shifts are on that date. (Source defect.) *Assumption used:* Keep the single date attached to the shift of {name}, as in the source. *In the delivered text:* Follows the assumption.
- **Q5.** Runtime values of {date}, {end_date} and {start_time} are unknown. If the app injects English formats, the Arabic strings will break the style guide's date and time rules. *Assumption used:* Copy the placeholders exactly and build wording that reads correctly if the value is in the style-guide format. *In the delivered text:* Follows the assumption: «يوم {date}», «يوم {end_date}», «الساعة {start_time}».
- **Q6.** S20: the content of {branch_name} is unknown. It may or may not already include the word "branch". *Assumption used:* Do not add «فرع» before the placeholder. *In the delivered text:* Follows the assumption.
- **Q7.** Mixed-direction text around placeholders: in S10, S20 and S33, Latin-script names can reorder visually in a right-to-left line. *Assumption used:* Add no invisible direction marks, and separate adjacent placeholders with Arabic words. *In the delivered text:* Follows the assumption. In the delivered Word file the placeholders, which are Latin text, sit inside right-to-left paragraphs.
- **Q8.** S10: the style guide prefers «تبي» for "you want", but also requires wording that fits a woman and a man in direct questions and in messages to {first_name}. «تبي» addresses a man. *Assumption used:* The neutrality rule wins in S10 and S53, and a neutral structure is used there. Elsewhere the default imperative the guide prescribes is used. *In the delivered text:* Follows the assumption: S10 «وش أول شي ودّك فيه؟», S53 «أكيد حذف هذي الوردية؟». The judge kept both on the same ground (findings S44-3 and S53).
- **Q9.** S57: "Still stuck?" is both a heading (level 1) and a short question the guide names as level 2. *Assumption used:* Level 2, because the guide names it explicitly. *In the delivered text:* Follows the assumption: «للحين ما انحلّت المشكلة؟».
- **Q10.** The register of ordinary explanatory paragraphs (for example S13, S26, S27, S34, S40 and the security warning S08) is not assigned to either level by the style guide. *Assumption used:* Plain, simple wording close to level 1 with no marked dialect words; level 2 only for the items the guide lists and the six quoted messages. *In the delivered text:* Does not follow the assumption: the explanatory paragraphs use Saudi conversational wording (for example S08 «ما راح نطلبه», S26 «تقدر تعدّل», S40 «معك لين»). No checking agent raised this as a finding; the dialect-consistency agent logged two preferences (S22, S26) and noted that the style guide does not assign body paragraphs to a level. The client should say which level these paragraphs take.
- **Q11.** S23 and S48 combine a conversational question with a step that names a button. *Assumption used:* The level switches at the sentence boundary, never inside a sentence. *In the delivered text:* Follows the assumption.
- **Q12.** Nine UI labels are not in the glossary: Create workspace, Add branch, Team (screen), Copy last week, Expired, Export, Resend code, Help, Chat with us. *Assumption used:* Coin them from glossary vocabulary, use them consistently, and list them as unverified against the real interface. "Plan" in Settings > Plan follows the glossary: «الباقة». *In the delivered text:* The term agents proposed a target for each (see the new terms above); the translator used those. None is confirmed by the client.
- **Q13.** Bold and quotation marks on UI labels: the source marks labels in bold; the guide requires « ». *Assumption used:* UI labels, including the role names that open S16 to S18, get « » and keep bold. The bold troubleshooting questions S47, S49, S51 and S55 keep bold only. *In the delivered text:* Follows the assumption.
- **Q14.** Dual numbers: the glossary gives «ورديتين» with no digit; S39 is a data line reading "2 shifts". *Assumption used:* Follow the glossary form without a digit in S39. All other numbers stay as Western digits. *In the delivered text:* Follows the assumption. The step-3 script flagged it (finding S39) and the judge ruled it not a defect.
- **Q15.** Money grammar: the guide's model is «19 ريال», where formal grammar would give «19 ريالاً». *Assumption used:* Follow the guide's model exactly. *In the delivered text:* Follows the assumption.
- **Q16.** S02, "as a manager", and the role label Manager: the reader's gender is unknown. *Assumption used:* «مدير» as the generic label form, per the glossary. *In the delivered text:* Follows the assumption: «بدور مدير».
- **Q17.** S60, the fictional-product line, is not marked as translatable or not. *Assumption used:* Translate it and keep the italic. *In the delivered text:* Follows the assumption.
- **Q18.** The deliverable format is not stated by the client files. *Assumption used:* One translated .docx with the same paragraph styles, right-to-left paragraphs, named with the prefix pack-a-gulf-sa. *In the delivered text:* Follows the assumption.
- **Q19.** Automatic list numbers in S05 to S07 are drawn by the file, so the translation text cannot control their digit set, and the guide forbids mixing digit sets. *Assumption used:* Leave the automatic numbering untouched and flag it for a layout check. The typed heading numbers "1." to "7." are kept as Western digits. *In the delivered text:* Follows the assumption. Which digits the automatic numbers show depends on the program that opens the file; this was not checked in Word.
- **Q20.** SOURCES.md, which the style guide cites for its numeral rule, was not supplied. *Assumption used:* Apply the Western-digits rule as written, without checking its evidence. *In the delivered text:* Follows the assumption.
- **Q21.** S17 (glossary): Manager is given as indefinite «مدير» with the note 'Keep the label in this form', while the other two role labels are definite («المالك», «عضو الفريق»). The role list in S16 to S18 is therefore inconsistent in form. Can the client confirm whether the app's label is «مدير» or «المدير», and correct the glossary if needed? (From the judge, finding S17.) *Assumption used:* Follow the glossary: «مدير». *In the delivered text:* Follows the assumption.
- **Q22.** S44 (round 2): the trial-end message is shown to the Owner, who may be a woman. The style guide asks for gender-neutral wording only in messages with {first_name} and in direct questions; this message is neither, and round 2 replaced «ولازم اختيار باقة» with the imperative «اختر باقة», the masculine form the guide prescribes for steps. Does the client want every in-app message gender-neutral? (From the round-2 judge, finding R2-S44.) *Assumption used:* The Address rule applies as written. *In the delivered text:* «اختر باقة عشان تبقى جداولك محفوظة.»
- **Q23.** S22 (round 2): "who" is «مين», a form used in Saudi Arabia and best known from Hejazi speech, in a text that otherwise uses Najdi-leaning forms such as «وش». The client named the variety "Gulf (Saudi Arabia)" and banned no Saudi form. Does the client want one regional form throughout? (From the round-2 judge, finding R2-S22.) *Assumption used:* Any form in general Saudi use is allowed. *In the delivered text:* «مين راح يشتغل في الوردية» is unchanged.
- **Q24.** Unnumbered body paragraphs that contain imperatives (for example S13, S14, S22, S32, S36) (round 3): the style guide gives standard wording to "the numbered steps" and Saudi conversational wording to a list of things the product "says", and names these paragraphs under neither level. This is the same gap as Q10, seen from the instructions inside those paragraphs. Which level should they take? (From the round-3 judge, finding R3-01.) *Assumption used:* They are not numbered steps, so they follow the general rule that the text must read "as written by a Saudi, not as Modern Standard Arabic". *In the delivered text:* Saudi conversational wording with short imperatives, unchanged.
- **Q25.** S13, S45, S56, S58 (round 3): menu paths use the sign ">" as the style guide prescribes («الإعدادات > الفروع»). How the sign is drawn in a right-to-left line was not checked in a rendered view. Can the client confirm that it points the way readers expect in the product's help center? (From the round-3 judge, finding R3-12.) *Assumption used:* Follow the style guide exactly. *In the delivered text:* ">" in all four paths, unchanged.

## 9. Quality gate

Quality gate: passed

The round-1 file passed on gate run 2. The round-2 file, which is the file now delivered, passed on gate run 3. Runs 1 and 2 below are round 1 and concern the round-1 file; run 3 is round 2. Round 3 ordered no correction, so the round-2 gate result stands for the final file, which is the same file; the gate was nevertheless run on the final file (run 4) and passed.

**Gate run 1** (on the saved file pack-a-gulf-sa-delivered.docx)

| # | Gate check | Result | Segments concerned |
|---|---|---|---|
| G1 | Same number of segments, order and structure as the source | Pass | None |
| G2 | No empty or untranslated segment | Pass | None |
| G3 | Placeholders and variables intact | Pass | None |
| G4 | Numbers in the form the style guide prescribes | Pass | None |
| G5 | Glossary terms used; no forbidden form | Fail | S08: form «موظفي» matches «موظف», which the glossary note for "team member" forbids |
| G6 | Brand names, codes, web and email addresses copied exactly | Pass | None |
| G7 | Mechanical locale rules: digit set, punctuation marks, quotation marks, spacing | Pass | None |
| G8 | Length of interface strings | Not applicable: the style guide sets no limit | None |
| G9 | Closing line (fictional content) present, last, translated | Pass | None |
| G10 | File set right to left | Pass | None |

The G5 flag became finding S08 (Found by: Quality gate), went to the devil's advocate and the judge, and was ruled Not a defect. The file was not touched; the rule was corrected (last gate rule note below).

**Gate run 2** (same saved file, corrected rule)

| # | Gate check | Result | Segments concerned |
|---|---|---|---|
| G1 | Same number of segments, order and structure as the source | Pass | None |
| G2 | No empty or untranslated segment | Pass | None |
| G3 | Placeholders and variables intact | Pass | None |
| G4 | Numbers in the form the style guide prescribes | Pass | None |
| G5 | Glossary terms used; no forbidden form | Pass | None |
| G6 | Brand names, codes, web and email addresses copied exactly | Pass | None |
| G7 | Mechanical locale rules: digit set, punctuation marks, quotation marks, spacing | Pass | None |
| G8 | Length of interface strings | Not applicable: the style guide sets no limit | None |
| G9 | Closing line (fictional content) present, last, translated | Pass | None |
| G10 | File set right to left | Pass | None |

**Gate run 3** (round 2, on the saved round-2 file round2/pack-a-gulf-sa-delivered.docx, new script)

| # | Gate check | Result | Segments concerned |
|---|---|---|---|
| G1 | Same number of segments, order and structure as the source | Pass | None |
| G2 | No empty or untranslated segment | Pass | None |
| G3 | Placeholders and variables intact | Pass | None |
| G4 | Numbers in the form the style guide prescribes | Pass | None |
| G5 | Glossary terms used; no forbidden form | Pass | None |
| G6 | Brand names, codes, web and email addresses copied exactly | Pass | None |
| G7 | Mechanical locale rules: digit set, punctuation marks, quotation marks, spacing | Pass | None |
| G8 | Length of interface strings | Not applicable: the style guide sets no limit | None |
| G9 | Closing line (fictional content) present, last, translated | Pass | None |
| G10 | File set right to left | Pass | None |

Run 3 raised no flag, so no gate finding went to the devil's advocate and the judge in round 2.

**Gate run 4** (round 3, on the saved final file final/pack-a-gulf-sa-delivered.docx, which is identical to the round-2 file; same script and rules as run 3)

| # | Gate check | Result | Segments concerned |
|---|---|---|---|
| G1 | Same number of segments, order and structure as the source | Pass | None |
| G2 | No empty or untranslated segment | Pass | None |
| G3 | Placeholders and variables intact | Pass | None |
| G4 | Numbers in the form the style guide prescribes | Pass | None |
| G5 | Glossary terms used; no forbidden form | Pass | None |
| G6 | Brand names, codes, web and email addresses copied exactly | Pass | None |
| G7 | Mechanical locale rules: digit set, punctuation marks, quotation marks, spacing | Pass | None |
| G8 | Length of interface strings | Not applicable: the style guide sets no limit | None |
| G9 | Closing line (fictional content) present, last, translated | Pass | None |
| G10 | File set right to left | Pass | None |

Run 4 raised no flag.

**Gate rule notes**

| Segments | What was flagged | Why it is not an error | How the rule was changed |
|---|---|---|---|
| S03, S44 (S44-1), S59 (S59-1) | Schedule: «الجدول» not found | Judge: «جدول» and «جداولك» are the approved term in the indefinite form and in the glossary's own plural with an attached pronoun. | The Schedule check also accepts the stems «جدول» and «جداول» (indefinite, plural, attached pronoun). |
| S04, S10, S16 (S16-1), S42 (S42-1), S43, S45 (S45-1) | workspace: «مساحة العمل» not found | Judge: «مساحة عملك», «مساحة عمل» and «مساحات العمل» are the approved term with an attached pronoun, indefinite, or plural. | The workspace check also accepts «مساحة/مساحات» + «عمل/العمل» with or without an attached pronoun. |
| S05, S36 (S36-1), S48 | mobile phone: «الجوال» not found | Judge: «جوالك» and «جوالاتهم» are the approved term with an attached pronoun, or plural with a pronoun. | The mobile phone check also accepts the stem «جوال» without the article (pronoun, plural). |
| S06, S14 (S14-1) | mobile number: «رقم الجوال» not found | Judge: «رقم جوالك» and «رقم جواله» are the approved term with an attached pronoun. | The mobile number check also accepts «رقم جوال» + attached pronoun. |
| S14 (S14-2), S49 | team member: «عضو الفريق» not found | Judge: «عضو فريق» is the indefinite form of the approved term. | The team member check also accepts the indefinite «عضو فريق». |
| S20 (S20-1) | invite: «دعوة» not found | Judge: «دعوتك» is the approved term with an attached pronoun. | The invite check also accepts «دعوت» + attached pronoun. |
| S26 (S26-1), S36 (S36-2) | clock in: «تسجيل الحضور» not found | Judge: «سجّل حضوره» and «يسجّل أعضاء الفريق حضورهم» are the glossary's running-text form in the past tense or with a plural subject. | The clock in check also accepts the verb «سجّل/يسجّل/يسجّلون» followed by «حضور» + pronoun, with the subject «أعضاء الفريق» allowed between them. |
| S36 (S36-3) | clock out: «تسجيل الانصراف» not found | Judge: «يسجّلون انصرافهم» is the glossary's running-text form with a plural subject. | The clock out check also accepts the verb «سجّل/يسجّل/يسجّلون» followed by «انصراف» + pronoun. |
| S26 (S26-2) | Publish: «نشر» not found | Judge: 'published' is an adjective here and «المنشورة» is the participle of the approved word. | The Publish check also accepts the participle stem «منشور». |
| S28 | Shift swap: «تبديل وردية» not found | Judge: «تبديل الورديات» is the approved term made definite and plural. | The Shift swap check also accepts «تبديل» + «وردية/ورديات/الوردية/الورديات». |
| S34 (S34-1) | Approve: «موافقة» not found | Judge: «يوافق عليه» is the running-text verb the glossary note prescribes, with an attached pronoun. | The Approve check also accepts «يوافق علي» + attached pronoun. |
| S44 (S44-2) | plan: «الباقة» not found | Judge: «باقة» is the approved term in the indefinite form. | The plan check also accepts the indefinite «باقة» and the plural stem «باقات». |
| S50 | Sign in: «تسجيل الدخول» not found | Judge: «سجّل دخوله» is the glossary's running-text verb with a third-person pronoun. | The Sign in check also accepts «سجّل دخول» + any attached pronoun. |
| S39 | number "2" not in the target in digits | Judge: the number is expressed by the dual «ورديتين», the counted form the glossary note prescribes. | The number check accepts the glossary's dual counted form «ورديتين» for the number 2. |
| S08 (gate run 1) | G5: form «موظفي» matches «موظف», which the glossary note for "team member" forbids | Judge: the note forbids «موظف» only as a replacement for 'team member'; the source here says 'Rotalume support staff', and «موظفي الدعم» renders it correctly. | The forbidden-form check for «موظف» does not flag the word when it is directly followed by «الدعم» (support staff). Every other occurrence of «موظف» is still flagged. |

All notes except the last settle step-3 flags that the judge ruled Not a defect; those rules were corrected before gate run 1, and the gate did not raise them again. A correction makes a check more exact; no check was switched off and no segment was skipped.

**Round-2 gate rule notes**

| Segments | What was flagged | Why it is not an error | How the rule was changed |
|---|---|---|---|
| S60 | Nothing was flagged. The closing-line check G9 looked for the word «خيالي». | Ruling R2-S60 replaced «خيالي» with «غير حقيقي», which says in plain words that the product is not real. | G9 accepts «غير حقيقي» as well as «خيالي». It still checks that the line is the last segment, is in Arabic, names Rotalume, keeps both sentences and keeps the italic. |
| S17 | First execution of the new script: Approve, approved term not found | «يوافق على الطلبات» is the running-text verb the glossary note prescribes («يوافق على»). The same flag appeared on the unchanged round-1 file: a fault in the new script, which had copied the round-1 rule only in its form with an attached pronoun. | The Approve check accepts «يوافق على» as well as «يوافق علي» + pronoun. |
| S36 | First execution of the new script: «الدوام» outside «سجل الدوام» | The word stands inside the quoted label «سجل الدوام»; the script had not removed the opening quotation mark before comparing. Same flag on the unchanged round-1 file. | The check removes « before it compares the word in front of «الدوام». |
| S08, S23, S58 | First execution of the new script: Latin text other than the brand and the addresses | The flagged items were "Rotalume." and the email address with the full stop that ends the sentence. Same flags on the unchanged round-1 file. | The check removes a full stop at the end of a Latin item before comparing. |

The last three notes are faults of the script written for round 2. They were corrected before any flag was recorded, as round 1 did with its own script fault at step 3. No check was switched off and no segment was skipped.

**Regression result**

Round 1: 1 changed segment (S16) re-read by the regression agent. The correction does what ruling S16-3 says, nothing else in the segment changed, and no new defect was found. No findings.

Round 2: 6 changed segments (S16, S23, S44, S53, S59, S60) re-read by the regression agent, each with the segment before and after it. Each correction does what its ruling says and nothing else in the segment changed (the script record shows the replaced words: S16 «ومنها» → «ومنه»; S23 «عليك بس تعديل» → «وعدّل بس»; S44 «ولازم اختيار» → «اختر»; S53 «حذف» → «نحذف»; S59 «دور نشر» → «انشر»; S60 «خيالي.» → «غير حقيقي.»). Checked: S16 «ومنه» agrees with «كل شي», and «منها» in S38 is untouched because its antecedent there is feminine; S23 keeps the label «نسخ الأسبوع الماضي» and its bold; S44 keeps {end_date}, «باقة» and «جداولك»; S53 follows S52 («Rotalume يطلب منك التأكيد») and keeps «الوردية»; S59 keeps «نشر» as the verb «انشر» and the one exclamation mark; S60 is still the last segment, in italic, with both sentences. No new defect was found. No findings.

Round 3: No segment changed; nothing to re-read.

## 10. Delivered text

Every segment as read back from the saved final file final/pack-a-gulf-sa-delivered.docx, which is identical to the round-2 file. Segments 16, 23, 44, 53, 59 and 60 differ from the round-1 file; the round-1 wording of each is in the issue log.

<div dir="rtl" lang="ar">

1. مركز المساعدة في Rotalume
2. البداية: أسبوعك الأول بدور مدير
3. حياك الله في Rotalume! هذا الدليل يمشي معك خطوة خطوة في الأساسيات، من تسجيل الدخول إلى نشر أول جدول لك. ياخذ منك حوالي 10 دقائق، وما يحتاج خبرة تقنية.
4. 1\. تسجيل الدخول وإعداد مساحة عملك
5. افتح تطبيق Rotalume على جوالك، أو انتقل إلى app.rotalume.example من الكمبيوتر.
6. اضغط «**تسجيل الدخول**» واكتب رقم جوالك. نرسل لك رسالة نصية تحتوي على رمز التحقق المكوّن من 6 أرقام. تنتهي صلاحية الرمز بعد 5 دقائق.
7. اكتب اسماً لمساحة عملك، ثم اضغط «**إنشاء مساحة العمل**».
8. لا تعطي رمز التحقق لأي أحد، حتى موظفي الدعم في Rotalume. ما راح نطلبه منك أبداً، لا بالاتصال ولا بالبريد الإلكتروني ولا في المحادثة.
9. أول مرة تسجّل دخولك، راح تشوف هذي الرسالة في «لوحة التحكم»:
10. هلا {first_name}! مساحة عملك «{workspace_name}» جاهزة. وش أول شي ودّك فيه؟
11. مو واضح من وين البداية؟ أول شي إضافة فروعك، وكل شي ثاني ينبني عليها.
12. 2\. إضافة الفروع وأعضاء الفريق
13. ادخل على «**الإعدادات > الفروع**» واضغط «**إضافة فرع**». اكتب لكل فرع اسمه وساعات العمل فيه، مثلاً من 7:00 ص إلى 11:30 م.
14. لإضافة أشخاص، افتح «**الفريق**» واضغط «**دعوة عضو للفريق**». اكتب اسم الشخص ورقم جواله، واختر الدور، ثم اضغط «**إرسال الدعوة**». كل عضو فريق جديد توصله رسالة نصية فيها رابط صالح لمدة 48 ساعة.
15. فيه ثلاثة أدوار:
16. «**المالك**»: يقدر يسوي كل شي، ومنه الفوترة. كل مساحة عمل لها «مالك» واحد بس.
17. «**مدير**»: يقدر يبني الجداول ويوافق على الطلبات ويصدّر سجلات الدوام، لكن لفروعه بس.
18. «**عضو الفريق**»: يقدر يشوف وردياته، ويسجّل حضوره ويسجّل انصرافه، ويرسل الطلبات.
19. لما ينضم أحد، يوصل مديره هذا الإشعار:
20. تم قبول دعوتك: {name} الحين ضمن {branch_name}.
21. 3\. إنشاء الجدول ونشره
22. افتح «**الجدول**» واختر الأسبوع. اضغط أي خانة فاضية لإضافة وردية، ثم اختر عضو الفريق ووقت البداية ووقت النهاية. وإذا ما تعرف للحين مين راح يشتغل في الوردية، احفظها كـ«**وردية مفتوحة**». وقتها أعضاء الفريق في هذا الفرع يقدرون ياخذونها بنفسهم.
23. ما عندك وقت؟ اضغط «**نسخ الأسبوع الماضي**» وخلّ الباقي على Rotalume. وعدّل بس اللي تغيّر.
24. فريقك ما يشوف أي شي لين تضغط «**نشر**». بعدها يوصل كل شخص إشعار مثل هذا:
25. ورديات جديدة لك هالأسبوع: %d. أول وردية لك تبدأ بكرة الساعة {start_time}.
26. تقدر تعدّل الوردية المنشورة في أي وقت، إلا إذا عضو الفريق سجّل حضوره. ولتعديل وردية جارية الحين، اطلب من عضو الفريق يسجّل انصرافه أول.
27. الوردية ما تزيد عن 12 ساعة. ويحذّرك Rotalume إذا كانت الراحة بين ورديتين لأي شخص أقل من 8 ساعات.
28. 4\. الطلبات: الإجازة وتبديل الورديات
29. أعضاء الفريق يقدرون يرسلون نوعين من الطلبات من التطبيق:
30. «**إجازة**»: ليوم واحد أو أكثر. لازم ينرسل الطلب قبلها بـ 3 أيام على الأقل.
31. «**تبديل وردية**»: لما يتفق اثنين من أعضاء الفريق على تبادل وردياتهم.
32. تلقاها كلها في «**الطلبات**». افتح الطلب واضغط «**موافقة**» أو «**رفض**». وإذا رفضت، اكتب ملاحظة قصيرة عشان يعرف الشخص السبب.
33. طلب تبديل وردية من {name}: وردية يوم {date} مع {other_name}.
34. التبديل ما يصير ساري إلا بعد ما يوافق عليه مدير، حتى لو كان الاثنين من أعضاء الفريق متفقين من قبل. والطلبات اللي ما أحد يرد عليها خلال 72 ساعة تتحول حالتها إلى «**منتهي الصلاحية**»، ونطلب من عضو الفريق يرسل طلب جديد.
35. 5\. سجل الدوام
36. لما يسجّل أعضاء الفريق حضورهم ويسجّلون انصرافهم من جوالاتهم، Rotalume يسجّل ساعاتهم عنك. في نهاية الشهر، افتح «**سجل الدوام**» وراجع المجاميع، ثم اضغط «**تصدير**» لتنزيل الملف.
37. هذا مثال لسطرين من سجل الدوام لشهر مارس 2027:
38. نورة: 22 وردية، 164.5 ساعة، منها 6.5 ساعات إضافية
39. فهد: ورديتين، 11 ساعة، بدون ساعات إضافية
40. معك لين يوم 5 من الشهر اللي بعده عشان تصحّح سجل الدوام. بعد هذا التاريخ ينقفل السجل، وما يقدر يفتحه إلا «المالك».
41. 6\. الباقات والفوترة
42. Rotalume مجاني لمساحات العمل اللي فيها 5 من أعضاء الفريق أو أقل، وبدون أي شروط مخفية. سعر باقة الفريق 19 ريال لكل عضو فريق في الشهر. الأسعار ما تشمل ضريبة القيمة المضافة (15%).
43. كل مساحة عمل جديدة تبدأ بفترة تجريبية مجانية لمدة 30 يوم على باقة الفريق. ولما تقرّب الفترة التجريبية من نهايتها، يشوف «المالك» هذي الرسالة:
44. فترتك التجريبية المجانية تنتهي يوم {end_date}. اختر باقة عشان تبقى جداولك محفوظة.
45. نرسل فاتورة على بريد «المالك» الإلكتروني يوم 1 من كل شهر. مثلاً، مساحة عمل فيها 14 من أعضاء الفريق تدفع 266.00 ريال قبل ضريبة القيمة المضافة. تقدر تغيّر باقتك أو تلغيها في أي وقت من «**الإعدادات > الباقة**».
46. 7\. حل المشكلات
47. **ما وصلني رمز التحقق.**
48. انتظر 60 ثانية، ثم اضغط «**إعادة إرسال الرمز**». تأكد إن في جوالك شبكة وإنك كتبت الرقم الصحيح. للحين ما وصل شي؟ تواصل معنا ونحلّها لك.
49. **عضو فريق ما يقدر يشوف وردياته.**
50. أول شي، تأكد إنك نشرت الجدول. بعدها تأكد إنه سجّل دخوله بنفس رقم الجوال اللي أرسلت عليه الدعوة.
51. **حذفت وردية بالغلط.**
52. قبل ما تحذف أي شي، Rotalume يطلب منك التأكيد:
53. أكيد نحذف هذي الوردية؟ ما فيه تراجع بعد الحذف.
54. الوردية المحذوفة ما ترجع، لكن تقدر تضيفها من جديد في ثواني.
55. **التطبيق يعرض وقت غلط.**
56. Rotalume يستخدم المنطقة الزمنية لكل فرع، مو المنطقة الزمنية لجوالك. تقدر تغيّرها من «**الإعدادات > الفروع**».
57. للحين ما انحلّت المشكلة؟
58. فريق الدعم عندنا موجود من الأحد إلى الخميس، من 9:00 ص إلى 6:00 م بتوقيت الرياض. في التطبيق، اضغط «**المساعدة > المحادثة معنا**»، أو راسلنا على help@rotalume.example. غالباً نرد عليك على طول في ساعات العمل.
59. بس كذا. كل شي جاهز عندك، والحين انشر أول جدول لك!
60. *Rotalume منتج غير حقيقي. هذا النص مكتوب كمحتوى تجريبي لعرض توضيحي للترجمة.*

</div>

## 11. Corrections to the round-1 report

The delivery review recomputed every number in the round-1 report from the files and found that all of them reconcile (segments, source words, 40 findings, 17 agent reports for 13 rows, the rulings, the 17 agents that ran, the preferences, the new terms and the open questions). No round-1 number was wrong, so none was changed. The following statements were corrected or completed in this version:

1. Job summary, Quality gate: the line "Quality gate: passed" did not say which run passed. It now says that the round-1 file passed on gate run 2 and the round-2 file on gate run 3.
2. Issue counts: a sentence was added saying that the step-3 script matches letters and that all 26 of its flags were inflected forms of approved terms or the glossary dual, not errors.
3. Top patterns: "No pattern" was correct by the rule that counts Defect rulings only, but it hid the one habit in the file. The pattern is now named, on the strength of four round-2 Defect rulings.
4. Five round-1 Preference rulings were wrong in outcome and were re-ruled as Defect in round 2: S16-2, S23, S44-3, S53, S59-2. In S23 and S44-3 the round-1 judge applied the neutral-structure rule outside the scope the style guide gives it; in S53 the judge rejected the proposed correction and left a defect it could have corrected itself; in S16-2 and S59-2 the finding was dismissed because it quoted no written reference.
5. Open question Q8 says that the judge kept S53 «أكيد حذف هذي الوردية؟» on the ground of the neutrality rule. That is what round 1 did. After round 2 the segment reads «أكيد نحذف هذي الوردية؟», which is still neutral; S44 now uses the imperative, and Q22 puts the question to the client.
6. Two items of the delivery review were not followed, and the text stays: S11 «أول شي إضافة فروعك» (ruled Preference, R2-S11) and S22 «مين» (ruled Preference, R2-S22, which the review itself calls defensible). The review's remark on the round-1 fix in S16 («مالك» in quotation marks) was ruled Not a defect (R2-S16-2).
7. Round 2 could not check, from the files it was given, that each round-1 agent received only its listed inputs.
8. Round 3 did not correct anything in the round-1 or round-2 report. One of its findings (R3-06) questioned a round-2 correction, «ومنه الفوترة» in S16, as awkward; the separate judge ruled it a Preference, so the round-2 correction stands. Round 2's own record says the independence of its checks was not assured; round 3 supplied a separate blind read.
