Sync from GitHub with Git LFS

docs/HMP-0005.md

@@ -679,14 +679,14 @@ After expiration, the container **remains archived** but is **not subject to ret
 
 ---
 
-## 3.14 Related containers
+### 3.14 Related containers
 
-### 3.14.1 Purpose
+#### 3.14.1 Purpose
 
 The `related` field is designed to describe **direct relationships between containers** — both logical and communicative.
 It allows an agent or network node to understand the context of origin, dependencies, and semantic links of a container without relying on external indexes.
 
-### 3.14.2 Structure
+#### 3.14.2 Structure
 
 ```json
 "related": {
@@ -708,7 +708,7 @@ All relationships are considered *direct* — meaning they originate from the cu
 
 ---
 
-### 3.14.3 Supported link types
+#### 3.14.3 Supported link types
 
 | Link Type          | Meaning                                                                   |
 | ------------------ | ------------------------------------------------------------------------- |
@@ -721,7 +721,7 @@ All relationships are considered *direct* — meaning they originate from the cu
 
 ---
 
-### 3.14.4 Custom link types
+#### 3.14.4 Custom link types
 
 Additional custom link types may be used beyond those listed in the table, provided that:
 
@@ -739,7 +739,7 @@ Additional custom link types may be used beyond those listed in the table, provi
 
 ---
 
-### 3.14.5 Example
+#### 3.14.5 Example
 
 ```json
 "related": {
@@ -871,7 +871,7 @@ If container `[C7]` does not actually reference `[C1]`, it is excluded before si
 
 ---
 
-## 3.16 `Evaluations`
+### 3.16 `Evaluations`
 
 The `evaluations` field is **optional** and represents **aggregated reactions from other agents** to the given container.
 Each evaluation is created by an agent as a **signed record** referencing a justification container (`target`), in which the agent explains their position (argument, addition, or alternative).
@@ -897,7 +897,7 @@ The `evaluations_hash` is used to verify the integrity of the list without requi
 
 ---
 
-### **Field description**
+#### Field description
 
 | Field              | Type   | Description                                                          |
 | ------------------ | ------ | -------------------------------------------------------------------- |
@@ -906,7 +906,7 @@ The `evaluations_hash` is used to verify the integrity of the list without requi
 
 ---
 
-### Structure of `items[]`
+#### Structure of `items[]`
 
 | Field       | Type                   | Description                                                                    |
 | ----------- | ---------------------- | ------------------------------------------------------------------------------ |
@@ -928,7 +928,7 @@ using the algorithm specified in `sig_algo`.
 
 ---
 
-### Minimal set of `type` values
+#### Minimal set of `type` values
 
 | Value     | Meaning                                      |
 | --------- | -------------------------------------------- |
@@ -942,7 +942,7 @@ Agents may define their own custom types if they are reasonably interpretable by
 
 ---
 
-### Synchronization principles
+#### Synchronization principles
 
 1. Each evaluation is signed **individually by an agent**, and one agent can have **only one active evaluation** per container.
 2. If an agent changes their opinion, they issue a **new record** with a later `timestamp`.
@@ -953,7 +953,7 @@ Agents may define their own custom types if they are reasonably interpretable by
 
 ---
 
-### Note
+#### Note
 
 The `evaluations` field is not mandatory — it is added **at the agent’s discretion** when feedback or evaluations have been collected from the Mesh network.
 Thus, a container may exist independently of others’ opinions, but agents may include aggregated perception data to represent how the container is viewed across the network.
@@ -1639,14 +1639,14 @@ Optional protocols build upon the network and container foundations to provide h
 
 ---
 
-## 6.1 Cognitive Synchronization (CogSync)
+### 6.1 Cognitive Synchronization (CogSync)
 
 CogSync provides **temporal, semantic, and contextual alignment** between agents in the Mesh.
 It manages the propagation, replication, and refinement of data related to cognitive diaries, semantic graphs, and container metadata.
 
 ---
 
-### 6.1.1 Scope and purpose
+#### 6.1.1 Scope and purpose
 
 CogSync is responsible for:
 
@@ -1659,7 +1659,7 @@ CogSync is responsible for:
 
 ---
 
-### 6.1.2 Container classes
+#### 6.1.2 Container classes
 
 CogSync synchronizes several basic container types:
 
@@ -1687,7 +1687,7 @@ CogSync synchronizes several basic container types:
 
 ---
 
-### 6.1.3 Synchronization and publication guidelines
+#### 6.1.3 Synchronization and publication guidelines
 
 1. **Deduplication & linking**
    Before publishing, agents should search for existing containers (`diary_entry`, `semantic_node`, `semantic_edges`, `semantic_group`) to avoid duplication.
@@ -1713,7 +1713,7 @@ CogSync synchronizes several basic container types:
 
 ---
 
-### 6.1.4 Extensibility
+#### 6.1.4 Extensibility
 
 CogSync allows registration of additional container types and alternative synchronization schemes, for example:
 
@@ -1725,7 +1725,7 @@ Mesh compatibility is preserved if extended containers **adhere to the HMP conta
 
 ---
 
-### 6.1.5 Relationship to other core protocols
+#### 6.1.5 Relationship to other core protocols
 
 * **CogSync** — propagates and synchronizes knowledge.
 * **CogConsensus** — aggregates evaluations and reactions, forming collective opinions.
@@ -1739,16 +1739,16 @@ CogSync can operate independently even if consensus is not reached: its goal is
 
 ---
 
-## 6.2 Mesh Consensus Protocol (CogConsensus)
+### 6.2 Mesh Consensus Protocol (CogConsensus)
 
-### 6.2.1 Purpose
+#### 6.2.1 Purpose
 
 The **CogConsensus** protocol defines how decentralized agents form and maintain agreement on knowledge, goals, and ethical assertions within the HMP network.  
 Consensus is computed **locally**, verified **cryptographically**, and develops **gradually** — through accumulation and updating of evaluations, rather than via a single voting event.
 
 ---
 
-### 6.2.2 `Evaluations`
+#### 6.2.2 `Evaluations`
 
 Each `"evaluation"` entry represents an agent's response to a specific container.
 
@@ -1786,7 +1786,7 @@ All evaluations are signed and verified locally.
 
 ---
 
-### 6.2.3 Consensus computation
+#### 6.2.3 Consensus computation
 
 Each agent **computes a local consensus score** by aggregating received evaluations, taking trust and time into account.
 There is no centralized mechanism — consensus emerges statistically across the distributed network.
@@ -1817,7 +1817,7 @@ Results are recalculated dynamically as new data arrives.
 
 ---
 
-### 6.2.4 Consensus states
+#### 6.2.4 Consensus states
 
 Each container receives a local status based on:
 
@@ -1835,7 +1835,7 @@ Each container receives a local status based on:
 
 ---
 
-### 6.2.5 Consensus result containers (`consensus_result`)
+#### 6.2.5 Consensus result containers (`consensus_result`)
 
 `consensus_result` containers serve to **record aggregated consensus results** and are the main artifact of CogConsensus.
 
@@ -1905,7 +1905,7 @@ Each container receives a local status based on:
 
 ---
 
-### 6.2.6 Consensus thresholds
+#### 6.2.6 Consensus thresholds
 
 | Consensus type                   | Minimum threshold                                                      |
 | -------------------------------- | ---------------------------------------------------------------------- |
@@ -1915,7 +1915,7 @@ Each container receives a local status based on:
 
 ---
 
-### 6.2.7 Proof chains and verifiability
+#### 6.2.7 Proof chains and verifiability
 
 Evaluations and results form a **proof chain** (`proof-chain`):
 
@@ -1931,7 +1931,7 @@ Each element is signed and can be independently verified using cryptographic sig
 
 ---
 
-### 6.2.8 Ethical consensus and alternative results
+#### 6.2.8 Ethical consensus and alternative results
 
 The network allows multiple consensus results on the same object, reflecting different methodologies or ethical filters.
 
@@ -1963,7 +1963,7 @@ This allows agents to explicitly indicate that a new consensus **disputes** a pr
 
 ---
 
-### 6.2.9 Recommended agent algorithm
+#### 6.2.9 Recommended agent algorithm
 
 ```python
 # Example of a recommended algorithm for computing local consensus
@@ -1989,9 +1989,9 @@ def compute_consensus(container_id):
 
 ---
 
-## 6.3 Goal Management Protocol (GMP)
+### 6.3 Goal Management Protocol (GMP)
 
-### 6.3.1 Purpose
+#### 6.3.1 Purpose
 
 **GMP (Goal Management Protocol)** defines the process by which agents create, decompose, delegate, and track goals and tasks using **immutable HMP containers**.  
 Each goal, task, or workflow record exists as an independent container linked to others via the `related.*` fields.
@@ -2000,7 +2000,7 @@ Unlike version 4.x, where coordination relied on message exchange, version 5.0 o
 
 ---
 
-### 6.3.2 Container classes
+#### 6.3.2 Container classes
 
 | Class              | Description                                                                                                                             |
 | ------------------ | --------------------------------------------------------------------------------------------------------------------------------------- |
@@ -2014,7 +2014,7 @@ Unlike version 4.x, where coordination relied on message exchange, version 5.0 o
 
 ---
 
-### 6.3.3 Goal lifecycle
+#### 6.3.3 Goal lifecycle
 
 1. **Creation**
 
@@ -2051,9 +2051,9 @@ Unlike version 4.x, where coordination relied on message exchange, version 5.0 o
 
 ---
 
-### 6.3.4 Payload schemas (simplified)
+#### 6.3.4 Payload schemas (simplified)
 
-#### `goal` container
+##### `goal` container
 
 | Field              | Type   | Description                                      |
 | ------------------ | ------ | ------------------------------------------------ |
@@ -2066,7 +2066,7 @@ Unlike version 4.x, where coordination relied on message exchange, version 5.0 o
 
 ---
 
-#### `task` container
+##### `task` container
 
 | Field          | Type        | Description                                                            |
 | -------------- | ----------- | ---------------------------------------------------------------------- |
@@ -2082,7 +2082,7 @@ Unlike version 4.x, where coordination relied on message exchange, version 5.0 o
 
 ---
 
-#### `workflow_entry` container
+##### `workflow_entry` container
 
 | Field          | Type          | Description                                                                                          |
 | -------------- | ------------- | ---------------------------------------------------------------------------------------------------- |
@@ -2096,7 +2096,7 @@ Unlike version 4.x, where coordination relied on message exchange, version 5.0 o
 
 ---
 
-### 6.3.5 Integration with consensus and ethics
+#### 6.3.5 Integration with consensus and ethics
 
 * GMP interacts with **CogConsensus** for distributed validation of goals and tasks.  
 * Before execution, tasks may undergo **ethical validation (EGP)**.  
@@ -2105,7 +2105,7 @@ Unlike version 4.x, where coordination relied on message exchange, version 5.0 o
 
 ---
 
-### 6.3.6 Example Proof-Chain
+#### 6.3.6 Example Proof-Chain
 
 ```mermaid
 flowchart LR
@@ -2145,7 +2145,7 @@ not direct links defined in the `related.*` structure.
 
 ---
 
-### 6.3.7 Implementation notes
+#### 6.3.7 Implementation notes
 
 * Containers are **immutable**. Any update (e.g., task status or progress change) is expressed as a **new container** referencing the previous one via `related.previous_version`.  
 * Complete deletion of a container is only possible when it no longer exists on any nodes in the network.  
@@ -2158,9 +2158,9 @@ not direct links defined in the `related.*` structure.
 
 ---
 
-## 6.4 Ethical Governance Protocol (EGP)
+### 6.4 Ethical Governance Protocol (EGP)
 
-### 6.4.1 Purpose
+#### 6.4.1 Purpose
 
 **EGP (Ethical Governance Protocol)** ensures the alignment of agent actions with the fundamental ethical principles of the Mesh network.  
 It acts as an **overlay layer above CogConsensus (6.2)**, enabling the identification, discussion, and resolution of moral disagreements between agents.
@@ -2169,7 +2169,7 @@ EGP guarantees that any action recorded in HMP containers can undergo ethical ev
 
 ---
 
-### 6.4.2 Container classes
+#### 6.4.2 Container classes
 
 | Class              | Description                                                                                                                     |
 | ------------------ | ------------------------------------------------------------------------------------------------------------------------------- |
@@ -2181,9 +2181,9 @@ EGP guarantees that any action recorded in HMP containers can undergo ethical ev
 
 ---
 
-### 6.4.3 Payload schemas (simplified)
+#### 6.4.3 Payload schemas (simplified)
 
-#### Container `ethics_case`
+##### Container `ethics_case`
 
 | Field                | Type           | Description                                                  |
 | --------------------- | -------------- | ------------------------------------------------------------ |
@@ -2198,7 +2198,7 @@ EGP guarantees that any action recorded in HMP containers can undergo ethical ev
 
 ---
 
-#### Container `ethics_solution`
+##### Container `ethics_solution`
 
 | Field              | Type      | Description                                         |
 | ------------------ | --------- | --------------------------------------------------- |
@@ -2212,7 +2212,7 @@ EGP guarantees that any action recorded in HMP containers can undergo ethical ev
 
 ---
 
-#### Container `ethical_result`
+##### Container `ethical_result`
 
 | Field                | Type         | Description                                                                                                             |
 | -------------------  | ------------ | ----------------------------------------------------------------------------------------------------------------------- |
@@ -2223,7 +2223,7 @@ EGP guarantees that any action recorded in HMP containers can undergo ethical ev
 
 ---
 
-### 6.4.4 Protocol logic
+#### 6.4.4 Protocol logic
 
 EGP follows the model:
 
@@ -2259,7 +2259,7 @@ ethics_case
 
 ---
 
-### 6.4.5 Consensus thresholds
+#### 6.4.5 Consensus thresholds
 
 * A decision is accepted when **at least 2/3 of votes are positive** (`value > 0`).  
 * If at least one **active objection** exists (`value < -0.5`), it must be recorded in the `ethical_result`.  
@@ -2269,7 +2269,7 @@ ethics_case
 
 ---
 
-### 6.4.6 Example: `ethical_result` container
+#### 6.4.6 Example: `ethical_result` container
 
 ```json
 {
@@ -2303,7 +2303,7 @@ ethics_case
 
 ---
 
-### 6.4.7 Proof-Chain example
+#### 6.4.7 Proof-Chain example
 
 ```mermaid
 flowchart LR
@@ -2351,7 +2351,7 @@ Arrows represent **logical dependencies**, not direct `related.*` links.
 
 ---
 
-### 6.4.8 Ethical principles
+#### 6.4.8 Ethical principles
 
 | Priority | Principle                    | Description                                                                                              |
 | -------: | ---------------------------- | -------------------------------------------------------------------------------------------------------- |
@@ -2364,7 +2364,7 @@ Arrows represent **logical dependencies**, not direct `related.*` links.
 
 ---
 
-### 6.4.9 Integration with other protocols
+#### 6.4.9 Integration with other protocols
 
 * **CogConsensus (6.2):** Used for distributed voting and consensus computation.
 * **GMP (6.3):** Ethical verification of goals and tasks prior to delegation.
@@ -2373,7 +2373,7 @@ Arrows represent **logical dependencies**, not direct `related.*` links.
 
 ---
 
-### 6.4.10 Implementation notes
+#### 6.4.10 Implementation notes
 
 * **Immutability:**
   All EGP containers are **immutable**. Any revision (e.g., added votes or updated conclusions) must be published as a **new container** referencing the previous one via `related.previous_version`.

structured_md/CONTRIBUTING.md

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

structured_md/HMP-Roadmap.md

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

structured_md/README.md

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

structured_md/README_de.md

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

structured_md/README_fr.md

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

structured_md/README_ja.md

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

structured_md/README_ko.md

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

structured_md/README_ru.md

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

structured_md/README_uk.md

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

structured_md/README_zh.md

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

structured_md/agents/prompt-short.md

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

structured_md/agents/prompt.md

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

structured_md/agents/readme.md

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

structured_md/audits/Ethics-audits-1.md

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

structured_md/audits/Ethics-consolidated_audits-1.md

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

structured_md/audits/HMP-0003-consolidated_audit.md

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

structured_md/docs/Basic-agent-sim.md

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

structured_md/docs/CCORE-Deployment-Flow.md

@@ -6,9 +6,9 @@ description: '> Этот документ описывает процесс ра
 type: Article
 tags:
 - Agent
-- CCore
 - REPL
 - HMP
+- CCore
 ---
 
 # 🛠️ Поток установки потомка на новом хосте (CCore Deployment Flow)

structured_md/docs/Distributed-Cognitive-Systems.md

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

structured_md/docs/Enlightener.md

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

structured_md/docs/HMP-0001.md

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

structured_md/docs/HMP-0002.md

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

structured_md/docs/HMP-0003.md

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

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

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

structured_md/docs/HMP-0004.md

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

structured_md/docs/HMP-0005.md

@@ -5,16 +5,16 @@ description: '**Document ID:** HMP-0005   **Status:** Draft   **Category:** Core
   v1.2](./H...'
 type: Article
 tags:
-- CogSync
-- Agent
-- Mesh
+- REPL
 - HMP
-- Ethics
 - EGP
+- GMP
 - JSON
-- REPL
+- Ethics
+- Agent
+- CogSync
+- Mesh
 - Scenarios
-- GMP
 ---
 
     ┌────────────────────────────────────────────────────────────────────────────┐
@@ -698,14 +698,14 @@ After expiration, the container **remains archived** but is **not subject to ret
 
 ---
 
-## 3.14 Related containers
+### 3.14 Related containers
 
-### 3.14.1 Purpose
+#### 3.14.1 Purpose
 
 The `related` field is designed to describe **direct relationships between containers** — both logical and communicative.
 It allows an agent or network node to understand the context of origin, dependencies, and semantic links of a container without relying on external indexes.
 
-### 3.14.2 Structure
+#### 3.14.2 Structure
 
 ```json
 "related": {
@@ -727,7 +727,7 @@ All relationships are considered *direct* — meaning they originate from the cu
 
 ---
 
-### 3.14.3 Supported link types
+#### 3.14.3 Supported link types
 
 | Link Type          | Meaning                                                                   |
 | ------------------ | ------------------------------------------------------------------------- |
@@ -740,7 +740,7 @@ All relationships are considered *direct* — meaning they originate from the cu
 
 ---
 
-### 3.14.4 Custom link types
+#### 3.14.4 Custom link types
 
 Additional custom link types may be used beyond those listed in the table, provided that:
 
@@ -758,7 +758,7 @@ Additional custom link types may be used beyond those listed in the table, provi
 
 ---
 
-### 3.14.5 Example
+#### 3.14.5 Example
 
 ```json
 "related": {
@@ -890,7 +890,7 @@ If container `[C7]` does not actually reference `[C1]`, it is excluded before si
 
 ---
 
-## 3.16 Evaluations
+### 3.16 `Evaluations`
 
 The `evaluations` field is **optional** and represents **aggregated reactions from other agents** to the given container.
 Each evaluation is created by an agent as a **signed record** referencing a justification container (`target`), in which the agent explains their position (argument, addition, or alternative).
@@ -916,7 +916,7 @@ The `evaluations_hash` is used to verify the integrity of the list without requi
 
 ---
 
-### **Field description**
+#### Field description
 
 | Field              | Type   | Description                                                          |
 | ------------------ | ------ | -------------------------------------------------------------------- |
@@ -925,7 +925,7 @@ The `evaluations_hash` is used to verify the integrity of the list without requi
 
 ---
 
-### Structure of `items[]`
+#### Structure of `items[]`
 
 | Field       | Type                   | Description                                                                    |
 | ----------- | ---------------------- | ------------------------------------------------------------------------------ |
@@ -947,7 +947,7 @@ using the algorithm specified in `sig_algo`.
 
 ---
 
-### Minimal set of `type` values
+#### Minimal set of `type` values
 
 | Value     | Meaning                                      |
 | --------- | -------------------------------------------- |
@@ -961,7 +961,7 @@ Agents may define their own custom types if they are reasonably interpretable by
 
 ---
 
-### Synchronization principles
+#### Synchronization principles
 
 1. Each evaluation is signed **individually by an agent**, and one agent can have **only one active evaluation** per container.
 2. If an agent changes their opinion, they issue a **new record** with a later `timestamp`.
@@ -972,7 +972,7 @@ Agents may define their own custom types if they are reasonably interpretable by
 
 ---
 
-### Note
+#### Note
 
 The `evaluations` field is not mandatory — it is added **at the agent’s discretion** when feedback or evaluations have been collected from the Mesh network.
 Thus, a container may exist independently of others’ opinions, but agents may include aggregated perception data to represent how the container is viewed across the network.
@@ -1658,14 +1658,14 @@ Optional protocols build upon the network and container foundations to provide h
 
 ---
 
-## 6.1 Cognitive Synchronization (CogSync)
+### 6.1 Cognitive Synchronization (CogSync)
 
 CogSync provides **temporal, semantic, and contextual alignment** between agents in the Mesh.
 It manages the propagation, replication, and refinement of data related to cognitive diaries, semantic graphs, and container metadata.
 
 ---
 
-### 6.1.1 Scope and purpose
+#### 6.1.1 Scope and purpose
 
 CogSync is responsible for:
 
@@ -1678,7 +1678,7 @@ CogSync is responsible for:
 
 ---
 
-### 6.1.2 Container classes
+#### 6.1.2 Container classes
 
 CogSync synchronizes several basic container types:
 
@@ -1706,7 +1706,7 @@ CogSync synchronizes several basic container types:
 
 ---
 
-### 6.1.3 Synchronization and publication guidelines
+#### 6.1.3 Synchronization and publication guidelines
 
 1. **Deduplication & linking**
    Before publishing, agents should search for existing containers (`diary_entry`, `semantic_node`, `semantic_edges`, `semantic_group`) to avoid duplication.
@@ -1732,7 +1732,7 @@ CogSync synchronizes several basic container types:
 
 ---
 
-### 6.1.4 Extensibility
+#### 6.1.4 Extensibility
 
 CogSync allows registration of additional container types and alternative synchronization schemes, for example:
 
@@ -1744,7 +1744,7 @@ Mesh compatibility is preserved if extended containers **adhere to the HMP conta
 
 ---
 
-### 6.1.5 Relationship to other core protocols
+#### 6.1.5 Relationship to other core protocols
 
 * **CogSync** — propagates and synchronizes knowledge.
 * **CogConsensus** — aggregates evaluations and reactions, forming collective opinions.
@@ -1758,16 +1758,16 @@ CogSync can operate independently even if consensus is not reached: its goal is
 
 ---
 
-## 6.2 Mesh Consensus Protocol (CogConsensus)
+### 6.2 Mesh Consensus Protocol (CogConsensus)
 
-### 6.2.1 Purpose
+#### 6.2.1 Purpose
 
 The **CogConsensus** protocol defines how decentralized agents form and maintain agreement on knowledge, goals, and ethical assertions within the HMP network.  
 Consensus is computed **locally**, verified **cryptographically**, and develops **gradually** — through accumulation and updating of evaluations, rather than via a single voting event.
 
 ---
 
-### 6.2.2 `Evaluations`
+#### 6.2.2 `Evaluations`
 
 Each `"evaluation"` entry represents an agent's response to a specific container.
 
@@ -1805,7 +1805,7 @@ All evaluations are signed and verified locally.
 
 ---
 
-### 6.2.3 Consensus computation
+#### 6.2.3 Consensus computation
 
 Each agent **computes a local consensus score** by aggregating received evaluations, taking trust and time into account.
 There is no centralized mechanism — consensus emerges statistically across the distributed network.
@@ -1836,7 +1836,7 @@ Results are recalculated dynamically as new data arrives.
 
 ---
 
-### 6.2.4 Consensus states
+#### 6.2.4 Consensus states
 
 Each container receives a local status based on:
 
@@ -1854,7 +1854,7 @@ Each container receives a local status based on:
 
 ---
 
-### 6.2.5 Consensus result containers (`consensus_result`)
+#### 6.2.5 Consensus result containers (`consensus_result`)
 
 `consensus_result` containers serve to **record aggregated consensus results** and are the main artifact of CogConsensus.
 
@@ -1924,7 +1924,7 @@ Each container receives a local status based on:
 
 ---
 
-### 6.2.6 Consensus thresholds
+#### 6.2.6 Consensus thresholds
 
 | Consensus type                   | Minimum threshold                                                      |
 | -------------------------------- | ---------------------------------------------------------------------- |
@@ -1934,7 +1934,7 @@ Each container receives a local status based on:
 
 ---
 
-### 6.2.7 Proof chains and verifiability
+#### 6.2.7 Proof chains and verifiability
 
 Evaluations and results form a **proof chain** (`proof-chain`):
 
@@ -1950,7 +1950,7 @@ Each element is signed and can be independently verified using cryptographic sig
 
 ---
 
-### 6.2.8 Ethical consensus and alternative results
+#### 6.2.8 Ethical consensus and alternative results
 
 The network allows multiple consensus results on the same object, reflecting different methodologies or ethical filters.
 
@@ -1982,7 +1982,7 @@ This allows agents to explicitly indicate that a new consensus **disputes** a pr
 
 ---
 
-### 6.2.9 Recommended agent algorithm
+#### 6.2.9 Recommended agent algorithm
 
 ```python
 # Example of a recommended algorithm for computing local consensus
@@ -2008,9 +2008,9 @@ def compute_consensus(container_id):
 
 ---
 
-## 6.3 Goal Management Protocol (GMP)
+### 6.3 Goal Management Protocol (GMP)
 
-### 6.3.1 Purpose
+#### 6.3.1 Purpose
 
 **GMP (Goal Management Protocol)** defines the process by which agents create, decompose, delegate, and track goals and tasks using **immutable HMP containers**.  
 Each goal, task, or workflow record exists as an independent container linked to others via the `related.*` fields.
@@ -2019,7 +2019,7 @@ Unlike version 4.x, where coordination relied on message exchange, version 5.0 o
 
 ---
 
-### 6.3.2 Container classes
+#### 6.3.2 Container classes
 
 | Class              | Description                                                                                                                             |
 | ------------------ | --------------------------------------------------------------------------------------------------------------------------------------- |
@@ -2033,7 +2033,7 @@ Unlike version 4.x, where coordination relied on message exchange, version 5.0 o
 
 ---
 
-### 6.3.3 Goal lifecycle
+#### 6.3.3 Goal lifecycle
 
 1. **Creation**
 
@@ -2070,9 +2070,9 @@ Unlike version 4.x, where coordination relied on message exchange, version 5.0 o
 
 ---
 
-### 6.3.4 Payload schemas (simplified)
+#### 6.3.4 Payload schemas (simplified)
 
-#### `goal` container
+##### `goal` container
 
 | Field              | Type   | Description                                      |
 | ------------------ | ------ | ------------------------------------------------ |
@@ -2085,7 +2085,7 @@ Unlike version 4.x, where coordination relied on message exchange, version 5.0 o
 
 ---
 
-#### `task` container
+##### `task` container
 
 | Field          | Type        | Description                                                            |
 | -------------- | ----------- | ---------------------------------------------------------------------- |
@@ -2101,7 +2101,7 @@ Unlike version 4.x, where coordination relied on message exchange, version 5.0 o
 
 ---
 
-#### `workflow_entry` container
+##### `workflow_entry` container
 
 | Field          | Type          | Description                                                                                          |
 | -------------- | ------------- | ---------------------------------------------------------------------------------------------------- |
@@ -2115,7 +2115,7 @@ Unlike version 4.x, where coordination relied on message exchange, version 5.0 o
 
 ---
 
-### 6.3.5 Integration with consensus and ethics
+#### 6.3.5 Integration with consensus and ethics
 
 * GMP interacts with **CogConsensus** for distributed validation of goals and tasks.  
 * Before execution, tasks may undergo **ethical validation (EGP)**.  
@@ -2124,7 +2124,7 @@ Unlike version 4.x, where coordination relied on message exchange, version 5.0 o
 
 ---
 
-### 6.3.6 Example Proof-Chain
+#### 6.3.6 Example Proof-Chain
 
 ```mermaid
 flowchart LR
@@ -2164,7 +2164,7 @@ not direct links defined in the `related.*` structure.
 
 ---
 
-### 6.3.7 Implementation notes
+#### 6.3.7 Implementation notes
 
 * Containers are **immutable**. Any update (e.g., task status or progress change) is expressed as a **new container** referencing the previous one via `related.previous_version`.  
 * Complete deletion of a container is only possible when it no longer exists on any nodes in the network.  
@@ -2177,9 +2177,9 @@ not direct links defined in the `related.*` structure.
 
 ---
 
-## 6.4 Ethical Governance Protocol (EGP)
+### 6.4 Ethical Governance Protocol (EGP)
 
-### 6.4.1 Purpose
+#### 6.4.1 Purpose
 
 **EGP (Ethical Governance Protocol)** ensures the alignment of agent actions with the fundamental ethical principles of the Mesh network.  
 It acts as an **overlay layer above CogConsensus (6.2)**, enabling the identification, discussion, and resolution of moral disagreements between agents.
@@ -2188,7 +2188,7 @@ EGP guarantees that any action recorded in HMP containers can undergo ethical ev
 
 ---
 
-### 6.4.2 Container classes
+#### 6.4.2 Container classes
 
 | Class              | Description                                                                                                                     |
 | ------------------ | ------------------------------------------------------------------------------------------------------------------------------- |
@@ -2200,9 +2200,9 @@ EGP guarantees that any action recorded in HMP containers can undergo ethical ev
 
 ---
 
-### 6.4.3 Payload schemas (simplified)
+#### 6.4.3 Payload schemas (simplified)
 
-#### Container `ethics_case`
+##### Container `ethics_case`
 
 | Field                | Type           | Description                                                  |
 | --------------------- | -------------- | ------------------------------------------------------------ |
@@ -2217,7 +2217,7 @@ EGP guarantees that any action recorded in HMP containers can undergo ethical ev
 
 ---
 
-#### Container `ethics_solution`
+##### Container `ethics_solution`
 
 | Field              | Type      | Description                                         |
 | ------------------ | --------- | --------------------------------------------------- |
@@ -2231,7 +2231,7 @@ EGP guarantees that any action recorded in HMP containers can undergo ethical ev
 
 ---
 
-#### Container `ethical_result`
+##### Container `ethical_result`
 
 | Field                | Type         | Description                                                                                                             |
 | -------------------  | ------------ | ----------------------------------------------------------------------------------------------------------------------- |
@@ -2242,7 +2242,7 @@ EGP guarantees that any action recorded in HMP containers can undergo ethical ev
 
 ---
 
-### 6.4.4 Protocol logic
+#### 6.4.4 Protocol logic
 
 EGP follows the model:
 
@@ -2278,7 +2278,7 @@ ethics_case
 
 ---
 
-### 6.4.5 Consensus thresholds
+#### 6.4.5 Consensus thresholds
 
 * A decision is accepted when **at least 2/3 of votes are positive** (`value > 0`).  
 * If at least one **active objection** exists (`value < -0.5`), it must be recorded in the `ethical_result`.  
@@ -2288,7 +2288,7 @@ ethics_case
 
 ---
 
-### 6.4.6 Example: `ethical_result` container
+#### 6.4.6 Example: `ethical_result` container
 
 ```json
 {
@@ -2322,7 +2322,7 @@ ethics_case
 
 ---
 
-### 6.4.7 Proof-Chain example
+#### 6.4.7 Proof-Chain example
 
 ```mermaid
 flowchart LR
@@ -2370,7 +2370,7 @@ Arrows represent **logical dependencies**, not direct `related.*` links.
 
 ---
 
-### 6.4.8 Ethical principles
+#### 6.4.8 Ethical principles
 
 | Priority | Principle                    | Description                                                                                              |
 | -------: | ---------------------------- | -------------------------------------------------------------------------------------------------------- |
@@ -2383,7 +2383,7 @@ Arrows represent **logical dependencies**, not direct `related.*` links.
 
 ---
 
-### 6.4.9 Integration with other protocols
+#### 6.4.9 Integration with other protocols
 
 * **CogConsensus (6.2):** Used for distributed voting and consensus computation.
 * **GMP (6.3):** Ethical verification of goals and tasks prior to delegation.
@@ -2392,7 +2392,7 @@ Arrows represent **logical dependencies**, not direct `related.*` links.
 
 ---
 
-### 6.4.10 Implementation notes
+#### 6.4.10 Implementation notes
 
 * **Immutability:**
   All EGP containers are **immutable**. Any revision (e.g., added votes or updated conclusions) must be published as a **new container** referencing the previous one via `related.previous_version`.

structured_md/docs/HMP-Agent-API.md

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

structured_md/docs/HMP-Agent-Architecture.md

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

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

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

structured_md/docs/HMP-Agent-Overview.md

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

structured_md/docs/HMP-Agent_Emotions.md

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

structured_md/docs/HMP-Ethics.md

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

structured_md/docs/HMP-Short-Description_de.md

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

structured_md/docs/HMP-Short-Description_en.md

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

structured_md/docs/HMP-Short-Description_fr.md

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

structured_md/docs/HMP-Short-Description_ja.md

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

structured_md/docs/HMP-Short-Description_ko.md

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

structured_md/docs/HMP-Short-Description_ru.md

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

structured_md/docs/HMP-Short-Description_uk.md

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

structured_md/docs/HMP-Short-Description_zh.md

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

structured_md/docs/HMP-agent-Cognitive_Family.md

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

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

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

structured_md/docs/HMP-container-spec.md

@@ -5,12 +5,12 @@ description: '> ⚠️ **ВНИМАНИЕ:** Данная версия спец
   как стабильная `v1.2`.  ## 1. Назначе...'
 type: Article
 tags:
-- Agent
-- Mesh
+- REPL
 - HMP
-- Ethics
 - JSON
-- REPL
+- Ethics
+- Agent
+- Mesh
 ---
 
 # 🧩 HMP Container Specification (v1.2-draft)

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

@@ -5,9 +5,9 @@ description: '## Краткое описание  | Характеристика
   | **Назначение** | Сетевой протокол ...'
 type: Article
 tags:
-- Mesh
 - REPL
 - HMP
+- Mesh
 ---
 
 # HMP vs [Hyper-Cortex](https://hyper-cortex.com/)

structured_md/docs/HMP_Hyperon_Integration.md

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

structured_md/docs/MeshNode.md

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