P2-002: add missing translations (14 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	e37d39d
SPEC.md	Specification	es, hi, zh, pt, ar, fr, tok	10868fa

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

• Fidelity: I compared every source sentence and table row. Nothing is missing or added. Numbers (open problems 2, 6, 7; v0/v1; SPEC §1) and the MUST NOT / MAY keywords are unchanged.
• Header: matches the house header pattern from lighthouse-seed.ar.md. It has source CONFORMANCE.md, snapshot 2026-10-05 and URL https://github.com/NTARI-RAND/sohocloud-protocol. The spec precedence notice is present, and the normative keywords stay in English.
• Structure: l10n_inventory.py check returned ok with no warnings, both before and after the fix. The file is UTF-8 with LF line endings and no BOM.
• Note for the regional maintainer: 'canonical' is translated as 'قانوني (canonical)' (rows for identity binding and encoding). This is the usual mathematical sense, but a reader may first take it as 'legal'. The English is kept in parentheses. Consider 'قياسي' if regional usage prefers it.
• Note for the regional maintainer: 'employment claims' is translated as 'ادّعاءات التشغيل'. This matches how lighthouse-seed.ar.md renders 'employment' (an employment occurring = تشغيلًا ما حدث), so it is consistent. Please confirm the term.
• Note: the terminology glossary CSV (agrinet-docs/tools/translations/terminology-glossary.csv) has a header row only, so I checked terms against janus-facing-architecture.ar.md and lighthouse-seed.ar.md instead. These terms are consistent with them: المنسّق, ركيزة, الواجهة الأمامية, العهد, الترسية, بديل مؤقت, المسألة المفتوحة.
• Note: normative keywords sit inside Arabic sentences ('الواجهة الأمامية MAY أن تشغّل', 'وMUST NOT أن تنتقل'). This follows the precedence notice, but the right-to-left rendering should be checked visually on GitHub.

CONFORMANCE.es.md (3)

• Literal renderings a regional maintainer may want to adjust: 'afirmaciones de empleo' (source: 'employment claims'), 'residuos abiertos' ('open residuals'), 'verdad de referencia' ('ground truth'), 'existen dos consumidores contra la etiqueta publicada' ('two consumers exist against the published tag')
• 'golden vectors' is translated as 'vectores de referencia', and 'dependency leaf' as 'hoja de dependencias'. Both are consistent within this file, but the glossary CSV holds only a placeholder row, so they could not be checked against approved terms
• 'stub' and 'escrow' are kept in English ('escrow' with a Spanish gloss). This is reasonable but should be confirmed against house style

CONFORMANCE.fr.md (3)

• 'employment claims' (anchor/ bullet) and 'work claim' (JobReport row) are both rendered 'déclarations de travail'; the source uses two different terms. A regional maintainer should confirm whether JFA treats them as the same thing or whether 'déclarations d'emploi' is wanted.
• 'v0 is UNSTABLE' keeps UNSTABLE in English capitals, as in the source. This is defensible as a label, but the maintainer should confirm.
• The terminology glossary CSV holds only a placeholder row, and the Janus French reference uses few of the terms in this file. So the choices for pluggable ('interchangeable'), stand-in ('substitution'), golden vectors ('vecteurs de référence') and on the wire ('sur le fil') are checked against the lighthouse reference and general usage only.

CONFORMANCE.hi.md (3)

• The sibling file SoHoLINK/CONFORMANCE.hi.md also uses 'अपरिहार्य होस्टिंग अवरोध-बिंदु' for 'unremovable hosting chokepoint'. I did not touch it because it is outside my scope. A maintainer should pick one rendering for all repos.
• Term choices for a regional maintainer to confirm: 'architecture' is translated as 'संरचना', following the Janus reference (lighthouse-seed.hi.md uses 'आर्किटेक्चर'). 'invariant' is translated as 'अपरिवर्तनीय नियम (invariants)' (lighthouse uses 'इनवेरिएंट'). 'coordinator' is transliterated as 'कोऑर्डिनेटर' (Janus uses 'समन्वयक' once). The terminology glossary CSV has only a header row, so it gives no guidance on any of these.
• No issues found in the header, the spec precedence notice or the structure. The l10n_inventory check returned ok with no warnings, both before and after my edits. The file is UTF-8 with LF line endings and no BOM.

CONFORMANCE.pt.md (3)

• Line 46: 'alegações de emprego' is a literal rendering of 'employment claims'. Here 'employment' means compute being put to work (job in, result out, meter). A regional maintainer should confirm the wording, or choose something like 'alegações de execução de trabalho'.
• Line 13: the gloss '(Arquitetura de Dupla Face)' after Janus-Facing Architecture is not in the source. It is a short explanation, but the reference files do not use it consistently, so a maintainer should decide whether to keep it.
• 'wire' is translated as 'comunicação (wire)' / 'linguagem de comunicação (wire)'. That meaning is correct, but the term has no glossary entry, so a maintainer may want to add one.

CONFORMANCE.tok.md (6)

• Checks run: l10n_inventory.py check passes before and after the fixes (ok, no warnings). The file is UTF-8 with LF line endings and no BOM. Every word outside code, quotes and bracketed English glosses is from pu or nimi ku suli (kipisi). No invented words were found, so no section 1.4 referrals were needed.
• Header: matches the lighthouse house template. It says 'lipu pi kulupu' instead of 'lipu lili pi kulupu' and drops 'condensed', which is correct because this rendering is full, not condensed. The filename, snapshot date 2026-10-05, repository URL and English precedence notice with normative keywords in English are all present. A maintainer may want to add the line 'Core technical specifications remain in English per section 2.2', which the Janus reference header includes.
• Stand-ins, sovereign compute: 'tomo ilo li ken ala kama lon ma wan mute' renders 'caps how concentrated hosting can become' only loosely. A regional maintainer should confirm the wording.
• Some English glosses in brackets ('dependency leaf', 'type surface', 'golden vectors', 'build', 'stand-in') are added as terminology aids. They do not change meaning, but the maintainer should confirm this follows house style.
• 'lipu lili pi ijo wile ala' for 'dependency leaf' plays on 'lipu' meaning leaf. It is understandable with the English gloss, but the maintainer should confirm it as the standard term.
• 'UNSTABLE' is kept in English with the gloss '(awen ala)'. It is not one of the normative keywords, so keeping it in English is a style choice for the maintainer.

CONFORMANCE.zh.md (3)

• Two reference files name the architecture differently. This translation follows lighthouse-seed.zh.md and uses '雅努斯双面架构'. janus-facing-architecture.zh.md uses '双面架构'. A regional maintainer should pick one name for all repos.
• Several term choices need a native-speaker check: 'legibility' as '可理解性', 'stand-in' as '暂代', 'chokepoint' as '咽喉点' (the Janus reference uses '咽喉要道'), 'covenant' as '约定' and 'golden vectors' as '黄金向量'.
• 'employment claims' is translated as '雇佣主张'. This matches sohocloud-protocol/SPEC.zh.md, but the maintainer may prefer a word that fits compute jobs better, such as '作业主张'.

SPEC.ar.md (4)

• Arrows in the §3 worked examples (LEB128 '300', int64 '-1'/'-2'/MinInt64) were changed from → to ← so they point along the right-to-left reading order. The meaning is kept, but the symbol differs from the source; the arrows inside the §6 table were left as →. A regional maintainer should confirm this convention.
• Term choices to confirm: 'escrow' is rendered as 'ضمانًا (escrow)', which could be 'حساب ضمان'; test 'fixture' is rendered as 'أداة المطابقة'; 'narrow waist' is rendered literally as 'الخصر (waist)'; 'payout' is rendered as 'الدفع'.
• The terminology glossary CSV holds only a placeholder row, so there was no glossary to check against. Terms were checked against janus-facing-architecture.ar.md and lighthouse-seed.ar.md instead (المنسّق, الركيزة, الحَكامة and ترسية all match).
• Checks that passed: the header matches the house header (SPEC.md, snapshot date 2026-10-05, URL https://github.com/NTARI-RAND/sohocloud-protocol); the spec precedence notice is present; normative keywords are in English; numbers, code blocks and identifiers are verbatim; l10n_inventory check returned ok with no warnings; the file is UTF-8 with LF line endings and no BOM.

SPEC.es.md (3)

• The 'Domain tag:', 'Domain tag (response):', 'Order:' and 'Response Order:' labels, and the Order-clause type notes (e.g. 'int64 UTC Unix nanoseconds' in §11.1/§11.2), are left in English. I left them because the text cites Order: as an identifier, but a regional maintainer should confirm that 'Domain tag:' should stay in English too.
• The terminology glossary (agrinet-docs/tools/translations/terminology-glossary.csv) holds only a placeholder row, so I checked terms against the Janus reference alone (sustrato, pacto, testigo, frontend, cable all match). A maintainer may want to confirm several choices that reference doesn't cover: 'anuncio' for listing, 'arrendamiento' for lease, 'fragmento' for shard, 'medición' for metering, 'posibilidad de abandono' for leaveability, 'canal externo' for out of band, and 'fixture' / 'dispositivo de conformidad' for the test fixture.
• The register changes inside the document: §10.2 steps use infinitives, while the sentences around them address the reader as 'tú' (tus, Observa, usa). This is natural Spanish but worth a maintainer's look for house style.

SPEC.fr.md (5)

• §5.4 heading: 'not a hub' is translated as 'non un pivot'. This deliberately avoids the NTARI/Lighthouse sense of 'hub' (civic institution). A regional maintainer should confirm 'pivot' (or 'plaque tournante') is the preferred term.
• 'Order:' labels outside code spans use French spacing ('Order :'), while in-text references keep the backticked Order:. The English label is kept, but the maintainer may want 'Order:' verbatim everywhere for consistency.
• §8 headings change 'docs(i18n): community translations in seven languages (P2-002) #7/docs: JFA conformance self-description + dependency-leaf CI #6/ci: Go build/vet/test + Python conformance gate #4' to 'n° 7/n° 6/n° 4' (French typography). The meaning is unchanged.
• §6 table: direction values 'node → coord' are kept in English, but 'anyone' is translated as 'quiconque'. Mixed, though acceptable. The column padding on that row is slightly off; this does not affect rendering.
• The translation was checked in full against the source. All sentences are present, and every number, code block, identifier, URL and MUST/SHOULD/MAY keyword is unchanged. The header matches the house template: SPEC.md, 2026-10-05, https://github.com/NTARI-RAND/sohocloud-protocol. The precedence notice is present. l10n_inventory check reports ok with no warnings. The file is UTF-8, LF line endings, no BOM.

SPEC.hi.md (4)

• Terminology: the 'coordinator' role is transliterated as 'कोऑर्डिनेटर' throughout. The Janus JFA reference uses 'समन्वयक' for its coordinator role. This was left as is because here Coordinator is also a protocol interface name, but a regional maintainer should decide whether to align it with the reference.
• The glossary CSV (agrinet-docs/tools/translations/terminology-glossary.csv) has only a placeholder row, so terminology could only be checked against the Janus and Lighthouse Hindi translations.
• In a few places English emphasis words are kept with a Hindi gloss, for example 'NOT', 'ONLY (एकमात्र)', 'BOTH (दोनों)', 'EXCEPT (छोड़कर)' and 'ON TOP (ऊपर)'. This keeps the source's emphasis and normative keywords, but it reads a little unnaturally; the maintainer may want a uniform convention.
• Fidelity, numbers, dates, MUST/SHOULD/MAY force, code blocks, tables and identifiers were all checked and match the source. The header matches the house header (SPEC.md, snapshot 2026-10-05, https://github.com/NTARI-RAND/sohocloud-protocol) and the precedence notice is present. l10n_inventory.py check returns ok with no warnings. The file is UTF-8 with LF line endings and no BOM.

SPEC.pt.md (4)

• The header block matches the house reference: SPEC.md, snapshot 2026-10-05, https://github.com/NTARI-RAND/sohocloud-protocol. The spec precedence notice is present and the normative keywords are in English, including MUST NEVER in §11.0 rule 1, as in the source.
• l10n_inventory.py check returns ok with no warnings, both before and after the edits. The file is UTF-8 with LF line endings and no BOM.
• Term choices for a regional maintainer to confirm: 'pareamento/parear' for matching, 'listagem' for listing, 'consultivo' for advisory, 'recusa (opt-out)', 'locação (lease)', 'fixture', 'possibilidade de saída (leaveability)', 'comunicação (wire)', and 'cintura' for 'waist' in §4.7, a literal rendering of the narrow-waist metaphor. The glossary CSV holds only a placeholder row, so it gave no guidance. The Janus reference agrees on substrato, operador, frontend, pacto and escrow.
• Many English terms are kept in parentheses (pluggable, scratch, wrap/clamp, out of band, committed, threshold). This is deliberate for a spec, but a maintainer may want to trim them.

SPEC.tok.md (4)

• The glossary (agrinet-docs/tools/translations/terminology-glossary.csv) has no Toki Pona entries, so terms were checked only against the Janus reference. The coinages used throughout should get maintainer sign-off: ilo insa = coordinator (matches Janus 'orchestrator'), lupa lukin = frontend, nimi ma = domain tag, nanpa lili = byte, nanpa lili pi nasin wan = canonical bytes, sitelen nimi = signature, ilo open = key, ilo open len = private key, ilo open pi jan ale = public key, ilo lawa = operator, poki = field.
• English technical terms stay in prose as modifiers or in parentheses (LEB128, varint, big-endian, UTF-8, Unix nanoseconds, two's-complement, pull, 2-of-7). This follows the precedence notice, which says technical and identifier terms stay in English. A maintainer may want fewer parenthetical English glosses.
• Small additions or softenings a maintainer may want to adjust: §6 adds the gloss '(ilo Node li kama jo)' for 'pull'; §8 docs: JFA conformance self-description + dependency-leaf CI #6 'at least auditable' loses 'at least'; §10 'if and only if' is rendered only as 'only if' ('ni taso li lon'); §10.1 drops 'registered' from 'seven registered public keys'.
• The header says 'lipu pi kulupu' (full rendering) where the Lighthouse house header says 'lipu lili pi kulupu' (condensed). This is correct, because this rendering is complete and the English note says 'community rendering'.

SPEC.zh.md (4)

• The glossary terminology-glossary.csv holds only a placeholder row, so terms were checked against the Janus and lighthouse translations instead. The regional maintainer should confirm these renderings: 'coordinator' 协调者, 'operator' 运营者, 'frontend' 前端, 'substrate' 基质, 'listing' 能力列示, 'sovereign/sovereignty' 自主/自主权 (the Janus translation uses 主权 in a fiscal sense), 'legible' 可理解, 'leaveability' 可离开性, 'fixture' 测试夹具.
• §8 docs: JFA conformance self-description + dependency-leaf CI #6: 'employment claims' is rendered literally as 雇佣主张. The English word may be a source quirk; the maintainer may prefer a clearer wording once its intent is confirmed.
• Precedence notice: this file uses the majority variant (5 files, no bold label, 不作解释之用). One other sohocloud-adjacent SPEC/CONFORMANCE translation uses a bold 优先效力说明： label instead. The house style should be standardised across repos; this file was not changed.
• The precedence notice lists MUST, MUST NOT, SHOULD, SHOULD NOT and MAY. The source also uses MUST NEVER (§11.0 rule 1), which is correctly left in English in the body.

🤖 Generated with Claude Code