Skip to content

docs(i18n): translate governance specifications and QA test guides to english #10

Closed

Description

@nicolasvd

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 from audit-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:

  1. docs/scripts-reference.md: Comprehensive reference for operational scripts, CLI arguments, and composition matrices.
  2. docs/qa-classification-test-guide.md: P6 QA contract, test scenarios, classification rules, and bug/crash test matrices.
  3. 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:

  1. Translate docs/scripts-reference.md: Convert all script execution documentation, command explanations, environment variable tables, and composition diagrams to English.
  2. Translate docs/qa-classification-test-guide.md: Translate test scenarios, QA classifications, bug triage tables, and verification matrices to English.
  3. Translate docs/analytics-taxonomy.md: Translate the event taxonomy definitions, privacy invariants, parameter schemas, and telemetry examples to English.
  4. Preserve Specification Contracts: Maintain all section anchors, byte budgets (enforced by scripts/validate-docs.sh), and markdown formatting.
  5. Quality Airbag Verification: Ensure ./scripts/validate-docs.sh continues to pass 100% with all contracts intact.

🧭 Native Metadata Triad

Activity

  1. self-assigned this
    on Sep 25, 2026
  2. nicolasvd commented on Sep 25, 2026

    @nicolasvd
    OwnerAuthor

    4-Pillar Inception Spec — Issue #10: 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
    Milestone: v1.0.0 · Priority: P1 · Size: S · Estimate: 0.5d
    Gate Status: Gate 1.4 — Inception Halt Active


    P1 · Product Spec & User Story (P1 — Product Planner)

    User Story (Gherkin)

    Feature: English-First Governance Documents and QA Guides
    
      Scenario: Reading scripts reference documentation
        Given an engineer, international contributor, or AI agent opens "docs/scripts-reference.md"
        When reviewing the operational tools, arguments, and orchestration skills
        Then all descriptions, CLI flags, output formats, and sequence diagrams are presented in standard English
    
      Scenario: Reviewing QA test scenarios and classification guidelines
        Given a QA engineer or agent consults "docs/qa-classification-test-guide.md"
        When executing test suites, triaging issues, or verifying severity criteria
        Then all test procedures, severity taxonomies, and expected results are in standard English
    
      Scenario: Inspecting Zero-PII analytics taxonomy
        Given a privacy engineer or developer reads "docs/analytics-taxonomy.md"
        When auditing event schemas and parameters
        Then all privacy invariants, parameter tables, and naming conventions are in standard English

    3-State Access Matrix

    State Behavior
    Guest Read-only access to all documentation in English.
    Solo Development and test execution adhering to English-first conventions.
    Duo Collaborative review and PR walkthroughs using English-first documentation baseline.

    Acceptance Criteria

    • docs/scripts-reference.md translated to 100% standard English.
    • docs/qa-classification-test-guide.md translated to 100% standard English.
    • docs/analytics-taxonomy.md translated to 100% standard English.
    • Byte budgets in scripts/validate-docs.sh strictly respected for all three documents.
    • ./scripts/validate-docs.sh exits 0.
    • ./scripts/quality-check.sh exits 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)

    • Zero-PII Preservation: The English translation of docs/analytics-taxonomy.md rigorously preserves the core Zero-PII invariants (no emails, user IDs, or personal payload fields).
    • Telemetry Contract Integrity: Event taxonomy names and parameter keys remain identical to avoid breaking analytics telemetry contracts.

    Pillar 3 · System Architecture Spec (P4 — System Architect)

    • Architecture Integrity: Preserve relative links, anchors, and references across docs/, scripts/, .agent/rules/, and .agent/skills/.
    • Atomic Diff Budget: ~250–300 lines diff across 3 markdown files (< 300 LOC diff).
    • Quality Airbag: Contract verification via ./scripts/validate-docs.sh and 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.

  3. added this to the v1.0.0 milestone on Sep 25, 2026
  4. moved this from Backlog to In progress in Agentic Delivery Boardon Sep 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions