| Decision area | What the project must name | Evidence before release |
|---|---|---|
| Audience | The exact Czechia-facing user and the job they need to complete | Approved journey, content owner, device assumptions, and accessible fallback |
| Language | Whether Czech copy is required and who performs qualified review | Reviewed interface text, diacritics, errors, emails, documents, and support wording |
| Data | Purpose, minimum fields, controller and processor roles, vendors, transfers, retention, and incident owner | Current notices, permissions, vendor record, deletion path, and tested response procedure |
| Commerce | Seller, customer, service class, CZK or other display and contract currency, settlement, invoice, tax adviser, and refund owner | Approved provider route, test transactions, reconciliation, failure messages, and accounting handoff |
| Identity | Which names, addresses, company data, or identifiers are truly necessary | Validated fields, format handling, least access, and a correction path |
| Timing | Czechia is normally six hours ahead of Georgia; daylight changes and project calendars still need checking | Named decision window, release window, incident contact, and asynchronous handoff |
| Acceptance | Who can approve content, technical behavior, privacy, commercial logic, and launch | A signed decision record, live checks, recovery proof, and owner-ready documentation |
Localization is a system behavior.
A Czechia-facing experience may need more than translated headings. Test Czech characters in search, sorting, exports, emails, generated documents, and database round trips. Confirm date, decimal, and currency display with the real audience. Do not add address, company, data-box, or identity fields merely because another product uses them. Every field should have a purpose and owner.
Vendor availability is part of architecture.
Hosting, payment, identity, maps, messaging, analytics, and AI providers can impose country, account, currency, or data conditions. Verify the client’s actual accounts and proposed service before designing around a logo on a vendor page. Record what happens if a dependency is unavailable or changes policy.
Decision discipline: a source link or research note creates a question and may shape a technical control. It does not by itself establish legal applicability, tax treatment, or permission to operate.