Repository navigation
docs(i18n): translate governance specifications and QA test guides to english #10
Copy link
Copy link
Closed
Labels
documentationImprovements or additions to documentationImprovements or additions to documentationgovernanceGovernance, lifecycle, and metadata policiesGovernance, lifecycle, and metadata policiesscope:i18nsource:internal
Milestone
Description
docs(i18n): Translate Governance Specifications and QA Test Guides to English
Parent Epic: #7
epic(i18n): establish english-first standard across validation engine, issue forms, and governance docs
Sprint: Sprint 2 — Internationalisation (English-First Standard)
Milestone:v1.0.0
Audit Findings: L-02, L-04 fromaudit-360-v1.0.md
📌 Context & Problem Statement
In the 360° Architecture Audit, findings L-02 and L-04 highlighted that while the root kernel definitions were hardened in English, foundational technical reference documents in docs/ remained in French:
docs/scripts-reference.md: Comprehensive reference for operational scripts, CLI arguments, and composition matrices.docs/qa-classification-test-guide.md: P6 QA contract, test scenarios, classification rules, and bug/crash test matrices.docs/analytics-taxonomy.md: P3 Data & Privacy contract, event naming taxonomy, Zero-PII principles, and schema definitions.
This introduces cognitive friction for international open-source contributors and multi-agent coordination engines expecting an English-first standard across all specifications.
💡 Proposed Solution
Translate all three technical governance documents in docs/ to 100% standard engineering English:
- Translate
docs/scripts-reference.md: Convert all script execution documentation, command explanations, environment variable tables, and composition diagrams to English. - Translate
docs/qa-classification-test-guide.md: Translate test scenarios, QA classifications, bug triage tables, and verification matrices to English. - Translate
docs/analytics-taxonomy.md: Translate the event taxonomy definitions, privacy invariants, parameter schemas, and telemetry examples to English. - Preserve Specification Contracts: Maintain all section anchors, byte budgets (enforced by
scripts/validate-docs.sh), and markdown formatting. - Quality Airbag Verification: Ensure
./scripts/validate-docs.shcontinues to pass 100% with all contracts intact.
🧭 Native Metadata Triad
- Priority (P1):
P1(Major) - Size (P4):
Size: S(½–1d, ~250–300 LOC diff lines) - Estimate (P1/P4):
0.5d - Parent Epic: epic(i18n): establish english-first standard across validation engine, issue forms, and governance docs #7
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
documentationImprovements or additions to documentationImprovements or additions to documentationgovernanceGovernance, lifecycle, and metadata policiesGovernance, lifecycle, and metadata policiesscope:i18nsource:internal
Projects
- StatusShow more project fieldsDone
Activity
nicolasvd commentedon Sep 25, 2026
4-Pillar Inception Spec — Issue #10: docs(i18n): translate governance specifications and QA test guides to english
P1 · Product Spec & User Story (P1 — Product Planner)
User Story (Gherkin)
3-State Access Matrix
Acceptance Criteria
docs/scripts-reference.mdtranslated to 100% standard English.docs/qa-classification-test-guide.mdtranslated to 100% standard English.docs/analytics-taxonomy.mdtranslated to 100% standard English.scripts/validate-docs.shstrictly respected for all three documents../scripts/validate-docs.shexits 0../scripts/quality-check.shexits 0.Pillar 1 · Design Spec (P2 — Design Lead)
Conditional Gate:
N/A — No visual/UI changes(Governance, documentation, and QA guides translation).Pillar 2 · Privacy & Data Spec (P3 — Privacy & Data Lead)
docs/analytics-taxonomy.mdrigorously preserves the core Zero-PII invariants (no emails, user IDs, or personal payload fields).Pillar 3 · System Architecture Spec (P4 — System Architect)
docs/,scripts/,.agent/rules/, and.agent/skills/../scripts/validate-docs.shand code sanity checks via./scripts/quality-check.sh.Important
Gate 1.4 Verification (STOP & WAIT): In accordance with
AGENTS.md§1.1, execution is strictly halted. Zero git branches will be cut and zero documentation files will be modified until explicit human written approval is granted.docs(i18n): generalize analytics taxonomy and QA test guide for kerne…