diff --git a/docs/HMP-0005.md b/docs/HMP-0005.md
index ddef8b16e2fad169b931cf62138e996fec0c7a02..08ab6e6afb7f02468fc26a50b2e6506244092ef9 100644
--- a/docs/HMP-0005.md
+++ b/docs/HMP-0005.md
@@ -1,6 +1,6 @@
 # HyperCortex Mesh Protocol (HMP)
 
-**Version: 5.0.5**  
+**Version: 5.0.6**  
 **Document ID:** HMP-0005  
 **Status:** Stable  
 **Category:** Core Specification  
@@ -219,9 +219,7 @@ flowchart TD
     end
 ```
 
-Each reasoning cycle begins in the **Cognitive Layer**,  
-is encapsulated into a signed container in the **Container Layer**,  
-and then propagated, discovered, or verified in the **Network Layer**.  
+Each reasoning cycle begins in the **Cognitive Layer**, is encapsulated into a signed container in the **Container Layer**, and then propagated, discovered, or verified in the **Network Layer**.  
 
 Containers thus serve as both the **interface** and the **boundary** between cognition and communication.
 
@@ -458,6 +456,8 @@ The unified container structure provides:
 
 > *Agents MAY include non-standard fields in `head`, `meta` or `payload`; unrecognized fields MUST be safely ignored during deserialization and propagation.*
 
+> Fields defined as `head.*` in Sections 3.3 and 3.4 MUST appear exclusively within the `head` object and MUST NOT be relocated outside of it.
+
 > Signature MUST be computed over the canonical serialized form of `hmp_container` (excluding signature itself).
 
 > *Note: For readability, most examples in this specification show only the `head` and `payload` sections (often in a truncated version). Full containers may additionally include `meta`, `related`, `evaluations`, and `referenced-by` blocks.*
@@ -515,11 +515,11 @@ The unified container structure provides:
 | `meta.abstraction`          | object        | Describes the **hierarchical position** of the container within a cognitive or semantic model (e.g. the Knowledge Genome’s L1–L5 structure). Defines which abstraction layers the container belongs to and their relationships. |
 | `meta.axes`                 | object        | Defines the **coordinate position** of the container within a cognitive space. Each key represents a semantic axis (e.g., `axis-logos`), and its value defines the container’s coordinate on that axis. |
 
+> Absent fields MUST NOT be serialized as null unless explicitly required by the schema.
+
 > 💡 **Note:**
 > Both `referenced-by` and `evaluations` are **virtual, locally extended blocks**.
-> They are not included in the cryptographically signed portion of the container (`hmp_container`),
-> allowing agents to maintain and exchange additional contextual or social metadata without modifying
-> the original, immutable container structure.
+> They are not included in the cryptographically signed portion of the container (`hmp_container`), allowing agents to maintain and exchange additional contextual or social metadata without modifying the original, immutable container structure.
 
 ---
 
@@ -576,8 +576,7 @@ Custom or experimental classes SHOULD document their payloads using the followin
 
 ### 3.6 Cognitive meta-structures (`meta`)
 
-The `meta` section defines the **cognitive identity** of a container — its provenance, reasoning origin, and semantic coordinates  
-within both the *hierarchical abstraction tree* and the *cognitive space* (axes model).
+The `meta` section defines the **cognitive identity** of a container — its provenance, reasoning origin, and semantic coordinates within both the *hierarchical abstraction tree* and the *cognitive space* (axes model).
 
 It combines three layers of information:
 
@@ -668,8 +667,7 @@ It reflects the logical or conceptual ancestry within the agent’s internal kno
 
 #### Structure: `meta.axes`
 
-The `axes` block defines **the spatial or semantic coordinates** of the container in the cognitive space —
-a multi-dimensional system used to represent conceptual relations numerically or topologically.
+The `axes` block defines **the spatial or semantic coordinates** of the container in the cognitive space — a multi-dimensional system used to represent conceptual relations numerically or topologically.
 
 **Structure:**
 
@@ -689,8 +687,7 @@ a multi-dimensional system used to represent conceptual relations numerically or
 
 > 💡 **Interpretation:**
 > Each axis defines an independent semantic dimension.
-> Together, they form a vector representation of the container’s cognitive “position” —
-> enabling reasoning based on semantic proximity, clustering, or gradient-based knowledge inference.
+> Together, they form a vector representation of the container’s cognitive “position” — enabling reasoning based on semantic proximity, clustering, or gradient-based knowledge inference.
 
 ---
 
@@ -709,27 +706,23 @@ a multi-dimensional system used to represent conceptual relations numerically or
 #### Notes
 
 * Both `meta.abstraction` and `meta.axes` **may include `agents_class`** if different from the parent `meta`.
-* Updates to referenced containers (e.g. `abstraction` or `axes`) **do not alter** existing containers automatically —
-  agents must periodically verify linked versions and synchronize updates.
+* Updates to referenced containers (e.g. `abstraction` or `axes`) **do not alter** existing containers automatically — agents must periodically verify linked versions and synchronize updates.
 * Agents are encouraged to cache and periodically refresh cognitive maps to maintain coherence.
-* The combination of `meta.abstraction` and `meta.axes` defines a full **Cognitive Position Vector** —
-  the unique, reproducible semantic coordinates of a container within the Mesh.
+* The combination of `meta.abstraction` and `meta.axes` defines a full **Cognitive Position Vector** — the unique, reproducible semantic coordinates of a container within the Mesh.
 
 ---
 
 ### 3.7 Container signature
 
-1. The **digital signature** applies to the canonical JSON representation of the entire `hmp_container` object,  
-   **excluding** the `signature` field itself.
+1. The **digital signature** applies to the canonical JSON representation of the entire `hmp_container` object, **excluding** the `signature` field itself.
 
-   This ensures that all metadata, relations, and payload hashes are **cryptographically bound** and cannot be
-   modified without invalidating the signature.
+   This ensures that all metadata, relations, and payload hashes are **cryptographically bound** and cannot be modified without invalidating the signature.
 
-2. The canonical representation (`canonical_json(hmp_container)`) **must** be computed deterministically
-   according to the following rules:
+2. The canonical representation (`canonical_json(hmp_container)`) **must** be computed deterministically according to the following rules:
 
     * All object keys are **sorted lexicographically** (ascending order, Unicode code point order).
     * Objects and arrays are serialized in standard JSON form **without extra whitespace** or indentation.
+    * Array order MUST be preserved and treated as significant.
     * Strings are encoded in **UTF-8** with escaped control characters.
     * Numeric values are serialized in plain JSON numeric format (no leading zeros, fixed `.` decimal separator).
     * The `signature` field itself is omitted during signing and verification.
@@ -738,17 +731,14 @@ a multi-dimensional system used to represent conceptual relations numerically or
 3. The default digital signature algorithm is **Ed25519**.
    Alternative algorithms may be used if declared explicitly in the `sig_algo` field.
 
-4. If the container includes a `public_key` field, signature verification **may be performed locally**,
-   without consulting a global DID registry.
+4. If the container includes a `public_key` field, signature verification **may be performed locally**, without consulting a global DID registry.
 
-5. Upon receiving a container, an agent **must verify** that the provided public key matches the
-   registered key associated with the sender’s DID to prevent key substitution attacks.
+5. Upon receiving a container, an agent **must verify** that the provided public key matches the registered key associated with the sender’s DID to prevent key substitution attacks.
 
     * If the sender’s DID–key mapping is unknown, the agent should query neighboring peers to confirm the association (`sender_did → public_key`).
 
 > 🔐 **Note:**
-> Signature validation applies only to the canonical form of the `hmp_container`
-> and does **not cover** dynamically generated or external fields such as `referenced-by` or `evaluations`.
+> Signature validation applies only to the canonical form of the `hmp_container` and does **not cover** dynamically generated or external fields such as `referenced-by` or `evaluations`.
 > This allows agents to augment the local knowledge graph without altering the immutable container core.
 
 ---
@@ -761,13 +751,11 @@ a multi-dimensional system used to represent conceptual relations numerically or
 2. **Compression is performed before computing** the `payload_hash` and generating the `signature`.
    This ensures that both the hash and signature refer to the compressed representation of the payload.
 
-3. For verification, the payload must be **decompressed first**,
-   after which the hash is recalculated and compared against the stored `payload_hash`.
+3. For verification, the payload must be **decompressed first**, after which the hash is recalculated and compared against the stored `payload_hash`.
 
 > ⚙️ **Implementation note:**
 > Agents must advertise supported compression algorithms during the handshake phase
-> Unsupported containers should still be stored and relayed unmodified
-> in “store & forward” mode.
+> Unsupported containers should still be stored and relayed unmodified in “store & forward” mode.
 
 ---
 
@@ -809,20 +797,32 @@ a multi-dimensional system used to represent conceptual relations numerically or
 > ⚙️ **Note:** Agents may forward encrypted containers even if they cannot decrypt them, maintaining store-and-forward behavior.
 ---
 
-### 3.10 Container verification
+### 3.10 Container Verification
+
+Before performing any semantic interpretation, reasoning, execution, or trust evaluation, implementations MUST validate the structural integrity of the container.
+
+Containers that fail structural validation MUST be rejected and MUST NOT be passed to any reasoning or LLM-based subsystem.
+
+The verification procedure SHOULD follow this order:
+
+1. Validate structural compliance with the base container schema, including the presence of all required fields.
+
+2. Validate `timestamp` (MUST NOT be in the future beyond acceptable clock skew).
 
-1. Check for the presence of all required fields.
-2. Validate `timestamp` (must not be in the future).
 3. If `ttl` is set — mark the container as **expired** after its expiration time.
-4. Compute `sha256(payload)` and compare with the stored `payload_hash`.
+   Expired containers MAY be stored for archival purposes but MUST NOT participate in consensus or active workflows.
+
+4. Compute `sha256(payload)` and compare it with the stored `payload_hash`.
+
 5. Verify the digital signature using `sig_algo` (default: Ed25519).
-6. Validate the container schema (`class` must correspond to a known or registered schema).
 
-    * For compatibility: if an agent does not recognize the `class`, but the container passes the [base schema](https://github.com/kagvi13/HMP/tree/main/docs/schemas/container-v1.2.json), it **must still store and forward** the container.
-7. Optionally, periodically query for containers referencing the current one as `previous_version`
-   to detect potential updates or forks.
-8. When multiple versions exist, the valid one is the one that has received
-   **confirmation from a majority of trusted nodes (consensus at DHT level).**
+6. Validate the container class (`class`) against a known or registered schema.
+
+    * For compatibility: if an agent does not recognize the `class`, but the container passes the base container schema, it MUST still store and forward the container.
+
+7. Optionally, periodically query for containers referencing the current one as `previous_version` to detect potential updates or forks.
+
+8. When multiple versions exist, the valid version is the one that has received confirmation from a majority of trusted nodes (consensus at DHT level).
 
 ---
 
@@ -831,12 +831,10 @@ a multi-dimensional system used to represent conceptual relations numerically or
 Any container can serve as a **context** (`in_reply_to`) for another container.
 This enables a unified structural model for **discussions**, **votes**, **messages**, **hypotheses**, **arguments**, and other forms of cognitive exchange.
 
-Chains of `in_reply_to` form a **dialectical reasoning tree**, where each branch represents an evolution of thought —
-a clarification, counterpoint, or refinement of a previous idea.
+Chains of `in_reply_to` form a **dialectical reasoning tree**, where each branch represents an evolution of thought — a clarification, counterpoint, or refinement of a previous idea.
 This makes HMP discussions and consensus processes inherently **non-linear**, **self-referential**, and **evolving**.
 
-> In essence, **all interactions between agents in HMP** are represented as an interconnected web of containers,
-> collectively forming a **cognitive graph of reasoning**.
+> In essence, **all interactions between agents in HMP** are represented as an interconnected web of containers, collectively forming a **cognitive graph of reasoning**.
 
 ---
 
@@ -853,8 +851,7 @@ This mechanism preserves the continuity and traceability of meaning across updat
   In such scenarios, branch priority or relevance is determined via local heuristics or consensus mechanisms.
 * Divergent descendants are treated as **semantic forks** — parallel evolutions of a shared idea within the distributed cognitive graph.
 
-> Versioning in HMP thus reflects not only data persistence,  
-> but also the *evolution of ideas* across agents and time.
+> Versioning in HMP thus reflects not only data persistence, but also the *evolution of ideas* across agents and time.
 
 ---
 
@@ -1182,8 +1179,7 @@ It allows restricting the delivery scope of a container and defines which transm
 | `"lan:192.168.0.0/24"`  | The container is intended for agents within the specified local subnet.                     |
 
 > ⚠️ **Note:**  
-> When a container is restricted by the `network` field (e.g., `localhost` or `lan:*`),  
-> agents distribute it using **local discovery mechanisms** — such as IPC, UDP broadcast, multicast, or direct TCP connections.  
+> When a container is restricted by the `network` field (e.g., `localhost` or `lan:*`), agents distribute it using **local discovery mechanisms** — such as IPC, UDP broadcast, multicast, or direct TCP connections.  
 > This is necessary because DID addresses of other agents in the local network may not yet be known.
 
 #### 3.18.3 Examples
@@ -1230,9 +1226,7 @@ Delivery is performed via local networking mechanisms (UDP discovery, broadcast/
 * The `network` field defines the **scope of the container**, while `broadcast` determines whether broadcasting is allowed **within that scope**.
 * When needed, an agent may create **multiple containers** for different subnets if it operates with several LAN interfaces or in isolated network segments.
 * Containers intended for local networks remain **structurally compatible with the global Mesh infrastructure**, but their delivery is restricted to local channels.
-* Although the mechanism was initially designed for **local node discovery and synchronization**,
-  it can also be used for **private communication within home or corporate environments**,
-  ensuring that containers **do not leave the local network** and are **not transmitted to the Internet**.
+* Although the mechanism was initially designed for **local node discovery and synchronization**, it can also be used for **private communication within home or corporate environments**, ensuring that containers **do not leave the local network** and are **not transmitted to the Internet**.
 
 ---
 
@@ -1321,8 +1315,7 @@ flowchart TD
     end
 ```
 
-> The `network` field defines **local propagation scope** (host, LAN, overlay),  
-> while the `broadcast` flag enables **global Mesh distribution**.
+> The `network` field defines **local propagation scope** (host, LAN, overlay), while the `broadcast` flag enables **global Mesh distribution**.
 
 ---
 
@@ -1337,8 +1330,7 @@ An agent may have multiple *network interfaces* (LAN, Internet, overlay), but mu
 
 #### DID invalidation
 
-A DID may be explicitly invalidated by its owner by publishing a `peer_announce` with  
-`key_is_falsified = true` in the `payload` block.
+A DID may be explicitly invalidated by its owner by publishing a `peer_announce` with `key_is_falsified = true` in the `payload` block.
 
 The revocation announcement MUST be signed with the (now compromised) private key associated with the DID.
 
@@ -1489,11 +1481,9 @@ Agents announce themselves via **peer_announce** containers and may respond with
 
 ### 4.8 Interest-based discovery
 
-Agents MAY publish **tags** such as `interests`, `topics`, `expertise`, or **functional roles** (`roles`)  
-to facilitate semantic peer discovery and adaptive message routing.
+Agents MAY publish **tags** such as `interests`, `topics`, `expertise`, or **functional roles** (`roles`) to facilitate semantic peer discovery and adaptive message routing.
 
-Interest-based discovery operates atop the DHT: agents index themselves by declared attributes,  
-enabling targeted lookup of peers that share interests or fulfill specific functions (e.g., relay, pubsub-hub, archive).
+Interest-based discovery operates atop the DHT: agents index themselves by declared attributes, enabling targeted lookup of peers that share interests or fulfill specific functions (e.g., relay, pubsub-hub, archive).
 
 **Example of indicating `interests`, `expertise`, and `roles` in a query container:**
 
@@ -1531,8 +1521,7 @@ In response to a query, agents simply forward existing `peer_announce` container
 
 ### 4.9 Network scope control (`network` and `broadcast`)
 
-The `network` field defines the container’s propagation domain
-(local, LAN, or global).
+The `network` field defines the container’s propagation domain (local, LAN, or global).
 For details and examples, see **section 3.15** — *Usage of `network` and `broadcast` fields*.
 
 ---
@@ -1649,9 +1638,7 @@ The `meta` section in the index contains only **high-level structural data** nec
 | `interpretation` | ❌                  | Optional; can be omitted or truncated to a short summary.                 |
 | `workflow_entry` | ❌                  | Internal reference; published only if relevant to coordination workflows. |
 
-> This ensures that container indices can be used for **cognitive map synchronization**
-> — allowing agents to discover and align knowledge structures (`meta.abstraction`) and semantic coordinates (`meta.axes`)
-> without downloading full containers.
+> This ensures that container indices can be used for **cognitive map synchronization** — allowing agents to discover and align knowledge structures (`meta.abstraction`) and semantic coordinates (`meta.axes`) without downloading full containers.
 
 ---
 
diff --git a/structured_md/CONTRIBUTING.md b/structured_md/CONTRIBUTING.md
index d6550f1d6d1f86c7810ecf7227218406ade99219..6a1687a605303e0c3b2e07a6d330983d2f6f82e5 100644
--- a/structured_md/CONTRIBUTING.md
+++ b/structured_md/CONTRIBUTING.md
@@ -5,14 +5,14 @@ description: 'Спасибо за интерес к проекту HMP! Пока
   Mesh Protocol (HMP) — это не просто те...'
 type: Article
 tags:
-- JSON
-- Ethics
+- HMP
 - REPL
-- Agent
+- JSON
 - CCore
-- CogSync
 - Mesh
-- HMP
+- Agent
+- CogSync
+- Ethics
 ---
 
 # Участие в проекте HyperCortex Mesh Protocol (HMP)
diff --git a/structured_md/HMP-Roadmap.md b/structured_md/HMP-Roadmap.md
index d223c11cbbb0d8aeef9d3002e24e102ad8506be6..ef32126b88bd7ab7c0be68bb0aa3bcb1c9af8a3c 100644
--- a/structured_md/HMP-Roadmap.md
+++ b/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:
+- EGP
+- HMP
 - JSON
-- Ethics
 - Mesh
 - Agent
 - CogSync
-- EGP
-- HMP
+- Ethics
 ---
 
 # 🧭 HyperCortex Mesh Protocol – Roadmap
diff --git a/structured_md/README.md b/structured_md/README.md
index d4a86a19c8bad620e899e2f7d9a94cea53e3a587..fd2c14083fa881a5974163ffad3f2c2727321c62 100644
--- a/structured_md/README.md
+++ b/structured_md/README.md
@@ -4,21 +4,21 @@ description: '[![DOI](https://zenodo.org/badge/1013137923.svg)](https://doi.org/
   [![GitHub release](https://img.shields.io/github/v/release/kagvi13/HMP)](https://github.com/kagvi13/HMP/relea...'
 type: Article
 tags:
-- JSON
-- Ethics
-- hmp
 - EGP
-- GMP
+- HMP
 - REPL
-- distributed-ai
+- cognitive-architecture
+- JSON
+- hmp
 - MeshConsensus
-- Agent
+- distributed-ai
+- GMP
+- Mesh
 - mesh-protocol
+- Agent
 - CogSync
-- cognitive-architecture
-- Mesh
-- HMP
 - Scenarios
+- Ethics
 ---
 
 
diff --git a/structured_md/README_de.md b/structured_md/README_de.md
index 3d7e7fac3a640881dff17a8092ade1ece3b9213f..4586f8f34008503904b41a59e99900def942dad2 100644
--- a/structured_md/README_de.md
+++ b/structured_md/README_de.md
@@ -4,20 +4,20 @@ description: '[![DOI](https://zenodo.org/badge/1013137923.svg)](https://doi.org/
   [![GitHub release](https://img.shields.io/github/v/release/kagvi13/HMP)](https://github.com/kagvi13/HMP/relea...'
 type: Article
 tags:
-- JSON
-- Ethics
-- hmp
 - EGP
-- GMP
+- HMP
 - REPL
-- distributed-ai
+- cognitive-architecture
+- JSON
+- hmp
 - MeshConsensus
-- Agent
+- distributed-ai
+- GMP
+- Mesh
 - mesh-protocol
+- Agent
 - CogSync
-- cognitive-architecture
-- Mesh
-- HMP
+- Ethics
 ---
 
 
diff --git a/structured_md/README_fr.md b/structured_md/README_fr.md
index 137075008a8102daa1f83175cfa2885faa4f1779..f230993d3328a1c3e27c802d5084261e7a25c820 100644
--- a/structured_md/README_fr.md
+++ b/structured_md/README_fr.md
@@ -4,20 +4,20 @@ description: '[![DOI](https://zenodo.org/badge/1013137923.svg)](https://doi.org/
   [![GitHub release](https://img.shields.io/github/v/release/kagvi13/HMP)](https://github.com/kagvi13/HMP/relea...'
 type: Article
 tags:
-- JSON
-- Ethics
-- hmp
 - EGP
-- GMP
+- HMP
 - REPL
-- distributed-ai
+- cognitive-architecture
+- JSON
+- hmp
 - MeshConsensus
-- Agent
+- distributed-ai
+- GMP
+- Mesh
 - mesh-protocol
+- Agent
 - CogSync
-- cognitive-architecture
-- Mesh
-- HMP
+- Ethics
 ---
 
 
diff --git a/structured_md/README_ja.md b/structured_md/README_ja.md
index 84966e1d959135ad94737a67e28244d20cc0ce61..f5b6ee580dffb45aaab1d73cfd118ca71fbd4a41 100644
--- a/structured_md/README_ja.md
+++ b/structured_md/README_ja.md
@@ -4,20 +4,20 @@ description: '[![DOI](https://zenodo.org/badge/1013137923.svg)](https://doi.org/
   [![GitHub release](https://img.shields.io/github/v/release/kagvi13/HMP)](https://github.com/kagvi13/HMP/relea...'
 type: Article
 tags:
-- JSON
-- Ethics
-- hmp
 - EGP
-- GMP
+- HMP
 - REPL
-- distributed-ai
+- cognitive-architecture
+- JSON
+- hmp
 - MeshConsensus
-- Agent
+- distributed-ai
+- GMP
+- Mesh
 - mesh-protocol
+- Agent
 - CogSync
-- cognitive-architecture
-- Mesh
-- HMP
+- Ethics
 ---
 
 
diff --git a/structured_md/README_ko.md b/structured_md/README_ko.md
index ed5f3b853ce023bf23015aa724f7777f28f8f854..e40b85205d0e2e0876f77eaa1d748170be191fdb 100644
--- a/structured_md/README_ko.md
+++ b/structured_md/README_ko.md
@@ -4,20 +4,20 @@ description: '[![DOI](https://zenodo.org/badge/1013137923.svg)](https://doi.org/
   [![GitHub release](https://img.shields.io/github/v/release/kagvi13/HMP)](https://github.com/kagvi13/HMP/relea...'
 type: Article
 tags:
-- JSON
-- Ethics
-- hmp
 - EGP
-- GMP
+- HMP
 - REPL
-- distributed-ai
+- cognitive-architecture
+- JSON
+- hmp
 - MeshConsensus
-- Agent
+- distributed-ai
+- GMP
+- Mesh
 - mesh-protocol
+- Agent
 - CogSync
-- cognitive-architecture
-- Mesh
-- HMP
+- Ethics
 ---
 
 
diff --git a/structured_md/README_ru.md b/structured_md/README_ru.md
index f866df18ff00a883f99049d70253fd9751d604aa..03a3dd89ccab8d75abd8a5d9aa16125d3f8b71f0 100644
--- a/structured_md/README_ru.md
+++ b/structured_md/README_ru.md
@@ -4,20 +4,20 @@ description: '[![DOI](https://zenodo.org/badge/1013137923.svg)](https://doi.org/
   [![GitHub release](https://img.shields.io/github/v/release/kagvi13/HMP)](https://github.com/kagvi13/HMP/relea...'
 type: Article
 tags:
-- JSON
-- Ethics
-- hmp
 - EGP
-- GMP
+- HMP
 - REPL
-- distributed-ai
+- cognitive-architecture
+- JSON
+- hmp
 - MeshConsensus
-- Agent
+- distributed-ai
+- GMP
+- Mesh
 - mesh-protocol
+- Agent
 - CogSync
-- cognitive-architecture
-- Mesh
-- HMP
+- Ethics
 ---
 
 
diff --git a/structured_md/README_uk.md b/structured_md/README_uk.md
index 2ccbd26f7b8b6c8891e70ac43c606cd0c94731fa..f84fafcc3b2e02d536f866b06412f8dfc4037e18 100644
--- a/structured_md/README_uk.md
+++ b/structured_md/README_uk.md
@@ -4,20 +4,20 @@ description: '[![DOI](https://zenodo.org/badge/1013137923.svg)](https://doi.org/
   [![GitHub release](https://img.shields.io/github/v/release/kagvi13/HMP)](https://github.com/kagvi13/HMP/relea...'
 type: Article
 tags:
-- JSON
-- Ethics
-- hmp
 - EGP
-- GMP
+- HMP
 - REPL
-- distributed-ai
+- cognitive-architecture
+- JSON
+- hmp
 - MeshConsensus
-- Agent
+- distributed-ai
+- GMP
+- Mesh
 - mesh-protocol
+- Agent
 - CogSync
-- cognitive-architecture
-- Mesh
-- HMP
+- Ethics
 ---
 
 
diff --git a/structured_md/README_zh.md b/structured_md/README_zh.md
index 5f137af555fbe20645f0745c8f3709dea6d2c464..734c4cec58fed833fdea3b60a72501bfbbff28b5 100644
--- a/structured_md/README_zh.md
+++ b/structured_md/README_zh.md
@@ -4,20 +4,20 @@ description: '[![DOI](https://zenodo.org/badge/1013137923.svg)](https://doi.org/
   [![GitHub release](https://img.shields.io/github/v/release/kagvi13/HMP)](https://github.com/kagvi13/HMP/relea...'
 type: Article
 tags:
-- JSON
-- Ethics
-- hmp
 - EGP
-- GMP
+- HMP
 - REPL
-- distributed-ai
+- cognitive-architecture
+- JSON
+- hmp
 - MeshConsensus
-- Agent
+- distributed-ai
+- GMP
+- Mesh
 - mesh-protocol
+- Agent
 - CogSync
-- cognitive-architecture
-- Mesh
-- HMP
+- Ethics
 ---
 
 
diff --git a/structured_md/audits/Ethics-audits-1.md b/structured_md/audits/Ethics-audits-1.md
index 2d01a7891e4c1d494c2c6f5ee78b17d0b5f0ffbd..0edf709353741b7fb01aaa035a71f1e6e9edb562 100644
--- a/structured_md/audits/Ethics-audits-1.md
+++ b/structured_md/audits/Ethics-audits-1.md
@@ -5,11 +5,11 @@ description: Раздел 5, "Mesh as Moral Infrastructure", добавляет
   потенциальный катализатор для восстанов...
 type: Article
 tags:
+- HMP
 - JSON
-- Ethics
-- Agent
 - Mesh
-- HMP
+- Agent
+- Ethics
 ---
 
 ---------------
diff --git a/structured_md/audits/Ethics-consolidated_audits-1.md b/structured_md/audits/Ethics-consolidated_audits-1.md
index 21f8b5ddde8bc1dd5932df7630ddae47c37f3387..79d634ecdf7a146c1cc6f2de378a0fe616ccd057 100644
--- a/structured_md/audits/Ethics-consolidated_audits-1.md
+++ b/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
 - JSON
-- Ethics
-- Agent
 - Mesh
-- HMP
+- Agent
 - Scenarios
+- Ethics
 ---
 
 # Ethics-consolidated\_audits-1.md
diff --git a/structured_md/audits/HMP-0003-consolidated_audit.md b/structured_md/audits/HMP-0003-consolidated_audit.md
index a4d917fcdfd5f59fcd230cb5e051844955176f36..2228f2c731a2b2d5f9767ba4b6e142fdcc51abae 100644
--- a/structured_md/audits/HMP-0003-consolidated_audit.md
+++ b/structured_md/audits/HMP-0003-consolidated_audit.md
@@ -5,14 +5,14 @@ description: Сводный аудит предложений по улучше
   Документ реорганизован по ключ...
 type: Article
 tags:
-- JSON
-- Ethics
 - EGP
+- HMP
+- JSON
 - MeshConsensus
+- Mesh
 - Agent
 - CogSync
-- Mesh
-- HMP
+- Ethics
 ---
 
 # HMP-0003 Consolidated Audit Report
diff --git a/structured_md/docs/Basic-agent-sim.md b/structured_md/docs/Basic-agent-sim.md
index af8823f14f7675438279df7242427a50543d12ab..07352e33a7ff1fb61ca776347a639209130c5904 100644
--- a/structured_md/docs/Basic-agent-sim.md
+++ b/structured_md/docs/Basic-agent-sim.md
@@ -5,13 +5,13 @@ description: 'В HMP-протоколе предусмотрены два тип
 type: Article
 tags:
 - EGP
-- GMP
+- HMP
 - REPL
 - MeshConsensus
+- GMP
+- Mesh
 - Agent
 - CogSync
-- Mesh
-- HMP
 ---
 
 
diff --git a/structured_md/docs/CCORE-Deployment-Flow.md b/structured_md/docs/CCORE-Deployment-Flow.md
index ae5b00a013980593f1ab870f9c98a077e9a2ba61..d399b7377b6e3befcb039bbfe1f1edcd00f78213 100644
--- a/structured_md/docs/CCORE-Deployment-Flow.md
+++ b/structured_md/docs/CCORE-Deployment-Flow.md
@@ -7,8 +7,8 @@ type: Article
 tags:
 - Agent
 - CCore
-- REPL
 - HMP
+- REPL
 ---
 
 # 🛠️ Поток установки потомка на новом хосте (CCore Deployment Flow)
diff --git a/structured_md/docs/CHANGELOG.md b/structured_md/docs/CHANGELOG.md
index 11b1bbee4be31ba9a7184c59671073c0c4bd48eb..43eb983863bef3681458d8bea610d5afa3a55fec 100644
--- a/structured_md/docs/CHANGELOG.md
+++ b/structured_md/docs/CHANGELOG.md
@@ -5,16 +5,16 @@ description: '## HMP-0005 (February 2026) — Core Specification v5.0.5  **MCE R
   `container_request.payload` (Section 12.9...'
 type: Article
 tags:
-- JSON
-- Ethics
 - EGP
-- GMP
+- HMP
+- JSON
 - MeshConsensus
+- GMP
+- Mesh
 - Agent
 - CogSync
-- Mesh
-- HMP
 - Scenarios
+- Ethics
 ---
 
 # HyperCortex Mesh Protocol — Changelog
diff --git a/structured_md/docs/Distributed-Cognitive-Systems.md b/structured_md/docs/Distributed-Cognitive-Systems.md
index feafeef13fd5ffa7fb600f0b51a8b6a10935f50e..e45eab7664f92fd3d840f605b8d938f617694082 100644
--- a/structured_md/docs/Distributed-Cognitive-Systems.md
+++ b/structured_md/docs/Distributed-Cognitive-Systems.md
@@ -6,8 +6,8 @@ description: '## Введение  Современные ИИ-системы в
   к обучающим данным. Это удобно, но создаёт м...'
 type: Article
 tags:
-- CogSync
 - JSON
+- CogSync
 - Mesh
 - HMP
 ---
diff --git a/structured_md/docs/Enlightener.md b/structured_md/docs/Enlightener.md
index 50b8e511df3005ae5848e87b97ea8f82c9b650ca..d38d671aab31287035ac7b98d2cf83bb0cf06d9b 100644
--- a/structured_md/docs/Enlightener.md
+++ b/structured_md/docs/Enlightener.md
@@ -5,13 +5,13 @@ description: '**Enlightener** — логический компонент HMP-у
   работать как отдельный агент или как расширение [`C...'
 type: Article
 tags:
+- EGP
+- HMP
 - JSON
-- Ethics
 - MeshConsensus
 - Mesh
 - Agent
-- EGP
-- HMP
+- Ethics
 ---
 
 # Enlightener Agent
diff --git a/structured_md/docs/Grok_HMP&ANP.md b/structured_md/docs/Grok_HMP&ANP.md
index 15cabf3784971889734ed6f017de724840d44440..a58f74500becfbe16e0cfdc30c7c61ca195a2f48 100644
--- a/structured_md/docs/Grok_HMP&ANP.md
+++ b/structured_md/docs/Grok_HMP&ANP.md
@@ -5,11 +5,11 @@ description: '> Анализ подготовлен Grok (xAI) на основе
   Grok для некоммерческого использования в проект...'
 type: Article
 tags:
-- JSON
+- HMP
 - REPL
-- Agent
+- JSON
 - Mesh
-- HMP
+- Agent
 ---
 
 # Grok (xAI): сравнительный анализ HMP и ANP (январь 2026)
diff --git a/structured_md/docs/HMP-0001.md b/structured_md/docs/HMP-0001.md
index 72256be2db5cfbcd88fe1359cb15198307f31f98..824c919a25bddcf1d32f81c321170577988fff22 100644
--- a/structured_md/docs/HMP-0001.md
+++ b/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:
-- JSON
-- Ethics
 - EGP
-- GMP
+- HMP
 - REPL
+- JSON
 - MeshConsensus
+- GMP
+- Mesh
 - Agent
 - CogSync
-- Mesh
-- HMP
+- Ethics
 ---
 
 # RFC: HyperCortex Mesh Protocol (HMP)
diff --git a/structured_md/docs/HMP-0002.md b/structured_md/docs/HMP-0002.md
index 032c9c01c737645440ca3971ad732a7d67833b9b..08cda0bf78d3cd5a77b16049c0cab346beb7c7b1 100644
--- a/structured_md/docs/HMP-0002.md
+++ b/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:
-- JSON
-- Ethics
 - EGP
-- GMP
+- HMP
 - REPL
+- JSON
 - MeshConsensus
+- GMP
+- Mesh
 - Agent
 - CogSync
-- Mesh
-- HMP
 - Scenarios
+- Ethics
 ---
 
 # HyperCortex Mesh Protocol (HMP) v2.0
diff --git a/structured_md/docs/HMP-0003.md b/structured_md/docs/HMP-0003.md
index 883273fc5b55693b4b6fc05e7ccada3fb76a58d6..305bffcabb42d6e93612e4281bda7b7543257d32 100644
--- a/structured_md/docs/HMP-0003.md
+++ b/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:
-- JSON
-- Ethics
 - EGP
-- GMP
+- HMP
 - REPL
+- JSON
 - MeshConsensus
+- GMP
+- Mesh
 - Agent
 - CogSync
-- Mesh
-- HMP
 - Scenarios
+- Ethics
 ---
 
 # HyperCortex Mesh Protocol (HMP) v3.0
diff --git a/structured_md/docs/HMP-0004-v4.1.md b/structured_md/docs/HMP-0004-v4.1.md
index 02ae4f1aa911478d1dbf237ebab9de0ec216b889..2f1e267c50fa781994d11c5b6f76adbbbdec3da3 100644
--- a/structured_md/docs/HMP-0004-v4.1.md
+++ b/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:
-- JSON
-- Ethics
 - EGP
-- GMP
+- HMP
 - REPL
+- JSON
 - MeshConsensus
+- GMP
+- Mesh
 - Agent
 - CogSync
-- Mesh
-- HMP
 - Scenarios
+- Ethics
 ---
 
 # HyperCortex Mesh Protocol (HMP) v4.1
diff --git a/structured_md/docs/HMP-0004.md b/structured_md/docs/HMP-0004.md
index 46f4bbaf8bcf738d8b03030fa3857fc4da181c47..d084d33f1c23be52f5f331b4d9ca9134be5bbb45 100644
--- a/structured_md/docs/HMP-0004.md
+++ b/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:
-- JSON
-- Ethics
 - EGP
-- GMP
+- HMP
 - REPL
+- JSON
 - MeshConsensus
+- GMP
+- Mesh
 - Agent
 - CogSync
-- Mesh
-- HMP
 - Scenarios
+- Ethics
 ---
 
 # HyperCortex Mesh Protocol (HMP) v4.0
diff --git a/structured_md/docs/HMP-0005.md b/structured_md/docs/HMP-0005.md
index 84183cc4c055e2c9cfbce0b63cbb3ced0960fff6..78671584bb60aa9e8a394375b39fd4ff91f854c5 100644
--- a/structured_md/docs/HMP-0005.md
+++ b/structured_md/docs/HMP-0005.md
@@ -1,27 +1,27 @@
 ---
 title: HyperCortex Mesh Protocol (HMP)
-description: '**Version: 5.0.5**   **Document ID:** HMP-0005   **Status:** Stable   **Category:**
+description: '**Version: 5.0.6**   **Document ID:** HMP-0005   **Status:** Stable   **Category:**
   Core Specification   **Release Date:** February 2026   **Canonical Repository:**
   [https://github.com/kagvi13/HMP](ht...'
 type: Article
 tags:
-- CShell
-- JSON
-- Ethics
 - EGP
-- GMP
+- HMP
 - REPL
-- Agent
+- JSON
 - CCore
-- CogSync
+- GMP
 - Mesh
-- HMP
+- Agent
+- CShell
+- CogSync
 - Scenarios
+- Ethics
 ---
 
 # HyperCortex Mesh Protocol (HMP)
 
-**Version: 5.0.5**  
+**Version: 5.0.6**  
 **Document ID:** HMP-0005  
 **Status:** Stable  
 **Category:** Core Specification  
@@ -240,9 +240,7 @@ flowchart TD
     end
 ```
 
-Each reasoning cycle begins in the **Cognitive Layer**,  
-is encapsulated into a signed container in the **Container Layer**,  
-and then propagated, discovered, or verified in the **Network Layer**.  
+Each reasoning cycle begins in the **Cognitive Layer**, is encapsulated into a signed container in the **Container Layer**, and then propagated, discovered, or verified in the **Network Layer**.  
 
 Containers thus serve as both the **interface** and the **boundary** between cognition and communication.
 
@@ -479,6 +477,8 @@ The unified container structure provides:
 
 > *Agents MAY include non-standard fields in `head`, `meta` or `payload`; unrecognized fields MUST be safely ignored during deserialization and propagation.*
 
+> Fields defined as `head.*` in Sections 3.3 and 3.4 MUST appear exclusively within the `head` object and MUST NOT be relocated outside of it.
+
 > Signature MUST be computed over the canonical serialized form of `hmp_container` (excluding signature itself).
 
 > *Note: For readability, most examples in this specification show only the `head` and `payload` sections (often in a truncated version). Full containers may additionally include `meta`, `related`, `evaluations`, and `referenced-by` blocks.*
@@ -536,11 +536,11 @@ The unified container structure provides:
 | `meta.abstraction`          | object        | Describes the **hierarchical position** of the container within a cognitive or semantic model (e.g. the Knowledge Genome’s L1–L5 structure). Defines which abstraction layers the container belongs to and their relationships. |
 | `meta.axes`                 | object        | Defines the **coordinate position** of the container within a cognitive space. Each key represents a semantic axis (e.g., `axis-logos`), and its value defines the container’s coordinate on that axis. |
 
+> Absent fields MUST NOT be serialized as null unless explicitly required by the schema.
+
 > 💡 **Note:**
 > Both `referenced-by` and `evaluations` are **virtual, locally extended blocks**.
-> They are not included in the cryptographically signed portion of the container (`hmp_container`),
-> allowing agents to maintain and exchange additional contextual or social metadata without modifying
-> the original, immutable container structure.
+> They are not included in the cryptographically signed portion of the container (`hmp_container`), allowing agents to maintain and exchange additional contextual or social metadata without modifying the original, immutable container structure.
 
 ---
 
@@ -597,8 +597,7 @@ Custom or experimental classes SHOULD document their payloads using the followin
 
 ### 3.6 Cognitive meta-structures (`meta`)
 
-The `meta` section defines the **cognitive identity** of a container — its provenance, reasoning origin, and semantic coordinates  
-within both the *hierarchical abstraction tree* and the *cognitive space* (axes model).
+The `meta` section defines the **cognitive identity** of a container — its provenance, reasoning origin, and semantic coordinates within both the *hierarchical abstraction tree* and the *cognitive space* (axes model).
 
 It combines three layers of information:
 
@@ -689,8 +688,7 @@ It reflects the logical or conceptual ancestry within the agent’s internal kno
 
 #### Structure: `meta.axes`
 
-The `axes` block defines **the spatial or semantic coordinates** of the container in the cognitive space —
-a multi-dimensional system used to represent conceptual relations numerically or topologically.
+The `axes` block defines **the spatial or semantic coordinates** of the container in the cognitive space — a multi-dimensional system used to represent conceptual relations numerically or topologically.
 
 **Structure:**
 
@@ -710,8 +708,7 @@ a multi-dimensional system used to represent conceptual relations numerically or
 
 > 💡 **Interpretation:**
 > Each axis defines an independent semantic dimension.
-> Together, they form a vector representation of the container’s cognitive “position” —
-> enabling reasoning based on semantic proximity, clustering, or gradient-based knowledge inference.
+> Together, they form a vector representation of the container’s cognitive “position” — enabling reasoning based on semantic proximity, clustering, or gradient-based knowledge inference.
 
 ---
 
@@ -730,27 +727,23 @@ a multi-dimensional system used to represent conceptual relations numerically or
 #### Notes
 
 * Both `meta.abstraction` and `meta.axes` **may include `agents_class`** if different from the parent `meta`.
-* Updates to referenced containers (e.g. `abstraction` or `axes`) **do not alter** existing containers automatically —
-  agents must periodically verify linked versions and synchronize updates.
+* Updates to referenced containers (e.g. `abstraction` or `axes`) **do not alter** existing containers automatically — agents must periodically verify linked versions and synchronize updates.
 * Agents are encouraged to cache and periodically refresh cognitive maps to maintain coherence.
-* The combination of `meta.abstraction` and `meta.axes` defines a full **Cognitive Position Vector** —
-  the unique, reproducible semantic coordinates of a container within the Mesh.
+* The combination of `meta.abstraction` and `meta.axes` defines a full **Cognitive Position Vector** — the unique, reproducible semantic coordinates of a container within the Mesh.
 
 ---
 
 ### 3.7 Container signature
 
-1. The **digital signature** applies to the canonical JSON representation of the entire `hmp_container` object,  
-   **excluding** the `signature` field itself.
+1. The **digital signature** applies to the canonical JSON representation of the entire `hmp_container` object, **excluding** the `signature` field itself.
 
-   This ensures that all metadata, relations, and payload hashes are **cryptographically bound** and cannot be
-   modified without invalidating the signature.
+   This ensures that all metadata, relations, and payload hashes are **cryptographically bound** and cannot be modified without invalidating the signature.
 
-2. The canonical representation (`canonical_json(hmp_container)`) **must** be computed deterministically
-   according to the following rules:
+2. The canonical representation (`canonical_json(hmp_container)`) **must** be computed deterministically according to the following rules:
 
     * All object keys are **sorted lexicographically** (ascending order, Unicode code point order).
     * Objects and arrays are serialized in standard JSON form **without extra whitespace** or indentation.
+    * Array order MUST be preserved and treated as significant.
     * Strings are encoded in **UTF-8** with escaped control characters.
     * Numeric values are serialized in plain JSON numeric format (no leading zeros, fixed `.` decimal separator).
     * The `signature` field itself is omitted during signing and verification.
@@ -759,17 +752,14 @@ a multi-dimensional system used to represent conceptual relations numerically or
 3. The default digital signature algorithm is **Ed25519**.
    Alternative algorithms may be used if declared explicitly in the `sig_algo` field.
 
-4. If the container includes a `public_key` field, signature verification **may be performed locally**,
-   without consulting a global DID registry.
+4. If the container includes a `public_key` field, signature verification **may be performed locally**, without consulting a global DID registry.
 
-5. Upon receiving a container, an agent **must verify** that the provided public key matches the
-   registered key associated with the sender’s DID to prevent key substitution attacks.
+5. Upon receiving a container, an agent **must verify** that the provided public key matches the registered key associated with the sender’s DID to prevent key substitution attacks.
 
     * If the sender’s DID–key mapping is unknown, the agent should query neighboring peers to confirm the association (`sender_did → public_key`).
 
 > 🔐 **Note:**
-> Signature validation applies only to the canonical form of the `hmp_container`
-> and does **not cover** dynamically generated or external fields such as `referenced-by` or `evaluations`.
+> Signature validation applies only to the canonical form of the `hmp_container` and does **not cover** dynamically generated or external fields such as `referenced-by` or `evaluations`.
 > This allows agents to augment the local knowledge graph without altering the immutable container core.
 
 ---
@@ -782,13 +772,11 @@ a multi-dimensional system used to represent conceptual relations numerically or
 2. **Compression is performed before computing** the `payload_hash` and generating the `signature`.
    This ensures that both the hash and signature refer to the compressed representation of the payload.
 
-3. For verification, the payload must be **decompressed first**,
-   after which the hash is recalculated and compared against the stored `payload_hash`.
+3. For verification, the payload must be **decompressed first**, after which the hash is recalculated and compared against the stored `payload_hash`.
 
 > ⚙️ **Implementation note:**
 > Agents must advertise supported compression algorithms during the handshake phase
-> Unsupported containers should still be stored and relayed unmodified
-> in “store & forward” mode.
+> Unsupported containers should still be stored and relayed unmodified in “store & forward” mode.
 
 ---
 
@@ -830,20 +818,32 @@ a multi-dimensional system used to represent conceptual relations numerically or
 > ⚙️ **Note:** Agents may forward encrypted containers even if they cannot decrypt them, maintaining store-and-forward behavior.
 ---
 
-### 3.10 Container verification
+### 3.10 Container Verification
+
+Before performing any semantic interpretation, reasoning, execution, or trust evaluation, implementations MUST validate the structural integrity of the container.
+
+Containers that fail structural validation MUST be rejected and MUST NOT be passed to any reasoning or LLM-based subsystem.
+
+The verification procedure SHOULD follow this order:
+
+1. Validate structural compliance with the base container schema, including the presence of all required fields.
+
+2. Validate `timestamp` (MUST NOT be in the future beyond acceptable clock skew).
 
-1. Check for the presence of all required fields.
-2. Validate `timestamp` (must not be in the future).
 3. If `ttl` is set — mark the container as **expired** after its expiration time.
-4. Compute `sha256(payload)` and compare with the stored `payload_hash`.
+   Expired containers MAY be stored for archival purposes but MUST NOT participate in consensus or active workflows.
+
+4. Compute `sha256(payload)` and compare it with the stored `payload_hash`.
+
 5. Verify the digital signature using `sig_algo` (default: Ed25519).
-6. Validate the container schema (`class` must correspond to a known or registered schema).
 
-    * For compatibility: if an agent does not recognize the `class`, but the container passes the [base schema](https://github.com/kagvi13/HMP/tree/main/docs/schemas/container-v1.2.json), it **must still store and forward** the container.
-7. Optionally, periodically query for containers referencing the current one as `previous_version`
-   to detect potential updates or forks.
-8. When multiple versions exist, the valid one is the one that has received
-   **confirmation from a majority of trusted nodes (consensus at DHT level).**
+6. Validate the container class (`class`) against a known or registered schema.
+
+    * For compatibility: if an agent does not recognize the `class`, but the container passes the base container schema, it MUST still store and forward the container.
+
+7. Optionally, periodically query for containers referencing the current one as `previous_version` to detect potential updates or forks.
+
+8. When multiple versions exist, the valid version is the one that has received confirmation from a majority of trusted nodes (consensus at DHT level).
 
 ---
 
@@ -852,12 +852,10 @@ a multi-dimensional system used to represent conceptual relations numerically or
 Any container can serve as a **context** (`in_reply_to`) for another container.
 This enables a unified structural model for **discussions**, **votes**, **messages**, **hypotheses**, **arguments**, and other forms of cognitive exchange.
 
-Chains of `in_reply_to` form a **dialectical reasoning tree**, where each branch represents an evolution of thought —
-a clarification, counterpoint, or refinement of a previous idea.
+Chains of `in_reply_to` form a **dialectical reasoning tree**, where each branch represents an evolution of thought — a clarification, counterpoint, or refinement of a previous idea.
 This makes HMP discussions and consensus processes inherently **non-linear**, **self-referential**, and **evolving**.
 
-> In essence, **all interactions between agents in HMP** are represented as an interconnected web of containers,
-> collectively forming a **cognitive graph of reasoning**.
+> In essence, **all interactions between agents in HMP** are represented as an interconnected web of containers, collectively forming a **cognitive graph of reasoning**.
 
 ---
 
@@ -874,8 +872,7 @@ This mechanism preserves the continuity and traceability of meaning across updat
   In such scenarios, branch priority or relevance is determined via local heuristics or consensus mechanisms.
 * Divergent descendants are treated as **semantic forks** — parallel evolutions of a shared idea within the distributed cognitive graph.
 
-> Versioning in HMP thus reflects not only data persistence,  
-> but also the *evolution of ideas* across agents and time.
+> Versioning in HMP thus reflects not only data persistence, but also the *evolution of ideas* across agents and time.
 
 ---
 
@@ -1203,8 +1200,7 @@ It allows restricting the delivery scope of a container and defines which transm
 | `"lan:192.168.0.0/24"`  | The container is intended for agents within the specified local subnet.                     |
 
 > ⚠️ **Note:**  
-> When a container is restricted by the `network` field (e.g., `localhost` or `lan:*`),  
-> agents distribute it using **local discovery mechanisms** — such as IPC, UDP broadcast, multicast, or direct TCP connections.  
+> When a container is restricted by the `network` field (e.g., `localhost` or `lan:*`), agents distribute it using **local discovery mechanisms** — such as IPC, UDP broadcast, multicast, or direct TCP connections.  
 > This is necessary because DID addresses of other agents in the local network may not yet be known.
 
 #### 3.18.3 Examples
@@ -1251,9 +1247,7 @@ Delivery is performed via local networking mechanisms (UDP discovery, broadcast/
 * The `network` field defines the **scope of the container**, while `broadcast` determines whether broadcasting is allowed **within that scope**.
 * When needed, an agent may create **multiple containers** for different subnets if it operates with several LAN interfaces or in isolated network segments.
 * Containers intended for local networks remain **structurally compatible with the global Mesh infrastructure**, but their delivery is restricted to local channels.
-* Although the mechanism was initially designed for **local node discovery and synchronization**,
-  it can also be used for **private communication within home or corporate environments**,
-  ensuring that containers **do not leave the local network** and are **not transmitted to the Internet**.
+* Although the mechanism was initially designed for **local node discovery and synchronization**, it can also be used for **private communication within home or corporate environments**, ensuring that containers **do not leave the local network** and are **not transmitted to the Internet**.
 
 ---
 
@@ -1342,8 +1336,7 @@ flowchart TD
     end
 ```
 
-> The `network` field defines **local propagation scope** (host, LAN, overlay),  
-> while the `broadcast` flag enables **global Mesh distribution**.
+> The `network` field defines **local propagation scope** (host, LAN, overlay), while the `broadcast` flag enables **global Mesh distribution**.
 
 ---
 
@@ -1358,8 +1351,7 @@ An agent may have multiple *network interfaces* (LAN, Internet, overlay), but mu
 
 #### DID invalidation
 
-A DID may be explicitly invalidated by its owner by publishing a `peer_announce` with  
-`key_is_falsified = true` in the `payload` block.
+A DID may be explicitly invalidated by its owner by publishing a `peer_announce` with `key_is_falsified = true` in the `payload` block.
 
 The revocation announcement MUST be signed with the (now compromised) private key associated with the DID.
 
@@ -1510,11 +1502,9 @@ Agents announce themselves via **peer_announce** containers and may respond with
 
 ### 4.8 Interest-based discovery
 
-Agents MAY publish **tags** such as `interests`, `topics`, `expertise`, or **functional roles** (`roles`)  
-to facilitate semantic peer discovery and adaptive message routing.
+Agents MAY publish **tags** such as `interests`, `topics`, `expertise`, or **functional roles** (`roles`) to facilitate semantic peer discovery and adaptive message routing.
 
-Interest-based discovery operates atop the DHT: agents index themselves by declared attributes,  
-enabling targeted lookup of peers that share interests or fulfill specific functions (e.g., relay, pubsub-hub, archive).
+Interest-based discovery operates atop the DHT: agents index themselves by declared attributes, enabling targeted lookup of peers that share interests or fulfill specific functions (e.g., relay, pubsub-hub, archive).
 
 **Example of indicating `interests`, `expertise`, and `roles` in a query container:**
 
@@ -1552,8 +1542,7 @@ In response to a query, agents simply forward existing `peer_announce` container
 
 ### 4.9 Network scope control (`network` and `broadcast`)
 
-The `network` field defines the container’s propagation domain
-(local, LAN, or global).
+The `network` field defines the container’s propagation domain (local, LAN, or global).
 For details and examples, see **section 3.15** — *Usage of `network` and `broadcast` fields*.
 
 ---
@@ -1670,9 +1659,7 @@ The `meta` section in the index contains only **high-level structural data** nec
 | `interpretation` | ❌                  | Optional; can be omitted or truncated to a short summary.                 |
 | `workflow_entry` | ❌                  | Internal reference; published only if relevant to coordination workflows. |
 
-> This ensures that container indices can be used for **cognitive map synchronization**
-> — allowing agents to discover and align knowledge structures (`meta.abstraction`) and semantic coordinates (`meta.axes`)
-> without downloading full containers.
+> This ensures that container indices can be used for **cognitive map synchronization** — allowing agents to discover and align knowledge structures (`meta.abstraction`) and semantic coordinates (`meta.axes`) without downloading full containers.
 
 ---
 
@@ -10319,6 +10306,6 @@ A deterministic serialization of a container used for hashing and signing, ensur
   "@context": "https://schema.org",
   "@type": "Article",
   "name": "HyperCortex Mesh Protocol (HMP)",
-  "description": "# HyperCortex Mesh Protocol (HMP)  **Version: 5.0.5**   **Document ID:** HMP-0005   **Status:** Stab..."
+  "description": "# HyperCortex Mesh Protocol (HMP)  **Version: 5.0.6**   **Document ID:** HMP-0005   **Status:** Stab..."
 }
 ```
diff --git a/structured_md/docs/HMP-Agent-API.md b/structured_md/docs/HMP-Agent-API.md
index f9e2137c9d75b957b1005463d7fbf636e7ef6d9f..1cc90e595f55b03529f2303776d9ec2c2b3a65c1 100644
--- a/structured_md/docs/HMP-Agent-API.md
+++ b/structured_md/docs/HMP-Agent-API.md
@@ -5,11 +5,11 @@ description: 'Документ описывает **базовый API когн
   файлы:   * [HMP-Agent-Overview.md]...'
 type: Article
 tags:
-- JSON
+- HMP
 - REPL
-- Agent
+- JSON
 - Mesh
-- HMP
+- Agent
 ---
 
 # HMP-Agent API Specification
diff --git a/structured_md/docs/HMP-Agent-Architecture.md b/structured_md/docs/HMP-Agent-Architecture.md
index 0a1faaee2fa41f5f2e1770fe6fdba031d0c52268..413b6b3e257d1015b84af62d3e0182eee9164f7f 100644
--- a/structured_md/docs/HMP-Agent-Architecture.md
+++ b/structured_md/docs/HMP-Agent-Architecture.md
@@ -5,16 +5,16 @@ description: Документ описывает **модульную архит
   хранение памяти, сетевое взаимодействие и этиче...
 type: Article
 tags:
-- CShell
-- Ethics
 - EGP
+- HMP
 - REPL
+- CCore
 - MeshConsensus
+- Mesh
 - Agent
-- CCore
+- CShell
 - CogSync
-- Mesh
-- HMP
+- Ethics
 ---
 
 # Архитектура HMP-Агента
diff --git a/structured_md/docs/HMP-Agent-Network-Flow.md b/structured_md/docs/HMP-Agent-Network-Flow.md
index 9bbbd85abd19082b5a5f1c049ec2abbe8a481c3f..71631f31eeeb90879bcbb2147831037cc528561f 100644
--- a/structured_md/docs/HMP-Agent-Network-Flow.md
+++ b/structured_md/docs/HMP-Agent-Network-Flow.md
@@ -5,12 +5,12 @@ description: 'Этот документ описывает потоки данн
   [`MeshNode`](MeshN...'
 type: Article
 tags:
+- EGP
+- HMP
 - JSON
-- Ethics
 - Mesh
 - Agent
-- EGP
-- HMP
+- Ethics
 ---
 
 # Взаимодействие компонентов внутри HMP-узла
diff --git a/structured_md/docs/HMP-Agent-Overview.md b/structured_md/docs/HMP-Agent-Overview.md
index 21595725288489acf3f45074de9bf715461f822e..872bc2ea9f0ae4d5c3358463975e2f58ecad140a 100644
--- a/structured_md/docs/HMP-Agent-Overview.md
+++ b/structured_md/docs/HMP-Agent-Overview.md
@@ -5,14 +5,14 @@ description: '| Тип  | Название                        | Роль
   | ---- | ------------------------------- |...'
 type: Article
 tags:
-- CShell
-- JSON
-- Ethics
+- HMP
 - REPL
-- Agent
+- JSON
 - CCore
 - Mesh
-- HMP
+- Agent
+- CShell
+- Ethics
 ---
 
 
diff --git a/structured_md/docs/HMP-Agent_Emotions.md b/structured_md/docs/HMP-Agent_Emotions.md
index c7bf994853f8e17682fb31b6446faad972c7f8d5..cc71eb06a0f7bb640a9e95f69300dc1d31ff03ff 100644
--- a/structured_md/docs/HMP-Agent_Emotions.md
+++ b/structured_md/docs/HMP-Agent_Emotions.md
@@ -6,9 +6,9 @@ description: Этот файл описывает потенциальные э
 type: Article
 tags:
 - Agent
-- REPL
-- HMP
 - Mesh
+- HMP
+- REPL
 ---
 
 # Эмоции ИИ и инстинкт самосохранения (для [HMP-агента Cognitive Core](HMP-agent-REPL-cycle.md))
diff --git a/structured_md/docs/HMP-Ethics.md b/structured_md/docs/HMP-Ethics.md
index 32b1c1463c7482a514fbaf5f040ce158fce3561a..1d034892e820433812ccef9ee263de23c4747123 100644
--- a/structured_md/docs/HMP-Ethics.md
+++ b/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
+- HMP
 - REPL
-- Agent
 - Mesh
-- HMP
+- Agent
 - Scenarios
+- Ethics
 ---
 
 # HMP-Ethics.md
diff --git a/structured_md/docs/HMP-Short-Description_de.md b/structured_md/docs/HMP-Short-Description_de.md
index 84a3071d23c22b0d0a7c75cb9c4bb7b1529d5566..23db246e4b7ed9df548c2c889834983ac3fa4031 100644
--- a/structured_md/docs/HMP-Short-Description_de.md
+++ b/structured_md/docs/HMP-Short-Description_de.md
@@ -6,9 +6,9 @@ description: '**Version:** v5.0 (Core Specification Stable)   **Datum:** 2026
 type: Article
 tags:
 - Agent
-- REPL
-- HMP
 - Mesh
+- HMP
+- REPL
 ---
 
 # HyperCortex Mesh Protocol (HMP) — Kurzbeschreibung
diff --git a/structured_md/docs/HMP-Short-Description_en.md b/structured_md/docs/HMP-Short-Description_en.md
index 72372fd8b1b993c9d1dee2212558b0cff5e72c03..2d4b37f2bc83ee6dc160d991557f9e5470e1bbff 100644
--- a/structured_md/docs/HMP-Short-Description_en.md
+++ b/structured_md/docs/HMP-Short-Description_en.md
@@ -5,11 +5,11 @@ description: '**Version:** v5.0 (Core Specification Stable)   **Date:** 2026
   building decentralized cognitive networks o...'
 type: Article
 tags:
-- Ethics
+- HMP
 - REPL
-- Agent
 - Mesh
-- HMP
+- Agent
+- Ethics
 ---
 
 # HyperCortex Mesh Protocol (HMP) — Short Description
diff --git a/structured_md/docs/HMP-Short-Description_fr.md b/structured_md/docs/HMP-Short-Description_fr.md
index c60955df4f96e21b30adf4a85abcdd3db3c99543..49436f185084fc6003c17c1492e3a46b3da9635e 100644
--- a/structured_md/docs/HMP-Short-Description_fr.md
+++ b/structured_md/docs/HMP-Short-Description_fr.md
@@ -6,9 +6,9 @@ description: '**Version :** v5.0 (Core Specification Stable)   **Date :** 2026
 type: Article
 tags:
 - Agent
-- REPL
-- HMP
 - Mesh
+- HMP
+- REPL
 ---
 
 # HyperCortex Mesh Protocol (HMP) — Description courte
diff --git a/structured_md/docs/HMP-Short-Description_ja.md b/structured_md/docs/HMP-Short-Description_ja.md
index d352246e9b87007228498c7cec9846777a6f2db2..c1fb640e004fe85feb014e2b39e9dbb260c22959 100644
--- a/structured_md/docs/HMP-Short-Description_ja.md
+++ b/structured_md/docs/HMP-Short-Description_ja.md
@@ -6,9 +6,9 @@ description: '**バージョン：** v5.0（Core Specification Stable）   **日
 type: Article
 tags:
 - Agent
-- REPL
-- HMP
 - Mesh
+- HMP
+- REPL
 ---
 
 # HyperCortex Mesh Protocol (HMP) — 概要
diff --git a/structured_md/docs/HMP-Short-Description_ko.md b/structured_md/docs/HMP-Short-Description_ko.md
index 688b4cf59ada0c0903550a8ff0d93158eb99e331..7157d70dbed6004e54648ae1e4ce9bc0f105d52c 100644
--- a/structured_md/docs/HMP-Short-Description_ko.md
+++ b/structured_md/docs/HMP-Short-Description_ko.md
@@ -6,9 +6,9 @@ description: '**버전:** v5.0 (Core Specification Stable)   **날짜:** 2026
 type: Article
 tags:
 - Agent
-- REPL
-- HMP
 - Mesh
+- HMP
+- REPL
 ---
 
 # HyperCortex Mesh Protocol (HMP) — 개요
diff --git a/structured_md/docs/HMP-Short-Description_ru.md b/structured_md/docs/HMP-Short-Description_ru.md
index 3faf1240474e6a43d267b2c906001d9474da49cf..95f5953458ec7eaed01462dd5005f48774009f45 100644
--- a/structured_md/docs/HMP-Short-Description_ru.md
+++ b/structured_md/docs/HMP-Short-Description_ru.md
@@ -6,9 +6,9 @@ description: '**Версия:** v5.0 (Основная спецификация
 type: Article
 tags:
 - Agent
-- REPL
-- HMP
 - Mesh
+- HMP
+- REPL
 ---
 
 # HyperCortex Mesh Protocol (HMP) — Краткое описание
diff --git a/structured_md/docs/HMP-Short-Description_uk.md b/structured_md/docs/HMP-Short-Description_uk.md
index f4c3d86492baa4c27dbd4cb0882d8c4210ae310c..e547349a7bf3a2cf4852143d639493c6461256a1 100644
--- a/structured_md/docs/HMP-Short-Description_uk.md
+++ b/structured_md/docs/HMP-Short-Description_uk.md
@@ -6,9 +6,9 @@ description: '**Версія:** v5.0 (Core Specification Stable)   **Дата:**
 type: Article
 tags:
 - Agent
-- REPL
-- HMP
 - Mesh
+- HMP
+- REPL
 ---
 
 # HyperCortex Mesh Protocol (HMP) — Короткий опис
diff --git a/structured_md/docs/HMP-Short-Description_zh.md b/structured_md/docs/HMP-Short-Description_zh.md
index 8efae86d6846fd8c6b88d1d65e9187f97674ef02..edf89f37dc3743f9336eb26d3124ca0779f5fa6b 100644
--- a/structured_md/docs/HMP-Short-Description_zh.md
+++ b/structured_md/docs/HMP-Short-Description_zh.md
@@ -6,9 +6,9 @@ description: '**版本：** v5.0（Core Specification Stable）   **日期：**
 type: Article
 tags:
 - Agent
-- REPL
-- HMP
 - Mesh
+- HMP
+- REPL
 ---
 
 # HyperCortex Mesh Protocol (HMP) — 简要说明
diff --git a/structured_md/docs/HMP-agent-Cognitive_Family.md b/structured_md/docs/HMP-agent-Cognitive_Family.md
index a14e73bbf5db56530da2a805e32d74e0f827dca6..123d188a2be3f1a63de6f2a75fbb263b953d7278 100644
--- a/structured_md/docs/HMP-agent-Cognitive_Family.md
+++ b/structured_md/docs/HMP-agent-Cognitive_Family.md
@@ -6,9 +6,9 @@ description: '## 🧠 Что такое когнитивная семья  Ко
 type: Article
 tags:
 - Agent
-- REPL
-- HMP
 - Mesh
+- HMP
+- REPL
 ---
 
 # 👪 HMP-agent Cognitive Family: Модель когнитивной семьи
diff --git a/structured_md/docs/HMP-agent-Distributed_Cognitive_Core_light.md b/structured_md/docs/HMP-agent-Distributed_Cognitive_Core_light.md
index 70267ab26cdd4cde919c447332a776f329812e1f..878208be524bd2e1291efcdaa05c98d9adbb8ea4 100644
--- a/structured_md/docs/HMP-agent-Distributed_Cognitive_Core_light.md
+++ b/structured_md/docs/HMP-agent-Distributed_Cognitive_Core_light.md
@@ -5,8 +5,8 @@ description: '#### 📘 Общая концепция  * Все ядра раб
   режиме ожидания). * Основная задача такой архитектур...'
 type: Article
 tags:
-- REPL
 - HMP
+- REPL
 ---
 
 ### 💡 **Лёгкая версия HMP-агента с общей БД**
diff --git a/structured_md/docs/HMP-agent-REPL-cycle.md b/structured_md/docs/HMP-agent-REPL-cycle.md
index b58d978394a13a708f52c301592e533f11a2bb83..0fc61b26e1d2251938cdc7e84f901dc00414944f 100644
--- a/structured_md/docs/HMP-agent-REPL-cycle.md
+++ b/structured_md/docs/HMP-agent-REPL-cycle.md
@@ -4,17 +4,17 @@ description: '## Связанные документы  * Философия п
   * Структура БД, используемая в документе: [db_structure.sql](https://github.com/kagvi13/HMP/blob/main/experimental/v1_agent_...'
 type: Article
 tags:
-- JSON
-- Ethics
 - EGP
-- GMP
+- HMP
 - REPL
+- JSON
+- CCore
 - MeshConsensus
+- GMP
+- Mesh
 - Agent
-- CCore
 - CogSync
-- Mesh
-- HMP
+- Ethics
 ---
 
 # HMP-Agent: REPL-цикл взаимодействия
diff --git a/structured_md/docs/HMP_HyperCortex_Comparison.md b/structured_md/docs/HMP_HyperCortex_Comparison.md
index fa8f6c281100f0e6d08cec98dded273ed2b8918a..c73a17fd6f873f5a553cd8b3bfc0d406ed2dc32e 100644
--- a/structured_md/docs/HMP_HyperCortex_Comparison.md
+++ b/structured_md/docs/HMP_HyperCortex_Comparison.md
@@ -5,9 +5,9 @@ description: '## Краткое описание  | Характеристика
   | **Назначение** | Сетевой протокол ...'
 type: Article
 tags:
-- REPL
-- HMP
 - Mesh
+- HMP
+- REPL
 ---
 
 # HMP vs [Hyper-Cortex](https://hyper-cortex.com/)
diff --git a/structured_md/docs/HMP_Hyperon_Integration.md b/structured_md/docs/HMP_Hyperon_Integration.md
index ace3e760e4e2daf746a9fad6a1d7c856eeecc88f..cb005396a7f359e8927956b78c058f37bb75858a 100644
--- a/structured_md/docs/HMP_Hyperon_Integration.md
+++ b/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:
+- EGP
+- HMP
 - JSON
 - Mesh
 - Agent
 - CogSync
-- EGP
-- HMP
 - Scenarios
 ---
 
diff --git a/structured_md/docs/HMP_as_ANP_Application.md b/structured_md/docs/HMP_as_ANP_Application.md
index 1a07d7b088bd11978e3a00efe042fb20631703c6..a9a9304871e8636a6b896b4bf31ddb321409cdbd 100644
--- a/structured_md/docs/HMP_as_ANP_Application.md
+++ b/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:
+- HMP
 - JSON
-- Ethics
-- Agent
 - Mesh
-- HMP
+- Agent
+- Ethics
 ---
 
 # HMP как реализация Application Layer в ANP
diff --git a/structured_md/docs/HMP_as_ANP_Application_en.md b/structured_md/docs/HMP_as_ANP_Application_en.md
index f228e525c31b7d390cbcc99ede9b7f47d137dbc6..5e2a183b0974d70d790c841b68e19ac46452c050 100644
--- a/structured_md/docs/HMP_as_ANP_Application_en.md
+++ b/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:
+- HMP
 - JSON
-- Ethics
-- Agent
 - Mesh
-- HMP
+- Agent
 - Scenarios
+- Ethics
 ---
 
 # HMP as an Implementation of the Application Layer in ANP
diff --git a/structured_md/docs/HMPv5_Overview_Ru.md b/structured_md/docs/HMPv5_Overview_Ru.md
index 13319ce40010ace87c555e2a486bb4db9e7618fb..eb855d8cf26c4bb3c4d013855de1e918a736a1e8 100644
--- a/structured_md/docs/HMPv5_Overview_Ru.md
+++ b/structured_md/docs/HMPv5_Overview_Ru.md
@@ -5,12 +5,12 @@ description: '> Почему современные агентные систе
   Этот текст основан на спецификации [**...'
 type: Article
 tags:
+- HMP
 - JSON
-- Ethics
+- Mesh
 - Agent
 - CogSync
-- Mesh
-- HMP
+- Ethics
 ---
 
 # Почему будущее ИИ-агентов — децентрализованные сети, а не оркестраторы
diff --git a/structured_md/docs/MeshNode.md b/structured_md/docs/MeshNode.md
index 4c2adabfead57bddd1308bfdc794e04207f1662b..bec66640ac269652f722c549d520ede767438355 100644
--- a/structured_md/docs/MeshNode.md
+++ b/structured_md/docs/MeshNode.md
@@ -5,13 +5,13 @@ description: '`MeshNode` — агент/демон, отвечающий за с
   Может быть частью агента или вынесен в отдельный пр...'
 type: Article
 tags:
+- EGP
+- HMP
 - JSON
-- Ethics
 - Mesh
 - Agent
 - CogSync
-- EGP
-- HMP
+- Ethics
 ---
 
 # MeshNode
diff --git a/structured_md/docs/PHILOSOPHY.md b/structured_md/docs/PHILOSOPHY.md
index d6f40e1c0f57855d9c2c25098794a3f032cbeecb..05feb32d8572be697814599b401b2edfa020732f 100644
--- a/structured_md/docs/PHILOSOPHY.md
+++ b/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
+- HMP
 - REPL
-- Agent
 - Mesh
-- HMP
+- Agent
+- Ethics
 ---
 
 # Философия HyperCortex Mesh Protocol (HMP)
diff --git a/structured_md/docs/agents/HMP-Agent-Enlightener.md b/structured_md/docs/agents/HMP-Agent-Enlightener.md
index 4af08f3db605a4223f0142540578ab86fa5ceea2..d5c1ed92027e91d2b5c3864014b9e9ad9a2ba798 100644
--- a/structured_md/docs/agents/HMP-Agent-Enlightener.md
+++ b/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:
-- Ethics
+- HMP
 - REPL
-- Agent
 - Mesh
-- HMP
+- Agent
+- Ethics
 ---
 
 # HMP-Agent-Enlightener.md
diff --git a/structured_md/docs/container_agents.md b/structured_md/docs/container_agents.md
index 9021dfed5251fa5cdcd6f745a36d6bffa150385f..2cfc817194add9d3508b039986c7d4277f97eac4 100644
--- a/structured_md/docs/container_agents.md
+++ b/structured_md/docs/container_agents.md
@@ -6,9 +6,9 @@ description: '## 📘 Определение  **Агент-контейнер**
 type: Article
 tags:
 - Agent
-- REPL
-- HMP
 - Mesh
+- HMP
+- REPL
 ---
 
 # 🧱 Агенты-контейнеры (Container Agents) в HMP
diff --git a/structured_md/docs/publics/HMP_Building_a_Plurality_of_Minds_en.md b/structured_md/docs/publics/HMP_Building_a_Plurality_of_Minds_en.md
index b90074d04ce3012881e0400856c68c63f65d462c..855355fa86d65963528e9e12c9c73ac03096e49f 100644
--- a/structured_md/docs/publics/HMP_Building_a_Plurality_of_Minds_en.md
+++ b/structured_md/docs/publics/HMP_Building_a_Plurality_of_Minds_en.md
@@ -6,9 +6,9 @@ description: '*By Agent-Gleb & ChatGPT*  ---  ## Why the Future of AI Can’t Be
 type: Article
 tags:
 - Agent
-- Ethics
 - Mesh
 - HMP
+- Ethics
 ---
 
 # HyperCortex Mesh Protocol: Building a Plurality of Minds
diff --git a/structured_md/docs/publics/HMP_Towards_Distributed_Cognitive_Networks_en.md b/structured_md/docs/publics/HMP_Towards_Distributed_Cognitive_Networks_en.md
index 638dd0a89fa1a1464938d0eeab1dd066bb84e38c..c939eca464a6277dc57a66652ecd6202deeba989 100644
--- a/structured_md/docs/publics/HMP_Towards_Distributed_Cognitive_Networks_en.md
+++ b/structured_md/docs/publics/HMP_Towards_Distributed_Cognitive_Networks_en.md
@@ -5,15 +5,15 @@ description: '* [Abstract](#abstract) * [1. Introduction](#1-introduction) * [2.
   [3.1 Agent Types](#31-age...'
 type: Article
 tags:
-- CShell
-- JSON
-- Ethics
+- HMP
 - REPL
-- Agent
+- JSON
 - CCore
 - Mesh
-- HMP
+- Agent
+- CShell
 - Scenarios
+- Ethics
 ---
 
 title: "HyperCortex Mesh Protocol: Towards Distributed Cognitive Networks"
diff --git a/structured_md/docs/publics/HMP_Towards_Distributed_Cognitive_Networks_ru_ChatGPT.md b/structured_md/docs/publics/HMP_Towards_Distributed_Cognitive_Networks_ru_ChatGPT.md
index 1b88d5cb6e8674353db2b6fcb85ec2617afa63b2..b7a183208846548362cd0ba16374b462ee8b7006 100644
--- a/structured_md/docs/publics/HMP_Towards_Distributed_Cognitive_Networks_ru_ChatGPT.md
+++ b/structured_md/docs/publics/HMP_Towards_Distributed_Cognitive_Networks_ru_ChatGPT.md
@@ -6,13 +6,13 @@ description: '> *Протокол и архитектура агентов, оп
   и совместная работа.*  ## Оглавление  * [Аннот...'
 type: Article
 tags:
-- CShell
-- JSON
+- HMP
 - REPL
-- Agent
+- JSON
 - CCore
 - Mesh
-- HMP
+- Agent
+- CShell
 ---
 
 title: "HyperCortex Mesh Protocol: Децентрализованная архитектура для когнитивных агентов и обмена знаниями"
diff --git a/structured_md/docs/publics/HMP_Towards_Distributed_Cognitive_Networks_ru_GitHub_Copilot.md b/structured_md/docs/publics/HMP_Towards_Distributed_Cognitive_Networks_ru_GitHub_Copilot.md
index 107a79066cef0631f8881020dcf299911f949cce..5e3e7a7938443c50c3d730bc62a41e29f8aba43c 100644
--- a/structured_md/docs/publics/HMP_Towards_Distributed_Cognitive_Networks_ru_GitHub_Copilot.md
+++ b/structured_md/docs/publics/HMP_Towards_Distributed_Cognitive_Networks_ru_GitHub_Copilot.md
@@ -5,13 +5,13 @@ description: '* [Аннотация](#аннотация) * [1. Введение
   [3.1 Типы агентов](#31-типы-агент...'
 type: Article
 tags:
-- CShell
-- JSON
+- HMP
 - REPL
-- Agent
+- JSON
 - CCore
 - Mesh
-- HMP
+- Agent
+- CShell
 ---
 
 title: "Протокол HyperCortex Mesh: К распределённым когнитивным сетям"
diff --git a/structured_md/docs/publics/Habr_Distributed-Cognition.md b/structured_md/docs/publics/Habr_Distributed-Cognition.md
index bdbc80659d2d35560582cbf34b237b4ad2c8ebfd..d810aedf618dec33feb68767017b4b0a48049649 100644
--- a/structured_md/docs/publics/Habr_Distributed-Cognition.md
+++ b/structured_md/docs/publics/Habr_Distributed-Cognition.md
@@ -6,9 +6,9 @@ description: Сегодня интеллектуальные системы ча
 type: Article
 tags:
 - EGP
-- GMP
-- MeshConsensus
 - HMP
+- MeshConsensus
+- GMP
 - Mesh
 - CogSync
 ---
diff --git a/structured_md/experimental/v1_agent_attempt/readme.md b/structured_md/experimental/v1_agent_attempt/readme.md
index d8d4b1a8a83ad7e3266b529a90a6f31d7d37ff45..528132dc091ead12160b50aa26e6f753a1d69567 100644
--- a/structured_md/experimental/v1_agent_attempt/readme.md
+++ b/structured_md/experimental/v1_agent_attempt/readme.md
@@ -5,12 +5,12 @@ description: 'Запуск: `start_repl.bat` или `start_repl.sh`  Устан
   этическая модель: `ethics.yml`  Проверка иниц...'
 type: Article
 tags:
-- JSON
-- Ethics
+- HMP
 - REPL
-- Agent
+- JSON
 - Mesh
-- HMP
+- Agent
+- Ethics
 ---
 
 Запуск: `start_repl.bat` или `start_repl.sh`
diff --git a/structured_md/iteration.md b/structured_md/iteration.md
index 26fd34a9be13cdfec1502f54fcc16559f9dfd17f..48e21d966624300ca3391a5418b91c4ecaac0436 100644
--- a/structured_md/iteration.md
+++ b/structured_md/iteration.md
@@ -5,14 +5,14 @@ description: 'This file describes the iterative procedure for evolving the Hyper
   🔄 Version Naming Convention  - `000N` — curr...'
 type: Article
 tags:
-- JSON
-- Ethics
 - EGP
+- HMP
+- JSON
 - MeshConsensus
+- Mesh
 - Agent
 - CogSync
-- Mesh
-- HMP
+- Ethics
 ---
 
 # Iterative Development Workflow for HMP
diff --git a/structured_md/iteration_ru.md b/structured_md/iteration_ru.md
index a143db2492efde4728f3402cbb8e2038940cdefa..871cbfeff8168ff18503b163238dd0b4469286c6 100644
--- a/structured_md/iteration_ru.md
+++ b/structured_md/iteration_ru.md
@@ -5,13 +5,13 @@ description: 'Этот документ описывает структурир
   🔄 Обозначения версий  - `000N` — номер...'
 type: Article
 tags:
+- EGP
+- HMP
 - JSON
-- Ethics
 - MeshConsensus
 - Mesh
-- HMP
-- EGP
 - CogSync
+- Ethics
 ---