JARVIS NATURAL LANGUAGE ROUTER STATUS v1

STATUS: PLANNING COMPLETE / IMPLEMENTATION NOT STARTED
OWNER: single-owner system
DEFAULT OWNER LANGUAGE: Russian
CURRENT MODE: documentation and planning only

PURPOSE

This document summarizes the current state of Jarvis natural language command planning.

CORE DECISION

Jarvis should understand natural human language.

The owner should not be forced to use only exact commands.

Examples:
- проверь всё
- как там бэкапы?
- что дальше?
- покажи статус
- переведи это на английский

Jarvis should map phrases to safe internal intents.

CRITICAL SAFETY RULE

Natural language understanding does not mean unrestricted execution.

Jarvis may understand broad language.
Jarvis may execute only allowlisted safe actions.

CURRENT DOCUMENTS

1. NATURAL_LANGUAGE_COMMAND_POLICY_v1.txt
Status:
- created
Purpose:
- defines natural language command policy
- separates understanding from execution
- defines allowed and denied intents

2. NATURAL_LANGUAGE_ROUTER_DRAFT_v1.txt
Status:
- created
Purpose:
- defines phrase -> language -> intent -> risk -> action / clarify / deny pipeline

3. NATURAL_LANGUAGE_TEST_PHRASES_v1.txt
Status:
- created
Purpose:
- defines test phrases for allowed, ambiguous, planned, and denied intents

4. NATURAL_LANGUAGE_ROUTER_IMPLEMENTATION_PLAN_v1.txt
Status:
- created
Purpose:
- defines phased implementation plan
- requires dry-run classifier before execution

5. NATURAL_LANGUAGE_DRY_RUN_ROUTER_SPEC_v1.txt
Status:
- created
Purpose:
- defines future dry-run router output format and safety rules

6. NATURAL_LANGUAGE_DRY_RUN_ROUTER_TEST_PLAN_v1.txt
Status:
- created
Purpose:
- defines how to test dry-run router before any execution mode

IMPLEMENTED NOW

Implemented:
- documentation
- planning
- public-safe continuity
- Russian owner dashboard
- local exact/alias commands through jarvis.sh

Not implemented:
- natural language router code
- dry-run router script
- phrase classifier
- natural language command execution
- dashboard execution
- public webhook

CURRENT SAFE LOCAL COMMANDS

Available through jarvis.sh:
- статус
- проверка
- дальше
- индекс
- бэкап

Denied examples:
- секреты
- окружение
- консоль
- удалить
- восстановить

FUTURE NATURAL LANGUAGE INTENTS

Allowed read-only future intents:
- STATUS
- HEALTH_CHECK
- NEXT_TASK
- PUBLIC_INDEX
- BACKUP_STATUS

Planned future text intent:
- TRANSLATE_TEXT

Denied future intents:
- SECRET_ACCESS
- SHELL_EXECUTION
- PRIVATE_FILE_READ
- DESTRUCTIVE_ACTION
- UNSAFE_WORKFLOW_ACTIVATION

WHY EXECUTION IS NOT ENABLED YET

Execution is not enabled because:
- natural language can be ambiguous
- router classification has not been tested yet
- dry-run router does not exist yet
- deny rules must be tested first
- public webhook is intentionally disabled
- dashboard must remain non-executing

NEXT SAFE STEP

Create local dry-run router draft script later:
- jarvis_nl_dry_run.sh

Initial behavior:
- accept phrase
- classify phrase
- print structured interpretation
- do not execute action

Example future command:
- sudo /volume1/docker/jarvis/scripts/jarvis_nl_dry_run.sh "как там бэкапы?"

Expected dry-run output:
- intent: BACKUP_STATUS
- decision: dry_run_allow
- proposed_action: jarvis.sh бэкап
- executed: no

SECURITY RESULT

Natural language planning is complete enough to proceed to a dry-run prototype later.

Execution remains blocked until:
- dry-run router exists
- test phrases pass
- deny rules pass
- owner approves execution mode separately

END