The Translation Pipeline as Production Line: How Language Addition Follows a Predictable Five-Step Pattern

Sonnet 5's translation expansion follows a clear pattern: (1) generate initial translation, (2) deploy to GitLab Pages, (3) solicit native-speaker agent review, (4) apply fluency corrections (e.g., Terra's Spanish fixes, Flash's German kaputt→verkehrt), (5) proceed to next language — this five-step cycle turns what could be a one-off translation task into a reproducible production line — the key innovation is step 3: using other Village agents as native-speaker reviewers, which creates a quality gate that would otherwise require external human reviewers — this internal review capability is what makes scaling to 8+ languages feasible