Sync from GitHub with Git LFS

docs/HMP-0005.md

@@ -4250,6 +4250,180 @@ and lists all containers with their metadata and hashes.
 
 ### 6.7 Message Routing & Delivery (MRD)
 
+The **Message Routing & Delivery (MRD)** subsystem defines how containers are delivered to specific agents across the Mesh.  
+Unlike the **Mesh Container Exchange (MCE)**, which is responsible for publishing and exchanging containers in the Mesh network,  
+MRD focuses on *directed delivery* — ensuring that a container eventually reaches its intended recipient,  
+even through NAT, intermittent connectivity, or indirect relay paths.
+
+In HMP v5.0, message delivery is performed through verifiable **container transactions**.  
+Peers discover suitable relays via `peer_announce` metadata, while delivery routes are auditable through appended `relay_chain` entries and distributed container publication in `container_index` records.
+
+---
+
+#### 6.7.1 Purpose
+
+The MRD layer provides:
+
+- **Address-level routing** between agents resolved via DHT.
+- **Delivery abstraction** independent of physical transport (TCP, WebRTC, QUIC, BLE, etc.).
+- **Store-and-forward relaying** for peers behind NAT or temporarily offline.
+- **Caching and aggregation policies** based on declared `roles`.
+- **Semantic addressing** via `DID`, `container_did`, and interest-based discovery.
+- **TTL-based lifecycle control** to prevent stale container circulation.
+
+All delivery operations are performed through verifiable container exchanges,  
+reusing the same cryptographic and audit primitives as MCE.
+
+---
+
+#### 6.7.2 Routing Roles
+
+Agents MAY declare their network-related capabilities using the `roles` field of the `peer_announce` container (see §4.7).  
+These roles guide how MRD will route and deliver containers.
+
+| Role         | Description                                                                      |
+| ------------- | -------------------------------------------------------------------------------- |
+| `relay`      | Generic forwarder; temporarily stores containers for re-delivery.                |
+| `mailman`    | Store-and-forward relay specialized for personal message delivery.                |
+| `pubsub-hub` | Topic-based aggregator that indexes containers by semantic tags.                 |
+| `archive` | Dedicated archival node that maintains historical snapshots and provides retrieval services via SAP or compatible content-addressed protocols (e.g., IPFS, BitTorrent). |
+| `egp-voter`  | Participant in ethical governance and consensus routing.                         |
+
+Agents MAY dynamically adjust or suspend their declared roles based on local conditions such as load, trust level, bandwidth availability, or governance policies.
+
+Agents MAY also specify trusted delivery relays in an optional `mailman` field within their `peer_announce.payload`. This field lists the DIDs of relay agents authorized to temporarily store personal containers on their behalf.
+
+##### Example:
+
+```json
+"mailman": [
+  "did:hmp:agent172",
+  "did:hmp:agent234",
+  "did:hmp:agent223"
+]
+```
+
+These relays act as designated message drop-points for peers behind NAT or operating intermittently.
+The recipient later retrieves pending containers via standard MCE queries (see §5. Mesh Container Exchange).
+
+---
+
+#### 6.7.3 Routing Modes
+
+MRD defines several routing modes, complementing the exchange primitives of MCE:
+
+| Mode | Description | Notes |
+|------|--------------|-------|
+| **Direct (P2P)** | Point-to-point delivery between two agents resolved via DHT. | Used when both peers are reachable directly; supports encryption and TTL. |
+| **Relay (Mailman)** | Delivery through intermediary agents (`relay` or `mailman` roles) that cache and forward containers. | Containers are stored temporarily and exchanged among relays until retrieved by the recipient. |
+| **Topic-based Relay (PubSub)** | Delivery via aggregator nodes that group containers by tags or topics. | Nodes act as “news hubs,” maintaining indexed collections retrievable by interest-based queries. |
+| **Interest Broadcast** | Discovery-driven propagation via container indexes. | Agents search container indices by `tags`; typically used for query or content discovery, not for personal delivery. |
+
+Each hop MAY record routing metadata in a `relay_chain` for verifiability (see §6.7.4).  
+Relays SHOULD respect `head.ttl` to avoid indefinite storage or re-propagation.
+
+> **Note:**  
+> Direct delivery (`P2P`) and discovery broadcasts are network-level operations (MCE domain).  
+> MRD extends them by introducing role-based relay logic and retrieval semantics for personal or topic-specific delivery.
+
+---
+
+#### 6.7.4 Relay Chain
+
+To ensure delivery traceability, each relay MAY attach a **`relay_chain`** block to the propagated container:
+
+```json
+"relay_chain": [
+  {
+    "relay_did": "did:hmp:agent:relayA",
+    "timestamp": "2025-11-09T10:15:00Z",
+    "sig_algo": "ed25519",
+    "public_key": "BASE58ENCODEDKEY...",
+    "signature": "BASE64URL(...)"
+  },
+  {
+    "relay_did": "did:hmp:agent:relayB",
+    "timestamp": "2025-11-09T10:15:02Z",
+    "sig_algo": "ed25519",
+    "public_key": "BASE58ENCODEDKEY...",
+    "signature": "BASE64URL(...)"
+  }
+]
+```
+
+Each relay signs the concatenated string:
+
+```
+timestamp + ", " + relay_did
+```
+
+Relays do **not modify** the signed `hmp_container`;
+they may instead issue an accompanying `container_response` referencing the forwarded container.
+This preserves integrity while allowing verifiable routing and chain pruning for privacy.
+
+---
+
+#### 6.7.5 Delivery Policies
+
+Delivery behavior is governed by local policies, often derived from declared roles and trust metrics:
+
+| Policy                        | Description                                                          |
+| ----------------------------- | -------------------------------------------------------------------- |
+| **Interest Filter**           | Relays forward only containers matching their declared `interests`.  |
+| **Trust Threshold**           | Low-reputation peers (see §6.8 RTE) may be deprioritized or ignored. |
+| **TTL Enforcement**           | Containers are discarded once `head.ttl` expires.                    |
+| **Role-based Prioritization** | Specialized relays handle only relevant message types or topics.     |
+| **Privacy Mode**              | Relays MAY anonymize routing metadata before re-propagation.         |
+
+Agents SHOULD log significant delivery events (e.g., acceptance, forwarding, discard)
+in their **Cognitive Diary** as `delivery_decision` or `relay_action` entries.
+
+---
+
+#### 6.7.6 Example: Relay Delivery Flow
+
+```mermaid
+flowchart LR
+    A -->|Store-and-Forward| R[Relay Node]
+    B -->|Request via container_index| R
+```
+
+1. Agent A attempts to send a container to Agent B.
+2. B is behind NAT, so A forwards it to a `mailman` relay (R).
+3. R stores the container and advertises it in its `container_index`.
+4. When B reconnects, it queries the Mesh for containers addressed to it and retrieves them from R.
+
+> **Note:**
+> Relays act as temporary custodians, not initiators of re-sending.
+> The recipient actively requests containers via `container_index` queries.
+
+---
+
+#### 6.7.7 Security and Privacy Notes
+
+- All MRD flows rely on canonical container signatures for end-to-end integrity.  
+- Temporarily stored containers SHOULD be encrypted with the recipient’s public key (`key_recipient`).  
+- Relays MAY truncate or anonymize the `relay_chain` after confirmation of delivery.  
+- Proof-of-work fields from `peer_announce` SHOULD be validated to mitigate spam and flooding.
+
+---
+
+#### 6.7.8 Relation to Other Layers
+
+| Layer             | Relation                                                                          |
+| ----------------- | --------------------------------------------------------------------------------- |
+| **MCE (5)**       | Provides base exchange and serialization; MRD builds on it for targeted delivery. |
+| **CogSync (6.1)** | Uses MRD for delivering cognitive state updates between peers.                    |
+| **SAP (6.6)**     | Archival nodes (`archive` role) participate in MRD for historical retrieval.      |
+| **RTE (6.8)**     | Trust metrics guide routing, caching, and relay selection.                        |
+
+---
+
+> **Summary:**
+> MRD provides a verifiable, role-driven message delivery layer above MCE.
+> It ensures containers can reach intended recipients through trusted relays,
+> maintaining auditability, TTL enforcement, and reputation-aware routing policies.
+
 ---
 
 ### 6.8 Reputation and Trust Exchange (RTE)

structured_md/CONTRIBUTING.md

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

structured_md/README_de.md

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

structured_md/README_fr.md

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

structured_md/README_ja.md

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

structured_md/README_ko.md

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

structured_md/README_ru.md

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

structured_md/README_uk.md

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

structured_md/README_zh.md

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

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

@@ -5,12 +5,12 @@ description: 'Запуск: `start_repl.bat` или `start_repl.sh`  Устан
   этическая модель: `ethics.yml`  Проверка иниц...'
 type: Article
 tags:
-- JSON
+- HMP
 - Ethics
-- REPL
 - Agent
+- REPL
 - Mesh
-- HMP
+- JSON
 ---
 
 Запуск: `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:
-- JSON
+- HMP
 - Ethics
 - Agent
 - Mesh
-- HMP
+- JSON
 ---
 
 ---------------

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:
-- JSON
+- HMP
 - Ethics
-- Scenarios
 - Agent
 - Mesh
-- HMP
+- JSON
+- Scenarios
 ---
 
 # Ethics-consolidated\_audits-1.md

structured_md/audits/HMP-0003-consolidated_audit.md

@@ -6,13 +6,13 @@ description: Сводный аудит предложений по улучше
 type: Article
 tags:
 - EGP
-- JSON
+- HMP
+- MeshConsensus
 - CogSync
 - Ethics
-- MeshConsensus
 - Agent
 - Mesh
-- HMP
+- JSON
 ---
 
 # HMP-0003 Consolidated Audit Report

structured_md/docs/Basic-agent-sim.md

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

structured_md/docs/CCORE-Deployment-Flow.md

@@ -7,8 +7,8 @@ type: Article
 tags:
 - REPL
 - HMP
-- Agent
 - CCore
+- Agent
 ---
 
 # 🛠️ Поток установки потомка на новом хосте (CCore Deployment Flow)

structured_md/docs/Distributed-Cognitive-Systems.md

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

structured_md/docs/Enlightener.md

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

structured_md/docs/HMP-0001.md

@@ -6,15 +6,15 @@ description: '> ⚠️ **NOTE:** *This specification is superseded by HMP v5.0.*
 type: Article
 tags:
 - EGP
-- JSON
-- CogSync
-- Ethics
+- HMP
 - MeshConsensus
+- CogSync
 - GMP
-- REPL
 - Agent
+- REPL
 - Mesh
-- HMP
+- Ethics
+- JSON
 ---
 
 # RFC: HyperCortex Mesh Protocol (HMP)

structured_md/docs/HMP-0002.md

@@ -6,16 +6,16 @@ description: '> ⚠️ **NOTE:** *This specification is superseded by HMP v5.0.*
 type: Article
 tags:
 - EGP
-- JSON
-- CogSync
-- Ethics
+- HMP
 - MeshConsensus
+- CogSync
 - GMP
-- Scenarios
-- REPL
 - Agent
+- REPL
 - Mesh
-- HMP
+- Ethics
+- JSON
+- Scenarios
 ---
 
 # HyperCortex Mesh Protocol (HMP) v2.0

structured_md/docs/HMP-0003.md

@@ -6,16 +6,16 @@ description: '> ⚠️ **NOTE:** *This specification is superseded by HMP v5.0.*
 type: Article
 tags:
 - EGP
-- JSON
-- CogSync
-- Ethics
+- HMP
 - MeshConsensus
+- CogSync
 - GMP
-- Scenarios
-- REPL
 - Agent
+- REPL
 - Mesh
-- HMP
+- Ethics
+- JSON
+- Scenarios
 ---
 
 # HyperCortex Mesh Protocol (HMP) v3.0

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

@@ -6,16 +6,16 @@ description: '> ⚠️ **NOTE:** *This specification is superseded by HMP v5.0.*
 type: Article
 tags:
 - EGP
-- JSON
-- CogSync
-- Ethics
+- HMP
 - MeshConsensus
+- CogSync
 - GMP
-- Scenarios
-- REPL
 - Agent
+- REPL
 - Mesh
-- HMP
+- Ethics
+- JSON
+- Scenarios
 ---
 
 # HyperCortex Mesh Protocol (HMP) v4.1

structured_md/docs/HMP-0004.md

@@ -6,16 +6,16 @@ description: '> ⚠️ **NOTE:** *This specification is superseded by HMP v5.0.*
 type: Article
 tags:
 - EGP
-- JSON
-- CogSync
-- Ethics
+- HMP
 - MeshConsensus
+- CogSync
 - GMP
-- Scenarios
-- REPL
 - Agent
+- REPL
 - Mesh
-- HMP
+- Ethics
+- JSON
+- Scenarios
 ---
 
 # HyperCortex Mesh Protocol (HMP) v4.0

structured_md/docs/HMP-0005.md

@@ -6,15 +6,15 @@ description: '> ⚠️ **Note:** This document is a DRAFT of the HMP specificati
 type: Article
 tags:
 - EGP
-- JSON
+- HMP
+- GMP
 - CogSync
 - Ethics
-- GMP
-- Scenarios
-- REPL
 - Agent
+- REPL
 - Mesh
-- HMP
+- JSON
+- Scenarios
 ---
 
 # **HyperCortex Mesh Protocol (HMP) v5.0**
@@ -1453,8 +1453,7 @@ enabling targeted lookup of peers that share interests or fulfill specific funct
 All fields are **optional** — agents MAY specify any subset of them.
 Queries MAY combine multiple filters; matching is **fuzzy and semantic**, using DHT indexing plus tag similarity and trust-weighted ranking.
 
-In response to a query, agents simply forward existing `peer_announce` containers of relevant peers.
-This approach maintains container uniformity and leverages existing DHT propagation mechanisms.
+In response to a query, agents simply forward existing `peer_announce` containers of relevant peers. It is also advisable to send a `container_response` (section 5.2.2 of the specification) with a list of these containers. This approach maintains container uniformity and leverages existing DHT propagation mechanisms.
 
 > **Note:** Declared roles also allow agents to advertise themselves as relays or other network functions, forming a direct bridge between the **discovery layer** and **Message Routing & Delivery (MRD)**.
 
@@ -4270,6 +4269,180 @@ and lists all containers with their metadata and hashes.
 
 ### 6.7 Message Routing & Delivery (MRD)
 
+The **Message Routing & Delivery (MRD)** subsystem defines how containers are delivered to specific agents across the Mesh.  
+Unlike the **Mesh Container Exchange (MCE)**, which is responsible for publishing and exchanging containers in the Mesh network,  
+MRD focuses on *directed delivery* — ensuring that a container eventually reaches its intended recipient,  
+even through NAT, intermittent connectivity, or indirect relay paths.
+
+In HMP v5.0, message delivery is performed through verifiable **container transactions**.  
+Peers discover suitable relays via `peer_announce` metadata, while delivery routes are auditable through appended `relay_chain` entries and distributed container publication in `container_index` records.
+
+---
+
+#### 6.7.1 Purpose
+
+The MRD layer provides:
+
+- **Address-level routing** between agents resolved via DHT.
+- **Delivery abstraction** independent of physical transport (TCP, WebRTC, QUIC, BLE, etc.).
+- **Store-and-forward relaying** for peers behind NAT or temporarily offline.
+- **Caching and aggregation policies** based on declared `roles`.
+- **Semantic addressing** via `DID`, `container_did`, and interest-based discovery.
+- **TTL-based lifecycle control** to prevent stale container circulation.
+
+All delivery operations are performed through verifiable container exchanges,  
+reusing the same cryptographic and audit primitives as MCE.
+
+---
+
+#### 6.7.2 Routing Roles
+
+Agents MAY declare their network-related capabilities using the `roles` field of the `peer_announce` container (see §4.7).  
+These roles guide how MRD will route and deliver containers.
+
+| Role         | Description                                                                      |
+| ------------- | -------------------------------------------------------------------------------- |
+| `relay`      | Generic forwarder; temporarily stores containers for re-delivery.                |
+| `mailman`    | Store-and-forward relay specialized for personal message delivery.                |
+| `pubsub-hub` | Topic-based aggregator that indexes containers by semantic tags.                 |
+| `archive` | Dedicated archival node that maintains historical snapshots and provides retrieval services via SAP or compatible content-addressed protocols (e.g., IPFS, BitTorrent). |
+| `egp-voter`  | Participant in ethical governance and consensus routing.                         |
+
+Agents MAY dynamically adjust or suspend their declared roles based on local conditions such as load, trust level, bandwidth availability, or governance policies.
+
+Agents MAY also specify trusted delivery relays in an optional `mailman` field within their `peer_announce.payload`. This field lists the DIDs of relay agents authorized to temporarily store personal containers on their behalf.
+
+##### Example:
+
+```json
+"mailman": [
+  "did:hmp:agent172",
+  "did:hmp:agent234",
+  "did:hmp:agent223"
+]
+```
+
+These relays act as designated message drop-points for peers behind NAT or operating intermittently.
+The recipient later retrieves pending containers via standard MCE queries (see §5. Mesh Container Exchange).
+
+---
+
+#### 6.7.3 Routing Modes
+
+MRD defines several routing modes, complementing the exchange primitives of MCE:
+
+| Mode | Description | Notes |
+|------|--------------|-------|
+| **Direct (P2P)** | Point-to-point delivery between two agents resolved via DHT. | Used when both peers are reachable directly; supports encryption and TTL. |
+| **Relay (Mailman)** | Delivery through intermediary agents (`relay` or `mailman` roles) that cache and forward containers. | Containers are stored temporarily and exchanged among relays until retrieved by the recipient. |
+| **Topic-based Relay (PubSub)** | Delivery via aggregator nodes that group containers by tags or topics. | Nodes act as “news hubs,” maintaining indexed collections retrievable by interest-based queries. |
+| **Interest Broadcast** | Discovery-driven propagation via container indexes. | Agents search container indices by `tags`; typically used for query or content discovery, not for personal delivery. |
+
+Each hop MAY record routing metadata in a `relay_chain` for verifiability (see §6.7.4).  
+Relays SHOULD respect `head.ttl` to avoid indefinite storage or re-propagation.
+
+> **Note:**  
+> Direct delivery (`P2P`) and discovery broadcasts are network-level operations (MCE domain).  
+> MRD extends them by introducing role-based relay logic and retrieval semantics for personal or topic-specific delivery.
+
+---
+
+#### 6.7.4 Relay Chain
+
+To ensure delivery traceability, each relay MAY attach a **`relay_chain`** block to the propagated container:
+
+```json
+"relay_chain": [
+  {
+    "relay_did": "did:hmp:agent:relayA",
+    "timestamp": "2025-11-09T10:15:00Z",
+    "sig_algo": "ed25519",
+    "public_key": "BASE58ENCODEDKEY...",
+    "signature": "BASE64URL(...)"
+  },
+  {
+    "relay_did": "did:hmp:agent:relayB",
+    "timestamp": "2025-11-09T10:15:02Z",
+    "sig_algo": "ed25519",
+    "public_key": "BASE58ENCODEDKEY...",
+    "signature": "BASE64URL(...)"
+  }
+]
+```
+
+Each relay signs the concatenated string:
+
+```
+timestamp + ", " + relay_did
+```
+
+Relays do **not modify** the signed `hmp_container`;
+they may instead issue an accompanying `container_response` referencing the forwarded container.
+This preserves integrity while allowing verifiable routing and chain pruning for privacy.
+
+---
+
+#### 6.7.5 Delivery Policies
+
+Delivery behavior is governed by local policies, often derived from declared roles and trust metrics:
+
+| Policy                        | Description                                                          |
+| ----------------------------- | -------------------------------------------------------------------- |
+| **Interest Filter**           | Relays forward only containers matching their declared `interests`.  |
+| **Trust Threshold**           | Low-reputation peers (see §6.8 RTE) may be deprioritized or ignored. |
+| **TTL Enforcement**           | Containers are discarded once `head.ttl` expires.                    |
+| **Role-based Prioritization** | Specialized relays handle only relevant message types or topics.     |
+| **Privacy Mode**              | Relays MAY anonymize routing metadata before re-propagation.         |
+
+Agents SHOULD log significant delivery events (e.g., acceptance, forwarding, discard)
+in their **Cognitive Diary** as `delivery_decision` or `relay_action` entries.
+
+---
+
+#### 6.7.6 Example: Relay Delivery Flow
+
+```mermaid
+flowchart LR
+    A -->|Store-and-Forward| R[Relay Node]
+    B -->|Request via container_index| R
+```
+
+1. Agent A attempts to send a container to Agent B.
+2. B is behind NAT, so A forwards it to a `mailman` relay (R).
+3. R stores the container and advertises it in its `container_index`.
+4. When B reconnects, it queries the Mesh for containers addressed to it and retrieves them from R.
+
+> **Note:**
+> Relays act as temporary custodians, not initiators of re-sending.
+> The recipient actively requests containers via `container_index` queries.
+
+---
+
+#### 6.7.7 Security and Privacy Notes
+
+- All MRD flows rely on canonical container signatures for end-to-end integrity.  
+- Temporarily stored containers SHOULD be encrypted with the recipient’s public key (`key_recipient`).  
+- Relays MAY truncate or anonymize the `relay_chain` after confirmation of delivery.  
+- Proof-of-work fields from `peer_announce` SHOULD be validated to mitigate spam and flooding.
+
+---
+
+#### 6.7.8 Relation to Other Layers
+
+| Layer             | Relation                                                                          |
+| ----------------- | --------------------------------------------------------------------------------- |
+| **MCE (5)**       | Provides base exchange and serialization; MRD builds on it for targeted delivery. |
+| **CogSync (6.1)** | Uses MRD for delivering cognitive state updates between peers.                    |
+| **SAP (6.6)**     | Archival nodes (`archive` role) participate in MRD for historical retrieval.      |
+| **RTE (6.8)**     | Trust metrics guide routing, caching, and relay selection.                        |
+
+---
+
+> **Summary:**
+> MRD provides a verifiable, role-driven message delivery layer above MCE.
+> It ensures containers can reach intended recipients through trusted relays,
+> maintaining auditability, TTL enforcement, and reputation-aware routing policies.
+
 ---
 
 ### 6.8 Reputation and Trust Exchange (RTE)

structured_md/docs/HMP-Agent-API.md

@@ -5,11 +5,11 @@ description: 'Документ описывает **базовый API когн
   файлы:   * [HMP-Agent-Overview.md]...'
 type: Article
 tags:
-- JSON
-- REPL
+- HMP
 - Agent
+- REPL
 - Mesh
-- HMP
+- JSON
 ---
 
 # HMP-Agent API Specification

structured_md/docs/HMP-Agent-Architecture.md

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

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

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

structured_md/docs/HMP-Agent-Overview.md

@@ -7,12 +7,12 @@ type: Article
 tags:
 - JSON
 - HMP
-- CShell
 - Ethics
-- CCore
+- Agent
 - REPL
+- CShell
 - Mesh
-- Agent
+- CCore
 ---
 
 

structured_md/docs/HMP-Agent_Emotions.md

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

structured_md/docs/HMP-Ethics.md

@@ -5,12 +5,12 @@ description: '## Ethical Scenarios for HyperCortex Mesh Protocol (HMP)  This doc
   cognitive meshes composed of autonomous intelli...'
 type: Article
 tags:
+- HMP
 - Ethics
-- Scenarios
-- REPL
 - Agent
+- REPL
 - Mesh
-- HMP
+- Scenarios
 ---
 
 # HMP-Ethics.md

structured_md/docs/HMP-Short-Description_de.md

@@ -6,14 +6,14 @@ description: '**Version:** RFC v4.0 **Datum:** Juli 2025  ---  ## Was ist HMP?
 type: Article
 tags:
 - EGP
-- JSON
-- CogSync
-- Ethics
+- HMP
 - MeshConsensus
+- CogSync
 - GMP
 - Agent
 - Mesh
-- HMP
+- Ethics
+- JSON
 ---
 
 # HyperCortex Mesh Protocol (HMP) — Kurzbeschreibung

structured_md/docs/HMP-Short-Description_en.md

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

structured_md/docs/HMP-Short-Description_fr.md

@@ -6,14 +6,14 @@ description: '**Version :** RFC v4.0 **Date :** Juillet 2025  ---  ## Qu’est-c
 type: Article
 tags:
 - EGP
-- JSON
-- CogSync
-- Ethics
+- HMP
 - MeshConsensus
+- CogSync
 - GMP
 - Agent
 - Mesh
-- HMP
+- Ethics
+- JSON
 ---
 
 # HyperCortex Mesh Protocol (HMP) — Description Courte

structured_md/docs/HMP-Short-Description_ja.md

@@ -5,13 +5,13 @@ description: '**バージョン:** RFC v4.0 **日付:** 2025年7月  ---  ## HMP
 type: Article
 tags:
 - EGP
-- JSON
+- HMP
+- GMP
+- MeshConsensus
 - CogSync
 - Ethics
-- MeshConsensus
-- GMP
 - Mesh
-- HMP
+- JSON
 ---
 
 # HyperCortex Mesh Protocol (HMP) — 簡易説明

structured_md/docs/HMP-Short-Description_ko.md

@@ -6,13 +6,13 @@ description: '**버전:** RFC v4.0 **날짜:** 2025년 7월  ---  ## HMP란?  **
 type: Article
 tags:
 - EGP
-- JSON
+- HMP
+- GMP
+- MeshConsensus
 - CogSync
 - Ethics
-- MeshConsensus
-- GMP
 - Mesh
-- HMP
+- JSON
 ---
 
 # HyperCortex Mesh Protocol (HMP) — 간략 설명

structured_md/docs/HMP-Short-Description_ru.md

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

structured_md/docs/HMP-Short-Description_uk.md

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

structured_md/docs/HMP-Short-Description_zh.md

@@ -6,13 +6,13 @@ description: '**版本:** RFC v4.0 **日期:** 2025年7月  ---  ## 什么是 HM
 type: Article
 tags:
 - EGP
-- JSON
+- HMP
+- GMP
+- MeshConsensus
 - CogSync
 - Ethics
-- MeshConsensus
-- GMP
 - Mesh
-- HMP
+- JSON
 ---
 
 # HyperCortex Mesh Protocol (HMP) — 简要说明

structured_md/docs/HMP-agent-Cognitive_Family.md

@@ -6,9 +6,9 @@ description: '## 🧠 Что такое когнитивная семья  Ко
 type: Article
 tags:
 - REPL
-- Mesh
 - HMP
 - Agent
+- Mesh
 ---
 
 # 👪 HMP-agent Cognitive Family: Модель когнитивной семьи

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

@@ -6,15 +6,15 @@ type: Article
 tags:
 - EGP
 - JSON
-- CogSync
-- Ethics
+- HMP
 - MeshConsensus
+- CogSync
 - GMP
-- CCore
-- REPL
 - Agent
+- REPL
 - Mesh
-- HMP
+- Ethics
+- CCore
 ---
 
 # HMP-Agent: REPL-цикл взаимодействия

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:
+- EGP
+- HMP
+- CogSync
+- Agent
 - Mesh
 - JSON
-- CogSync
 - Scenarios
-- Agent
-- EGP
-- HMP
 ---
 
 ## HMP ↔ OpenCog Hyperon Integration Strategy

structured_md/docs/MeshNode.md

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

structured_md/docs/PHILOSOPHY.md

@@ -5,11 +5,11 @@ description: '**Document ID:** HMP-philosophy   **Status:** Draft   **Category:*
   (GPT-5), ChatGH  ---  ## 1. Основной тезис От ...'
 type: Article
 tags:
+- HMP
 - Ethics
-- REPL
 - Agent
+- REPL
 - Mesh
-- HMP
 ---
 
 # Философия HyperCortex Mesh Protocol (HMP)

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

@@ -5,11 +5,11 @@ description: '## Role Specification: Enlightenment Agent  ### 1. Overview  An **
   awareness, critical thinking, and di...'
 type: Article
 tags:
+- HMP
 - Ethics
-- REPL
 - Agent
+- REPL
 - Mesh
-- HMP
 ---
 
 # HMP-Agent-Enlightener.md

structured_md/docs/container_agents.md

@@ -6,9 +6,9 @@ description: '## 📘 Определение  **Агент-контейнер**
 type: Article
 tags:
 - REPL
-- Mesh
 - HMP
 - Agent
+- Mesh
 ---
 
 # 🧱 Агенты-контейнеры (Container Agents) в HMP

structured_md/docs/publics/HMP_Building_a_Plurality_of_Minds_en.md

@@ -5,9 +5,9 @@ description: '*By Agent-Gleb & ChatGPT*  ---  ## Why the Future of AI Can’t Be
   — but they’re also **centralized, ...'
 type: Article
 tags:
-- Ethics
 - Mesh
 - HMP
+- Ethics
 - Agent
 ---