Files
jobtrackingapp/docs/i18n/00/RISKS_AND_APPROVALS.md
T

2.9 KiB

Risks, blockers and independent approval

ID Risk / unresolved item Owner and closure evidence
I00-01 Catalogue scan is not every-string contextual inventory UI/backend owners triage literals, all callers, runtime/ARIA/export states; no unknown required surface
I00-02 CLDR is not complete national/regional legal authority Product research owner checks official country records, political/territory scope and versioned licence before activating suggestions
I00-03 No allocated translators/native reviewers Product owner assigns named reviewers per locale/surface; critical legal/billing/security needs qualified review
I00-04 Implementation predecessor gates unresolved Owner records Phase10/product review and explicit I18N entry against accepted baseline; this document cannot approve them
I00-05 Plurals, gender, inflection, word order ICU whole-sentence contexts, Slavic/Irish/Welsh fixtures, native review; no fragment concatenation
I00-06 Turkish casing, Greek accents, Serbian script, names Locale-aware search/display separate from invariant IDs; preserve original names and qualification titles
I00-07 Dates/timezones/DST, salary/currency UTC storage, partial-date precision, explicit timezone; formatting never FX conversion
I00-08 Fonts/glyphs, RTL readiness, long labels Licensed extended Latin/Greek/Cyrillic font tests, logical layout and focus; RTL activation only when approved
I00-09 Career fact loss, frozen PDF drift, stale writes UI switch never mutates facts/history/undo; ApplicationAssetsService and revision contracts retained
I00-10 Private content external translation No PII export; separately approved consent/contracts/data controls before external translation; no live-model calls
I00-11 Draft locale exposed as supported Per-surface publication gate, English fallback; no selector/SEO claims from catalogue presence
I00-12 Backend literal errors and queue drift Stable error codes, typed escaped params, deterministic event-time locale and retry tests

Public release requires required-key completeness, syntax/placeholders/plurals and escaping checks, whole critical journeys, native/proficient review, accessibility/device/PDF tests, country/provider truthfulness, owner release decision and actual deployed identity. Status advances separately per surface: planned → draft/machine_draft → review_required → reviewed → qa_passed → release_approved → released. No generated JSON grants review or approval. Approval evidence must be externally controlled and source-bound. All catalogue entries here are planned; existing en/nb code presence is independently recorded, not relabelled as newly qualified release.

Human/native/legal/device/physical-print review: pending, not executed. Provider and live-model tests: not run. Implementation/release: not authorised. Independent planning can continue on I00-01/02 without waiting for runtime gates.