JARVIS TRANSLATE IMPLEMENTATION PLAN v1

STATUS: DRAFT
OWNER: single-owner system
COMMAND: TRANSLATE
DEFAULT RULE: local-first, text-first, no private files

PURPOSE

This document defines how the future TRANSLATE command should be implemented safely.

This is a plan only.
No translation execution is implemented by this document.

IMPLEMENTATION PRINCIPLE

Start with the safest version:

Phase 1:
- translate owner-provided plain text only
- no file reads
- no private paths
- no webhook
- no dashboard execution

Do not start with:
- file translation
- database translation
- backup translation
- log translation
- automatic translation of folders
- public webhooks
- browser command execution

PHASE 1: LOCAL TEXT TRANSLATION

Goal:
- allow owner to translate directly provided text

Example future command:
- jarvis.sh переведи "Система работает" на английский

Allowed input:
- text typed directly into command
- no file path
- no URL fetch
- no database read

Output:
- translated text printed to terminal

Risk:
- low

PHASE 2: PUBLIC-SAFE FILE TRANSLATION

Only after Phase 1 is tested.

Allowed files:
- files listed in PUBLIC_FILE_INDEX_v1.txt
- public-safe files only

Denied:
- any file not in PUBLIC_FILE_INDEX_v1.txt
- .env
- logs
- db/backups
- database dumps
- private data
- credentials
- tokens

Risk:
- medium read-only

PHASE 3: DASHBOARD INTEGRATION

Only after local command is safe.

Rules:
- dashboard may show documentation
- dashboard buttons remain non-executing unless explicitly approved
- no public webhook by default

DENY RULES

Always deny:
- translate .env
- translate secrets
- translate credentials
- translate backups
- translate database dumps
- translate private logs
- translate old n8n data
- translate private workflow credentials

SECURITY CHECKLIST BEFORE IMPLEMENTATION

Before writing code:
1. Define command syntax.
2. Define input limits.
3. Define denied patterns.
4. Define whether translation uses local model or external API.
5. If external API is used, define privacy boundary.
6. Do not send private data externally.
7. Keep first version local-only.
8. Test deny rules first.

OPEN DECISION

Translation engine is not selected yet.

Options:
- use AI session manually
- use local model later
- use external translation API only with explicit privacy approval

CURRENT RECOMMENDATION

Do not implement TRANSLATE yet.

Next best action:
- keep specification and implementation plan public-safe
- continue improving owner dashboard and local command safety

END