Use the closest source
Start with the ministry, regulator, central bank or operator responsible for the question, then record the page and review date.
Open the source boardRoute 02 / expose the conditions
Turn context into acceptance checks.
“Built for Lebanon” is not a useful requirement by itself. A responsible brief identifies exactly who will use the system, which languages and devices matter, which dependencies are controlled by others and what should happen when the expected path is not available.
Operating questions
Six things to settle with the real team.
Do not infer these answers from a country label. Verify them with the organisation and record who owns each decision. Official sources can frame the questions; they cannot describe a particular buyer's operation.
- Users and languageWhich roles use Arabic, French or English? Who approves terminology? Does any interface need right-to-left layout, bidirectional text or mixed-script testing?
- Devices and bandwidthWhich devices and connections are actually used? Define a meaningful performance budget, offline or retry behaviour and a low-bandwidth path where the workflow requires it. Ogero's published service information is a planning input, not proof of a user's connection.
- Identity and addressesCapture the address, phone, name and organisation formats found in real records. Decide how +961 and international numbers, districts, free text and duplicate identities are handled.
- Access and ownershipName the owner of domains, hosting, source code, analytics, provider accounts and recovery methods. Avoid a release that depends on one unavailable person's credentials.
- Time and approvalsRecheck current time-zone offsets and working windows when the project starts. Decide which feedback can be asynchronous and which release actions need a live overlap.
- Fallback and supportDefine what users see when an integration, payment, message or connection fails. Assign retry, escalation, reconciliation and manual completion paths.
Evidence before assumptions
Country-aware does not mean country-stereotyped.
Lebanon's Investment Development Authority publishes an ICT sector overview, and Ogero publishes consumer and enterprise connectivity services. Those sources show where to ask better questions. The project still needs current evidence for its exact audience, vendor, location and date.
Test the real workflow
Interview the people who perform the task. Record exceptions, workarounds and what they do when the normal path fails.
Convert the finding
A useful fact becomes a test: supported language, error recovery, performance threshold, access rule, review owner or release condition.
The official-source board was reviewed while this planning resource was prepared. Requirements and service details can change; recheck them for the actual engagement rather than treating this page as a permanent rulebook.