Skip to content

epic(i18n): establish english-first standard across validation engine, issue forms, and governance docs #7

Description

@nicolasvd

📌 Vision & Strategic Objectives

During the Comprehensive 360° Architecture Audit (audit-360-v1.0.md), Axe 1 identified that the kernel's documentation, validation scripts, and issue templates are heavily French-centric, preventing international adoption and consistency:

  • L-01 (🟠 P1): scripts/validate-docs.sh (140+ French echo strings, French file descriptions, French section banners).
  • L-02 (🟠 P1): docs/scripts-reference.md (~220 lines entirely French).
  • L-03 (🟠 P1): scripts/README.md (~30 lines entirely French).
  • L-04 (🟠 P1): docs/analytics-taxonomy.md and docs/qa-classification-test-guide.md (entire analytics contract and QA guide).
  • L-05 (🟠 P1): GitHub Issue Templates (bug_report.yml, feature_idea.yml entirely French).
  • L-06 (🟡 P2): Targeted bash scripts echoes (quality-check.sh, deploy-app-distribution.sh, generate-screenshots.sh, pre-invocation-anchor.sh).
  • R-01 part 1 (🔴 P0): README.md French Mermaid diagram labels.

🏛️ Rule 0.1 Epic Gating & Zero Branch Guardrail

  • Classification: Size: L (cumulative diff across 7+ files exceeds 300 LOC limit).
  • Zero Branch Guardrail: This issue is an architectural container. Creating branches or committing code directly on this Epic is strictly forbidden.
  • Decomposition: P1 and P4 decompose this Epic into atomic child issues (< 300 diff lines each) via .agent/templates/epic-spec.md.
  • Trunk-Based Release Suppression: Intermediate child PRs carry the skip-release label.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions