Default language, language switching, RTL direction and Nastaliq shaping — treated as functional behaviour, not cosmetics.
For an Urdu-first product, language is behaviour. If the default language is wrong, the direction does not flip, or Urdu text renders in a font that breaks Nastaliq shaping, the product is broken for its primary audience — even if every button works. The bilingual pack tests language the way the platform tests billing: with deterministic assertions on real pages in a real browser.
The pack's public part executes today on the pilot product. Its authenticated depth — Urdu validation messages inside the app, mixed Urdu/English/number layouts, Urdu PDF exports — is defined as skeletons that stay blocked until TEST-QA credentials exist, and that state is reported honestly rather than passed over.
The login page of the Urdu-first pilot loads with lang=ur, dir=rtl and Urdu UI text, re-verified on every run. The Oct 2026 walkthrough established Urdu as the server-rendered default; this case makes sure it stays that way.
Switching Urdu → English flips the page to LTR with English UI, and switching back restores Urdu RTL — using the page's own language control, exactly as a user would.
The computed font stack of the Urdu page is recorded. The check fails only if Arabic-script text renders with no Arabic-script font anywhere in the stack — shaping quality is observed and evidenced, not guessed.
Urdu validation messages, mixed-content layout without clipping at mobile and desktop sizes, and PDF exports keeping correct Urdu shaping. Blocked until TEST-QA credentials exist. Hijri-date checks from Section 23.3 do not apply to the pilot: it shows no Hijri dates on any observed surface.
| Profile | Status | Reason (from the profile definition) |
|---|---|---|
| POS / Retail | Attached | The product is Urdu-first (Urdu is the server-rendered default; English, Pashto-draft and Persian-draft also offered). The pack's public part (default language, switching, font) is executable now (BI-DUK-01..03); authenticated depth is PROPOSED. |
| Madrasah / Masjid / Maktab | Attached | Urdu/English bilingual UI is a core module of this category (Section 22). The pack applies in full, including Urdu PDF shaping and Urdu-content import checks. |
Automated language checks verify language attributes, direction, text presence and font stacks. They do not certify translation quality — a human still reads the Urdu. The platform's own client reports are produced in English and Urdu, and the pack's PDF checks exist because Urdu shaping in generated PDFs is exactly where bilingual products most often break silently.
Pack checks run under the platform's standing safety rules: TEST-QA accounts and TEST-QA-marked data only, no real payments, credentials only through the secret store, and every result — pass, fail, blocked or needs-review — reported as it actually is. Read how the resulting evidence becomes a readiness score and coverage figure.
