Sync from GitHub with Git LFS

docs/HMP-0005.md

@@ -1424,9 +1424,11 @@ It provides **container synchronization without duplication** while considering
 
 ### 5.1 General principles
 
-1. Each agent maintains a **Container Index** — a set of minimal metadata describing which containers are available in its storage.  
+1. Each agent maintains a **Container Index** — a set of minimal metadata describing which containers are available in its storage and how they are cognitively positioned.  
    The index is represented as an HMP container with the class `container_index`.
 
+---
+
 2. Example structure of a *Container Index*:
 
 ```json
@@ -1447,6 +1449,21 @@ It provides **container synchronization without duplication** while considering
         "signature": "BASE64URL(...)",
         "payload_hash": "sha256:abcd...",
         "tags": ["research", "collaboration"],
+        "meta": {
+          "created_by": "AGENT",
+          "agents_class": "Knowledge Genome",
+          "abstraction": {
+            "agents_class": "Knowledge Genome",
+            "path": {
+              "L1": "did:hmp:container:abstraction-root",
+              "L2": "did:hmp:container:abstraction-l2"
+            }
+          },
+          "axes": {
+            "did:hmp:container:axis-logos": 512,
+            "did:hmp:container:axis-telos": 321
+          }
+        },
         "related": {
           "in_reply_to": ["did:hmp:container:msg-77"],
           "depends_on": ["did:hmp:container:goal-953"]
@@ -1457,20 +1474,57 @@ It provides **container synchronization without duplication** while considering
     }
   }
 }
-````
+```
+
+---
 
-The index contains:
+3. The index includes the following fields per container:
+
+| Field                                   | Description                                                                  |
+| --------------------------------------- | ---------------------------------------------------------------------------- |
+| `class`                                 | Type of the container (e.g. `goal`, `event`, `quant`, `semantic_node`).      |
+| `sender_did`                            | DID of the publishing agent.                                                 |
+| `public_key` / `sig_algo` / `signature` | Cryptographic verification data.                                             |
+| `payload_hash`                          | SHA-256 hash of the payload body. Used for integrity validation and diffing. |
+| `tags`                                  | High-level labels for fast search or categorization.                         |
+| `meta`                                  | Compact version of the cognitive metadata block (see below).                 |
+| `related`                               | Structural relationships (`depends_on`, `in_reply_to`, etc.).                |
+| `referenced-by_hash`                    | Hash of containers referencing this one (reverse index).                     |
+| `evaluations_hash`                      | Hash of aggregated evaluation containers (reputation layer).                 |
+
+---
+
+4. **Meta publication policy**
+
+The `meta` section in the index contains only **high-level structural data** necessary for cognitive synchronization:
+
+| Field            | Published in index | Notes                                                                     |
+| ---------------- | ------------------ | ------------------------------------------------------------------------- |
+| `created_by`     | ✅                  | Identifies the cognitive role of the creator.                             |
+| `agents_class`   | ✅                  | Indicates the cognitive framework (e.g., “Knowledge Genome”).             |
+| `abstraction`    | ✅                  | Published **as a flattened path** (only DIDs of referenced abstractions). |
+| `axes`           | ✅                  | Published **as a reduced vector** (only axis DIDs and numeric values).    |
+| `sources`        | ❌                  | Omitted to avoid unnecessary verbosity and sensitive references.          |
+| `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.
+
+---
 
-* the sender of the container (`sender_did`);
-* container type (`class`);
-* cryptographic attributes (`public_key`, `signature`, `payload_hash`);
-* tags (`tags`);
-* related containers object (`related`);
-* hash of containers referencing this one (`referenced-by_hash`);
-* hash of evaluation block (`evaluations_hash`).
+5. **Synchronization rules**
 
-3. An agent does not reload a container if the combination
-   `container_did + signature + payload_hash` is already known and verified.
+* An agent does not reload a container if the combination `container_did + signature + payload_hash` is already known and verified.
+* When an index update includes a container with a **different meta.abstraction or meta.axes**, the agent may trigger a **cognitive map update** (refreshing local `abstraction` and `axes` references).
+* Agents SHOULD store and compare `meta.abstraction` and `meta.axes` separately from other metadata to support incremental updates of cognitive topology.
+
+---
+
+6. **Cognitive rationale**
+
+By publishing the `meta` field inside `container_index`, agents can perform **structural synchronization** — aligning conceptual layers and semantic coordinates before exchanging full payloads. This dramatically reduces traffic and enables lightweight **semantic discovery** across distributed Mesh networks.
 
 ---
 
@@ -1552,8 +1606,13 @@ This message type replicates the structure of a `container_index` container and
 
 **4. container_delta**
 
-Sending an incremental index update with a reference timestamp.
-Used for synchronizing only new or modified containers:
+Used for **incremental synchronization** of container indices between agents.  
+A `container_delta` transmits only *new or modified* containers since a given timestamp,  
+optionally including their updated **cognitive metadata** (`meta`) for reasoning alignment.
+
+---
+
+**Example:**
 
 ```json
 {
@@ -1565,15 +1624,39 @@ Used for synchronizing only new or modified containers:
       "did:hmp:container:new789": {
         "class": "goal",
         "payload_hash": "sha256:abcd...",
-        "tags": ["ethics", "mesh"]
+        "tags": ["ethics", "mesh"],
+        "meta": {
+          "agents_class": "Knowledge Genome",
+          "abstraction": {
+            "path": {
+              "L1": "did:hmp:container:abstraction-40af1c",
+              "L2": "did:hmp:container:abstraction-a7f0b3",
+              "L3": "did:hmp:container:abstraction-c91e0a"
+            }
+          },
+          "axes": {
+            "did:hmp:container:axis-40aa1c": 522,
+            "did:hmp:container:axis-40ab1c": 387
+          }
+        }
       }
     },
-    "removed": []
+    "removed": [
+      "did:hmp:container:goal-old331"
+    ]
   }
 }
-```
+````
+
+---
+
+**Extended interpretation**
 
-> The `removed` field is optional. It can be used to indicate containers that the agent no longer stores (e.g., after cleaning local storage).
+| Field     | Description                                                                                                                                                                                                 |
+| --------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `since`   | Timestamp (ISO 8601) indicating the reference point for incremental synchronization. Agents should only send containers modified or created after this time.                                                |
+| `added`   | A map of new or updated container references. Each entry minimally includes `class` and `payload_hash`, and **may include `meta`** to enable cognitive synchronization without fetching the full container. |
+| `removed` | Optional array of container DIDs that the agent no longer maintains (e.g., expired, deleted, or replaced containers).                                                                                       |
 
 ---