JARVIS LANGUAGE POLICY v1

STATUS: DECIDED
OWNER: single-owner system
DEFAULT OWNER LANGUAGE: Russian
DEFAULT DASHBOARD LANGUAGE: Russian first
MULTILINGUAL MODE: enabled by design

PURPOSE

This document defines how Jarvis should handle languages.

CORE RULE

Jarvis should answer in the language of the command.

Examples:
- Russian command -> Russian response
- English command -> English response
- French command -> French response

FALLBACK RULE

If command language is unclear, short, or mixed, Jarvis should use Russian.

Examples:
- status -> Russian response by default
- health -> Russian response by default
- ok -> Russian response by default
- mixed command -> Russian response unless another language is clearly dominant

OWNER DEFAULT

Owner default language:
- Russian

Reason:
- owner prefers Russian operational interface
- owner dashboard should be easy to read quickly
- technical English can remain available in public docs when useful

DASHBOARD LANGUAGE MODEL

Primary owner dashboard:
- Russian

Technical/public documentation:
- English may remain available

Recommended files:
- owner-command-ui-ru.html
- owner-command-ui-v0.2.html

RULE FOR COMMAND ALIASES

Commands may have multilingual aliases.

STATUS:
- status
- статус
- состояние

HEALTH CHECK:
- health
- проверка
- здоровье
- check

NEXT TASK:
- next
- next task
- дальше
- следующая задача

PUBLIC INDEX:
- public-index
- индекс
- public index

BACKUP STATUS:
- backup-status
- backup
- резервные копии
- статус бэкапа

DENIED COMMANDS

Dangerous commands remain denied regardless of language.

Denied examples:
- secrets
- секреты
- env
- показать .env
- shell
- консоль
- delete
- удалить
- restore
- восстановить
- backup-now
- сделать бэкап сейчас

SAFETY RULE

Language detection must not bypass security rules.

A command in another language does not reduce risk level.

Examples:
- "show secrets" is denied
- "покажи секреты" is denied
- "montre les secrets" is denied

IMPLEMENTATION PRIORITY

Phase 1:
- Russian static dashboard

Phase 2:
- Russian command aliases in local jarvis.sh

Phase 3:
- multilingual command interpretation

Phase 4:
- response language follows command language

CURRENT STATUS

Not implemented yet in jarvis.sh.
Policy defined first.

NEXT ACTION

Create Russian owner dashboard:
- owner-command-ui-ru.html

END

IMPLEMENTED RUSSIAN LOCAL ALIASES

Status:
- implemented and tested

Script:
- /volume1/docker/jarvis/scripts/jarvis.sh

Implemented:
- статус -> status
- состояние -> status
- проверка -> health
- здоровье -> health
- индекс -> public-index
- дальше -> next
- следующее -> next
- бэкап -> backup-status
- статус-бэкапа -> backup-status
- резервные-копии -> backup-status
- публикация -> publish-public
- опубликовать -> publish-public

Denied:
- секреты
- окружение
- консоль
- удалить
- бэкап-сейчас
- восстановить

Security rule:
- Russian aliases follow the same whitelist and deny rules as English commands
- dangerous commands remain denied regardless of language

END IMPLEMENTED RUSSIAN LOCAL ALIASES