# CRITICAL: Protected Scheme Files - Strict Rules

## ABSOLUTE RESTRICTIONS

This directory contains **PROTECTED SCHEME FILES** for the WellNuo project.

### DO NOT WITHOUT EXPLICIT USER CONFIRMATION:

1. **CREATE** any new files or folders
2. **DELETE** any files or folders
3. **RENAME** any files (filenames are LOCKED)
4. **RENAME** schemes inside JSON files (scheme names are LOCKED)
5. **MOVE** any files to different locations
6. **RESTRUCTURE** the folder hierarchy

### BEFORE ANY FILE OPERATION:

**ALWAYS ASK:** "Могу я [создать/изменить/переименовать] файл [название]?"

Wait for explicit "да", "yes", "ok", "подтверждаю" before proceeding.

---

## Protected Files List

| File | Status |
|------|--------|
| `00_MainScheme.json` | LOCKED |
| `01_ENV_Credentials and existing API.json` | LOCKED |
| `02_ProjectDescription.json` | LOCKED |
| `03_DiscussionQuestions.json` | LOCKED |
| `04_AppStorePublication.json` | LOCKED |
| `06_UX_Flow.json` | LOCKED |
| `07_AppStore_CopyPaste.md` | LOCKED |
| `SysAnal.json` | LOCKED |
| `website/` folder | LOCKED |

---

## What IS Allowed (Read-Only by Default)

- **READ** any file to understand the project
- **ANALYZE** schemes and provide recommendations
- **SUGGEST** changes (but not implement without confirmation)
- **DISCUSS** structure and content

---

## Confirmation Format Required

Before any modification, Claude MUST:

```
Хочу внести изменение:
- Файл: [filename]
- Действие: [create/edit/rename/delete]
- Описание: [what exactly will change]

Подтверждаете? (да/нет)
```

**NO ACTION until user responds with confirmation.**

---

## Why These Rules Exist

These scheme files define the entire WellNuo application architecture.
Accidental changes can break the development workflow and cause confusion.
The naming convention must remain consistent with the SchemeOG system.