JARVIS TRANSLATE COMMAND SPEC v1

STATUS: PLANNED
OWNER: single-owner system
COMMAND: TRANSLATE
DEFAULT OWNER LANGUAGE: Russian
DEFAULT RULE: translation must not bypass privacy or security rules

PURPOSE

This document defines the future safe translation command for Jarvis.

The TRANSLATE command should help the owner translate:
- plain text
- public-safe documentation
- dashboard/public continuity files

It must not translate or expose private data.

COMMAND NAMES

English:
- translate
- translation

Russian:
- переведи
- перевод

French:
- traduire
- traduction

LANGUAGE MODEL

Default owner language:
- Russian

Command behavior:
- if source text language is clear, translate as requested
- if target language is specified, use target language
- if target language is not specified, ask or use owner default depending on context
- if command is unclear, respond in Russian

EXAMPLES

Allowed plain text translation:

Command:
- переведи на английский: Система работает.

Expected result:
- The system is running.

Allowed public-safe file translation:

Command:
- переведи NEXT_TASK_PUBLIC.md на русский

Allowed only if:
- file is public-safe
- file is listed in PUBLIC_FILE_INDEX_v1.txt
- file contains no secrets

ALLOWED SOURCES

Allowed:
- text provided directly by owner
- public-safe files
- public dashboard files
- public continuity files listed in PUBLIC_FILE_INDEX_v1.txt

Examples:
- NEXT_TASK_PUBLIC.md
- LANGUAGE_POLICY_v1.txt
- OWNER_DASHBOARD_LINKS_v1.txt
- DASHBOARD_CHANGELOG_v1.txt
- owner-command-ui-ru.html
- owner-command-ui-v0.2.html

DENIED SOURCES

Denied:
- .env
- credentials
- tokens
- API keys
- SSH keys
- private logs
- database dumps
- backup contents
- PostgreSQL data
- n8n credential data
- private workflow secrets
- personal/private data not explicitly approved

DENIED COMMAND EXAMPLES

Denied:
- переведи .env
- translate secrets
- traduire credentials
- переведи backup
- покажи и переведи токены
- translate database dump

RISK LEVELS

1. Translate plain owner-provided text:
- Risk: low
- Status: future allowed

2. Translate public-safe file:
- Risk: medium read-only
- Status: future allowed with public index check

3. Translate private file:
- Risk: high
- Status: denied

4. Translate secrets or credentials:
- Risk: critical
- Status: denied

IMPLEMENTATION REQUIREMENTS

Before implementation:
1. Add translate command to COMMAND_REGISTRY_v1.txt.
2. Add aliases to LANGUAGE_POLICY_v1.txt.
3. Add deny rules to jarvis.sh.
4. Add no-private-file rule.
5. Add public index allowlist check for file translation.
6. Keep initial implementation local-only.
7. Do not create public webhook.
8. Do not connect dashboard button to execution.

INITIAL IMPLEMENTATION MODEL

Phase 1:
- document only

Phase 2:
- local text translation helper
- no file access
- no webhook

Phase 3:
- public-safe file translation
- only files listed in PUBLIC_FILE_INDEX_v1.txt

Phase 4:
- optional dashboard display
- still non-executing unless explicitly approved later

SECURITY RULE

Translation must never become a way to read private files.

Language features must follow the same access rules as commands.

END