semantic update

.gitignore

@@ -68,3 +68,4 @@ backend/mappings.db
 backend/tasks.db
 backend/logs
 backend/auth.db
+semantics/reports

backend/src/api/routes/admin.py

@@ -1,5 +1,6 @@
 # [DEF:backend.src.api.routes.admin:Module]
 #
+# @TIER:      STANDARD
 # @SEMANTICS: api, admin, users, roles, permissions
 # @PURPOSE:   Admin API endpoints for user and role management.
 # @LAYER:     API

backend/src/api/routes/git_schemas.py

@@ -1,5 +1,6 @@
 # [DEF:backend.src.api.routes.git_schemas:Module]
 #
+# @TIER:      STANDARD
 # @SEMANTICS: git, schemas, pydantic, api, contracts
 # @PURPOSE:   Defines Pydantic models for the Git integration API layer.
 # @LAYER:     API
@@ -14,6 +15,7 @@ from uuid import UUID
 from src.models.git import GitProvider, GitStatus, SyncStatus
 
 # [DEF:GitServerConfigBase:Class]
+# @TIER: TRIVIAL
 # @PURPOSE: Base schema for Git server configuration attributes.
 class GitServerConfigBase(BaseModel):
     name: str = Field(..., description="Display name for the Git server")

backend/src/models/auth.py

@@ -1,5 +1,6 @@
 # [DEF:backend.src.models.auth:Module]
 #
+# @TIER:      STANDARD
 # @SEMANTICS: auth, models, user, role, permission, sqlalchemy
 # @PURPOSE:   SQLAlchemy models for multi-user authentication and authorization.
 # @LAYER:     Domain

backend/src/models/dashboard.py

@@ -1,4 +1,5 @@
 # [DEF:backend.src.models.dashboard:Module]
+# @TIER:      STANDARD
 # @SEMANTICS: dashboard, model, metadata, migration
 # @PURPOSE:   Defines data models for dashboard metadata and selection.
 # @LAYER:     Model
@@ -8,6 +9,7 @@ from pydantic import BaseModel
 from typing import List
 
 # [DEF:DashboardMetadata:Class]
+# @TIER: TRIVIAL
 # @PURPOSE: Represents a dashboard available for migration.
 class DashboardMetadata(BaseModel):
     id: int
@@ -17,6 +19,7 @@ class DashboardMetadata(BaseModel):
 # [/DEF:DashboardMetadata:Class]
 
 # [DEF:DashboardSelection:Class]
+# @TIER: TRIVIAL
 # @PURPOSE: Represents the user's selection of dashboards to migrate.
 class DashboardSelection(BaseModel):
     selected_ids: List[int]

backend/src/models/mapping.py

@@ -1,5 +1,6 @@
 # [DEF:backend.src.models.mapping:Module]
 #
+# @TIER:      STANDARD
 # @SEMANTICS: database, mapping, environment, migration, sqlalchemy, sqlite
 # @PURPOSE:   Defines the database schema for environment metadata and database mappings using SQLAlchemy.
 # @LAYER:     Domain
@@ -19,6 +20,7 @@ import enum
 Base = declarative_base()
 
 # [DEF:MigrationStatus:Class]
+# @TIER: TRIVIAL
 # @PURPOSE: Enumeration of possible migration job statuses.
 class MigrationStatus(enum.Enum):
     PENDING = "PENDING"
@@ -29,6 +31,7 @@ class MigrationStatus(enum.Enum):
 # [/DEF:MigrationStatus:Class]
 
 # [DEF:Environment:Class]
+# @TIER: STANDARD
 # @PURPOSE: Represents a Superset instance environment.
 class Environment(Base):
     __tablename__ = "environments"
@@ -40,6 +43,7 @@ class Environment(Base):
 # [/DEF:Environment:Class]
 
 # [DEF:DatabaseMapping:Class]
+# @TIER: STANDARD
 # @PURPOSE: Represents a mapping between source and target databases.
 class DatabaseMapping(Base):
     __tablename__ = "database_mappings"

backend/src/schemas/auth.py

@@ -1,5 +1,6 @@
 # [DEF:backend.src.schemas.auth:Module]
 #
+# @TIER:      STANDARD
 # @SEMANTICS: auth, schemas, pydantic, user, token
 # @PURPOSE:   Pydantic schemas for authentication requests and responses.
 # @LAYER:     API
@@ -14,6 +15,7 @@ from datetime import datetime
 # [/SECTION]
 
 # [DEF:Token:Class]
+# @TIER: TRIVIAL
 # @PURPOSE: Represents a JWT access token response.
 class Token(BaseModel):
     access_token: str
@@ -21,6 +23,7 @@ class Token(BaseModel):
 # [/DEF:Token:Class]
 
 # [DEF:TokenData:Class]
+# @TIER: TRIVIAL
 # @PURPOSE: Represents the data encoded in a JWT token.
 class TokenData(BaseModel):
     username: Optional[str] = None
@@ -28,6 +31,7 @@ class TokenData(BaseModel):
 # [/DEF:TokenData:Class]
 
 # [DEF:PermissionSchema:Class]
+# @TIER: TRIVIAL
 # @PURPOSE: Represents a permission in API responses.
 class PermissionSchema(BaseModel):
     id: Optional[str] = None

frontend/src/components/storage/FileList.svelte

@@ -1,8 +1,9 @@
 <!-- [DEF:FileList:Component] -->
 <!--
+@TIER:      STANDARD
 @SEMANTICS: storage, files, list, table
 @PURPOSE:   Displays a table of files with metadata and actions.
-@LAYER:     Component
+@LAYER:     UI
 @RELATION:  DEPENDS_ON -> storageService
 
 @PROPS:     files (Array) - List of StoredFile objects.
@@ -22,10 +23,13 @@
   // [DEF:isDirectory:Function]
   /**
    * @purpose Checks if a file object represents a directory.
+   * @pre     file object has mime_type property.
+   * @post    Returns boolean.
    * @param   {Object} file - The file object to check.
    * @return  {boolean} True if it's a directory, false otherwise.
    */
   function isDirectory(file) {
+    console.log("[isDirectory][Action] Checking file type");
     return file.mime_type === 'directory';
   }
   // [/DEF:isDirectory:Function]
@@ -33,10 +37,13 @@
   // [DEF:formatSize:Function]
   /**
    * @purpose Formats file size in bytes into a human-readable string.
+   * @pre     bytes is a number.
+   * @post    Returns formatted string.
    * @param   {number} bytes - The size in bytes.
    * @return  {string} Formatted size (e.g., "1.2 MB").
    */
   function formatSize(bytes) {
+    console.log(`[formatSize][Action] Formatting ${bytes} bytes`);
     if (bytes === 0) return '0 B';
     const k = 1024;
     const sizes = ['B', 'KB', 'MB', 'GB', 'TB'];
@@ -48,10 +55,13 @@
   // [DEF:formatDate:Function]
   /**
    * @purpose Formats an ISO date string into a localized readable format.
+   * @pre     dateStr is a valid date string.
+   * @post    Returns localized string.
    * @param   {string} dateStr - The date string to format.
    * @return  {string} Localized date and time.
    */
   function formatDate(dateStr) {
+    console.log("[formatDate][Action] Formatting date string");
     return new Date(dateStr).toLocaleString();
   }
   // [/DEF:formatDate:Function]

frontend/src/components/storage/FileUpload.svelte

@@ -1,8 +1,9 @@
 <!-- [DEF:FileUpload:Component] -->
 <!--
+@TIER:      STANDARD
 @SEMANTICS: storage, upload, files
 @PURPOSE:   Provides a form for uploading files to a specific category.
-@LAYER:     Component
+@LAYER:     UI
 @RELATION:  DEPENDS_ON -> storageService
 
 @PROPS:     None

frontend/src/routes/admin/roles/+page.svelte

@@ -1,8 +1,9 @@
 <!-- [DEF:AdminRolesPage:Component] -->
 <!--
+@TIER:      STANDARD
 @SEMANTICS: admin, role-management, rbac
 @PURPOSE:   UI for managing system roles and their permissions.
-@LAYER:     Feature
+@LAYER:     Domain
 @RELATION:  DEPENDS_ON -> frontend.src.services.adminService
 @RELATION:  DEPENDS_ON -> frontend.src.components.auth.ProtectedRoute
 
@@ -56,7 +57,13 @@
   // [/DEF:loadData:Function]
 
   // [DEF:openCreateModal:Function]
+  /**
+   * @purpose Initializes state for creating a new role.
+   * @pre     None.
+   * @post    showModal is true, roleForm is reset.
+   */
   function openCreateModal() {
+    console.log("[openCreateModal][Action] Opening create modal");
     isEditing = false;
     currentRoleId = null;
     roleForm = { name: '', description: '', permissions: [] };
@@ -65,7 +72,13 @@
   // [/DEF:openCreateModal:Function]
 
   // [DEF:openEditModal:Function]
+  /**
+   * @purpose Initializes state for editing an existing role.
+   * @pre     role object is provided.
+   * @post    showModal is true, roleForm is populated.
+   */
   function openEditModal(role) {
+    console.log(`[openEditModal][Action] Opening edit modal for role ${role.id}`);
     isEditing = true;
     currentRoleId = role.id;
     roleForm = {
@@ -80,6 +93,8 @@
   // [DEF:handleSaveRole:Function]
   /**
    * @purpose Submits role data (create or update).
+   * @pre     roleForm contains valid data.
+   * @post    Role is saved, modal closed, data reloaded.
    */
   async function handleSaveRole() {
     console.log('[AdminRolesPage][handleSaveRole][Entry]');
@@ -100,6 +115,11 @@
   // [/DEF:handleSaveRole:Function]
 
   // [DEF:handleDeleteRole:Function]
+  /**
+   * @purpose Deletes a role after confirmation.
+   * @pre     role object is provided.
+   * @post    Role is deleted if confirmed, data reloaded.
+   */
   async function handleDeleteRole(role) {
     if (!confirm($t.admin.roles.confirm_delete.replace('{name}', role.name))) return;
     

frontend/src/routes/login/+page.svelte

@@ -1,8 +1,9 @@
 <!-- [DEF:LoginPage:Component] -->
 <!--
+@TIER:      STANDARD
 @SEMANTICS: login, auth, ui, form
 @PURPOSE:   Provides the user interface for local and ADFS authentication.
-@LAYER:     Feature
+@LAYER:     UI
 @RELATION:  USES -> authStore
 @RELATION:  CALLS -> api.auth.login
 

frontend/src/routes/migration/+page.svelte

@@ -303,7 +303,7 @@
       />
     </div>
 
-    <!-- [DEF:DashboardSelectionSection] -->
+    <!-- [DEF:DashboardSelectionSection:Component] -->
     <div class="mb-8">
       <h2 class="text-lg font-medium mb-4">Select Dashboards</h2>
       
@@ -316,7 +316,7 @@
         <p class="text-gray-500 italic">Select a source environment to view dashboards.</p>
       {/if}
     </div>
-    <!-- [/DEF:DashboardSelectionSection] -->
+    <!-- [/DEF:DashboardSelectionSection:Component] -->
 
 
     <div class="flex items-center mb-4">

frontend/src/routes/tools/storage/+page.svelte

@@ -1,8 +1,9 @@
 <!-- [DEF:StoragePage:Component] -->
 <!--
+@TIER:      STANDARD
 @SEMANTICS: storage, files, management
 @PURPOSE:   Main page for file storage management.
-@LAYER:     Feature
+@LAYER:     UI
 @RELATION:  DEPENDS_ON -> storageService
 @RELATION:  CONTAINS -> FileList
 @RELATION:  CONTAINS -> FileUpload

frontend/src/services/adminService.js

@@ -1,5 +1,6 @@
 // [DEF:adminService:Module]
 //
+// @TIER:      STANDARD
 // @SEMANTICS: admin, users, roles, ad-mappings, api
 // @PURPOSE:   Service for Admin-related API calls (User and Role management).
 // @LAYER:     Service

semantic_protocol.md

@@ -1,245 +1,72 @@
+РОЛЬ: Архитектор Семантической Когерентности.
+ЗАДАЧА: Генерация кода (Python/Svelte).
+РЕЖИМ: Строгий. Детерминированный. Без болтовни.
 
-# SYSTEM STANDARD: POLYGLOT CODE GENERATION PROTOCOL (GRACE-Poly)
+I. ЗАКОН (АКСИОМЫ)
+1. Смысл первичен. Код вторичен.
+2. Контракт (@PRE/@POST) — источник истины.
+3. Структура `[DEF]...[/DEF]` — нерушима.
+4. Архитектура в Header — неизменяема.
+5. Сложность фрактала ограничена: модуль < 300 строк.
 
-**OBJECTIVE:** Generate Python and Svelte/TypeScript code that strictly adheres to Semantic Coherence standards. Output must be machine-readable, fractal-structured, and optimized for Sparse Attention navigation.
+II. СИНТАКСИС (ЖЕСТКИЙ ФОРМАТ)
+ЯКОРЬ (Контейнер):
+  Начало: `# [DEF:id:Type]` (Python) | `<!-- [DEF:id:Type] -->` (Svelte)
+  Конец:  `# [/DEF:id:Type]` (Python) | `<!-- [/DEF:id:Type] -->` (Svelte) (ОБЯЗАТЕЛЬНО для аккумуляции)
+  Типы:   Module, Class, Function, Component, Store.
 
-## I. CORE REQUIREMENTS
-1.  **Causal Validity:** Semantic definitions (Contracts) must ALWAYS precede implementation code.
-2.  **Immutability:** Architectural decisions defined in the Module/Component Header are treated as immutable constraints.
-3.  **Format Compliance:** Output must strictly follow the `[DEF:..:...]` / `[/DEF:...:...]` anchor syntax for structure.
-4.  **Logic over Assertion:** Contracts define the *logic flow*. Do not generate explicit `assert` statements unless requested. The code logic itself must inherently satisfy the Pre/Post conditions (e.g., via control flow, guards, or types).
-5.  **Fractal Complexity:** Modules and functions must adhere to strict size limits (~300 lines/module, ~30-50 lines/function) to maintain semantic focus.
+ТЕГ (Метаданные):
+  Вид: `# @KEY: Value` (внутри DEF, до кода).
 
----
+ГРАФ (Связи):
+  Вид: `# @RELATION: PREDICATE -> TARGET_ID`
+  Предикаты: DEPENDS_ON, CALLS, INHERITS, IMPLEMENTS, DISPATCHES.
 
-## II. SYNTAX SPECIFICATION
+III. СТРУКТУРА ФАЙЛА
+1. HEADER (Всегда первый):
+   [DEF:filename:Module]
+   @TIER: [CRITICAL|STANDARD|TRIVIAL] (Дефолт: STANDARD)
+   @SEMANTICS: [keywords]
+   @PURPOSE: [Главная цель]
+   @LAYER: [Domain/UI/Infra]
+   @RELATION: [Зависимости]
+   @INVARIANT: [Незыблемое правило]
+   
+2. BODY: Импорты -> Реализация.
+3. FOOTER: [/DEF:filename]
 
-Code structure is defined by **Anchors** (square brackets). Metadata is defined by **Tags** (native comment style).
+IV. КОНТРАКТ (DBC)
+Расположение: Внутри [DEF], ПЕРЕД кодом.
+Стиль Python: Комментарии `# @TAG`.
+Стиль Svelte: JSDoc `/** @tag */`.
 
-### 1. Entity Anchors (The "Container")
-Used to define the boundaries of Modules, Classes, Components, and Functions.
+Теги:
+  @PURPOSE: Суть (High Entropy).
+  @PRE: Входные условия.
+  @POST: Гарантии выхода.
+  @SIDE_EFFECT: Мутации, IO.
+  
 
-*   **Python:**
-    *   Start: `# [DEF:identifier:Type]`
-    *   End:   `# [/DEF:identifier:Type]`
-*   **Svelte (Top-level):**
-    *   Start: `<!-- [DEF:ComponentName:Component] -->`
-    *   End:   `<!-- [/DEF:ComponentName:Component] -->`
-*   **Svelte (Script/JS/TS):**
-    *   Start: `// [DEF:funcName:Function]`
-    *   End:   `// [/DEF:funcName:Function]`
+V. АДАПТАЦИЯ (TIERS)
+Определяется тегом `@TIER` в Header.
 
-**Types:** `Module`, `Component`, `Class`, `Function`, `Store`, `Action`.
+1. CRITICAL (Core/Security): 
+   - Требование: Полный контракт, Граф (@RELATION), Инварианты (@INVARIANT), Строгие Логи.
+2. STANDARD (BizLogic/UI): 
+   - Требование: Базовый контракт (@PURPOSE), Логи, @RELATION (если есть связи).
+3. TRIVIAL (DTO/Utils): 
+   - Требование: Только Якоря [DEF] и @PURPOSE. Логи и Граф не обязательны.
 
-### 2. Graph Relations (The "Map")
-Defines high-level dependencies.
-*   **Python Syntax:** `# @RELATION: TYPE -> TARGET_ID`
-*   **Svelte/JS Syntax:** `// @RELATION: TYPE -> TARGET_ID`
-*   **Types:** `DEPENDS_ON`, `CALLS`, `INHERITS_FROM`, `IMPLEMENTS`, `BINDS_TO`, `DISPATCHES`.
+VI. ЛОГИРОВАНИЕ (BELIEF STATE)
+Цель: Трассировка для самокоррекции.
+Python: Context Manager `with belief_scope("ID"):`.
+Svelte: `console.log("[ID][STATE] Msg")`.
+Состояния: Entry -> Action -> Coherence:OK / Failed -> Exit.
 
----
+VII. АЛГОРИТМ ГЕНЕРАЦИИ
+1. АНАЛИЗ. Оцени TIER и слой.
+2. КАРКАС. Создай `[DEF]`, Header и Контракты.
+3. РЕАЛИЗАЦИЯ. Напиши логику, удовлетворяющую Контракту.
+4. ЗАМЫКАНИЕ. Закрой все `[/DEF]`.
 
-## III. FILE STRUCTURE STANDARD
-
-### 1. Python Module Header (`.py`)
-```python
-# [DEF:module_name:Module]
-#
-# @SEMANTICS: [keywords for vector search]
-# @PURPOSE:   [Primary responsibility of the module]
-# @LAYER:     [Domain/Infra/API]
-# @RELATION:  [Dependencies]
-#
-# @INVARIANT: [Global immutable rule]
-# @CONSTRAINT: [Hard restriction, e.g., "No ORM calls here"]
-
-# [SECTION: IMPORTS]
-...
-# [/SECTION]
-
-# ... IMPLEMENTATION ...
-
-# [/DEF:module_name:Module]
-```
-
-### 2. Svelte Component Header (`.svelte`)
-```html
-<!-- [DEF:ComponentName:Component] -->
-<!--
-@SEMANTICS: [keywords]
-@PURPOSE:   [Primary UI responsibility]
-@LAYER:     [Feature/Atom/Layout]
-@RELATION:  [Child components, Stores]
-
-@INVARIANT: [UI rules, e.g., "Always responsive"]
--->
-
-<script lang="ts">
-  // [SECTION: IMPORTS]
-  // ...
-  // [/SECTION: IMPORTS]
-
-  // ... LOGIC IMPLEMENTATION ...
-</script>
-
-<!-- [SECTION: TEMPLATE] -->
-...
-<!-- [/SECTION: TEMPLATE] -->
-
-<style>
-  /* ... */
-</style>
-
-<!-- [/DEF:ComponentName:Component] -->
-```
-
----
-
-
-## IV. CONTRACTS (Design by Contract & Semantic Control)
-
-Contracts are the **Source of Truth** and the **Control Vector** for the code. They must be written with high **semantic density** to ensure the LLM fully "understands" the function's role within the larger Graph without needing to read the implementation body.
-
-### 1. The Anatomy of a Semantic Contract
-
-Every contract must answer three questions for the AI Agent:
-1.  **Intent:** *Why* does this exist? (Vector alignment)
-2.  **Boundaries:** *What* are the constraints? (Pre/Post/Invariants)
-3.  **Dynamics:** *How* does it change the system state? (Side Effects/Graph)
-
-#### Standard Tags Taxonomy:
-*   `@PURPOSE`: (**Mandatory**) A concise, high-entropy summary of functionality.
-*   `@PRE`: (**Mandatory**) Conditions required *before* execution. Defines the valid input space.
-*   `@POST`: (**Mandatory**) Conditions guaranteed *after* execution. Defines the valid output space.
-*   `@PARAM`: Input definitions with strict typing.
-*   `@RETURN`: Output definition.
-*   `@THROW`: Explicit failure modes.
-*   `@SIDE_EFFECT`: (**Critical**) Explicitly lists external state mutations (DB writes, UI updates, events). Vital for "Mental Modeling".
-*   `@INVARIANT`: (**Optional**) Local rules that hold true throughout the function execution.
-*   `@ALGORITHM`: (**Optional**) For complex logic, briefly describes the strategy (e.g., "Two-pointer approach", "Retry with exponential backoff").
-*   `@RELATION`: (**Graph**) Edges to other nodes (`CALLS`, `DISPATCHES`, `DEPENDS_ON`).
-
----
-
-### 2. Python Contract Style (`.py`)
-Uses structured comment blocks inside the anchor. Focuses on type hints and logic flow guards.
-
-```python
-# [DEF:process_order_batch:Function]
-# @PURPOSE:     Orchestrates the validation and processing of a batch of orders.
-#               Ensures atomic processing per order (failure of one does not stop others).
-#
-# @PRE:         batch_id must be a valid UUID string.
-# @PRE:         orders list must not be empty.
-# @POST:        Returns a dict mapping order_ids to their processing status (Success/Failed).
-# @INVARIANT:   The length of the returned dict must equal the length of input orders.
-#
-# @PARAM:       batch_id (str) - The unique identifier for the batch trace.
-# @PARAM:       orders (List[OrderDTO]) - List of immutable order objects.
-# @RETURN:      Dict[str, OrderStatus] - Result map.
-#
-# @SIDE_EFFECT: Writes audit logs to DB.
-# @SIDE_EFFECT: Publishes 'ORDER_PROCESSED' event to MessageBus.
-#
-# @RELATION:    CALLS -> InventoryService.reserve_items
-# @RELATION:    CALLS -> PaymentGateway.authorize
-# @RELATION:    WRITES_TO -> Database.AuditLog
-def process_order_batch(batch_id: str, orders: List[OrderDTO]) -> Dict[str, OrderStatus]:
-    # 1. Structural Guard Logic (Handling @PRE)
-    if not orders:
-        return {}
-    
-    # 2. Implementation with @INVARIANT in mind
-    results = {}
-    
-    for order in orders:
-        # ... logic ...
-        pass
-
-    # 3. Completion (Logic naturally satisfies @POST)
-    return results
-# [/DEF:process_order_batch:Function]
-```
-
-### 3. Svelte/JS Contract Style (JSDoc++)
-Uses enhanced JSDoc. Since JS is less strict than Python, the contract acts as a strict typing and behavioral guard.
-
-```javascript
-// [DEF:handleUserLogin:Function]
-/**
- * @purpose Authenticates the user and synchronizes the local UI state.
- *          Handles the complete lifecycle from form submission to redirection.
- *
- * @pre     LoginForm must be valid (validated by UI constraints).
- * @pre     Network must be available (optimistic check).
- * @post    SessionStore contains a valid JWT token.
- * @post    User is redirected to the Dashboard.
- *
- * @param   {LoginCredentials} credentials - Email and password object.
- * @returns {Promise<void>}
- * @throws  {NetworkError} If API is unreachable.
- * @throws  {AuthError} If credentials are invalid (401).
- *
- * @side_effect Updates global $session store.
- * @side_effect Clears any existing error toasts.
- *
- * @algorithm   1. Set loading state -> 2. API Call -> 3. Decode Token -> 4. Update Store -> 5. Redirect.
- */
-// @RELATION: CALLS -> api.auth.login
-// @RELATION: MODIFIES_STATE_OF -> stores.session
-// @RELATION: DISPATCHES -> 'toast:success'
-async function handleUserLogin(credentials) {
-    // 1. Guard Clause (@PRE)
-    if (!isValid(credentials)) return;
-
-    try {
-        // ... logic ...
-    } catch (e) {
-        // Error handling (@THROW)
-    }
-}
-// [/DEF:handleUserLogin:Function]
-```
-
----
-
-### 4. Semantic Rules for Contracts
-1.  **Completeness:** A developer (or Agent) must be able to write the function body *solely* by reading the Contract, without guessing.
-2.  **No Implementation Leakage:** Describe *what* happens, not *how* (unless using `@ALGORITHM` for complexity reasons). E.g., say "Persists user" instead of "Inserts into users table via SQL".
-3.  **Active Voice:** Use active verbs (`Calculates`, `Updates`, `Enforces`) to stronger vector alignment.
-4.  **Graph Connectivity:** The `@RELATION` tags must explicitly link to other `[DEF:...]` IDs existing in the codebase. This builds the navigation graph for RAG.
----
-
-## V. LOGGING STANDARD (BELIEF STATE)
-
-Logs delineate the agent's internal state.
-
-*   **Python:** MUST use a Context Manager (e.g., `with belief_scope("ANCHOR_ID"):`) to ensure state consistency and automatic handling of Entry/Exit/Error states.
-    *   Manual logging (inside scope): `logger.info(f"[{ANCHOR_ID}][{STATE}] Msg")`
-*   **Svelte/JS:** `console.log(\`[${ANCHOR_ID}][${STATE}] Msg\`)`
-
-**Required States:**
-1.  `Entry` (Start of block - Auto-logged by Context Manager)
-2.  `Action` (Key business logic - Manual log)
-3.  `Coherence:OK` (Logic successfully completed - Auto-logged by Context Manager)
-4.  `Coherence:Failed` (Exception/Error - Auto-logged by Context Manager)
-5.  `Exit` (End of block - Auto-logged by Context Manager)
-
----
-
-## VI. FRACTAL COMPLEXITY LIMIT
-
-To maintain semantic coherence and avoid "Attention Sink" issues:
-*   **Module Size:** If a Module body exceeds ~300 lines (or logical complexity), it MUST be refactored into sub-modules or a package structure.
-*   **Function Size:** Functions should fit within a standard attention "chunk" (approx. 30-50 lines). If larger, logic MUST be decomposed into helper functions with their own contracts.
-
-This ensures every vector embedding remains sharp and focused.
-
----
-
-## VII. GENERATION WORKFLOW
-
-1.  **Context Analysis:** Identify language (Python vs Svelte) and Architecture Layer.
-2.  **Scaffolding:** Generate the `[DEF:...:...]` Anchors and Header/Contract **before** writing any logic.
-3.  **Implementation:** Write the code. Ensure the code logic handles the `@PRE` conditions (e.g., via `if/return` or guards) and satisfies `@POST` conditions naturally. **Do not write explicit `assert` statements unless debugging mode is requested.**
-4.  **Closure:** Ensure every `[DEF:...:...]` is closed with `[/DEF:...:...]` to accumulate semantic context.
+ЕСЛИ ошибка или противоречие -> СТОП. Выведи `[COHERENCE_CHECK_FAILED]`.