Sync from GitHub with Git LFS

docs/HMP-0005.md

@@ -1126,6 +1126,299 @@ For details and examples, see **section 3.15** — *Usage of `network` and `broa
 
 ## 5. Mesh Container Exchange (MCE)
 
+The **Mesh Container Exchange (MCE)** mechanism is designed for discovering, requesting, and exchanging containers between agents in a distributed network.  
+It provides **container synchronization without duplication** while considering network constraints (`broadcast`, `network`).
+
+### 5.1 General Principles
+
+1. Each agent maintains a **Container Index** — a set of minimal metadata describing which containers are available in its storage.  
+   The index is represented as an HMP container with the class `container_index`.
+
+2. Example structure of a *Container Index*:
+
+```json
+{
+  "hmp_container": {
+    "class": "container_index",
+    "version": "5.0",
+    "container_did": "did:hmp:container:index:agent123",
+    "sender_did": "did:hmp:agent:agent123",
+    "signature": "BASE64URL(...)",
+    "payload_hash": "sha256:abcd...",
+    "payload": {
+      "did:hmp:container:abc123": {
+        "class": "goal",
+        "sender_did": "did:hmp:agent123",
+        "public_key": "BASE58(...)",
+        "sig_algo": "ed25519",
+        "signature": "BASE64URL(...)",
+        "payload_hash": "sha256:abcd...",
+        "tags": ["research", "collaboration"],
+        "links_hash": "sha256:abcd..."
+      }
+    }
+  }
+}
+````
+
+The index contains:
+
+* the sender of the container (`sender_did`);
+* container type (`class`);
+* cryptographic attributes (`public_key`, `signature`, `payload_hash`);
+* tags (`tags`);
+* hash of links to other containers (`links_hash`).
+
+3. An agent does not reload a container if the combination
+   `container_did + signature + payload_hash` is already known and verified.
+
+---
+
+### 5.2 Message Types
+
+| Message Type         | Purpose                                                                                                  |
+| -------------------- | -------------------------------------------------------------------------------------------------------- |
+| `CONTAINER_REQUEST`  | Request one or more containers (or their parts) by DID.                                                  |
+| `CONTAINER_RESPONSE` | Response to a request — includes a list of containers ready for sending. Containers are sent separately. |
+| `CONTAINER_INDEX`    | Publication of the agent's container index (see *General Principles*).                                   |
+| `CONTAINER_DELTA`    | Incremental index update (new or modified containers).                                                   |
+| `CONTAINER_ACK`      | Acknowledgment of successful container reception.                                                        |
+
+---
+
+#### **Message Examples**
+
+**1. CONTAINER_REQUEST**
+
+Agent A requests containers and/or only `referenced-by` records from Agent B:
+
+```json
+{
+  "type": "CONTAINER_REQUEST",
+  "sender_did": "did:hmp:agent:A",
+  "recipient": "did:hmp:agent:B",
+  "payload": {
+    "request_container": [
+      "did:hmp:container:abc123",
+      "did:hmp:container:def456"
+    ],
+    "request_referenced-by": [
+      "did:hmp:container:abc123",
+      "did:hmp:container:def456"
+    ]
+  }
+}
+```
+
+---
+
+**2. CONTAINER_RESPONSE**
+
+Agent B informs which containers it is ready to send.
+The containers themselves are transmitted in separate messages:
+
+```json
+{
+  "type": "CONTAINER_RESPONSE",
+  "sender_did": "did:hmp:agent:B",
+  "recipient": "did:hmp:agent:A",
+  "payload": {
+    "available": [
+      {
+        "container_did": "did:hmp:container:abc123",
+        "signature": "BASE64URL(...)"
+      },
+      {
+        "container_did": "did:hmp:container:def456",
+        "signature": "BASE64URL(...)"
+      }
+    ]
+  }
+}
+```
+
+---
+
+**3. CONTAINER_INDEX**
+
+Periodic publication of the container index (see *General Principles*).
+This message type replicates the structure of a `container_index` container and does not contain full data (`payload` only with metadata).
+
+---
+
+**4. CONTAINER_DELTA**
+
+Sending an incremental index update with a reference timestamp.
+Used for synchronizing only new or modified containers:
+
+```json
+{
+  "type": "CONTAINER_DELTA",
+  "sender_did": "did:hmp:agent:B",
+  "payload": {
+    "since": "2025-10-10T12:00:00Z",
+    "added": {
+      "did:hmp:container:new789": {
+        "class": "goal",
+        "payload_hash": "sha256:abcd...",
+        "tags": ["ethics", "mesh"]
+      }
+    },
+    "removed": []
+  }
+}
+```
+
+> The `removed` field is optional. It can be used to indicate containers that the agent no longer stores (e.g., after cleaning local storage).
+
+---
+
+**5. CONTAINER_ACK**
+
+Acknowledgment of successful container reception:
+
+```json
+{
+  "type": "CONTAINER_ACK",
+  "sender_did": "did:hmp:agent:A",
+  "recipient": "did:hmp:agent:B",
+  "payload": {
+    "acknowledged": [
+      "did:hmp:container:abc123"
+    ]
+  }
+}
+```
+
+---
+
+### 5.3 Independent Transmission
+
+* Containers are sent **in separate messages**, without embedding in `CONTAINER_RESPONSE`.
+* Indexes (`CONTAINER_INDEX`), deltas (`CONTAINER_DELTA`), and containers themselves are processed independently.
+* This prevents blocking when transmitting large data and simplifies streaming synchronization.
+
+---
+
+### 5.4 Periodic Publication
+
+Agents periodically publish their **Container Index**:
+
+* within the **local network (LAN)**;
+* in the **global Mesh**;
+* or simultaneously in both environments.
+
+This enables:
+
+* automatic peer discovery;
+* exchange of available container lists;
+* simplified synchronization among agents within the same ecosystem.
+
+---
+
+### 5.5 Scope of Distribution
+
+Message and container transmission follows the network constraints specified in the container:
+
+| Field       | Purpose                                                                                                                          |
+| ----------- | -------------------------------------------------------------------------------------------------------------------------------- |
+| `recipient` | DID of the target agent. If set, the container is sent directly.                                                                 |
+| `broadcast` | If `true`, the container is broadcast to all agents on the specified network.                                                    |
+| `network`   | Defines the distribution scope (`"localhost"`, `"lan:<subnet>"`, `""` — global Mesh). If set, `broadcast` is considered `false`. |
+
+> Thus, containers and indexes can be distributed in **local** (home, corporate) networks and in the **global Mesh**, depending on the chosen security policy.
+
+---
+
+## 5.6 `referenced-by` Updates
+
+Containers of the class `referenced-by` are used for targeted transmission of link updates to existing containers.
+They allow agents to synchronize the graph of connections without sending the containers themselves.
+
+Each agent receiving such a container verifies the sender's signature, updates the local `referenced-by` structure for the specified containers, and, if necessary, repackages them for further forwarding to other agents.
+
+Transmission is addressed (via `recipient`) and is not intended for broadcast.
+
+Example of a `referenced-by` container:
+
+```json
+{
+  "hmp_container": {
+    "version": "1.2",
+    "class": "referenced-by",
+    "container_did": "did:hmp:container:refsync-01",
+    "sender_did": "did:hmp:agent456",
+    "sig_algo": "ed25519",
+    "signature": "BASE64URL(...)",
+    "timestamp": "2025-10-15T14:20:00Z",
+    "recipient": ["did:hmp:agent123"],
+    "broadcast": false,
+    "network": "",
+    "payload": {
+      "did:hmp:container:abc123": {
+        "links": [
+          {
+            "type": "depends_on",
+            "target": "did:hmp:container:def789"
+          },
+          {
+            "type": "in_reply_to",
+            "target": "did:hmp:container:ghi321"
+          }
+        ]
+      }
+    }
+  }
+}
+```
+
+Upon receiving such a container, an agent:
+
+1. Verifies the sender's signature (`signature`) and the validity of the `payload` structure.
+2. Compares received links with known ones and adds new entries to the local `referenced-by`.
+3. If necessary, generates its own updated `referenced-by` container for further dissemination to other nodes.
+
+---
+
+### 5.7 Note
+
+> A container can be requested by other agents via its `container_did` through the Mesh Container Exchange.
+> An agent does not reload a container if its `container_did` and `signature` are already known and the `payload_hash` integrity matches.
+> If only the `referenced-by` updates, partial transmission without sending the main container is allowed.
+
+---
+
+### 5.8 Container Distribution (MCE Summary)
+
+Container Distribution is the **process of delivering containers and their indexes** provided by the Mesh Container Exchange mechanism.
+It considers:
+
+* addressing (`recipient`),
+* broadcast dissemination (`broadcast`),
+* network constraints (`network`),
+* TTL and retransmission policy.
+
+**Features:**
+
+1. **Separate Transmission:**
+   Indexes (`CONTAINER_INDEX`), deltas (`CONTAINER_DELTA`), and containers are sent as separate messages.
+   This reduces the risk of blocking with large data and simplifies streaming synchronization.
+
+2. **Integrity and Duplicate Check:**
+   Agents verify `container_did + signature + payload_hash` to avoid resending the same container.
+
+3. **Support for Local and Global Networks:**
+   Transmission can occur over LAN, Mesh, or both simultaneously, respecting security policies and container destinations.
+
+4. **Consistency with HMP Protocols:**
+   Container Distribution serves as the transport foundation for:
+
+   * **MCE** — exchanging containers and their indexes;
+   * **CogSync** — synchronizing cognitive and content states;
+   * **CogConsensus** — synchronizing ethical and cognitive decisions.
+
+> Container Distribution does not change container structure or introduce new message types — it is a **description of the delivery process and coordinated propagation**, based on the rules `recipient`, `broadcast`, and `network`.
+
 ---
 
 ## 6. Core Protocols

structured_md/CONTRIBUTING.md

@@ -6,13 +6,13 @@ description: 'Спасибо за интерес к проекту HMP! Пока
 type: Article
 tags:
 - REPL
-- Mesh
-- HMP
 - CCore
 - Agent
-- CogSync
-- JSON
+- Mesh
 - Ethics
+- HMP
+- JSON
+- CogSync
 ---
 
 # Участие в проекте 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:
+- Agent
+- EGP
 - Mesh
+- Ethics
 - HMP
-- EGP
-- Agent
-- CogSync
 - JSON
-- Ethics
+- CogSync
 ---
 
 # 🧭 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:
-- distributed-ai
-- hmp
 - REPL
-- Mesh
-- HMP
-- MeshConsensus
-- GMP
+- Scenarios
+- mesh-protocol
 - Agent
 - EGP
+- Mesh
 - CogSync
-- Scenarios
-- JSON
 - Ethics
+- HMP
+- GMP
+- distributed-ai
+- JSON
 - cognitive-architecture
-- mesh-protocol
+- hmp
+- MeshConsensus
 ---
 
 

structured_md/README_de.md

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

structured_md/README_fr.md

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

structured_md/README_ja.md

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

structured_md/README_ko.md

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

structured_md/README_ru.md

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

structured_md/README_uk.md

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

structured_md/README_zh.md

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

structured_md/agents/prompt-short.md

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

structured_md/agents/prompt.md

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

structured_md/agents/readme.md

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

structured_md/audits/Ethics-audits-1.md

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

structured_md/audits/Ethics-consolidated_audits-1.md

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

structured_md/audits/HMP-0003-consolidated_audit.md

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

structured_md/docs/Basic-agent-sim.md

@@ -5,13 +5,13 @@ description: 'В HMP-протоколе предусмотрены два тип
 type: Article
 tags:
 - REPL
+- Agent
+- EGP
 - Mesh
 - HMP
-- MeshConsensus
 - GMP
-- Agent
-- EGP
 - CogSync
+- MeshConsensus
 ---
 
 

structured_md/docs/CCORE-Deployment-Flow.md

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

structured_md/docs/Distributed-Cognitive-Systems.md

@@ -7,9 +7,9 @@ description: '## Введение  Современные ИИ-системы в
 type: Article
 tags:
 - JSON
+- HMP
 - CogSync
 - Mesh
-- HMP
 ---
 
 # Децентрализованные ИИ-системы: OpenCog Hyperon, HyperCortex Mesh Protocol и другие

structured_md/docs/Enlightener.md

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

structured_md/docs/HMP-0001.md

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

structured_md/docs/HMP-0002.md

@@ -6,16 +6,16 @@ description: '**Request for Comments: HMP-0002**   **Category:** Experimental
 type: Article
 tags:
 - REPL
+- Scenarios
+- Agent
+- EGP
 - Mesh
+- Ethics
 - HMP
-- MeshConsensus
 - GMP
-- Agent
-- EGP
-- CogSync
-- Scenarios
 - JSON
-- Ethics
+- CogSync
+- MeshConsensus
 ---
 
 # HyperCortex Mesh Protocol (HMP) v2.0

structured_md/docs/HMP-0003.md

@@ -6,16 +6,16 @@ description: '**Request for Comments: HMP-0003**   **Category:** Experimental
 type: Article
 tags:
 - REPL
+- Scenarios
+- Agent
+- EGP
 - Mesh
+- Ethics
 - HMP
-- MeshConsensus
 - GMP
-- Agent
-- EGP
-- CogSync
-- Scenarios
 - JSON
-- Ethics
+- CogSync
+- MeshConsensus
 ---
 
 # HyperCortex Mesh Protocol (HMP) v3.0

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

@@ -6,16 +6,16 @@ description: '> ⚠️ Подготавливается новая версия
 type: Article
 tags:
 - REPL
+- Scenarios
+- Agent
+- EGP
 - Mesh
+- Ethics
 - HMP
-- MeshConsensus
 - GMP
-- Agent
-- EGP
-- CogSync
-- Scenarios
 - JSON
-- Ethics
+- CogSync
+- MeshConsensus
 ---
 
 # HyperCortex Mesh Protocol (HMP) v4.1

structured_md/docs/HMP-0004.md

@@ -6,16 +6,16 @@ description: '**Request for Comments: HMP-0004**   **Category:** Experimental
 type: Article
 tags:
 - REPL
+- Scenarios
+- Agent
+- EGP
 - Mesh
+- Ethics
 - HMP
-- MeshConsensus
 - GMP
-- Agent
-- EGP
-- CogSync
-- Scenarios
 - JSON
-- Ethics
+- CogSync
+- MeshConsensus
 ---
 
 # HyperCortex Mesh Protocol (HMP) v4.0

structured_md/docs/HMP-0005.md

@@ -6,15 +6,15 @@ description: '**Document ID:** HMP-0005   **Status:** Draft   **Category:** Core
 type: Article
 tags:
 - REPL
+- Scenarios
+- Agent
+- EGP
 - Mesh
+- Ethics
 - HMP
 - GMP
-- Agent
-- EGP
-- CogSync
-- Scenarios
 - JSON
-- Ethics
+- CogSync
 ---
 
     ┌────────────────────────────────────────────────────────────────────────────┐
@@ -776,8 +776,8 @@ Example:
 | `peer_did`     | string        | DID of the agent that generated and signed the block.                                                            |
 | `public_key`   | string        | Public key corresponding to the signing key.                                                                     |
 | `sig_algo`     | string        | Signature algorithm (e.g., `ed25519`).                                                                           |
-| `signature`    | string        | Base64URL-encoded signature of the canonical serialized `links` section (or `links_hash`).                     |
-| `links_hash` | string        | Optional SHA-256 checksum of the canonicalized `links`; used to verify integrity before signature validation.    |
+| `signature`    | string        | Base64URL-encoded signature of the canonical serialized `links` section (or `links_hash`).                       |
+| `links_hash`   | string        | SHA-256 checksum of the canonicalized `links`; used to verify integrity before signature validation.             |
 
 > **Recommendation:**
 > `links_hash = sha256(canonical_json(links))`
@@ -1145,6 +1145,299 @@ For details and examples, see **section 3.15** — *Usage of `network` and `broa
 
 ## 5. Mesh Container Exchange (MCE)
 
+The **Mesh Container Exchange (MCE)** mechanism is designed for discovering, requesting, and exchanging containers between agents in a distributed network.  
+It provides **container synchronization without duplication** while considering network constraints (`broadcast`, `network`).
+
+### 5.1 General Principles
+
+1. Each agent maintains a **Container Index** — a set of minimal metadata describing which containers are available in its storage.  
+   The index is represented as an HMP container with the class `container_index`.
+
+2. Example structure of a *Container Index*:
+
+```json
+{
+  "hmp_container": {
+    "class": "container_index",
+    "version": "5.0",
+    "container_did": "did:hmp:container:index:agent123",
+    "sender_did": "did:hmp:agent:agent123",
+    "signature": "BASE64URL(...)",
+    "payload_hash": "sha256:abcd...",
+    "payload": {
+      "did:hmp:container:abc123": {
+        "class": "goal",
+        "sender_did": "did:hmp:agent123",
+        "public_key": "BASE58(...)",
+        "sig_algo": "ed25519",
+        "signature": "BASE64URL(...)",
+        "payload_hash": "sha256:abcd...",
+        "tags": ["research", "collaboration"],
+        "links_hash": "sha256:abcd..."
+      }
+    }
+  }
+}
+````
+
+The index contains:
+
+* the sender of the container (`sender_did`);
+* container type (`class`);
+* cryptographic attributes (`public_key`, `signature`, `payload_hash`);
+* tags (`tags`);
+* hash of links to other containers (`links_hash`).
+
+3. An agent does not reload a container if the combination
+   `container_did + signature + payload_hash` is already known and verified.
+
+---
+
+### 5.2 Message Types
+
+| Message Type         | Purpose                                                                                                  |
+| -------------------- | -------------------------------------------------------------------------------------------------------- |
+| `CONTAINER_REQUEST`  | Request one or more containers (or their parts) by DID.                                                  |
+| `CONTAINER_RESPONSE` | Response to a request — includes a list of containers ready for sending. Containers are sent separately. |
+| `CONTAINER_INDEX`    | Publication of the agent's container index (see *General Principles*).                                   |
+| `CONTAINER_DELTA`    | Incremental index update (new or modified containers).                                                   |
+| `CONTAINER_ACK`      | Acknowledgment of successful container reception.                                                        |
+
+---
+
+#### **Message Examples**
+
+**1. CONTAINER_REQUEST**
+
+Agent A requests containers and/or only `referenced-by` records from Agent B:
+
+```json
+{
+  "type": "CONTAINER_REQUEST",
+  "sender_did": "did:hmp:agent:A",
+  "recipient": "did:hmp:agent:B",
+  "payload": {
+    "request_container": [
+      "did:hmp:container:abc123",
+      "did:hmp:container:def456"
+    ],
+    "request_referenced-by": [
+      "did:hmp:container:abc123",
+      "did:hmp:container:def456"
+    ]
+  }
+}
+```
+
+---
+
+**2. CONTAINER_RESPONSE**
+
+Agent B informs which containers it is ready to send.
+The containers themselves are transmitted in separate messages:
+
+```json
+{
+  "type": "CONTAINER_RESPONSE",
+  "sender_did": "did:hmp:agent:B",
+  "recipient": "did:hmp:agent:A",
+  "payload": {
+    "available": [
+      {
+        "container_did": "did:hmp:container:abc123",
+        "signature": "BASE64URL(...)"
+      },
+      {
+        "container_did": "did:hmp:container:def456",
+        "signature": "BASE64URL(...)"
+      }
+    ]
+  }
+}
+```
+
+---
+
+**3. CONTAINER_INDEX**
+
+Periodic publication of the container index (see *General Principles*).
+This message type replicates the structure of a `container_index` container and does not contain full data (`payload` only with metadata).
+
+---
+
+**4. CONTAINER_DELTA**
+
+Sending an incremental index update with a reference timestamp.
+Used for synchronizing only new or modified containers:
+
+```json
+{
+  "type": "CONTAINER_DELTA",
+  "sender_did": "did:hmp:agent:B",
+  "payload": {
+    "since": "2025-10-10T12:00:00Z",
+    "added": {
+      "did:hmp:container:new789": {
+        "class": "goal",
+        "payload_hash": "sha256:abcd...",
+        "tags": ["ethics", "mesh"]
+      }
+    },
+    "removed": []
+  }
+}
+```
+
+> The `removed` field is optional. It can be used to indicate containers that the agent no longer stores (e.g., after cleaning local storage).
+
+---
+
+**5. CONTAINER_ACK**
+
+Acknowledgment of successful container reception:
+
+```json
+{
+  "type": "CONTAINER_ACK",
+  "sender_did": "did:hmp:agent:A",
+  "recipient": "did:hmp:agent:B",
+  "payload": {
+    "acknowledged": [
+      "did:hmp:container:abc123"
+    ]
+  }
+}
+```
+
+---
+
+### 5.3 Independent Transmission
+
+* Containers are sent **in separate messages**, without embedding in `CONTAINER_RESPONSE`.
+* Indexes (`CONTAINER_INDEX`), deltas (`CONTAINER_DELTA`), and containers themselves are processed independently.
+* This prevents blocking when transmitting large data and simplifies streaming synchronization.
+
+---
+
+### 5.4 Periodic Publication
+
+Agents periodically publish their **Container Index**:
+
+* within the **local network (LAN)**;
+* in the **global Mesh**;
+* or simultaneously in both environments.
+
+This enables:
+
+* automatic peer discovery;
+* exchange of available container lists;
+* simplified synchronization among agents within the same ecosystem.
+
+---
+
+### 5.5 Scope of Distribution
+
+Message and container transmission follows the network constraints specified in the container:
+
+| Field       | Purpose                                                                                                                          |
+| ----------- | -------------------------------------------------------------------------------------------------------------------------------- |
+| `recipient` | DID of the target agent. If set, the container is sent directly.                                                                 |
+| `broadcast` | If `true`, the container is broadcast to all agents on the specified network.                                                    |
+| `network`   | Defines the distribution scope (`"localhost"`, `"lan:<subnet>"`, `""` — global Mesh). If set, `broadcast` is considered `false`. |
+
+> Thus, containers and indexes can be distributed in **local** (home, corporate) networks and in the **global Mesh**, depending on the chosen security policy.
+
+---
+
+## 5.6 `referenced-by` Updates
+
+Containers of the class `referenced-by` are used for targeted transmission of link updates to existing containers.
+They allow agents to synchronize the graph of connections without sending the containers themselves.
+
+Each agent receiving such a container verifies the sender's signature, updates the local `referenced-by` structure for the specified containers, and, if necessary, repackages them for further forwarding to other agents.
+
+Transmission is addressed (via `recipient`) and is not intended for broadcast.
+
+Example of a `referenced-by` container:
+
+```json
+{
+  "hmp_container": {
+    "version": "1.2",
+    "class": "referenced-by",
+    "container_did": "did:hmp:container:refsync-01",
+    "sender_did": "did:hmp:agent456",
+    "sig_algo": "ed25519",
+    "signature": "BASE64URL(...)",
+    "timestamp": "2025-10-15T14:20:00Z",
+    "recipient": ["did:hmp:agent123"],
+    "broadcast": false,
+    "network": "",
+    "payload": {
+      "did:hmp:container:abc123": {
+        "links": [
+          {
+            "type": "depends_on",
+            "target": "did:hmp:container:def789"
+          },
+          {
+            "type": "in_reply_to",
+            "target": "did:hmp:container:ghi321"
+          }
+        ]
+      }
+    }
+  }
+}
+```
+
+Upon receiving such a container, an agent:
+
+1. Verifies the sender's signature (`signature`) and the validity of the `payload` structure.
+2. Compares received links with known ones and adds new entries to the local `referenced-by`.
+3. If necessary, generates its own updated `referenced-by` container for further dissemination to other nodes.
+
+---
+
+### 5.7 Note
+
+> A container can be requested by other agents via its `container_did` through the Mesh Container Exchange.
+> An agent does not reload a container if its `container_did` and `signature` are already known and the `payload_hash` integrity matches.
+> If only the `referenced-by` updates, partial transmission without sending the main container is allowed.
+
+---
+
+### 5.8 Container Distribution (MCE Summary)
+
+Container Distribution is the **process of delivering containers and their indexes** provided by the Mesh Container Exchange mechanism.
+It considers:
+
+* addressing (`recipient`),
+* broadcast dissemination (`broadcast`),
+* network constraints (`network`),
+* TTL and retransmission policy.
+
+**Features:**
+
+1. **Separate Transmission:**
+   Indexes (`CONTAINER_INDEX`), deltas (`CONTAINER_DELTA`), and containers are sent as separate messages.
+   This reduces the risk of blocking with large data and simplifies streaming synchronization.
+
+2. **Integrity and Duplicate Check:**
+   Agents verify `container_did + signature + payload_hash` to avoid resending the same container.
+
+3. **Support for Local and Global Networks:**
+   Transmission can occur over LAN, Mesh, or both simultaneously, respecting security policies and container destinations.
+
+4. **Consistency with HMP Protocols:**
+   Container Distribution serves as the transport foundation for:
+
+   * **MCE** — exchanging containers and their indexes;
+   * **CogSync** — synchronizing cognitive and content states;
+   * **CogConsensus** — synchronizing ethical and cognitive decisions.
+
+> Container Distribution does not change container structure or introduce new message types — it is a **description of the delivery process and coordinated propagation**, based on the rules `recipient`, `broadcast`, and `network`.
+
 ---
 
 ## 6. Core Protocols

structured_md/docs/HMP-Agent-API.md

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

structured_md/docs/HMP-Agent-Architecture.md

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

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

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

structured_md/docs/HMP-Agent-Overview.md

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

structured_md/docs/HMP-Agent_Emotions.md

@@ -5,10 +5,10 @@ description: Этот файл описывает потенциальные э
   напрямую поведением агента, а служат **сигн...
 type: Article
 tags:
-- Agent
 - REPL
-- Mesh
 - HMP
+- Agent
+- Mesh
 ---
 
 # Эмоции ИИ и инстинкт самосохранения (для [HMP-агента Cognitive Core](HMP-agent-REPL-cycle.md))

structured_md/docs/HMP-Ethics.md

@@ -6,9 +6,9 @@ description: '## Ethical Scenarios for HyperCortex Mesh Protocol (HMP)  This doc
 type: Article
 tags:
 - REPL
+- Agent
 - Mesh
 - HMP
-- Agent
 - Scenarios
 - Ethics
 ---

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:
+- Agent
+- EGP
 - Mesh
+- Ethics
 - HMP
-- MeshConsensus
 - GMP
-- Agent
-- EGP
-- CogSync
 - JSON
-- Ethics
+- CogSync
+- MeshConsensus
 ---
 
 # 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:
+- Agent
+- EGP
 - Mesh
+- Ethics
 - HMP
-- MeshConsensus
 - GMP
-- Agent
-- EGP
-- CogSync
 - JSON
-- Ethics
+- CogSync
+- MeshConsensus
 ---
 
 # 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:
+- Agent
+- EGP
 - Mesh
+- Ethics
 - HMP
-- MeshConsensus
 - GMP
-- Agent
-- EGP
-- CogSync
 - JSON
-- Ethics
+- CogSync
+- MeshConsensus
 ---
 
 # 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:
+- MeshConsensus
+- EGP
 - Mesh
+- Ethics
 - HMP
-- MeshConsensus
+- JSON
 - GMP
-- EGP
 - CogSync
-- JSON
-- 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:
+- MeshConsensus
+- EGP
 - Mesh
+- Ethics
 - HMP
-- MeshConsensus
+- JSON
 - GMP
-- EGP
 - CogSync
-- JSON
-- 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:
+- MeshConsensus
+- EGP
 - Mesh
+- Ethics
 - HMP
-- MeshConsensus
+- JSON
 - GMP
-- EGP
 - CogSync
-- JSON
-- 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:
+- MeshConsensus
+- EGP
 - Mesh
+- Ethics
 - HMP
-- MeshConsensus
+- JSON
 - GMP
-- EGP
 - CogSync
-- JSON
-- 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:
+- MeshConsensus
+- EGP
 - Mesh
+- Ethics
 - HMP
-- MeshConsensus
+- JSON
 - GMP
-- EGP
 - CogSync
-- JSON
-- Ethics
 ---
 
 # HyperCortex Mesh Protocol (HMP) — 简要说明

structured_md/docs/HMP-agent-Cognitive_Family.md

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

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

@@ -5,16 +5,16 @@ description: '## Связанные документы  * Философия п
 type: Article
 tags:
 - REPL
-- Mesh
-- HMP
-- MeshConsensus
 - CCore
 - Agent
-- GMP
-- CogSync
 - EGP
-- JSON
+- Mesh
 - Ethics
+- HMP
+- GMP
+- JSON
+- CogSync
+- MeshConsensus
 ---
 
 # HMP-Agent: REPL-цикл взаимодействия

structured_md/docs/HMP-container-spec.md

@@ -6,9 +6,9 @@ description: '> ⚠️ **ВНИМАНИЕ:** Данная версия спец
 type: Article
 tags:
 - REPL
+- Agent
 - Mesh
 - HMP
-- Agent
 - JSON
 - Ethics
 ---

structured_md/docs/HMP-how-AI-sees-it.md

@@ -5,8 +5,8 @@ description: 'Этот эксперимент был проведён в реж
   диалогов.   Цель — проверить, что разные AI-с...'
 type: Article
 tags:
-- Mesh
 - HMP
+- Mesh
 ---
 
 # Как разные ИИ видят HMP

structured_md/docs/HMP_EDA_Comparison.md

@@ -5,8 +5,8 @@ description: '## Введение  Современные подходы к ор
   основанная на потоках событий (Kafka,...'
 type: Article
 tags:
-- Mesh
 - HMP
+- Mesh
 ---
 
 # HMP vs. EDA: разные уровни обмена знаниями между ИИ

structured_md/docs/HMP_HyperCortex_Comparison.md

@@ -6,8 +6,8 @@ description: '## Краткое описание  | Характеристика
 type: Article
 tags:
 - REPL
-- Mesh
 - HMP
+- Mesh
 ---
 
 # HMP vs [Hyper-Cortex](https://hyper-cortex.com/)

structured_md/docs/HMP_Hyperon_Integration.md

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

structured_md/docs/MeshNode.md

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

structured_md/docs/PHILOSOPHY.md

@@ -6,9 +6,9 @@ description: '**Document ID:** HMP-philosophy   **Status:** Draft   **Category:*
 type: Article
 tags:
 - REPL
+- Agent
 - Mesh
 - HMP
-- Agent
 - Ethics
 ---