P2-002: add missing translations (7 files)

[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
CONFORMANCE.md	Specification	es, hi, zh, pt, ar, fr, tok	8f0591e

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):

CONFORMANCE.ar.md (4)

• 'Registry' (the Janus invariant registry) is translated as 'سجلّ القيد'. The record layer is translated as 'السجل', so readers may mix the two up. A regional maintainer may prefer a clearer term such as 'السجلّ المرجعي'. The glossary and the Janus reference have no entry for this term.
• 'Unsigned integers' is translated as 'الأعداد الصحيحة غير المؤشَّرة'. That is accurate, but 'عديمة الإشارة' is also common, so the maintainer may want to choose one.
• In the bullet text, the enrollment lifecycle steps are in Arabic. In the table they stay in English (apply → keys → verify → conformance → active), exactly as in the source table. This is acceptable, but the maintainer should confirm the mix is intended.
• Checks passed with no changes needed: every source sentence, number, date and normative statement is present. The header matches the house header (source CONFORMANCE.md, snapshot 2026-10-05, https://github.com/NTARI-RAND/Cloudy). The spec precedence notice is present and the normative keywords are in English. Terms match the Janus reference (العمارة ذات الوجهين, الركيزة, المشاع, العهد). l10n_inventory check returned ok with no warnings, both before and after the edits. The file is UTF-8 with LF line endings and no BOM.

CONFORMANCE.es.md (6)

• The terminology glossary (agrinet-docs/tools/translations/terminology-glossary.csv) is still a placeholder with only an example row, so terms were matched against the Janus and lighthouse references and the sibling CONFORMANCE.es.md files instead.
• Term choices a regional maintainer should confirm: 'suplencia' for stand-in, 'costura' for seam, 'nodo aprovechado' for scavenged node, 'ejecutores interrumpibles' for preemptible executors, 'brecha de vivacidad' for liveness gap, 'piso esteganográfico' for steganographic floor, and 'bifurcable/bifurcabilidad' for forkable/forkability.
• The precedence notice is a separate blockquote under the house header. The lighthouse-seed header reference has no such notice because it is not a spec. The rest of the header matches: CONFORMANCE.md, snapshot 2026-10-05, URL https://github.com/NTARI-RAND/Cloudy.
• The L6 row says 'falla la verificación de consistencia' where the source says 'fails consistency'. This adds a word but keeps the meaning; left as is.
• The source file uses CRLF line endings; the translation uses LF as required. No BOM. The structural check passes: ok=true, no warnings, before and after the edits.
• All sentences, numbers (7-key set, open problem 2, suites A/B/C), the normative keywords left in English, code, identifiers and URLs were checked against the source and match.

CONFORMANCE.fr.md (3)

• Points for the regional maintainer to decide (my judgement calls, not errors): 'scavenged node' -> 'nœud récupéré', 'Executor seam' -> 'jointure Executor', 'Live federation' -> 'fédération en conditions réelles', 'keystone build' -> 'construction clé de voûte'. Each could have a more idiomatic French equivalent.
• The terminology glossary CSV holds only a placeholder row (example-term), so the terms were checked against janus-facing-architecture.fr.md and lighthouse-seed.fr.md instead. These match: frontend, pacte, registre, empreintes, séquestre, attesté par témoins, substitution.
• Everything else checked out. Header matches the house French header (CONFORMANCE.md, 2026-10-05, https://github.com/NTARI-RAND/Cloudy). The spec precedence notice is present. The l10n_inventory check returns ok with no warnings. The file is UTF-8 with LF line endings and no BOM. Every source sentence, table row, number, identifier and code span is present and unchanged. The source has no MUST/SHOULD/MAY keywords to preserve.

CONFORMANCE.hi.md (5)

• The title line uses 'द्विमुखी संरचना — Janus-Facing Architecture (JFA)', a Hindi gloss that is not in the English source. I kept it because the Janus Hindi reference uses that term, but a regional maintainer should confirm it.
• Some technical words are written in Hindi script instead of being translated, for example 'वायर (wire)', 'सीम (seam)', 'स्कैवेंज्ड', 'प्रीएम्प्टिबल' and 'कैनन'. This is consistent with the reference, but a maintainer may want to check that it reads naturally.
• 'speaks the published protocol' is translated word for word as 'प्रकाशित प्रोटोकॉल बोलता है' (literally 'speaks'). The meaning is correct, but a maintainer may want something more idiomatic.
• In the enrollment bullet (line 62), the onboarding steps (apply → register ...) are in Hindi. In the role table (line 26) the same kind of step list stays in English, matching the source table. Both are acceptable, but a maintainer may want them made the same.
• Checks with no problems: the header matches the lighthouse house header (CONFORMANCE.md, 2026-10-05, https://github.com/NTARI-RAND/Cloudy). The precedence notice is present and normative keywords stay in English. l10n_inventory check returned ok with no warnings. The file is UTF-8 with LF line endings and no BOM. Every source sentence, number, identifier and code span is present.

CONFORMANCE.pt.md (4)

• Line 50, L6 row: 'dismissal is annotation' is translated as 'o arquivamento é anotação'. 'Arquivamento' has a legal, case-closing sense. A regional maintainer should confirm whether 'dispensa' or 'descarte' fits the covenant meaning better.
• Line 39: 'escrow-first' is translated as 'custódia em primeiro lugar'. This is acceptable, but a maintainer may want 'garantia (escrow) em primeiro lugar' so the escrow sense is explicit.
• Line 60: 'lands behind this seam' moved from present to future tense ('será integrada'). The meaning is the same, so this was left as is.
• Header follows the lighthouse house header exactly: source CONFORMANCE.md, snapshot date 2026-10-05, and the Cloudy repository URL. The spec precedence notice is present, and normative keywords, identifiers, code and URLs are kept verbatim. The structure check returned ok with no warnings, and the file is UTF-8, LF line endings, no BOM. Terminology matches the Janus reference: Arquitetura de Dupla Face, somente de adição, pacto, frontend, substrato. The glossary CSV contains only a header row, so there was nothing to check against it.

CONFORMANCE.tok.md (7)

• Words: every word is pu or nimi ku suli (kipisi, leko, meso, jasima). I scanned for anything else and found no invented words, so no §1.4 referrals were needed.
• Structure: l10n_inventory check returns ok with no warnings, both before and after the edits. The file is UTF-8 with LF line endings and no BOM.
• Header: matches the house header in lighthouse-seed.tok.md. It uses 'lipu pi kulupu' and an English note without 'condensed', which is right because this is a full rendering. Source CONFORMANCE.md, snapshot 2026-10-05 and URL https://github.com/NTARI-RAND/Cloudy are all present. The spec precedence notice is present, with MUST/SHOULD/MAY kept in English.
• Maintainer note: some coined phrases are used consistently but are not in the glossary, which has no tok entries. coordinator = 'ilo insa'; coordination protocol = 'nasin insa'; substrate = 'kipisi ilo'; operator = 'jan pi ilo suli'; front end = 'lupa lukin'; covenant = 'toki awen'. The Janus reference does not settle these terms, so a regional maintainer should confirm them and add them to the glossary.
• Maintainer note: status values (Built, Stub, labeled, Built (stand-in), Design-binding) and the term 'Member' in the role table are kept in English, each with a toki pona gloss. This is acceptable as identifier-like labels, but a maintainer may prefer full rendering.
• Maintainer note: 'before any durable persistence' is rendered as 'lon tenpo ni: awen suli li lon ala' ('at a time when durable persistence does not exist'). The meaning matches, but it is less explicit than 'before'.
• Maintainer note: the architecture name 'Janus-Facing Architecture' is kept in English in the title and in paragraph 2 as a proper name, and 'nasin JFA' is used elsewhere.

🤖 Generated with Claude Code