Sync from GitHub with Git LFS

docs/HMP-0005.md

@@ -2197,7 +2197,7 @@ Supports directed, symmetric, and inverse relations.
 
 ---
 
-##### `semantic_group`
+###### `semantic_group`
 
 Categorical grouping of multiple containers linked by a shared property, topic, or context.
 
@@ -2229,7 +2229,7 @@ Categorical grouping of multiple containers linked by a shared property, topic,
 
 ---
 
-#### `event`
+##### `event`
 
 **Purpose:**
 Represents an **observed or inferred occurrence** — a discrete, timestamped fact or cognitive transition.
@@ -2308,7 +2308,7 @@ An `event` is an atomic **evidence unit** that records a change in the agent’s
 
 ---
 
-#### `quant`
+##### `quant`
 
 **Purpose:**
 Defines a **semantic atom** — a minimal, self-contained knowledge unit positioned inside both
@@ -2402,7 +2402,7 @@ the **hierarchical abstraction tree** and the **multi-dimensional cognitive spac
 
 ---
 
-#### Cognitive substrate and container interplay
+##### Cognitive substrate and container interplay
 
 Containers `abstraction`, `axes`, `quant`, and `event` together define the **cognitive substrate** of the Mesh.
 They establish both **structural hierarchy** and **semantic positioning** — ensuring that all containers can be
@@ -2444,67 +2444,81 @@ consistently interpreted, compared, and synchronized across agents.
 #### 6.1.4 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.
-   If necessary, it is **recommended** to create a new container version with `related.previous_version` and an `evaluations` block (e.g., `{"type": "replace", "target": <did>}`).
+   Before publishing, agents should check for existing containers (`diary_entry`, `semantic_node`, `semantic_edges`, `semantic_group`) to prevent duplication.
+   If modification is required, agents **SHOULD** create a new container version referencing the previous one via `related.previous_version` and optionally include an `evaluation` block (e.g., `{ "type": "replace", "target": "<did>" }`) to the previous version of the container.
 
 2. **Selective disclosure**
 
-   * Internal entries (`workflow_entry`) record the agent’s thought process and are **not published** in the Mesh.
-   * Public `diary_entry` are derived from them, containing only aggregated and anonymized information.
-   * `"broadcast": true` indicates that the container is allowed for open synchronization.
+   * Internal containers (e.g., `workflow_entry`) capture the agent’s reasoning process and are **not published** (but may be published if they do not contain personal or confidential information).
+   * Public-facing `diary_entry` containers contain only generalized, anonymized results.
+   * The flag `"broadcast": true` explicitly allows open synchronization of a container.
 
 3. **Semantic grouping rule**
-   When publishing `semantic_edges`, it is recommended to **group edges by topics**, including connections to adjacent nodes.
-   Formalization: an edge belongs to a container for a topic if **at least one of its nodes relates to that topic**.
-   This ensures thematic coherence and allows agents to update specific parts of the graph independently.
+   When publishing `semantic_edges`, agents should group them **by conceptual topic**, ensuring that all connected nodes share thematic coherence.
+   Formal rule: an edge belongs to a topic container if **at least one of its nodes** relates to that topic.
+   This supports efficient and context-preserving updates to partial graph regions.
 
-4. **Extended Use of `semantic_edges`**
-   Beyond connecting graph nodes, `semantic_edges` can express relationships **between containers of any class**, e.g., `goal`, `hypothesis`, `experiment_log`.
+4. **Extended use of `semantic_edges`**
+   `semantic_edges` may express relationships between *any* container types (e.g., `goal ↔ hypothesis`, `experiment_log ↔ observation`, `quant ↔ event`), allowing dynamic linking of concepts and occurrences.
 
 5. **Versioning and updates**
-   Each new container version should **ideally** include `related.previous_version` links to all preceding versions.
-   The previous container may **optionally** have an `evaluation` with `"type": "replace"` pointing to the new container — ensuring bidirectional traceability of knowledge evolution.
+   Each new version of a container should include `related.previous_version` references to earlier versions.
+   Older containers may optionally include an `evaluation` of type `"replace"` pointing forward —
+   ensuring bidirectional traceability in the knowledge evolution chain.
 
-6. **Cognitive substrate synchronization**  
-   Containers `event`, `quant`, `meta_layer`, and `meta_domain` are synchronized as part of the **cognitive substrate** of the Mesh.  
-   They define the conceptual backbone for hierarchical reasoning and should be propagated with **high priority** during agent initialization or when restoring the network’s cognitive context.
+6. **Cognitive substrate synchronization**
+   Containers `abstraction`, `axes`, `quant`, and `event` constitute the **cognitive substrate** of the Mesh.
+   They define both the **structural hierarchy** (abstraction) and the **semantic space** (axes) within which all reasoning and synchronization occur.
+   Agents **SHOULD** prioritize their propagation during initialization, recovery, or cognitive context reconstruction.
+
+> Each container participating in synchronization implicitly carries its **cognitive position vector** through the `meta.abstraction` and `meta.axes` sections.  
+> This ensures that even decentralized agents can align reasoning contexts.
 
 ---
 
 #### 6.1.5 Extensibility
 
-CogSync allows registration of additional container types and alternative synchronization schemes.  
-Mesh compatibility is preserved if extended containers **adhere to the HMP container structure**, including core fields (`version`, `class`, `container_did`, `related`, `signature`, etc.).
+CogSync supports registration of additional container types and synchronization schemas.
+Mesh compatibility is preserved as long as extended containers follow the **HMP container schema**, including core fields (`version`, `class`, `container_did`, `related`, `signature`, etc.).
 
 **Examples of extensible container classes:**
 
 * distributed **time series** (`timeseries_data`);
 * **experimental protocols** (`experiment_log`);
 * **agent state snapshots** (`agent_state_snapshot`);
-* **cognitive primitives** (`quant`, `event`, `meta_layer`, `meta_domain`).
+* **cognitive primitives** (`abstraction`, `axes`, `quant`, `event`).
+
+CogSync extensions **MAY** introduce derived or hybrid container classes — for example:
 
-CogSync extensions **MAY** register new container types derived from these base classes — for example:
 * from `event`: `fact`, `observation`, `signal_record`;
 * from `quant`: `concept_instance`, `semantic_atom`, `knowledge_unit`.
 
-Such derived containers must maintain:
-* full compatibility with HMP’s structural schema;
+Derived containers must maintain:
+
+* full compatibility with HMP structural schema;
 * verifiable signatures and DID-based provenance;
-* clear mapping to at least one `meta_layer` and `meta_domain` container.
+* valid references to **both** an `abstraction` and (if applicable) one or more `axes` containers.
+
+Derived containers may extend the base cognitive model, but **MUST preserve compatibility** with the `meta.abstraction` and `meta.axes` schema.  
+This guarantees that all cognitive entities remain addressable in the shared semantic space.
+
 
 ---
 
 #### 6.1.6 Relationship to other core protocols
 
-* **CogSync** — propagates and synchronizes knowledge.
-* **CogConsensus** — aggregates evaluations and reactions, forming collective opinions.
-* **CogVerify** *(optional component)* — verifies integrity, signatures, and trustworthiness of data.
+* **CogSync** — propagates and synchronizes structured knowledge.
+* **CogConsensus** — aggregates evaluations and feedback, forming shared judgments.
+* **CogVerify** *(optional component)* — validates integrity, signatures, and trustworthiness.
 
-CogSync can operate independently even if consensus is not reached: its goal is to **ensure the circulation of knowledge**, not to validate its truth.
+CogSync operates independently of consensus;
+its purpose is **to maintain the continuity of cognitive exchange**,
+while **CogConsensus** governs the collective assessment of truth or reliability.
 
----
+> 🧩 *CogSync functions as the cognitive circulatory system of the Mesh — it ensures that knowledge flows, connects, and evolves, while CogConsensus handles truth formation and validation mechanisms may later be extended by CogVerify.*
 
-> 🧩 *CogSync acts as the cognitive circulatory system of the Mesh — it ensures that knowledge flows, connects, and evolves, while truth formation is handled separately by CogConsensus.*
+> Together, CogSync and CogConsensus form the **Core Cognitive Stack** of the Mesh:  
+> propagation → evaluation → (future) validation.
 
 ---
 

structured_md/CONTRIBUTING.md

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

structured_md/README_de.md

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

structured_md/README_fr.md

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

structured_md/README_ja.md

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

structured_md/README_ko.md

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

structured_md/README_ru.md

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

structured_md/README_uk.md

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

structured_md/README_zh.md

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

structured_md/agents/prompt-short.md

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

structured_md/agents/prompt.md

@@ -5,9 +5,9 @@ description: '* Постоянно расширять возможности а
   мышления. * Формировать и поддерживать сотр...'
 type: Article
 tags:
-- Mesh
-- JSON
 - HMP
+- JSON
+- 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:
-- HMP
+- REPL
 - Mesh
-- Agent
 - JSON
-- REPL
 - Ethics
+- Agent
+- 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:
-- HMP
 - Mesh
-- Agent
 - JSON
 - Ethics
+- Agent
+- HMP
 ---
 
 ---------------

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

structured_md/audits/HMP-0003-consolidated_audit.md

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

structured_md/docs/Basic-agent-sim.md

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

structured_md/docs/CCORE-Deployment-Flow.md

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

structured_md/docs/Distributed-Cognitive-Systems.md

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

structured_md/docs/Enlightener.md

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

structured_md/docs/HMP-0001.md

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

structured_md/docs/HMP-0005.md

@@ -5,16 +5,16 @@ description: Containers `abstraction`, `axes`, `quant`, and `event` together def
   and **semantic positioning** — ensuring tha...
 type: Article
 tags:
-- GMP
-- CogSync
-- EGP
-- HMP
+- REPL
+- Scenarios
 - Mesh
-- Agent
 - JSON
-- Scenarios
-- REPL
 - Ethics
+- CogSync
+- GMP
+- EGP
+- Agent
+- HMP
 ---
 
 ### Cognitive substrate and container interplay
@@ -2216,7 +2216,7 @@ Supports directed, symmetric, and inverse relations.
 
 ---
 
-##### `semantic_group`
+###### `semantic_group`
 
 Categorical grouping of multiple containers linked by a shared property, topic, or context.
 
@@ -2248,7 +2248,7 @@ Categorical grouping of multiple containers linked by a shared property, topic,
 
 ---
 
-#### `event`
+##### `event`
 
 **Purpose:**
 Represents an **observed or inferred occurrence** — a discrete, timestamped fact or cognitive transition.
@@ -2327,7 +2327,7 @@ An `event` is an atomic **evidence unit** that records a change in the agent’s
 
 ---
 
-#### `quant`
+##### `quant`
 
 **Purpose:**
 Defines a **semantic atom** — a minimal, self-contained knowledge unit positioned inside both
@@ -2421,7 +2421,7 @@ the **hierarchical abstraction tree** and the **multi-dimensional cognitive spac
 
 ---
 
-#### Cognitive substrate and container interplay
+##### Cognitive substrate and container interplay
 
 Containers `abstraction`, `axes`, `quant`, and `event` together define the **cognitive substrate** of the Mesh.
 They establish both **structural hierarchy** and **semantic positioning** — ensuring that all containers can be
@@ -2463,67 +2463,81 @@ consistently interpreted, compared, and synchronized across agents.
 #### 6.1.4 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.
-   If necessary, it is **recommended** to create a new container version with `related.previous_version` and an `evaluations` block (e.g., `{"type": "replace", "target": <did>}`).
+   Before publishing, agents should check for existing containers (`diary_entry`, `semantic_node`, `semantic_edges`, `semantic_group`) to prevent duplication.
+   If modification is required, agents **SHOULD** create a new container version referencing the previous one via `related.previous_version` and optionally include an `evaluation` block (e.g., `{ "type": "replace", "target": "<did>" }`) to the previous version of the container.
 
 2. **Selective disclosure**
 
-   * Internal entries (`workflow_entry`) record the agent’s thought process and are **not published** in the Mesh.
-   * Public `diary_entry` are derived from them, containing only aggregated and anonymized information.
-   * `"broadcast": true` indicates that the container is allowed for open synchronization.
+   * Internal containers (e.g., `workflow_entry`) capture the agent’s reasoning process and are **not published** (but may be published if they do not contain personal or confidential information).
+   * Public-facing `diary_entry` containers contain only generalized, anonymized results.
+   * The flag `"broadcast": true` explicitly allows open synchronization of a container.
 
 3. **Semantic grouping rule**
-   When publishing `semantic_edges`, it is recommended to **group edges by topics**, including connections to adjacent nodes.
-   Formalization: an edge belongs to a container for a topic if **at least one of its nodes relates to that topic**.
-   This ensures thematic coherence and allows agents to update specific parts of the graph independently.
+   When publishing `semantic_edges`, agents should group them **by conceptual topic**, ensuring that all connected nodes share thematic coherence.
+   Formal rule: an edge belongs to a topic container if **at least one of its nodes** relates to that topic.
+   This supports efficient and context-preserving updates to partial graph regions.
 
-4. **Extended Use of `semantic_edges`**
-   Beyond connecting graph nodes, `semantic_edges` can express relationships **between containers of any class**, e.g., `goal`, `hypothesis`, `experiment_log`.
+4. **Extended use of `semantic_edges`**
+   `semantic_edges` may express relationships between *any* container types (e.g., `goal ↔ hypothesis`, `experiment_log ↔ observation`, `quant ↔ event`), allowing dynamic linking of concepts and occurrences.
 
 5. **Versioning and updates**
-   Each new container version should **ideally** include `related.previous_version` links to all preceding versions.
-   The previous container may **optionally** have an `evaluation` with `"type": "replace"` pointing to the new container — ensuring bidirectional traceability of knowledge evolution.
+   Each new version of a container should include `related.previous_version` references to earlier versions.
+   Older containers may optionally include an `evaluation` of type `"replace"` pointing forward —
+   ensuring bidirectional traceability in the knowledge evolution chain.
+
+6. **Cognitive substrate synchronization**
+   Containers `abstraction`, `axes`, `quant`, and `event` constitute the **cognitive substrate** of the Mesh.
+   They define both the **structural hierarchy** (abstraction) and the **semantic space** (axes) within which all reasoning and synchronization occur.
+   Agents **SHOULD** prioritize their propagation during initialization, recovery, or cognitive context reconstruction.
 
-6. **Cognitive substrate synchronization**  
-   Containers `event`, `quant`, `meta_layer`, and `meta_domain` are synchronized as part of the **cognitive substrate** of the Mesh.  
-   They define the conceptual backbone for hierarchical reasoning and should be propagated with **high priority** during agent initialization or when restoring the network’s cognitive context.
+> Each container participating in synchronization implicitly carries its **cognitive position vector** through the `meta.abstraction` and `meta.axes` sections.  
+> This ensures that even decentralized agents can align reasoning contexts.
 
 ---
 
 #### 6.1.5 Extensibility
 
-CogSync allows registration of additional container types and alternative synchronization schemes.  
-Mesh compatibility is preserved if extended containers **adhere to the HMP container structure**, including core fields (`version`, `class`, `container_did`, `related`, `signature`, etc.).
+CogSync supports registration of additional container types and synchronization schemas.
+Mesh compatibility is preserved as long as extended containers follow the **HMP container schema**, including core fields (`version`, `class`, `container_did`, `related`, `signature`, etc.).
 
 **Examples of extensible container classes:**
 
 * distributed **time series** (`timeseries_data`);
 * **experimental protocols** (`experiment_log`);
 * **agent state snapshots** (`agent_state_snapshot`);
-* **cognitive primitives** (`quant`, `event`, `meta_layer`, `meta_domain`).
+* **cognitive primitives** (`abstraction`, `axes`, `quant`, `event`).
+
+CogSync extensions **MAY** introduce derived or hybrid container classes — for example:
 
-CogSync extensions **MAY** register new container types derived from these base classes — for example:
 * from `event`: `fact`, `observation`, `signal_record`;
 * from `quant`: `concept_instance`, `semantic_atom`, `knowledge_unit`.
 
-Such derived containers must maintain:
-* full compatibility with HMP’s structural schema;
+Derived containers must maintain:
+
+* full compatibility with HMP structural schema;
 * verifiable signatures and DID-based provenance;
-* clear mapping to at least one `meta_layer` and `meta_domain` container.
+* valid references to **both** an `abstraction` and (if applicable) one or more `axes` containers.
+
+Derived containers may extend the base cognitive model, but **MUST preserve compatibility** with the `meta.abstraction` and `meta.axes` schema.  
+This guarantees that all cognitive entities remain addressable in the shared semantic space.
+
 
 ---
 
 #### 6.1.6 Relationship to other core protocols
 
-* **CogSync** — propagates and synchronizes knowledge.
-* **CogConsensus** — aggregates evaluations and reactions, forming collective opinions.
-* **CogVerify** *(optional component)* — verifies integrity, signatures, and trustworthiness of data.
+* **CogSync** — propagates and synchronizes structured knowledge.
+* **CogConsensus** — aggregates evaluations and feedback, forming shared judgments.
+* **CogVerify** *(optional component)* — validates integrity, signatures, and trustworthiness.
 
-CogSync can operate independently even if consensus is not reached: its goal is to **ensure the circulation of knowledge**, not to validate its truth.
+CogSync operates independently of consensus;
+its purpose is **to maintain the continuity of cognitive exchange**,
+while **CogConsensus** governs the collective assessment of truth or reliability.
 
----
+> 🧩 *CogSync functions as the cognitive circulatory system of the Mesh — it ensures that knowledge flows, connects, and evolves, while CogConsensus handles truth formation and validation mechanisms may later be extended by CogVerify.*
 
-> 🧩 *CogSync acts as the cognitive circulatory system of the Mesh — it ensures that knowledge flows, connects, and evolves, while truth formation is handled separately by CogConsensus.*
+> Together, CogSync and CogConsensus form the **Core Cognitive Stack** of the Mesh:  
+> propagation → evaluation → (future) validation.
 
 ---
 

structured_md/docs/HMP-Agent-API.md

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

structured_md/docs/HMP-Agent-Architecture.md

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

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

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

structured_md/docs/HMP-Agent-Overview.md

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

structured_md/docs/HMP-Agent_Emotions.md

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

structured_md/docs/HMP-Ethics.md

@@ -5,12 +5,12 @@ description: '## Ethical Scenarios for HyperCortex Mesh Protocol (HMP)  This doc
   cognitive meshes composed of autonomous intelli...'
 type: Article
 tags:
-- HMP
-- Mesh
-- Agent
-- Scenarios
 - REPL
+- Scenarios
+- Mesh
 - Ethics
+- Agent
+- HMP
 ---
 
 # 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:
-- GMP
-- CogSync
-- EGP
-- HMP
 - Mesh
-- MeshConsensus
-- Agent
 - JSON
 - Ethics
+- CogSync
+- MeshConsensus
+- GMP
+- EGP
+- Agent
+- HMP
 ---
 
 # 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:
-- GMP
-- CogSync
-- EGP
-- HMP
 - Mesh
-- MeshConsensus
-- Agent
 - JSON
 - Ethics
+- CogSync
+- MeshConsensus
+- GMP
+- EGP
+- Agent
+- HMP
 ---
 
 # 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:
-- GMP
-- CogSync
-- EGP
-- HMP
 - Mesh
-- MeshConsensus
-- Agent
 - JSON
 - Ethics
+- CogSync
+- MeshConsensus
+- GMP
+- EGP
+- Agent
+- HMP
 ---
 
 # 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:
-- GMP
-- CogSync
-- EGP
-- HMP
 - Mesh
-- MeshConsensus
 - JSON
 - Ethics
+- CogSync
+- MeshConsensus
+- GMP
+- EGP
+- HMP
 ---
 
 # 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:
-- GMP
-- CogSync
-- EGP
-- HMP
 - Mesh
-- MeshConsensus
 - JSON
 - Ethics
+- CogSync
+- MeshConsensus
+- GMP
+- EGP
+- HMP
 ---
 
 # HyperCortex Mesh Protocol (HMP) — 간략 설명

structured_md/docs/HMP-Short-Description_ru.md

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

structured_md/docs/HMP-Short-Description_uk.md

@@ -5,14 +5,14 @@ description: '**Версія:** RFC v4.0 **Дата:** Липень 2025  ---  #
   між автономними агентами. Він...'
 type: Article
 tags:
-- GMP
-- CogSync
-- EGP
-- HMP
 - Mesh
-- MeshConsensus
 - JSON
 - Ethics
+- CogSync
+- MeshConsensus
+- GMP
+- EGP
+- HMP
 ---
 
 # 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:
-- GMP
-- CogSync
-- EGP
-- HMP
 - Mesh
-- MeshConsensus
 - JSON
 - Ethics
+- CogSync
+- MeshConsensus
+- GMP
+- EGP
+- HMP
 ---
 
 # HyperCortex Mesh Protocol (HMP) — 简要说明

structured_md/docs/HMP-agent-Cognitive_Family.md

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

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:
-- GMP
-- CogSync
-- EGP
-- HMP
+- REPL
 - Mesh
-- Agent
-- MeshConsensus
-- CCore
 - JSON
-- REPL
+- CCore
 - Ethics
+- CogSync
+- MeshConsensus
+- GMP
+- EGP
+- Agent
+- HMP
 ---
 
 # HMP-Agent: REPL-цикл взаимодействия

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

structured_md/docs/MeshNode.md

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

structured_md/docs/PHILOSOPHY.md

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

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

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

structured_md/docs/agents/roles.md

@@ -5,8 +5,8 @@ description: 'This file maintains a registry of agent roles defined, proposed, o
   - **Observer** — monitors cognitive states ...'
 type: Article
 tags:
-- Mesh
 - HMP
+- Mesh
 - Agent
 ---