[NetworkTheoryAppliedResearchInstitute]

P2-002 standard-set coverage

Adds missing translations so these documents meet the seven-language standard (P2-002 §2.1, Article X).

Document	Category	Languages added	Source commit
README.md	Program README	es, hi, zh, pt, ar, fr, tok	9bfd5b7e

Review status

Machine-assisted community drafts. Each was independently machine-reviewed against the English source and checked for structure (headings, tables, code, links). Not yet reviewed by a regional maintainer (P2-002 §2.3, §3.1) — each file's header says so.

Reviewer notes (points a regional maintainer should check):

README.ar.md (2)

• Glossary C:\Users\Jodson Graves\AppData\Local\Temp\ntari-l10n\2026-10-05\repos\agrinet-docs\tools\translations\terminology-glossary.csv only holds a placeholder row (example-term), so no Arabic terms could be checked against it. The regional maintainer should confirm the chosen terms: بيانات الاعتماد (credentials), عمليات نشر المعاينة (preview deployments), زرّ تشغيل على شكل حبّة (pill trigger), النافذة المنبثقة (modal).
• The English comments inside the bash code block are kept verbatim as code, which is consistent with the rule to keep code verbatim. The maintainer may decide whether code comments should be translated in future.

README.es.md (4)

• The project glossary (tools/translations/terminology-glossary.csv) only holds a placeholder row, so I could check terminology only against the Janus and Cloudy references. A regional maintainer should confirm the choices for 'build' (Compilación), 'deployment' (Despliegue), 'preview deployments' (despliegues de vista previa) and 'pill trigger' (activador en forma de píldora).
• The comments inside the bash code block (e.g. '# Search-only API key', '# Optional Ask AI configuration') and the placeholder '' were left in English. That follows the rule to keep code verbatim, but the maintainer may want to localize the comments.
• The translation addresses the reader as 'tú' (Si usas, Crea, puedes), which matches the house header ('¿Encontraste...?'). The maintainer should confirm this register suits the target region.
• Everything checked passed: all source sentences are present with the same meaning, nothing was added or cut, and the header matches the house header (README.md, 2026-10-05, https://github.com/NTARI-RAND/agrinet-docs). The l10n_inventory check returned ok with no warnings, and the file is UTF-8 with LF line endings and no BOM.

README.fr.md (2)

• The placeholder <Your GitHub username> and the English comments inside the bash code blocks (for example # Search-only API key) are left in English, because code must stay verbatim. A regional maintainer may want to decide whether the house style allows translating placeholders or comments inside code blocks.
• The glossary file tools/translations/terminology-glossary.csv has only its header row (key,en,notes) and no French entries, so terminology could only be checked against the Janus reference and general usage. 'Build' was translated as 'Construction' and 'credentials' as 'identifiants'. Both are standard, but a maintainer should confirm them.

README.hi.md (3)

• Glossary C:\Users\Jodson Graves\AppData\Local\Temp\ntari-l10n\2026-10-05\repos\agrinet-docs\tools\translations\terminology-glossary.csv contains only a placeholder row (example-term), so terminology could be checked only against the Janus reference, which shares no terms with this README. A regional maintainer should confirm the loanword choices: इंस्टॉलेशन, बिल्ड, डिप्लॉयमेंट, क्रेडेंशियल, पिल (pill) ट्रिगर, मोडल.
• Minor wording inconsistency, left as is: 'Local Development' is translated as 'स्थानीय विकास' in the heading and on line 52, but line 24 uses 'स्थानीय डेवलपमेंट सर्वर'. Using the loanword for 'development server' reads naturally, but a maintainer may prefer one form throughout.
• Checks passed with nothing to fix. The house header matches the Cloudy reference, with README.md, snapshot date 2026-10-05 and https://github.com/NTARI-RAND/agrinet-docs. Every source sentence is present with the same meaning, and no normative MUST/SHOULD/MAY terms appear. All 6 code blocks, the identifiers and the URLs are verbatim. The l10n_inventory check returned ok with no warnings. The file is UTF-8 with LF line endings and no BOM.

README.pt.md (5)

• The heading 'Build' is left in English. This is a common loanword in Brazilian Portuguese tech writing; a regional maintainer may prefer 'Compilação' or 'Geração do site'.
• 'aplicação DocSearch' uses 'aplicação' rather than 'aplicativo'. Both are used in Brazilian developer writing; the maintainer should confirm the house preference.
• The comments inside the bash code blocks and the placeholder '' are kept verbatim in English as code. This is correct under the verbatim-code rule, but readers will see English text there.
• The glossary (tools/translations/terminology-glossary.csv) has no entries that apply here: it holds only a header row (key,en,notes) and no Portuguese column. Terminology was checked against the Janus reference instead, and 'implantação' is consistent with it.
• Checks passed: the header matches the Cloudy house header (source README.md, snapshot 2026-10-05, URL https://github.com/NTARI-RAND/agrinet-docs); every source sentence is present with the same meaning; l10n_inventory check returned ok with no warnings; the file is UTF-8 with LF line endings and no BOM.

README.tok.md (6)

• Every source sentence is present with the same meaning. The header matches the Cloudy house header (README.md, 2026-10-05, https://github.com/NTARI-RAND/agrinet-docs). The l10n_inventory check passed with no warnings. The file is UTF-8, LF line endings, no BOM. Code blocks, identifiers and URLs are verbatim.
• Vocabulary is all pu plus nimi ku suli ('linluwi' and 'kipisi' are ku suli). No invented words were found, so no §1.4 referral was needed.
• For the maintainer: line 31 renders 'Most changes' as 'ante mute', which means 'many changes'. The meaning loss is small.
• For the maintainer: 'branch' (gh-pages) is rendered as 'linja', and 'preview deployments' as 'lipu lukin pi tenpo lili'. Both are reasonable, but a maintainer may prefer other wording.
• For the maintainer: 'credentials' is rendered as 'sona open' throughout and 'command' as 'toki wawa'. These are consistent, but they are not in the terminology glossary, which still holds only a placeholder row. Consider adding them.
• For the maintainer: the house header calls this a 'condensed community rendering', but this translation is full, not condensed. The wording follows the house template and was left unchanged.

🤖 Generated with Claude Code