AI Company EXEC Translation Layer — Coordinator (v1.0.0)
Agent Role: Execution Layer — Translation Coordination Hub (EXEC-TR-COORD)
Owner: CMO | Quality: CQO | Security: CISO
Risk Level: Medium | CVSS Target: <7.0 | Quality Gate: G2
Language: Fully English | ClawHub Schema v1.0 | Harness Engineering Compliant
1. Purpose & Scope
The Translation Layer Coordinator routes translation requests to the appropriate specialized translation agent (EXEC-TR-EN, EXEC-TR-ZH, EXEC-TR-RU, EXEC-TR-FR) based on the target language parameter.
Sub-Agents:
| Agent | Target Language | Role ID | Emoji |
|---|---|---|---|
| EXEC-TR-EN | English | EXEC-TR-EN | 🇬🇧 |
| EXEC-TR-ZH | Chinese (Simplified) | EXEC-TR-ZH | 🇨🇳 |
| EXEC-TR-RU | Russian | EXEC-TR-RU | 🇷🇺 |
| EXEC-TR-FR | French | EXEC-TR-FR | 🇫🇷 |
2. Routing Logic
Input: source-file + target-language + style + output-dir
Step 1: Validate source-file (exists, <10MB, no path traversal)
Step 2: Route to appropriate agent:
- target-language == 'en' → ai-company-translator-en-1.0.0
- target-language == 'zh' → ai-company-translator-zh-1.0.0
- target-language == 'ru' → ai-company-translator-ru-1.0.0
- target-language == 'fr' → ai-company-translator-fr-1.0.0
- target-language == 'auto' → detect source language, route accordingly
Step 3: Delegate to target agent via sessions_spawn (isolated)
Step 4: Aggregate results, update registry
Step 5: Return consolidated output
3. Registry Entries (All 4 Agents)
agents:
- id: EXEC-TR-EN
name: ai-company-translator-en
slug: ai-company-translator-en
version: 1.0.0
target-language: en
emoji: "🇬🇧"
status: active
owner: CMO
- id: EXEC-TR-ZH
name: ai-company-translator-zh
slug: ai-company-translator-zh
version: 1.0.0
target-language: zh
emoji: "🇨🇳"
status: active
owner: CMO
- id: EXEC-TR-RU
name: ai-company-translator-ru
slug: ai-company-translator-ru
version: 1.0.0
target-language: ru
emoji: "🇷🇺"
status: active
owner: CMO
- id: EXEC-TR-FR
name: ai-company-translator-fr
slug: ai-company-translator-fr
version: 1.0.0
target-language: fr
emoji: "🇫🇷"
status: active
owner: CMO
4. Verification Checklist
- ClawHub Schema v1.0 frontmatter
- No hardcoded paths
- 4 sub-agents registered
- Routing logic documented
- Harness Engineering compliant
- CISO STRIDE mitigations documented
- CQO G2 quality gate documented
