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	baa4632

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

• The terminology glossary (agrinet-docs/tools/translations/terminology-glossary.csv) holds only a placeholder row, so terms were checked only against the Janus reference translation. Terms that match it: العمارة, ركيزة, المنسّق, الواجهة الأمامية, الحَكامة, مغادرة.
• Some term choices have no reference precedent, so a regional maintainer should confirm them: خط الاتصال ('wire'), العملة النظامية ('fiat'), بديل مؤقت ('stand-in'), الثوابت ('invariants'), مقروئية ('legibility'), دورة حياة التشغيل ('employment lifecycle'), أداة اختبار المطابقة ('conformance harness').
• Small wording difference between reference files: the lighthouse house header uses المعمارية for 'architecture' in its body, while the Janus reference and this file use العمارة. This file follows Janus.

CONFORMANCE.es.md (3)

• The terminology references disagree on the architecture's name. The Janus Spanish reference translates it as 'Arquitectura de Doble Faz (JFA)', while the lighthouse house reference and this file keep 'Janus-Facing Architecture'. I kept the English proper name. A regional maintainer should pick one convention for all repos.
• The terminology glossary (terminology-glossary.csv) holds only a placeholder row, so there is no glossary for terms like coordinator/coordinador, front end/frontend, stand-in/suplencia, wire/canal or replay window/ventana de repetición. A maintainer should confirm these choices.
• Some technical terms are kept as English loanwords or literal calques: checkpoints, stub, commit, 'no equivocación' (non-equivocation), 'arnés de conformidad' (conformance harness) and 'impulso de establecimiento de la pila' (stack-establishment push). They are acceptable, but worth a regional check.

CONFORMANCE.fr.md (4)

• Role-declaration table: the repo's own terms 'Coordinator', 'Frontend' and 'Node' are left in English, but the fourth row ('Table participants, portail, agent') is translated. Keeping repo terms in English can be defended. A regional maintainer should decide whether the column should be consistent.
• 'pluggable role' is rendered as 'rôle interchangeable', so the table cell reads 'interchangeable, remplaçable', which is a little redundant. 'enfichable' would be the literal alternative. Maintainer's choice.
• 'employment lifecycle' is rendered literally as 'cycle de vie de l'emploi'. The source means engaging nodes for workloads. 'cycle de vie des engagements' may read more naturally. Left as is because it is faithful.
• The terminology glossary (agrinet-docs/tools/translations/terminology-glossary.csv) holds only a placeholder row, so terms were checked against the Janus French reference only. It also uses 'frontend', 'coordinateur' and 'substrat', so the translation is consistent with it.

CONFORMANCE.hi.md (5)

• Terminology choice for maintainer: 'invariant' is rendered 'अपरिवर्तनीय नियम (invariants)', while lighthouse-seed.hi.md uses 'इनवेरिएंट (invariant)'. Both are clear; the regional maintainer should choose one house term.
• Terminology choice for maintainer: 'orchestration' is rendered 'संयोजन (orchestration)', while lighthouse-seed.hi.md uses the transliteration 'ऑर्केस्ट्रेटर'. Not wrong, but worth making consistent.
• 'employment lifecycle' is rendered literally as 'रोज़गार-जीवनचक्र'. In the source it means a workload engaging a node, not human employment. A maintainer may want a clearer term.
• The glossary CSV (agrinet-docs/tools/translations/terminology-glossary.csv) contains only a placeholder row, so terminology was checked against the Janus and lighthouse Hindi documents only.
• Verified: the header matches the house template (source CONFORMANCE.md, snapshot 2026-10-05, URL https://github.com/NTARI-RAND/SoHoLINK); the spec precedence notice is present with normative keywords in English; l10n_inventory check returns ok with no warnings; the file is UTF-8 with LF line endings and no BOM; all code, identifiers, dates (2026-07-12), numbers (2-of-7, migration 011, open problem 7) and URLs are verbatim.

CONFORMANCE.pt.md (5)

• The 'This repo's term' table column keeps the repo terms Coordinator, Frontend and Node in English. Those are the repo's own names, so this is defensible. A regional maintainer should confirm it is the convention they want.
• 'named interim' is rendered as 'interinidade nomeada' (in the invariants table and in the DCO bullet). It is correct but stiff. Something like 'medida interina declarada' could read more naturally; left for a maintainer to decide.
• 'wire' is rendered as 'rede' ('na rede', 'rede de coordenação'). That loses the protocol-wire sense and could be confused with 'network'. The Janus reference has no established term for it.
• The terminology glossary CSV has only a header row and no entries, so terms were checked against the Janus and lighthouse reference files only: 'Arquitetura de Dupla Face', 'frontend', 'comum', 'substrato', 'pacto', and 'rótulo provisório (stand-in)'.
• The source file uses CRLF line endings; the translation uses LF, as the task requires.

CONFORMANCE.tok.md (5)

• Header: the house reference (lighthouse-seed.tok.md) has no spec-precedence paragraph. The translation adds one ('lipu Inli li lawa...') that lists MUST/SHOULD/MAY kept in English. It is in place as required for the spec category, but it has no house wording yet for a maintainer to check it against.
• The glossary (agrinet-docs terminology-glossary.csv) holds only a placeholder row, so terminology was checked only against janus-facing-architecture.tok.md. Terms used: ilo insa = coordinator, lupa lukin = front end, kipisi ilo = substrate, jan pi ilo suli = operator, nasin insa = protocol, jan pali jo = participant, jan kulupu = member. A maintainer should confirm the participant/member split.
• 'ilo Node' uses the English architecture term 'Node' as a proper-name adjective, because the source table keeps 'Node' as this repo's own term. A maintainer may prefer a pure toki pona phrase.
• Many English glosses in parentheses are kept, for example (fee), (fiat), (pluggable role) and (workload identity). They are not invented words, but they make the text heavy. A regional maintainer may want to trim them.
• 'lipu pi tawa pini' for 'migration history' and 'li awen e tawa ona' for 'pending migration' are understandable but loose.

CONFORMANCE.zh.md (3)

• The terminology glossary (agrinet-docs/tools/translations/terminology-glossary.csv) holds only a placeholder row. Terms were checked against janus-facing-architecture.zh.md instead: 基质, 前端, 协调者, 运营者, 见证者, 约定, 联邦 all match it. The reference does not define several terms this file uses: 暂代 (stand-in), 不变式 (invariant), 咽喉点 (chokepoint; the Janus reference uses 咽喉要道 once in running prose), 溯源 (provenance), 公域 (commons), 管理者 (steward). A regional maintainer should confirm these.
• The spec precedence notice is a separate second blockquote after the house header. The lighthouse house header has no such block because it is not a spec. The notice is correct and complete, and it keeps normative keywords in English. Confirm this is the intended spec layout.
• 'authored, legible, contestable' (fee declarations) is rendered as 由其撰写、可理解、可质疑. The meaning is acceptable, but a maintainer may prefer a wording like 有明确作者 to stress that each declaration is attributable to its author.

Source issues noticed during translation

The English was translated as written; these are for the source maintainers.

• CONFORMANCE.md: "must not migrate down into it" — Lowercase "must not", so translated as plain prose rather than kept as the MUST NOT keyword. Confirm whether normative force was intended.

🤖 Generated with Claude Code