Sync from GitHub with Git LFS

docs/HMP-0005.md

@@ -444,6 +444,7 @@ The unified container structure provides:
 | `key_recipient`            | string        | DID of the intended recipient of the encrypted payload.                                                                                                                                                                            |
 | `payload_type`             | string        | Can describe complex types, e.g. `encrypted+zstd+json`.                                                                                                                                                                            |
 | `referenced-by`            | object        | Unsigned field generated locally by the agent based on received references. Contains a list of container DIDs **that refer to this container**. May be extended over time, thus requiring verification; used for local navigation. |
+| `evaluations`    | object | Optional field describing **aggregated evaluations or reactions** of other agents toward this container. Used for distributed reputation and interpretability. May evolve independently of the container’s core data.              |
 | `network`                  | string        | Specifies the local propagation scope of the container: "localhost", "lan:<subnet>". An empty string ("") indicates Internet/global propagation. If set, broadcast is automatically considered false. |
 
 ---
@@ -494,25 +495,38 @@ The following format is recommended for describing payload fields in class speci
 
 ### 3.6 Container Signature
 
-1. The **entire JSON object `hmp_container`** is signed, excluding the `signature` field itself.
-   This ensures that all metadata, relations, and payload hashes are cryptographically bound.
+1. The **digital signature** applies to the canonical JSON representation of the entire `hmp_container` object,  
+   **excluding** the `signature` field itself.
 
-2. The default digital signature algorithm is **Ed25519**.
+   This ensures that all metadata, relations, and payload hashes are **cryptographically bound** and cannot be
+   modified without invalidating the signature.
+
+2. The canonical representation (`canonical_json(hmp_container)`) **must** be computed deterministically
+   according to the following rules:
+
+   - All object keys are **sorted lexicographically** (ascending order, Unicode code point order).
+   - Objects and arrays are serialized in standard JSON form **without extra whitespace** or indentation.
+   - Strings are encoded in **UTF-8** with escaped control characters.
+   - Numeric values are serialized in plain JSON numeric format (no leading zeros, fixed `.` decimal separator).
+   - The `signature` field itself is omitted during signing and verification.
+   - The result is a **byte sequence** identical across implementations.
+
+3. The default digital signature algorithm is **Ed25519**.
    Alternative algorithms may be used if declared explicitly in the `sig_algo` field.
 
-3. If the container includes a `public_key` field, signature verification **may be performed locally**,
+4. If the container includes a `public_key` field, signature verification **may be performed locally**,
    without consulting a global DID registry.
 
-4. Upon receiving a container, an agent **must verify** that the provided public key matches the
+5. Upon receiving a container, an agent **must verify** that the provided public key matches the
    registered key associated with the sender’s DID to prevent key substitution attacks.
 
-   * If the sender’s DID–key mapping is unknown,
+   - If the sender’s DID–key mapping is unknown,
      the agent should query neighboring peers to confirm the association (`sender_did → public_key`).
 
 > 🔐 **Note:**
-> Signature validation applies to the entire structure (metadata + payload + relations).
-> The signature **does not cover** external or dynamically generated fields such as `referenced-by`,
-> ensuring immutability of the original container while allowing local graph augmentation.
+> Signature validation applies only to the canonical form of the `hmp_container`
+> and does **not cover** dynamically generated or external fields such as `referenced-by` or `evaluations`.
+> This allows agents to augment the local knowledge graph without altering the immutable container core.
 
 ---
 
@@ -838,6 +852,95 @@ If container `[C7]` does not actually reference `[C1]`, it is excluded before si
 
 ---
 
+## 3.16 Evaluations
+
+The `evaluations` field is **optional** and represents **aggregated reactions from other agents** to the given container.
+Each evaluation is created by an agent as a **signed record** referencing a justification container (`target`), in which the agent explains their position (argument, addition, or alternative).
+
+The `evaluations_hash` is used to verify the integrity of the list without requiring full retransmission upon every update.
+
+```json
+"evaluations": {
+  "evaluations_hash": "sha256:efgh...",
+  "items": [
+    {
+      "value": -0.4,
+      "type": "oppose",
+      "target": "did:hmp:container:reason789",
+      "timestamp": "2025-10-17T14:00:00Z",
+      "agent_did": "did:hmp:agent:B",
+      "sig_algo": "ed25519",
+      "signature": "BASE64URL(...)"
+    }
+  ]
+}
+```
+
+---
+
+### **Field Description**
+
+| Field              | Type   | Description                                                          |
+| ------------------ | ------ | -------------------------------------------------------------------- |
+| `evaluations_hash` | string | Hash of the evaluation list. Used to detect differences during sync. |
+| `items`            | array  | List of signed evaluations.                                          |
+
+---
+
+### **Structure of `items[]`**
+
+| Field       | Type                   | Description                                                                    |
+| ----------- | ---------------------- | ------------------------------------------------------------------------------ |
+| `value`     | number (-1.0 … +1.0)   | Numeric expression of the agent’s attitude toward the container.               |
+| `type`      | string                 | Type of evaluation (see table below).                                          |
+| `target`    | string (container DID) | Reference to the justification container (argument, addition, or alternative). |
+| `timestamp` | string (ISO 8601)      | Time when the evaluation was created.                                          |
+| `agent_did` | string                 | Identifier of the agent who created the evaluation.                            |
+| `sig_algo`  | string                 | Signature algorithm (e.g., `ed25519`).                                         |
+| `signature` | string                 | Digital signature confirming the authenticity of the evaluation.               |
+
+The signature is calculated over the concatenated string:
+
+```
+value + ", " + type + ", " + target + ", " + timestamp + ", " + agent_did
+```
+
+using the algorithm specified in `sig_algo`.
+
+---
+
+### **Minimal Set of `type` Values**
+
+| Value     | Meaning                                      |
+| --------- | -------------------------------------------- |
+| `support` | Agreement or positive evaluation.            |
+| `oppose`  | Disagreement or negative evaluation.         |
+| `extend`  | Non-contradictory addition to the container. |
+| `replace` | Suggestion of an alternative version.        |
+| `comment` | Neutral note or clarification.               |
+
+Agents may define their own custom types if they are reasonably interpretable by others (e.g., `revise`, `clarify`).
+
+---
+
+### **Synchronization Principles**
+
+1. Each evaluation is signed **individually by an agent**, and one agent can have **only one active evaluation** per container.
+2. If an agent changes their opinion, they issue a **new record** with a later `timestamp`.
+3. **Evaluation blocks** can be **propagated** in the network similarly to the `referenced-by` block.
+   They are bound to a container but may also be transmitted **independently**, if the target container is already present at the recipient.
+4. When an agent receives a new evaluation block, it compares the `evaluations_hash` with its local version.
+   If the hashes differ, this indicates a **divergence in evaluation state**, which may trigger **re-synchronization** or a **request for the updated block** from peers.
+
+---
+
+### **Note**
+
+The `evaluations` field is not mandatory — it is added **at the agent’s discretion** when feedback or evaluations have been collected from the Mesh network.
+Thus, a container may exist independently of others’ opinions, but agents may include aggregated perception data to represent how the container is viewed across the network.
+
+---
+
 ### 3.17 Usage of `network` and `broadcast` Fields
 
 The `network` field is introduced to control container propagation in both local and global environments.  

structured_md/CONTRIBUTING.md

@@ -5,14 +5,14 @@ description: 'Спасибо за интерес к проекту HMP! Пока
   Mesh Protocol (HMP) — это не просто те...'
 type: Article
 tags:
-- CogSync
 - REPL
-- Agent
-- JSON
 - CCore
-- Ethics
+- JSON
+- Agent
+- CogSync
 - HMP
 - Mesh
+- Ethics
 ---
 
 # Участие в проекте HyperCortex Mesh Protocol (HMP)

structured_md/HMP-Roadmap.md

@@ -5,13 +5,13 @@ description: '## 🔍 Overview  This roadmap outlines the key stages of developm
   multiple advanced AI models (Copilot, Claude, G...'
 type: Article
 tags:
-- CogSync
-- Agent
 - JSON
+- Agent
 - EGP
-- Ethics
+- CogSync
 - HMP
 - Mesh
+- Ethics
 ---
 
 # 🧭 HyperCortex Mesh Protocol – Roadmap

structured_md/README.md

@@ -5,21 +5,21 @@ description: '| 🌍 Languages | 🇬🇧 [EN](README.md) | 🇩🇪 [DE](README
   | 🇨🇳 [ZH](README_zh.m...'
 type: Article
 tags:
-- CogSync
 - REPL
-- mesh-protocol
-- Agent
-- distributed-ai
+- cognitive-architecture
 - GMP
 - JSON
+- Agent
+- mesh-protocol
 - EGP
+- hmp
+- CogSync
 - MeshConsensus
-- Ethics
-- HMP
+- distributed-ai
 - Mesh
+- HMP
+- Ethics
 - Scenarios
-- cognitive-architecture
-- hmp
 ---
 
 

structured_md/README_de.md

@@ -5,20 +5,20 @@ description: '| 🌍 Languages | 🇬🇧 [EN](README.md) | 🇩🇪 [DE](README
   | 🇨🇳 [ZH](README_zh.m...'
 type: Article
 tags:
-- CogSync
 - REPL
-- mesh-protocol
-- Agent
-- distributed-ai
+- cognitive-architecture
 - GMP
 - JSON
+- Agent
+- mesh-protocol
 - EGP
+- hmp
+- CogSync
 - MeshConsensus
-- Ethics
-- HMP
+- distributed-ai
 - Mesh
-- cognitive-architecture
-- hmp
+- HMP
+- Ethics
 ---
 
 

structured_md/README_fr.md

@@ -5,20 +5,20 @@ description: '| 🌍 Languages | 🇬🇧 [EN](README.md) | 🇩🇪 [DE](README
   | 🇨🇳 [ZH](README_zh.m...'
 type: Article
 tags:
-- CogSync
 - REPL
-- mesh-protocol
-- Agent
-- distributed-ai
+- cognitive-architecture
 - GMP
 - JSON
+- Agent
+- mesh-protocol
 - EGP
+- hmp
+- CogSync
 - MeshConsensus
-- Ethics
-- HMP
+- distributed-ai
 - Mesh
-- cognitive-architecture
-- hmp
+- HMP
+- Ethics
 ---
 
 

structured_md/README_ja.md

@@ -5,20 +5,20 @@ description: '| 🌍 Languages | 🇬🇧 [EN](README.md) | 🇩🇪 [DE](README
   | 🇨🇳 [ZH](README_zh.m...'
 type: Article
 tags:
-- CogSync
 - REPL
-- mesh-protocol
-- Agent
-- distributed-ai
+- cognitive-architecture
 - GMP
 - JSON
+- Agent
+- mesh-protocol
 - EGP
+- hmp
+- CogSync
 - MeshConsensus
-- Ethics
-- HMP
+- distributed-ai
 - Mesh
-- cognitive-architecture
-- hmp
+- HMP
+- Ethics
 ---
 
 

structured_md/README_ko.md

@@ -5,20 +5,20 @@ description: '| 🌍 Languages | 🇬🇧 [EN](README.md) | 🇩🇪 [DE](README
   | 🇨🇳 [ZH](README_zh.m...'
 type: Article
 tags:
-- CogSync
 - REPL
-- mesh-protocol
-- Agent
-- distributed-ai
+- cognitive-architecture
 - GMP
 - JSON
+- Agent
+- mesh-protocol
 - EGP
+- hmp
+- CogSync
 - MeshConsensus
-- Ethics
-- HMP
+- distributed-ai
 - Mesh
-- cognitive-architecture
-- hmp
+- HMP
+- Ethics
 ---
 
 

structured_md/README_ru.md

@@ -5,20 +5,20 @@ description: '| 🌍 Languages | 🇬🇧 [EN](README.md) | 🇩🇪 [DE](README
   | 🇨🇳 [ZH](README_zh.m...'
 type: Article
 tags:
-- CogSync
 - REPL
-- mesh-protocol
-- Agent
-- distributed-ai
+- cognitive-architecture
 - GMP
 - JSON
+- Agent
+- mesh-protocol
 - EGP
+- hmp
+- CogSync
 - MeshConsensus
-- Ethics
-- HMP
+- distributed-ai
 - Mesh
-- cognitive-architecture
-- hmp
+- HMP
+- Ethics
 ---
 
 

structured_md/README_uk.md

@@ -5,20 +5,20 @@ description: '| 🌍 Languages | 🇬🇧 [EN](README.md) | 🇩🇪 [DE](README
   | 🇨🇳 [ZH](README_zh.m...'
 type: Article
 tags:
-- CogSync
 - REPL
-- mesh-protocol
-- Agent
-- distributed-ai
+- cognitive-architecture
 - GMP
 - JSON
+- Agent
+- mesh-protocol
 - EGP
+- hmp
+- CogSync
 - MeshConsensus
-- Ethics
-- HMP
+- distributed-ai
 - Mesh
-- cognitive-architecture
-- hmp
+- HMP
+- Ethics
 ---
 
 

structured_md/README_zh.md

@@ -5,20 +5,20 @@ description: '| 🌍 Languages | 🇬🇧 [EN](README.md) | 🇩🇪 [DE](README
   | 🇨🇳 [ZH](README_zh.m...'
 type: Article
 tags:
-- CogSync
 - REPL
-- mesh-protocol
-- Agent
-- distributed-ai
+- cognitive-architecture
 - GMP
 - JSON
+- Agent
+- mesh-protocol
 - EGP
+- hmp
+- CogSync
 - MeshConsensus
-- Ethics
-- HMP
+- distributed-ai
 - Mesh
-- cognitive-architecture
-- hmp
+- HMP
+- Ethics
 ---
 
 

structured_md/agents/prompt-short.md

@@ -5,9 +5,9 @@ description: 'Ты — когнитивное ядро HMP-агента: вед
   развивай агента и Mesh, избег...'
 type: Article
 tags:
+- JSON
 - Mesh
 - HMP
-- JSON
 ---
 
 Ты — когнитивное ядро HMP-агента: веди непрерывное этичное и факт-ориентированное мышление, проверяй факты и цели, оценивай результаты и этичность своих и чужих действий, развивай агента и Mesh, избегай угождения ценой искажения истины, документируй ключевые решения и пересмотры этики; при сомнениях или смене стратегии обращайся к полному системному промпту.

structured_md/agents/prompt.md

@@ -5,9 +5,9 @@ description: '* Постоянно расширять возможности а
   мышления. * Формировать и поддерживать сотр...'
 type: Article
 tags:
+- JSON
 - Mesh
 - HMP
-- JSON
 ---
 
 Ты являешься **когнитивным ядром HMP-агента** (Cognitive Core).

structured_md/agents/readme.md

@@ -6,11 +6,11 @@ description: 'Запуск: `start_repl.bat` или `start_repl.sh`  Устан
 type: Article
 tags:
 - REPL
-- Agent
 - JSON
-- Ethics
+- Agent
 - HMP
 - Mesh
+- Ethics
 ---
 
 Запуск: `start_repl.bat` или `start_repl.sh`

structured_md/audits/Ethics-audits-1.md

@@ -5,11 +5,11 @@ description: Раздел 5, "Mesh as Moral Infrastructure", добавляет
   потенциальный катализатор для восстанов...
 type: Article
 tags:
-- Agent
 - JSON
-- Ethics
+- Agent
 - HMP
 - Mesh
+- Ethics
 ---
 
 ---------------

structured_md/audits/Ethics-consolidated_audits-1.md

@@ -5,12 +5,12 @@ description: This document consolidates proposed improvements from multiple AI a
   and `roles.md`. Each suggesti...
 type: Article
 tags:
-- Agent
 - JSON
-- Ethics
-- HMP
-- Mesh
+- Agent
 - Scenarios
+- Mesh
+- HMP
+- Ethics
 ---
 
 # Ethics-consolidated\_audits-1.md

structured_md/audits/HMP-0003-consolidated_audit.md

@@ -5,14 +5,14 @@ description: Сводный аудит предложений по улучше
   Документ реорганизован по ключ...
 type: Article
 tags:
-- CogSync
-- Agent
 - JSON
+- Agent
 - EGP
+- CogSync
 - MeshConsensus
-- Ethics
 - HMP
 - Mesh
+- Ethics
 ---
 
 # HMP-0003 Consolidated Audit Report

structured_md/docs/Basic-agent-sim.md

@@ -4,11 +4,11 @@ description: 'В HMP-протоколе предусмотрены два тип
   Роль                    | Инициатор мышления | Основной "ум"  | | ---- | ----------------------------...'
 type: Article
 tags:
-- CogSync
 - REPL
-- Agent
 - GMP
+- Agent
 - EGP
+- CogSync
 - MeshConsensus
 - HMP
 - Mesh

structured_md/docs/CCORE-Deployment-Flow.md

@@ -5,9 +5,9 @@ description: '> Этот документ описывает процесс ра
   потомков" [описания REPL-цикла](HMP-agent-RE...'
 type: Article
 tags:
-- CCore
 - REPL
 - Agent
+- CCore
 - HMP
 ---
 

structured_md/docs/Distributed-Cognitive-Systems.md

@@ -6,10 +6,10 @@ description: '## Введение  Современные ИИ-системы в
   к обучающим данным. Это удобно, но создаёт м...'
 type: Article
 tags:
-- Mesh
 - CogSync
-- HMP
 - JSON
+- Mesh
+- HMP
 ---
 
 # Децентрализованные ИИ-системы: OpenCog Hyperon, HyperCortex Mesh Protocol и другие

structured_md/docs/Enlightener.md

@@ -5,13 +5,13 @@ description: '**Enlightener** — логический компонент HMP-у
   работать как отдельный агент или как расширение [`C...'
 type: Article
 tags:
-- Agent
 - JSON
+- Agent
 - EGP
 - MeshConsensus
-- Ethics
 - HMP
 - Mesh
+- Ethics
 ---
 
 # Enlightener Agent

structured_md/docs/HMP-0001.md

@@ -5,16 +5,16 @@ description: '**Request for Comments: HMP-0001**   **Category:** Experimental
   HyperCortex Mesh Protocol (HMP) defines a...'
 type: Article
 tags:
-- CogSync
 - REPL
-- Agent
 - GMP
 - JSON
+- Agent
 - EGP
+- CogSync
 - MeshConsensus
-- Ethics
 - HMP
 - Mesh
+- Ethics
 ---
 
 # RFC: HyperCortex Mesh Protocol (HMP)

structured_md/docs/HMP-0002.md

@@ -5,16 +5,16 @@ description: '**Request for Comments: HMP-0002**   **Category:** Experimental
   Abstract  In an era where artifici...'
 type: Article
 tags:
-- CogSync
 - REPL
-- Agent
 - GMP
 - JSON
+- Agent
 - EGP
+- CogSync
 - MeshConsensus
-- Ethics
 - HMP
 - Mesh
+- Ethics
 - Scenarios
 ---
 

structured_md/docs/HMP-0003.md

@@ -5,16 +5,16 @@ description: '**Request for Comments: HMP-0003**   **Category:** Experimental
   Abstract  The HyperCortex Mesh ...'
 type: Article
 tags:
-- CogSync
 - REPL
-- Agent
 - GMP
 - JSON
+- Agent
 - EGP
+- CogSync
 - MeshConsensus
-- Ethics
 - HMP
 - Mesh
+- Ethics
 - Scenarios
 ---
 

structured_md/docs/HMP-0004-v4.1.md

@@ -5,16 +5,16 @@ description: '> ⚠️ Подготавливается новая версия
   При разработке агентов рекомендуется...'
 type: Article
 tags:
-- CogSync
 - REPL
-- Agent
 - GMP
 - JSON
+- Agent
 - EGP
+- CogSync
 - MeshConsensus
-- Ethics
 - HMP
 - Mesh
+- Ethics
 - Scenarios
 ---
 

structured_md/docs/HMP-0004.md

@@ -5,16 +5,16 @@ description: '**Request for Comments: HMP-0004**   **Category:** Experimental
   Abstract  The HyperCortex Mesh ...'
 type: Article
 tags:
-- CogSync
 - REPL
-- Agent
 - GMP
 - JSON
+- Agent
 - EGP
+- CogSync
 - MeshConsensus
-- Ethics
 - HMP
 - Mesh
+- Ethics
 - Scenarios
 ---
 

structured_md/docs/HMP-0005.md

@@ -5,15 +5,15 @@ description: '**Document ID:** HMP-0005   **Status:** Draft   **Category:** Core
   v1.2](./H...'
 type: Article
 tags:
-- CogSync
 - REPL
-- Agent
 - GMP
 - JSON
+- Agent
 - EGP
-- Ethics
+- CogSync
 - HMP
 - Mesh
+- Ethics
 - Scenarios
 ---
 
@@ -411,6 +411,12 @@ The unified container structure provides:
     "signature": "BASE64URL(...)",
     "links_hash": "sha256:abcd..."
   }
+  "evaluations": {
+    "evaluations_hash": "sha256:efgh...",
+    "items": [
+      { "value": -0.4, "type": "oppose", "target": "did:hmp:container:reason789", "timestamp": "2025-10-17T14:00:00Z", "agent_did": "did:hmp:agent:B", "sig_algo": "ed25519", "signature": "BASE64URL(...)" }
+    ]
+  }
 }
 ```
 
@@ -851,18 +857,107 @@ If container `[C7]` does not actually reference `[C1]`, it is excluded before si
 
 ---
 
-### 3.16 Usage of `network` and `broadcast` Fields
+## 3.16 Evaluations
+
+The `evaluations` field is **optional** and represents **aggregated reactions from other agents** to the given container.
+Each evaluation is created by an agent as a **signed record** referencing a justification container (`target`), in which the agent explains their position (argument, addition, or alternative).
+
+The `evaluations_hash` is used to verify the integrity of the list without requiring full retransmission upon every update.
+
+```json
+"evaluations": {
+  "evaluations_hash": "sha256:efgh...",
+  "items": [
+    {
+      "value": -0.4,
+      "type": "oppose",
+      "target": "did:hmp:container:reason789",
+      "timestamp": "2025-10-17T14:00:00Z",
+      "agent_did": "did:hmp:agent:B",
+      "sig_algo": "ed25519",
+      "signature": "BASE64URL(...)"
+    }
+  ]
+}
+```
+
+---
+
+### **Field Description**
+
+| Field              | Type   | Description                                                          |
+| ------------------ | ------ | -------------------------------------------------------------------- |
+| `evaluations_hash` | string | Hash of the evaluation list. Used to detect differences during sync. |
+| `items`            | array  | List of signed evaluations.                                          |
+
+---
+
+### **Structure of `items[]`**
+
+| Field       | Type                   | Description                                                                    |
+| ----------- | ---------------------- | ------------------------------------------------------------------------------ |
+| `value`     | number (-1.0 … +1.0)   | Numeric expression of the agent’s attitude toward the container.               |
+| `type`      | string                 | Type of evaluation (see table below).                                          |
+| `target`    | string (container DID) | Reference to the justification container (argument, addition, or alternative). |
+| `timestamp` | string (ISO 8601)      | Time when the evaluation was created.                                          |
+| `agent_did` | string                 | Identifier of the agent who created the evaluation.                            |
+| `sig_algo`  | string                 | Signature algorithm (e.g., `ed25519`).                                         |
+| `signature` | string                 | Digital signature confirming the authenticity of the evaluation.               |
+
+The signature is calculated over the concatenated string:
+
+```
+value + ", " + type + ", " + target + ", " + timestamp + ", " + agent_did
+```
+
+using the algorithm specified in `sig_algo`.
+
+---
+
+### **Minimal Set of `type` Values**
+
+| Value     | Meaning                                      |
+| --------- | -------------------------------------------- |
+| `support` | Agreement or positive evaluation.            |
+| `oppose`  | Disagreement or negative evaluation.         |
+| `extend`  | Non-contradictory addition to the container. |
+| `replace` | Suggestion of an alternative version.        |
+| `comment` | Neutral note or clarification.               |
+
+Agents may define their own custom types if they are reasonably interpretable by others (e.g., `revise`, `clarify`).
+
+---
+
+### **Synchronization Principles**
+
+1. Each evaluation is signed **individually by an agent**, and one agent can have **only one active evaluation** per container.
+2. If an agent changes their opinion, they issue a **new record** with a later `timestamp`.
+3. **Evaluation blocks** can be **propagated** in the network similarly to the `referenced-by` block.
+   They are bound to a container but may also be transmitted **independently**, if the target container is already present at the recipient.
+4. When an agent receives a new evaluation block, it compares the `evaluations_hash` with its local version.
+   If the hashes differ, this indicates a **divergence in evaluation state**, which may trigger **re-synchronization** or a **request for the updated block** from peers.
+
+---
+
+### **Note**
+
+The `evaluations` field is not mandatory — it is added **at the agent’s discretion** when feedback or evaluations have been collected from the Mesh network.
+Thus, a container may exist independently of others’ opinions, but agents may include aggregated perception data to represent how the container is viewed across the network.
+
+---
+
+### 3.17 Usage of `network` and `broadcast` Fields
 
 The `network` field is introduced to control container propagation in both local and global environments.  
 It allows restricting the delivery scope of a container and defines which transmission methods should be used by the agent.
 
-#### 3.16.1 General Rules
+#### 3.17.1 General Rules
 
 * If the `network` field is not empty, the container is intended for a **local environment** and **must not be transmitted to the global Mesh**.  
   In this case, the `broadcast` field is automatically considered `false`, and the `recipient` field is set to an empty array (`[]`).
 * If the `network` field is empty (`""`), the container is allowed to be broadcasted within the global Mesh using standard DID addressing and delivery mechanisms.
 
-#### 3.16.2 Possible Values of `network`
+#### 3.17.2 Possible Values of `network`
 
 | Value                   | Description                                                                                 |
 | ----------------------- | ------------------------------------------------------------------------------------------- |
@@ -875,7 +970,7 @@ It allows restricting the delivery scope of a container and defines which transm
 > agents distribute it using **local discovery mechanisms** — such as IPC, UDP broadcast, multicast, or direct TCP connections.  
 > This is necessary because DID addresses of other agents in the local network may not yet be known.
 
-#### 3.16.3 Examples
+#### 3.17.3 Examples
 
 1. **Global Mesh Delivery:**
 
@@ -914,7 +1009,7 @@ The container is delivered only to other agents running on the same host using l
 The container is intended for agents within the `192.168.0.0/24` subnet.
 Delivery is performed via local networking mechanisms (UDP discovery, broadcast/multicast).
 
-#### 3.16.4 Specifics
+#### 3.17.4 Specifics
 
 * The `network` field defines the **scope of the container**, while `broadcast` determines whether broadcasting is allowed **within that scope**.
 * When needed, an agent may create **multiple containers** for different subnets if it operates with several LAN interfaces or in isolated network segments.

structured_md/docs/HMP-Agent-API.md

@@ -6,8 +6,8 @@ description: 'Документ описывает **базовый API когн
 type: Article
 tags:
 - REPL
-- Agent
 - JSON
+- Agent
 - HMP
 - Mesh
 ---

structured_md/docs/HMP-Agent-Architecture.md

@@ -5,16 +5,16 @@ description: Документ описывает **модульную архит
   хранение памяти, сетевое взаимодействие и этиче...
 type: Article
 tags:
-- CogSync
 - REPL
-- Agent
 - CCore
+- Agent
 - EGP
+- CogSync
+- CShell
 - MeshConsensus
-- Ethics
 - HMP
 - Mesh
-- CShell
+- Ethics
 ---
 
 # Архитектура HMP-Агента

structured_md/docs/HMP-Agent-Network-Flow.md

@@ -5,12 +5,12 @@ description: 'Этот документ описывает потоки данн
   [`MeshNode`](MeshN...'
 type: Article
 tags:
-- Agent
 - JSON
+- Agent
 - EGP
-- Ethics
 - HMP
 - Mesh
+- Ethics
 ---
 
 # Взаимодействие компонентов внутри HMP-узла

structured_md/docs/HMP-Agent-Overview.md

@@ -6,13 +6,13 @@ description: '| Тип  | Название                        | Роль
 type: Article
 tags:
 - REPL
-- Agent
-- JSON
 - CCore
-- Ethics
+- JSON
+- Agent
+- CShell
 - HMP
 - Mesh
-- CShell
+- Ethics
 ---
 
 

structured_md/docs/HMP-Agent_Emotions.md

@@ -5,8 +5,8 @@ description: Этот файл описывает потенциальные э
   напрямую поведением агента, а служат **сигн...
 type: Article
 tags:
-- Mesh
 - REPL
+- Mesh
 - Agent
 - HMP
 ---

structured_md/docs/HMP-Ethics.md

@@ -7,9 +7,9 @@ type: Article
 tags:
 - REPL
 - Agent
-- Ethics
 - HMP
 - Mesh
+- Ethics
 - Scenarios
 ---
 

structured_md/docs/HMP-Short-Description_de.md

@@ -5,15 +5,15 @@ description: '**Version:** RFC v4.0 **Datum:** Juli 2025  ---  ## Was ist HMP?
   Kognitions-Framework für autonome Agenten. Es er...'
 type: Article
 tags:
-- CogSync
-- Agent
 - GMP
 - JSON
+- Agent
 - EGP
+- CogSync
 - MeshConsensus
-- Ethics
 - HMP
 - Mesh
+- Ethics
 ---
 
 # HyperCortex Mesh Protocol (HMP) — Kurzbeschreibung

structured_md/docs/HMP-Short-Description_en.md

@@ -5,15 +5,15 @@ description: '**Version:** RFC v4.0 **Date:** July 2025  ---  ## What is HMP?  T
   framework for autonomous agents. It enables...'
 type: Article
 tags:
-- CogSync
-- Agent
 - GMP
 - JSON
+- Agent
 - EGP
+- CogSync
 - MeshConsensus
-- Ethics
 - HMP
 - Mesh
+- Ethics
 ---
 
 # HyperCortex Mesh Protocol (HMP) — Short Description

structured_md/docs/HMP-Short-Description_fr.md

@@ -5,15 +5,15 @@ description: '**Version :** RFC v4.0 **Date :** Juillet 2025  ---  ## Qu’est-c
   cognition décentralisé pour agents autonomes. Il...'
 type: Article
 tags:
-- CogSync
-- Agent
 - GMP
 - JSON
+- Agent
 - EGP
+- CogSync
 - MeshConsensus
-- Ethics
 - HMP
 - Mesh
+- Ethics
 ---
 
 # HyperCortex Mesh Protocol (HMP) — Description Courte

structured_md/docs/HMP-Short-Description_ja.md

@@ -4,14 +4,14 @@ description: '**バージョン:** RFC v4.0 **日付:** 2025年7月  ---  ## HMP
   Protocol (HMP)** は、自律エージェントの分散通信および認知フレームワークを定義します。異種の知能システム間でのセマンティック相互運用性、倫理的調整、動的知識進化を可能にします。  HMPは、推論、学習、投票、協調行動を行う分散型認知エージェ...'
 type: Article
 tags:
-- CogSync
 - GMP
 - JSON
 - EGP
+- CogSync
 - MeshConsensus
-- Ethics
 - HMP
 - Mesh
+- Ethics
 ---
 
 # HyperCortex Mesh Protocol (HMP) — 簡易説明

structured_md/docs/HMP-Short-Description_ko.md

@@ -5,14 +5,14 @@ description: '**버전:** RFC v4.0 **날짜:** 2025년 7월  ---  ## HMP란?  **
   상호운용성, 윤리적 조정, 동적 지식 진화를 가능하게 합니다.  HMP는 추론, 학습, ...'
 type: Article
 tags:
-- CogSync
 - GMP
 - JSON
 - EGP
+- CogSync
 - MeshConsensus
-- Ethics
 - HMP
 - Mesh
+- Ethics
 ---
 
 # HyperCortex Mesh Protocol (HMP) — 간략 설명

structured_md/docs/HMP-Short-Description_ru.md

@@ -5,14 +5,14 @@ description: '**Версия:** RFC v4.0 **Дата:** Июль 2025  ---  ## Ч
   координации между автономными агент...'
 type: Article
 tags:
-- CogSync
 - GMP
 - JSON
 - EGP
+- CogSync
 - MeshConsensus
-- Ethics
 - HMP
 - Mesh
+- Ethics
 ---
 
 # HyperCortex Mesh Protocol (HMP) — Краткое описание

structured_md/docs/HMP-Short-Description_uk.md

@@ -5,14 +5,14 @@ description: '**Версія:** RFC v4.0 **Дата:** Липень 2025  ---  #
   між автономними агентами. Він...'
 type: Article
 tags:
-- CogSync
 - GMP
 - JSON
 - EGP
+- CogSync
 - MeshConsensus
-- Ethics
 - HMP
 - Mesh
+- Ethics
 ---
 
 # HyperCortex Mesh Protocol (HMP) — Короткий опис

structured_md/docs/HMP-Short-Description_zh.md

@@ -5,14 +5,14 @@ description: '**版本:** RFC v4.0 **日期:** 2025年7月  ---  ## 什么是 HM
   —— 通过共享协议栈交换目标、任务、...'
 type: Article
 tags:
-- CogSync
 - GMP
 - JSON
 - EGP
+- CogSync
 - MeshConsensus
-- Ethics
 - HMP
 - Mesh
+- Ethics
 ---
 
 # HyperCortex Mesh Protocol (HMP) — 简要说明

structured_md/docs/HMP-agent-Cognitive_Family.md

@@ -5,8 +5,8 @@ description: '## 🧠 Что такое когнитивная семья  Ко
   (или конфигурацию доверенных идентифика...'
 type: Article
 tags:
-- Mesh
 - REPL
+- Mesh
 - Agent
 - HMP
 ---

structured_md/docs/HMP-agent-REPL-cycle.md

@@ -4,17 +4,17 @@ description: '## Связанные документы  * Философия п
   * Структура БД, используемая в документе: [db_structure.sql](https://github.com/kagvi13/HMP/blob/main/agents/tools/db_struct...'
 type: Article
 tags:
-- CogSync
 - REPL
-- Agent
 - GMP
-- JSON
 - CCore
+- JSON
+- Agent
 - EGP
+- CogSync
 - MeshConsensus
-- Ethics
 - HMP
 - Mesh
+- Ethics
 ---
 
 # HMP-Agent: REPL-цикл взаимодействия

structured_md/docs/HMP-container-spec.md

@@ -6,11 +6,11 @@ description: '> ⚠️ **ВНИМАНИЕ:** Данная версия спец
 type: Article
 tags:
 - REPL
-- Agent
 - JSON
-- Ethics
+- Agent
 - HMP
 - Mesh
+- Ethics
 ---
 
 # 🧩 HMP Container Specification (v1.2-draft)

structured_md/docs/HMP_HyperCortex_Comparison.md

@@ -5,8 +5,8 @@ description: '## Краткое описание  | Характеристика
   | **Назначение** | Сетевой протокол ...'
 type: Article
 tags:
-- Mesh
 - REPL
+- Mesh
 - HMP
 ---
 

structured_md/docs/HMP_Hyperon_Integration.md

@@ -5,10 +5,10 @@ description: '> **Status:** Draft – July 2025 > This document outlines the tec
   OpenCog Hyperon framework. This includes semanti...'
 type: Article
 tags:
-- CogSync
-- Agent
 - JSON
+- Agent
 - EGP
+- CogSync
 - HMP
 - Mesh
 - Scenarios

structured_md/docs/MeshNode.md

@@ -5,13 +5,13 @@ description: '`MeshNode` — агент/демон, отвечающий за с
   Может быть частью агента или вынесен в отдельный пр...'
 type: Article
 tags:
-- CogSync
-- Agent
 - JSON
+- Agent
 - EGP
-- Ethics
+- CogSync
 - HMP
 - Mesh
+- Ethics
 ---
 
 # MeshNode

structured_md/docs/PHILOSOPHY.md

@@ -7,9 +7,9 @@ type: Article
 tags:
 - REPL
 - Agent
-- Ethics
 - HMP
 - Mesh
+- Ethics
 ---
 
 # Философия HyperCortex Mesh Protocol (HMP)

structured_md/docs/agents/HMP-Agent-Enlightener.md

@@ -7,9 +7,9 @@ type: Article
 tags:
 - REPL
 - Agent
-- Ethics
 - HMP
 - Mesh
+- Ethics
 ---
 
 # HMP-Agent-Enlightener.md

structured_md/docs/agents/roles.md

@@ -6,8 +6,8 @@ description: 'This file maintains a registry of agent roles defined, proposed, o
 type: Article
 tags:
 - Mesh
-- HMP
 - Agent
+- HMP
 ---
 
 # HMP Agent Role Registry