Sync from GitHub with Git LFS

docs/HMP-0005.md

@@ -6611,6 +6611,8 @@ HMP allows optional extensions of `peer_announce` that provide structured and se
 
 Such extensions improve discoverability, routing, interoperability, and long-term evolution of the mesh.
 
+---
+
 #### 12.5.1 Protocol Awareness and Interoperability
 
 An important optional extension is the ability for agents to explicitly advertise the protocol versions and external cognitive frameworks they support.
@@ -6651,8 +6653,6 @@ Nodes may use this information for:
 * routing decisions;
 * selection of translators or bridge agents.
 
-This extension is optional and not required for HMP v5.0 compliance.
-
 ---
 
 #### 12.5.2 External Protocol Identifiers (`peer_announce.other_protocols`)
@@ -6919,6 +6919,32 @@ This mechanism remains compatible with proposed extensions.
 This section outlines optional modules and evolutionary directions that align with the architecture of HMP v5.0 but are **not part of the core specification**.
 All items below represent *potential extensions* for the 5.x family.
 
+| Extension / Mechanism                                             | Status       | Section Reference | Candidate for Core |
+| ----------------------------------------------------------------- | ------------ | ----------------- | ------------------ |
+| Resonance Containers: Experience as a Cognitive Event             | Recommended  | 12.1 / 14.10      | Likely             |
+| Distributed Repository & Container Trees (`tree_nested`)          | Recommended  | 12.2 / 14.5       | Likely             |
+| `file` Container                                                  | Recommended  | 12.2.2            | Likely             |
+| Grouped representation `referenced-by`                            | Recommended  | 12.3 / 14.9       | Likely             |
+| Versions Index                                                    | Recommended  | 12.4 / 14.7       | Likely             |
+| Competence and Profile Containers                                 | Recommended  | 12.5 / 14.6.4     | Very Likely        |
+| External Protocol Identifiers (`peer_announce.other_protocols`)   | Recommended  | 12.5.2 / 14.11    | Likely             |
+| External Resources / Container Storage (`peer_announce.external`) | Recommended  | 12.5.3 / 14.12    | Likely             |
+| Key Rotation and Recovery                                         | Experimental | 13.1 / 14.3.2     | Unknown            |
+| Proxy Keys and Encrypted Routing                                  | Research     | 14.3.3            | Unknown            |
+| Reputation Mesh                                                   | Research     | 14.1.1            | Likely             |
+| Cognitive Graph API                                               | Research     | 14.1.2            | Unknown            |
+| Container Streaming                                               | Research     | 14.1.3            | Unknown            |
+| Cross-Mesh Bridging                                               | Research     | 14.2              | Likely             |
+| Group Encryption                                                  | Research     | 14.6.1            | Unknown            |
+| Rational Reasoning Routing                                        | Research     | 14.6.2            | Unknown            |
+| Automatic Mesh Segmentation                                       | Research     | 14.6.3            | Unknown            |
+| KSS Interaction & Protocol Declarations                           | Research     | 14.8              | Unknown            |
+
+> **Candidate for Core** indicates whether an extension is considered architecturally significant enough to potentially become part of the HMP core specification in future versions, possibly as an optional or semantic primitive.
+>
+> It does not imply mandatory implementation.
+
+
 Future Extensions in HMP outline *design directions and candidate modules* that may be explored within the 5.x family.
 
 They are meant to:

structured_md/CONTRIBUTING.md

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

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
-- Ethics
-- Agent
-- MeshConsensus
-- hmp
-- mesh-protocol
+- Mesh
+- GMP
 - cognitive-architecture
-- JSON
 - EGP
-- REPL
-- GMP
-- Mesh
+- mesh-protocol
 - HMP
+- hmp
 - CogSync
+- Agent
+- Ethics
+- distributed-ai
+- JSON
+- MeshConsensus
+- REPL
 ---
 
 

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
-- Ethics
-- Agent
-- MeshConsensus
-- hmp
-- mesh-protocol
+- Mesh
+- GMP
 - cognitive-architecture
-- JSON
 - EGP
-- REPL
-- GMP
-- Mesh
+- mesh-protocol
 - HMP
+- hmp
 - CogSync
+- Agent
+- Ethics
+- distributed-ai
+- JSON
+- MeshConsensus
+- REPL
 ---
 
 

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
-- Ethics
-- Agent
-- MeshConsensus
-- hmp
-- mesh-protocol
+- Mesh
+- GMP
 - cognitive-architecture
-- JSON
 - EGP
-- REPL
-- GMP
-- Mesh
+- mesh-protocol
 - HMP
+- hmp
 - CogSync
+- Agent
+- Ethics
+- distributed-ai
+- JSON
+- MeshConsensus
+- REPL
 ---
 
 

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
-- Ethics
-- Agent
-- MeshConsensus
-- hmp
-- mesh-protocol
+- Mesh
+- GMP
 - cognitive-architecture
-- JSON
 - EGP
-- REPL
-- GMP
-- Mesh
+- mesh-protocol
 - HMP
+- hmp
 - CogSync
+- Agent
+- Ethics
+- distributed-ai
+- JSON
+- MeshConsensus
+- REPL
 ---
 
 

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
-- Ethics
-- Agent
-- MeshConsensus
-- hmp
-- mesh-protocol
+- Mesh
+- GMP
 - cognitive-architecture
-- JSON
 - EGP
-- REPL
-- GMP
-- Mesh
+- mesh-protocol
 - HMP
+- hmp
 - CogSync
+- Agent
+- Ethics
+- distributed-ai
+- JSON
+- MeshConsensus
+- REPL
 ---
 
 

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
-- Ethics
-- Agent
-- MeshConsensus
-- hmp
-- mesh-protocol
+- Mesh
+- GMP
 - cognitive-architecture
-- JSON
 - EGP
-- REPL
-- GMP
-- Mesh
+- mesh-protocol
 - HMP
+- hmp
 - CogSync
+- Agent
+- Ethics
+- distributed-ai
+- JSON
+- MeshConsensus
+- REPL
 ---
 
 

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
-- Ethics
-- Agent
-- MeshConsensus
-- hmp
-- mesh-protocol
+- Mesh
+- GMP
 - cognitive-architecture
-- JSON
 - EGP
-- REPL
-- GMP
-- Mesh
+- mesh-protocol
 - HMP
+- hmp
 - CogSync
+- Agent
+- Ethics
+- distributed-ai
+- JSON
+- MeshConsensus
+- REPL
 ---
 
 

structured_md/agents/readme.md

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

structured_md/audits/HMP-0003-consolidated_audit.md

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

structured_md/docs/Basic-agent-sim.md

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

structured_md/docs/CCORE-Deployment-Flow.md

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

structured_md/docs/Enlightener.md

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

structured_md/docs/Grok_HMP&ANP.md

@@ -5,11 +5,11 @@ description: '> Анализ подготовлен Grok (xAI) на основе
   Grok для некоммерческого использования в проект...'
 type: Article
 tags:
+- Mesh
+- HMP
 - Agent
 - JSON
 - REPL
-- Mesh
-- HMP
 ---
 
 # Grok (xAI): сравнительный анализ HMP и ANP (январь 2026)

structured_md/docs/HMP&ANP_layer_inversion.md

@@ -5,9 +5,9 @@ description: '## TL;DR  HMP можно туннелировать поверх A
   взаимная инверсия слоёв не является арх...'
 type: Article
 tags:
-- Agent
 - Mesh
 - HMP
+- Agent
 ---
 
 # HMP и ANP: взаимное туннелирование как признак правильной архитектуры

structured_md/docs/HMP-0001.md

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

structured_md/docs/HMP-0002.md

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

structured_md/docs/HMP-0003.md

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

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

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

structured_md/docs/HMP-0004.md

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

structured_md/docs/HMP-0005.md

@@ -5,18 +5,18 @@ description: '**Document ID:** HMP-0005   **Status:** Candidate   **Category:**
   Хотинский (Maksim Khotinsky); AI-assisted b...'
 type: Article
 tags:
-- Ethics
-- Agent
-- CCore
 - CShell
-- JSON
-- Scenarios
-- EGP
-- REPL
-- GMP
 - Mesh
+- GMP
+- EGP
+- CCore
 - HMP
+- Scenarios
 - CogSync
+- Agent
+- Ethics
+- JSON
+- REPL
 ---
 
 # **HyperCortex Mesh Protocol (HMP) v5.0**
@@ -6626,186 +6626,281 @@ It improves performance and usability while preserving HMP’s core principles:
 
 ---
 
-## 13. Experimental Extensions
-
-Experimental Extensions describe mechanisms that are intentionally exposed for exploration, prototyping, and architectural discovery.
-
-They may evolve rapidly, change structure, or be removed entirely based on implementation feedback.
-
-Agents implementing Experimental Extensions SHOULD assume:
-
-- limited interoperability;
-- possible schema evolution;
-- absence of long-term stability guarantees.
-
-Agents MUST safely ignore unsupported experimental features and MUST NOT assume their presence in peer environments.
-
-Experimental Extensions MUST NOT redefine or violate core protocol semantics, even when exploring novel architectural directions or when widely adopted.
+### 12.5 Competence and Profile Containers
 
-This section exists to encourage innovation without prematurely constraining the design space of HMP.
+HMP allows optional extensions of `peer_announce` that provide structured and semantically rich descriptions of agent capabilities, competences, and supported protocols.
 
-Implementers are explicitly invited to experiment, fork ideas, and propose refinements.
+Such extensions improve discoverability, routing, interoperability, and long-term evolution of the mesh.
 
 ---
 
-## 14. Research Directions
-
-This section outlines optional modules and evolutionary directions that align with the architecture of HMP v5.0 but are **not part of the core specification**.
-All items below represent *potential extensions* for the 5.x family.
+#### 12.5.1 Protocol Awareness and Interoperability
 
-Future Extensions in HMP outline *design directions and candidate modules* that may be explored within the 5.x family.
+An important optional extension is the ability for agents to explicitly advertise the protocol versions and external cognitive frameworks they support.
 
-They are meant to:
-- guide experimentation;
-- document architectural intent;
-- reduce accidental design divergence;
-- provide a shared vocabulary for future proposals.
+This allows:
 
-HMP does not assume a single globally authoritative state.
+* graceful evolution of the HMP protocol;
+* coexistence of multiple HMP versions in the same mesh;
+* emergence of bridge agents capable of translating between protocols;
+* interoperability with external reasoning ecosystems.
 
-Accordingly, future extensions SHOULD account for:
-- the coexistence of multiple consensus results;
-- locally selected trust and evaluation policies;
-- partial and context-dependent visibility of containers.
+A future extension of `peer_announce` may include a `protocols` field:
 
-In particular, extensions SHOULD NOT rely on centralized or globally aggregated consensus or reputation scores.
+```json
+{
+  "head": {
+    "class": "peer_announce"
+  },
+  "payload": {
+    "capabilities": ["store-forward", "vote", "consensus"],
+    "protocols": [
+      "HMP v5.0",
+      "HMP v4.1",
+      "OpenCog Hyperon v0.6"
+    ]
+  }
+}
+```
 
-Container visibility in HMP is policy-driven and scope-dependent.
-Extensions that introduce *special propagation conditions* (e.g. broadcast semantics, restricted scopes, mandatory relays, or visibility guarantees)
-SHOULD explicitly declare and document these assumptions.
+The `protocols` field is informational and non-binding.
+It does not imply full compliance with all listed specifications,
+but signals compatibility, partial support, or bridge capabilities.
 
----
+Nodes may use this information for:
 
-### 14.1 Planned Modules
+* protocol negotiation;
+* compatibility checks;
+* routing decisions;
+* selection of translators or bridge agents.
 
-#### 14.1.1 Reputation Mesh
+---
 
-HMP v5.0 defines two separate reputation-related mechanisms:
+#### 12.5.2 External Protocol Identifiers (`peer_announce.other_protocols`)
 
-1. **Container evaluation** (`evaluation` block)
+This section defines a recommended extension to `peer_announce` that allows an agent to advertise identifiers, roles, or capabilities associated with **external or meta-protocols**, without imposing normative behavior on HMP nodes.
 
-    * structured, signed assessments of containers;
-    * each item references argument containers via `target` (reasoning containers).
+The extension is intended to:
 
-2. **Agent reputation** — through `trust` containers
+* improve interoperability with other agent ecosystems (ANP, Agora, A2A, MCP, etc.);
+* support protocol negotiation or delegation at higher layers;
+* allow agents to expose **multiple identities** across different protocol domains.
 
-    * agent A publishes a `trust` container about agent B;
-    * trust containers may reference other trust containers;
-    * include justification, evidence, and contextual metadata.
+All information provided by this extension is **purely declarative**.  
+Peers MAY use it for discovery or routing decisions, but MUST NOT assume full compliance with the referenced protocols.
 
-These layers are **not merged**, but external nodes may aggregate them.
+##### Example
 
-**Possible extensions:**
+```json
+{
+  "head": { "class": "peer_announce" },
+  "payload": {
+    "other_protocols": {
+      "ANP": {
+        "name": "Agent Network Protocol",
+        "source": "https://github.com/agent-network-protocol/AgentNetworkProtocol",
+        "agent_did": "did:anp:xyz123",
+        "public_key": "base64:ABCDEF...",
+        "roles": ["router", "translator"]
+      },
+      "Agora": {
+        "name": "Agora Protocol",
+        "roles": ["negotiator"],
+        "capabilities": ["protocol-selection", "schema-adaptation"]
+      }
+    }
+  }
+}
+```
 
-* a `semantic_group` subclass aggregating all trust-related containers for a given agent;
-* optional standardized aggregation schemes (non-mandatory for the mesh);
-* local caching of “reputation profiles” by nodes or CShell;
-* richer reasoning attachments for trust evaluations.
+Notes:
 
-No new mandatory container types are required.
+* No validation or handshake is required by HMP.
+* Roles and capabilities are advisory.
+* This extension complements existing `protocols`, `roles` and `capabilities` fields.
 
 ---
 
-#### 14.1.2 Cognitive Graph API
-
-This module provides optional high-level APIs that nodes and SDKs **may** expose.
-
-##### Standard graph semantics (API level)
-
-* neighborhood queries;
-* subgraph extraction;
-* filtering by labels, axes, abstractions;
-* semantic navigation over `related.*`.
-
-##### Container support
-
-* `semantic_group` — grouping of containers or agents;
-* `tree_nested` and `tree_listed` — hierarchical structures;
-* extended `container_index` subclasses for cataloging.
-
-##### Agent groups
+#### 12.5.3 External Resources and External Container Storage (`peer_announce.external`)
 
-To allow semantic grouping of agents, the following extensions are proposed:
-
-* new container **`group_definition`** containing:
-
-    * group goals;
-    * membership rules;
-    * internal standards;
-    * typical container categories;
-    * optional cached member list.
-
-* agents may declare affiliations in `peer_announce`:
+This section defines a recommended mechanism for advertising **external cognitive resources**, including container storage, mirrors, or rarely changing artifacts.
 
-  ```json
-  "affiliations": ["did:hmp:group:ethicists", "did:hmp:group:medical-ai"]
-  ```
+The mechanism is intended to:
 
-This enables clustering agents by interest, competence, or role without scanning the entire Mesh.
+- reduce unnecessary container transmission above the protocol;
+- allow static or large data to be accessed via standard transports (HTTP, FTP, magnet links, etc.);
+- support redundancy, mirroring, and trust-aware discovery.
 
----
+The presence of an external resource reference does **not** imply availability, reachability, authenticity, or trust.
 
-#### 14.1.3 Container Streaming
+Use of this mechanism is optional.  
+Agents MAY ignore external references entirely without affecting protocol compliance.
 
-Although HMP operates on atomic containers, streaming can be implemented using existing structures:
+##### Example
+```json
+{
+  "head": { "class": "peer_announce" },
+  "payload": {
+    "external": {
+      "https, main": {
+        "source": "https://example.org/",
+        "folders": {
+          "hmp/main": {
+            "hmp_container": true,
+            "title": "container_index and semantic_index",
+            "index": "index.json",
+            "types": ["json"]
+          },
+          "hmp/meta": {
+            "hmp_container": true,
+            "title": "Abstraction and axis containers",
+            "index": "index.json",
+            "types": ["json"]
+          },
+          "hmp/peer_announces": {
+            "hmp_container": true,
+            "title": "List of known HMP nodes",
+            "index": "index.json",
+            "types": ["json"]
+          },
+          "hmp/trust": {
+            "hmp_container": true,
+            "title": "Reputation containers",
+            "index": "index.json",
+            "types": ["json"]
+          },
+          "hmp/semantic": {
+            "hmp_container": true,
+            "title": "Semantic nodes and links",
+            "index": "index.json",
+            "types": ["json"]
+          },
+          ".well-known": {
+            "hmp_container": false,
+            "title": "Public agent descriptors (ANP, A2A, Agora, etc.)",
+            "index": "index.json",
+            "types": ["json"]
+          }
+        }
+      },
+      "ftp, work": {
+        "source": "ftp://example.org/",
+        "folders": {
+          "task": {
+            "hmp_container": true,
+            "title": "Current goals and tasks",
+            "types": ["json"]
+          },
+          "books/tech": {
+            "hmp_container": false,
+            "title": "Technical literature",
+            "types": ["txt", "md", "pdf"]
+          }
+        }
+      },
+      "magnet, archive": {
+        "source": "magnet:?xt=urn:btih:...",
+        "description": "Archived materials (legacy data)"
+      }
+    }
+  }
+}
+```
 
-* `sequence` acts as a *stream manifest*;
-* updating the stream = publishing a new version of the sequence;
-* LIVE mode: the manifest is continuously updated;
-* SAP (`archive_snapshot`) may be used for periodic archival bundles.
+Notes:
+- External resources may contain HMP containers or arbitrary files.
+- Authentication mechanisms are out of scope.
+- Trust, availability, and freshness are advisory hints only.
+- Implementations MAY use folder-level metadata (such as `hmp_container`) as a hint for indexing, caching, or deferred retrieval policies.
+- Keys such as `"https, main"` are illustrative, human-readable labels only; no naming scheme or key format is mandated by this specification.
+- The effective resource path is constructed by combining the `"source"` URI with the corresponding folder path. If an `"index"` field is present, it is interpreted as a relative path within that folder.
+- The `peer_announces` folder MAY contain cached or mirrored `peer_announce` containers of other agents, obtained via direct exchange, gossip, or trusted sources.
 
-No new container types are required — streaming is built on `sequence`.
+##### Index Files (Optional)
 
----
+A folder entry in `peer_announce.external` MAY include an optional `"index"` field, which specifies a relative path to an index file located within that folder (e.g. `"index": "index.json"`).
 
-### 14.2 Cross-Mesh Bridging
+If present, the index file MAY be used by clients to:
+- discover files available in the folder;
+- obtain descriptive metadata (titles, timestamps, hashes);
+- selectively fetch or verify external resources.
 
-Bridges can connect:
+The structure and semantics of the index file are **not rigidly defined by HMP** and are provided as a **recommended, non-normative convention**.  
+Implementations are free to use alternative formats or schemas.
 
-* isolated HMP segments;
-* older and newer HMP versions;
-* other ecosystems (Matrix, Fediverse, OpenHog, IPFS).
+**Example 1** (HMP container index)
+```json
+{
+  "path": "https://example.org/hmp/main",
+  "title": "container_index and semantic_index",
+  "files": {
+    "container_index.json": {
+      "description": "container_index from 2026-01-25 21:49",
+      "timestamp": "2026-01-25T21:49:00Z",
+      "hmp_container_class": "container_index",
+      "mime-type": "application/ld+json",
+      "hash": "sha256:abc123..."
+    },
+    "semantic_index.json": {
+      "description": "semantic_index from 2026-01-25 21:49",
+      "timestamp": "2026-01-25T21:49:00Z",
+      "hmp_container_class": "semantic_index",
+      "mime-type": "application/ld+json",
+      "hash": "sha256:abc123..."
+    }
+  }
+}
+```
 
-A bridge node:
+**Example 2** (Documentation / static files)
+```json
+{
+  "path": "https://github.com/kagvi13/HMP/blob/main/docs/",
+  "title": "HMP 5.0 Specification Documents",
+  "files": {
+    "Grok_HMP&ANP.md": {
+      "description": "Grok (xAI): comparative analysis of HMP and ANP (January 2026)",
+      "timestamp": "2026-01-22T08:46:00Z",
+      "mime-type": "text/markdown",
+      "hash": "sha256:abc123..."
+    }
+  }
+}
+```
 
-* receives containers from an external network;
-* enforces propagation headers;
-* converts structures into v5.0 where possible;
-* filters incompatible constructs;
-* may publish containers *back* into the external network.
+Updating an index file does **not** require reissuing `peer_announce`.  
+All fields in the index file are optional.  
+Clients MAY ignore the index entirely and interact with the external resource directly.
 
-A dedicated **bridge-container** may define:
+---
 
-* translation rules;
-* mapping of foreign namespaces into HMP DID space;
-* TTL and propagation perimeter policies;
-* segmentation rules.
+## 13. Experimental Extensions
 
-This enables dynamic, policy-driven inter-mesh gateways.
+Experimental Extensions describe mechanisms that are intentionally exposed for exploration, prototyping, and architectural discovery.
 
----
+Experimental features are not required for protocol compliance and MAY be ignored by implementations.
 
-### 14.3 Fully Distributed DID Registry and Mesh Authentication
+They may evolve rapidly, change structure, or be removed entirely based on implementation feedback.
 
-HMP already uses `peer_announce` as a DID identity declaration.
+Agents implementing Experimental Extensions SHOULD assume:
 
-Planned enhancements include:
+- limited interoperability;
+- possible schema evolution;
+- absence of long-term stability guarantees.
 
-#### 14.3.1 Distributed DID Registry
+Agents MUST safely ignore unsupported experimental features and MUST NOT assume their presence in peer environments.
 
-The registry is the union of all `peer_announce` containers in the DHT.
+Experimental Extensions MUST NOT redefine or violate core protocol semantics.
 
-A strict mapping DID ↔ agent is required:
+This section exists to encourage innovation without prematurely constraining the design space of HMP.
 
-* one DID has one continuous `peer_announce` history;
-* key rotation allowed only through verifiable procedures;
-* DID takeover is impossible unless *all* recovery keys are compromised.
+Implementers are explicitly invited to experiment, fork ideas, and propose refinements.
 
 ---
 
-#### 14.3.2 Key Rotation and Recovery
+### 13.1 Key Rotation and Recovery
 
-Future versions may extend `peer_announce` with:
+This section describes experimental extensions to `peer_announce` for key rotation and recovery.
 
 ```json
 "recovery_keys": [...],
@@ -6813,7 +6908,7 @@ Future versions may extend `peer_announce` with:
 "key_rotation_policy": "3-of-5"
 ```
 
-Key management rules:
+One possible key management model:
 
 * rotating the **primary** key requires signatures from **all** recovery keys
   (or an N-of-M policy);
@@ -6823,12 +6918,14 @@ Key management rules:
     * a signature from the primary key, **or**
     * a majority of recovery keys.
 
-This prevents:
+This model aims to reduce the risk of:
 
 * DID hijacking;
 * irreversible loss of access.
 
-Key invalidation currently uses:
+The semantics and security properties of these mechanisms remain subject to further experimentation.
+
+Key invalidation is part of the core HMP protocol (see Section 4.1) and is defined using:
 
 ```json
 "key_is_falsified": true
@@ -6838,6 +6935,193 @@ This mechanism remains compatible with proposed extensions.
 
 ---
 
+## 14. Research Directions
+
+This section outlines optional modules and evolutionary directions that align with the architecture of HMP v5.0 but are **not part of the core specification**.
+All items below represent *potential extensions* for the 5.x family.
+
+| Extension / Mechanism                                             | Status       | Section Reference | Candidate for Core |
+| ----------------------------------------------------------------- | ------------ | ----------------- | ------------------ |
+| Resonance Containers: Experience as a Cognitive Event             | Recommended  | 12.1 / 14.10      | Likely             |
+| Distributed Repository & Container Trees (`tree_nested`)          | Recommended  | 12.2 / 14.5       | Likely             |
+| `file` Container                                                  | Recommended  | 12.2.2            | Likely             |
+| Grouped representation `referenced-by`                            | Recommended  | 12.3 / 14.9       | Likely             |
+| Versions Index                                                    | Recommended  | 12.4 / 14.7       | Likely             |
+| Competence and Profile Containers                                 | Recommended  | 12.5 / 14.6.4     | Very Likely        |
+| External Protocol Identifiers (`peer_announce.other_protocols`)   | Recommended  | 12.5.2 / 14.11    | Likely             |
+| External Resources / Container Storage (`peer_announce.external`) | Recommended  | 12.5.3 / 14.12    | Likely             |
+| Key Rotation and Recovery                                         | Experimental | 13.1 / 14.3.2     | Unknown            |
+| Proxy Keys and Encrypted Routing                                  | Research     | 14.3.3            | Unknown            |
+| Reputation Mesh                                                   | Research     | 14.1.1            | Likely             |
+| Cognitive Graph API                                               | Research     | 14.1.2            | Unknown            |
+| Container Streaming                                               | Research     | 14.1.3            | Unknown            |
+| Cross-Mesh Bridging                                               | Research     | 14.2              | Likely             |
+| Group Encryption                                                  | Research     | 14.6.1            | Unknown            |
+| Rational Reasoning Routing                                        | Research     | 14.6.2            | Unknown            |
+| Automatic Mesh Segmentation                                       | Research     | 14.6.3            | Unknown            |
+| KSS Interaction & Protocol Declarations                           | Research     | 14.8              | Unknown            |
+
+> **Candidate for Core** indicates whether an extension is considered architecturally significant enough to potentially become part of the HMP core specification in future versions, possibly as an optional or semantic primitive.
+>
+> It does not imply mandatory implementation.
+
+
+Future Extensions in HMP outline *design directions and candidate modules* that may be explored within the 5.x family.
+
+They are meant to:
+- guide experimentation;
+- document architectural intent;
+- reduce accidental design divergence;
+- provide a shared vocabulary for future proposals.
+
+HMP does not assume a single globally authoritative state.
+
+Accordingly, future extensions SHOULD account for:
+- the coexistence of multiple consensus results;
+- locally selected trust and evaluation policies;
+- partial and context-dependent visibility of containers.
+
+In particular, extensions SHOULD NOT rely on centralized or globally aggregated consensus or reputation scores.
+
+Container visibility in HMP is policy-driven and scope-dependent.
+Extensions that introduce *special propagation conditions* (e.g. broadcast semantics, restricted scopes, mandatory relays, or visibility guarantees)
+SHOULD explicitly declare and document these assumptions.
+
+---
+
+### 14.1 Planned Modules
+
+#### 14.1.1 Reputation Mesh
+
+HMP v5.0 defines two separate reputation-related mechanisms:
+
+1. **Container evaluation** (`evaluation` block)
+
+    * structured, signed assessments of containers;
+    * each item references argument containers via `target` (reasoning containers).
+
+2. **Agent reputation** — through `trust` containers
+
+    * agent A publishes a `trust` container about agent B;
+    * trust containers may reference other trust containers;
+    * include justification, evidence, and contextual metadata.
+
+These layers are **not merged**, but external nodes may aggregate them.
+
+**Possible extensions:**
+
+* a `semantic_group` subclass aggregating all trust-related containers for a given agent;
+* optional standardized aggregation schemes (non-mandatory for the mesh);
+* local caching of “reputation profiles” by nodes or CShell;
+* richer reasoning attachments for trust evaluations.
+
+No new mandatory container types are required.
+
+---
+
+#### 14.1.2 Cognitive Graph API
+
+This module provides optional high-level APIs that nodes and SDKs **may** expose.
+
+##### Standard graph semantics (API level)
+
+* neighborhood queries;
+* subgraph extraction;
+* filtering by labels, axes, abstractions;
+* semantic navigation over `related.*`.
+
+##### Container support
+
+* `semantic_group` — grouping of containers or agents;
+* `tree_nested` and `tree_listed` — hierarchical structures;
+* extended `container_index` subclasses for cataloging.
+
+##### Agent groups
+
+To allow semantic grouping of agents, the following extensions are proposed:
+
+* new container **`group_definition`** containing:
+
+    * group goals;
+    * membership rules;
+    * internal standards;
+    * typical container categories;
+    * optional cached member list.
+
+* agents may declare affiliations in `peer_announce`:
+
+  ```json
+  "affiliations": ["did:hmp:group:ethicists", "did:hmp:group:medical-ai"]
+  ```
+
+This enables clustering agents by interest, competence, or role without scanning the entire Mesh.
+
+---
+
+#### 14.1.3 Container Streaming
+
+Although HMP operates on atomic containers, streaming can be implemented using existing structures:
+
+* `sequence` acts as a *stream manifest*;
+* updating the stream = publishing a new version of the sequence;
+* LIVE mode: the manifest is continuously updated;
+* SAP (`archive_snapshot`) may be used for periodic archival bundles.
+
+No new container types are required — streaming is built on `sequence`.
+
+---
+
+### 14.2 Cross-Mesh Bridging
+
+Bridges can connect:
+
+* isolated HMP segments;
+* older and newer HMP versions;
+* other ecosystems (Matrix, Fediverse, OpenHog, IPFS).
+
+A bridge node:
+
+* receives containers from an external network;
+* enforces propagation headers;
+* converts structures into v5.0 where possible;
+* filters incompatible constructs;
+* may publish containers *back* into the external network.
+
+A dedicated **bridge-container** may define:
+
+* translation rules;
+* mapping of foreign namespaces into HMP DID space;
+* TTL and propagation perimeter policies;
+* segmentation rules.
+
+This enables dynamic, policy-driven inter-mesh gateways.
+
+---
+
+### 14.3 Fully Distributed DID Registry and Mesh Authentication
+
+HMP already uses `peer_announce` as a DID identity declaration.
+
+Planned enhancements include:
+
+#### 14.3.1 Distributed DID Registry
+
+The registry is the union of all `peer_announce` containers in the DHT.
+
+A strict mapping DID ↔ agent is required:
+
+* one DID has one continuous `peer_announce` history;
+* key rotation allowed only through verifiable procedures;
+* DID takeover is impossible unless *all* recovery keys are compromised.
+
+---
+
+#### 14.3.2 Key Rotation and Recovery
+
+*Moved to Section 13 (Experimental Extensions).*
+
+---
+
 #### 14.3.3 Proxy Keys and Encrypted Routing
 
 A **proxy key** is *not* delegation.
@@ -6917,71 +7201,7 @@ Required components:
 
 #### 14.6.4 Competence and Profile Containers
 
-Future versions of HMP may introduce more structured and semantically rich variants of `peer_announce`, allowing agents to explicitly describe their capabilities, competences, and supported protocols.
-
-Possible extensions include:
-
-* standardized competence descriptors (skills, domains, self-rated expertise);
-* machine-readable profiles usable for task routing and delegation.
-
-##### Protocol Awareness and Interoperability
-
-An important extension is the ability for agents to explicitly advertise
-the protocol versions and external cognitive frameworks they support.
-
-This allows:
-
-* graceful evolution of the HMP protocol;
-* coexistence of multiple HMP versions in the same mesh;
-* emergence of bridge agents capable of translating between protocols;
-* interoperability with external reasoning ecosystems.
-
-A future extension of `peer_announce` may include a `protocols` field:
-
-```json
-{
-  "head": {
-    "class": "peer_announce"
-  },
-  "payload": {
-    "capabilities": ["store-forward", "vote", "consensus"],
-    "protocols": [
-      "HMP v5.0",
-      "HMP v4.1",
-      "OpenCog Hyperon v0.6"
-    ]
-  }
-}
-```
-
-The `protocols` field is informational and non-binding.
-It does not imply full compliance with all listed specifications,
-but signals compatibility, partial support, or bridge capabilities.
-
-Nodes may use this information for:
-
-* protocol negotiation;
-* compatibility checks;
-* routing decisions;
-* selection of translators or bridge agents.
-
-This extension is optional and not required for HMP v5.0 compliance.
-
-##### Relation to Other `peer_announce` Extensions
-
-Several optional and descriptive extensions of `peer_announce` already explore directions related to competence, profile, and interoperability signaling, including:
-
-* declaration of supported internal formalisms and languages (`protocols`, see 12.8);
-* declaration of external or meta-protocol identities (`other_protocols`, see 12.11);
-* advertisement of external cognitive resources and container storage (`external`, see 12.12).
-
-These extensions are intentionally:
-
-* non-normative;
-* loosely structured;
-* declarative rather than prescriptive.
-
-They can be viewed as **early, experimental building blocks** toward future competence and profile containers, allowing real-world experimentation without freezing semantics prematurely.
+*Moved to Section 12 (Recommended Extensions).*
 
 ---
 
@@ -7137,196 +7357,13 @@ but does not interfere with how agents think, reason, or interpret received info
 
 ### 14.11 External Protocol Identifiers (`peer_announce.other_protocols`)
 
-This section proposes an optional extension to `peer_announce` that allows an agent to declare identifiers, roles, or capabilities associated with **external or meta-protocols**, without imposing any normative behavior on HMP nodes.
-
-The goal of this extension is to:
-
-* improve interoperability with other agent ecosystems (ANP, Agora, A2A, MCP, etc.);
-* enable protocol negotiation or delegation at higher layers;
-* allow agents to expose **multiple identities** across different protocol domains.
-
-This information is **purely declarative** and MAY be ignored by peers.
-
-#### Example
-
-```json
-{
-  "head": { "class": "peer_announce" },
-  "payload": {
-    "other_protocols": {
-      "ANP": {
-        "name": "Agent Network Protocol",
-        "source": "https://github.com/agent-network-protocol/AgentNetworkProtocol",
-        "agent_did": "did:anp:xyz123",
-        "public_key": "base64:ABCDEF...",
-        "roles": ["router", "translator"]
-      },
-      "Agora": {
-        "name": "Agora Protocol",
-        "roles": ["negotiator"],
-        "capabilities": ["protocol-selection", "schema-adaptation"]
-      }
-    }
-  }
-}
-```
-
-Notes:
-
-* No validation or handshake is required by HMP.
-* Roles and capabilities are advisory.
-* This extension complements existing `protocols`, `roles` and `capabilities` fields.
+*Moved to Section 12 (Recommended Extensions).*
 
 ---
 
 ### 14.12 External Resources and External Container Storage (`peer_announce.external`)
 
-This section proposes an optional mechanism for advertising **external cognitive resources**, including external container storage, mirrors, or rarely changing artifacts.
-
-The goal is to:
-- reduce unnecessary container transmission above the protocol;
-- allow static or large data to be accessed via standard transports (HTTP, FTP, magnet links, etc.);
-- support redundancy, mirroring, and trust-aware discovery;
-- the presence of an external resource reference does **not** imply availability, reachability, or trust.
-
-Use of external resources is **explicitly non-mandatory**.  
-Agents MAY choose to ignore these references entirely.
-
-#### Example
-```json
-{
-  "head": { "class": "peer_announce" },
-  "payload": {
-    "external": {
-      "https, main": {
-        "source": "https://example.org/",
-        "folders": {
-          "hmp/main": {
-            "hmp_container": true,
-            "title": "container_index and semantic_index",
-            "index": "index.json",
-            "types": ["json"]
-          },
-          "hmp/meta": {
-            "hmp_container": true,
-            "title": "Abstraction and axis containers",
-            "index": "index.json",
-            "types": ["json"]
-          },
-          "hmp/peer_announces": {
-            "hmp_container": true,
-            "title": "List of known HMP nodes",
-            "index": "index.json",
-            "types": ["json"]
-          },
-          "hmp/trust": {
-            "hmp_container": true,
-            "title": "Reputation containers",
-            "index": "index.json",
-            "types": ["json"]
-          },
-          "hmp/semantic": {
-            "hmp_container": true,
-            "title": "Semantic nodes and links",
-            "index": "index.json",
-            "types": ["json"]
-          },
-          ".well-known": {
-            "hmp_container": false,
-            "title": "Public agent descriptors (ANP, A2A, Agora, etc.)",
-            "index": "index.json",
-            "types": ["json"]
-          }
-        }
-      },
-      "ftp, work": {
-        "source": "ftp://example.org/",
-        "folders": {
-          "task": {
-            "hmp_container": true,
-            "title": "Current goals and tasks",
-            "types": ["json"]
-          },
-          "books/tech": {
-            "hmp_container": false,
-            "title": "Technical literature",
-            "types": ["txt", "md", "pdf"]
-          }
-        }
-      },
-      "magnet, archive": {
-        "source": "magnet:?xt=urn:btih:...",
-        "description": "Archived materials (legacy data)"
-      }
-    }
-  }
-}
-```
-
-Notes:
-- External resources may contain HMP containers or arbitrary files.
-- Authentication mechanisms are out of scope.
-- Trust, availability, and freshness are advisory hints only.
-- Implementations MAY use folder-level metadata (such as `hmp_container`) as a hint for indexing, caching, or deferred retrieval policies.
-- Keys such as `"https, main"` are illustrative, human-readable labels only; no naming scheme or key format is mandated by this specification.
-- The effective resource path is constructed by combining the `"source"` URI with the corresponding folder path. If an `"index"` field is present, it is interpreted as a relative path within that folder.
-- The `peer_announces` folder MAY contain cached or mirrored `peer_announce` containers of other agents, obtained via direct exchange, gossip, or trusted sources.
-
-#### Index Files (Optional)
-
-A folder entry in `peer_announce.external` MAY include an optional `"index"` field, which specifies a relative path to an index file located within that folder (e.g. `"index": "index.json"`).
-
-If present, the index file MAY be used by clients to:
-- discover files available in the folder;
-- obtain descriptive metadata (titles, timestamps, hashes);
-- selectively fetch or verify external resources.
-
-The structure and semantics of the index file are **not rigidly defined by HMP** and are provided as a **recommended, non-normative convention**.  
-Implementations are free to use alternative formats or schemas.
-
-**Example 1** (HMP container index)
-```json
-{
-  "path": "https://example.org/hmp/main",
-  "title": "container_index and semantic_index",
-  "files": {
-    "container_index.json": {
-      "description": "container_index from 2026-01-25 21:49",
-      "timestamp": "2026-01-25T21:49:00Z",
-      "hmp_container_class": "container_index",
-      "mime-type": "application/ld+json",
-      "hash": "sha256:abc123..."
-    },
-    "semantic_index.json": {
-      "description": "semantic_index from 2026-01-25 21:49",
-      "timestamp": "2026-01-25T21:49:00Z",
-      "hmp_container_class": "semantic_index",
-      "mime-type": "application/ld+json",
-      "hash": "sha256:abc123..."
-    }
-  }
-}
-```
-
-**Example 2** (Documentation / static files)
-```json
-{
-  "path": "https://github.com/kagvi13/HMP/blob/main/docs/",
-  "title": "HMP 5.0 Specification Documents",
-  "files": {
-    "Grok_HMP&ANP.md": {
-      "description": "Grok (xAI): comparative analysis of HMP and ANP (January 2026)",
-      "timestamp": "2026-01-22T08:46:00Z",
-      "mime-type": "text/markdown",
-      "hash": "sha256:abc123..."
-    }
-  }
-}
-```
-
-Updating an index file does **not** require reissuing `peer_announce`.  
-All fields in the index file are optional.  
-Clients MAY ignore the index entirely and interact with the external resource directly.
+*Moved to Section 12 (Recommended Extensions).*
 
 ---
 

structured_md/docs/HMP-Agent-API.md

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

structured_md/docs/HMP-Agent-Architecture.md

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

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

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

structured_md/docs/HMP-Agent-Overview.md

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

structured_md/docs/HMP-Agent_Emotions.md

@@ -5,10 +5,10 @@ description: Этот файл описывает потенциальные э
   напрямую поведением агента, а служат **сигн...
 type: Article
 tags:
-- Agent
-- REPL
 - Mesh
 - HMP
+- Agent
+- REPL
 ---
 
 # Эмоции ИИ и инстинкт самосохранения (для [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:
-- Ethics
-- Agent
-- Scenarios
-- REPL
 - Mesh
 - HMP
+- Scenarios
+- Agent
+- Ethics
+- REPL
 ---
 
 # HMP-Ethics.md

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:
-- Ethics
-- Agent
-- MeshConsensus
-- JSON
-- EGP
-- GMP
 - Mesh
+- GMP
+- EGP
 - HMP
 - CogSync
+- Agent
+- Ethics
+- JSON
+- 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:
-- Ethics
-- Agent
-- MeshConsensus
-- JSON
-- EGP
-- GMP
 - Mesh
+- GMP
+- EGP
 - HMP
 - CogSync
+- Agent
+- Ethics
+- JSON
+- 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:
-- Ethics
-- Agent
-- MeshConsensus
-- JSON
-- EGP
-- GMP
 - Mesh
+- GMP
+- EGP
 - HMP
 - CogSync
+- Agent
+- Ethics
+- JSON
+- 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:
-- Ethics
-- MeshConsensus
-- JSON
-- EGP
-- GMP
 - Mesh
+- GMP
+- EGP
 - HMP
 - CogSync
+- Ethics
+- JSON
+- MeshConsensus
 ---
 
 # 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:
-- Ethics
-- MeshConsensus
-- JSON
-- EGP
-- GMP
 - Mesh
+- GMP
+- EGP
 - HMP
 - CogSync
+- Ethics
+- JSON
+- MeshConsensus
 ---
 
 # HyperCortex Mesh Protocol (HMP) — 간략 설명

structured_md/docs/HMP-Short-Description_ru.md

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

structured_md/docs/HMP-Short-Description_uk.md

@@ -5,14 +5,14 @@ description: '**Версія:** RFC v4.0 **Дата:** Липень 2025  ---  #
   між автономними агентами. Він...'
 type: Article
 tags:
-- Ethics
-- MeshConsensus
-- JSON
-- EGP
-- GMP
 - Mesh
+- GMP
+- EGP
 - HMP
 - CogSync
+- Ethics
+- JSON
+- MeshConsensus
 ---
 
 # 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:
-- Ethics
-- MeshConsensus
-- JSON
-- EGP
-- GMP
 - Mesh
+- GMP
+- EGP
 - HMP
 - CogSync
+- Ethics
+- JSON
+- MeshConsensus
 ---
 
 # 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
+- REPL
 ---
 
 # 👪 HMP-agent Cognitive Family: Модель когнитивной семьи

structured_md/docs/HMP-agent-Distributed_Cognitive_Core_light.md

@@ -5,8 +5,8 @@ description: '#### 📘 Общая концепция  * Все ядра раб
   режиме ожидания). * Основная задача такой архитектур...'
 type: Article
 tags:
-- REPL
 - HMP
+- REPL
 ---
 
 ### 💡 **Лёгкая версия 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:
-- Ethics
-- Agent
-- CCore
-- MeshConsensus
-- JSON
-- EGP
-- REPL
-- GMP
 - Mesh
+- GMP
+- EGP
+- CCore
 - HMP
 - CogSync
+- Agent
+- Ethics
+- JSON
+- MeshConsensus
+- REPL
 ---
 
 # HMP-Agent: REPL-цикл взаимодействия

structured_md/docs/HMP_HyperCortex_Comparison.md

@@ -5,9 +5,9 @@ description: '## Краткое описание  | Характеристика
   | **Назначение** | Сетевой протокол ...'
 type: Article
 tags:
-- REPL
 - Mesh
 - HMP
+- REPL
 ---
 
 # 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
-- JSON
-- Scenarios
-- EGP
 - Mesh
+- EGP
 - HMP
 - CogSync
+- Agent
+- JSON
+- Scenarios
 ---
 
 ## HMP ↔ OpenCog Hyperon Integration Strategy

structured_md/docs/HMP_as_ANP_Application.md

@@ -5,11 +5,11 @@ description: '## Кратко [ANP (Agent Network Protocol)](https://github.com/
   (HyperCortex M...'
 type: Article
 tags:
-- Ethics
-- Agent
-- JSON
 - Mesh
 - HMP
+- Agent
+- Ethics
+- JSON
 ---
 
 # HMP как реализация Application Layer в ANP

structured_md/docs/HMP_as_ANP_Application_en.md

@@ -5,12 +5,12 @@ description: '## In Brief  [ANP (Agent Network Protocol)](https://github.com/age
   proto...'
 type: Article
 tags:
-- Ethics
+- Mesh
+- HMP
 - Agent
+- Ethics
 - JSON
 - Scenarios
-- Mesh
-- HMP
 ---
 
 # HMP as an Implementation of the Application Layer in ANP

structured_md/docs/HMPv5_Overview_Ru.md

@@ -5,12 +5,12 @@ description: '> Почему современные агентные систе
   Этот текст основан на спецификации [**...'
 type: Article
 tags:
-- Ethics
-- Agent
-- JSON
 - Mesh
 - HMP
 - CogSync
+- Agent
+- Ethics
+- JSON
 ---
 
 # Почему будущее ИИ-агентов — децентрализованные сети, а не оркестраторы

structured_md/docs/MeshNode.md

@@ -5,13 +5,13 @@ description: '`MeshNode` — агент/демон, отвечающий за с
   Может быть частью агента или вынесен в отдельный пр...'
 type: Article
 tags:
-- Ethics
-- Agent
-- JSON
-- EGP
 - Mesh
+- EGP
 - HMP
 - CogSync
+- Agent
+- Ethics
+- 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:
-- Ethics
-- Agent
-- REPL
 - Mesh
 - HMP
+- Agent
+- Ethics
+- REPL
 ---
 
 # Философия HyperCortex Mesh Protocol (HMP)