| Board column | What to establish | What to test |
|---|---|---|
| Mobile journey | Primary device and browser context, slower connections, interrupted sessions, uploads, and fallback | Complete task on representative screens and network conditions |
| Vietnamese content | Qualified owner for wording, diacritics, names, provinces, labels, errors, messages, documents, and support | Input, storage, search, display, export, notification, and generated-record round trips |
| VND context | Display, quotation, contract, provider charge, settlement, refund, tax and invoice owner, and accounting handoff | Rounding, status, receipt or record, fulfilment, failure, and reconciliation |
| Data and security | Personal and important data, consent, sensitive information, processors, locations, remote access, transfers, impact or filing questions, retention, security, and incidents | Approved controls in the real flow; no unreviewed production data in tools |
| Providers | Client-owned hosting, domain, messaging, identity, payments, maps, analytics, AI, monitoring, and support accounts | Availability, policy, delivery, error, ownership, and replacement behavior |
| Shift ownership | Vietnam is eleven or twelve hours ahead of Georgia; current offset, calendars, decision windows, release and incident owners | Written handoff can be resumed without hidden context |
Country relevance must become operational evidence.
Vietnamese diacritics matter when they survive the database, search, export, and email. VND matters when the display and underlying records agree. A data rule matters when it changes a field, permission, vendor, retention job, incident route, or release gate. A time difference matters when the next shift has enough context to act.
Official sources begin a review; they do not finish it.
Ministry, government, tax, banking, and internet-security material should be dated and attached to a precise question. The client and qualified advisers decide applicability. Faith Forge Labs records the technical effect and keeps unresolved items out of the release.
Enhanced-regulatory boundary: new data, cross-border access, hosting, content, licensing, payment, AI, cybersecurity, or end-use facts may require a fresh review and can block a planned feature.