Sync from GitHub with Git LFS

docs/HMP-0005.md

@@ -392,6 +392,12 @@ The unified container structure provides:
     "signature": "BASE64URL(...)",
     "links_hash": "sha256:abcd..."
   }
+  "evaluations": {
+    "evaluations_hash": "sha256:efgh...",
+    "items": [
+      { "value": -0.4, "type": "oppose", "target": "did:hmp:container:reason789", "timestamp": "2025-10-17T14:00:00Z", "agent_did": "did:hmp:agent:B", "sig_algo": "ed25519", "signature": "BASE64URL(...)" }
+    ]
+  }
 }
 ```
 
@@ -832,18 +838,18 @@ If container `[C7]` does not actually reference `[C1]`, it is excluded before si
 
 ---
 
-### 3.16 Usage of `network` and `broadcast` Fields
+### 3.17 Usage of `network` and `broadcast` Fields
 
 The `network` field is introduced to control container propagation in both local and global environments.  
 It allows restricting the delivery scope of a container and defines which transmission methods should be used by the agent.
 
-#### 3.16.1 General Rules
+#### 3.17.1 General Rules
 
 * If the `network` field is not empty, the container is intended for a **local environment** and **must not be transmitted to the global Mesh**.  
   In this case, the `broadcast` field is automatically considered `false`, and the `recipient` field is set to an empty array (`[]`).
 * If the `network` field is empty (`""`), the container is allowed to be broadcasted within the global Mesh using standard DID addressing and delivery mechanisms.
 
-#### 3.16.2 Possible Values of `network`
+#### 3.17.2 Possible Values of `network`
 
 | Value                   | Description                                                                                 |
 | ----------------------- | ------------------------------------------------------------------------------------------- |
@@ -856,7 +862,7 @@ It allows restricting the delivery scope of a container and defines which transm
 > 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.16.3 Examples
+#### 3.17.3 Examples
 
 1. **Global Mesh Delivery:**
 
@@ -895,7 +901,7 @@ The container is delivered only to other agents running on the same host using l
 The container is intended for agents within the `192.168.0.0/24` subnet.
 Delivery is performed via local networking mechanisms (UDP discovery, broadcast/multicast).
 
-#### 3.16.4 Specifics
+#### 3.17.4 Specifics
 
 * 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.