The next language milestone should not be framed as cosmetic localization. It is part of PLENA’s trust moat: consent, identity, proof packets, institutional accountability, and appeal rights cannot depend on unstable machine translation.
When a user signs, accepts, appeals, submits, or shares a proof packet, comprehension is part of consent.
Buttons, warnings, consent text, and irreversible actions must be native-dictionary controlled.
Credential, country, institution, and identity labels must preserve meaning across scripts and languages.
Human review receipts must be understandable to the person affected and the institution reviewing them.
Deadlines, appeal routes, missing-items warnings, and evidence requests must not be machine-translation guesses.
The checklist is strict because PlenaProof is becoming a trust-and-proof system, not a decorative website.
| Audit area | Pass condition | Why it matters |
|---|---|---|
| Native dictionary runtime | No Google Translate dependency, no widget loaders, no hidden machine-translation fallbacks. | Proof and consent must remain stable. |
| Critical controls | Submit, approve, reject, appeal, download, verify, consent, delete, and payment-related labels localized natively. | Users must understand consequential actions. |
| Wallet and receipts | Wallet identity, receipt timeline, QR profile, verification status, and proof packet labels localized. | The wallet becomes lifetime proof identity. |
| Institutional surfaces | Command Center, Trust Center, Academy, sector suites, procurement, and readiness pages localized. | Institutions need defensible multilingual deployment. |
| East African languages | Kiswahili, Ikirundi, and Ikinyarwanda checked for visible UI coverage, not only language-bar presence. | Strategic regional credibility and inclusion. |
| RTL and script handling | Arabic and Farsi direction, alignment, and fonts stable without dancing or layout collapse. | Proof workflows must stay usable across scripts. |
| Dynamic content | MutationObserver or equivalent catches generated panels, modals, cards, and result previews. | Important proof text often appears after user action. |
| Regression test | Language switch survives navigation across homepage, wallet, verify, AI oversight, sector suites, and all 14 platforms. | Language must travel with the proof journey. |
Strategic framing for the next milestone: “PLENA makes trusted proof accessible in people’s own languages.” This is stronger than “multilingual support” because it connects language to proof, consent, identity, appeal, and institutional accountability.