Sync from GitHub with Git LFS

docs/HMP-0005.md

@@ -8508,18 +8508,35 @@ The consensus container:
 
 Conceptually, the proof chain forms the following graph:
 
-```
-workflow_entry
-      ▲
-      │
-     goal
-      ▲▲
-      │├── vote (Agent B)
-      │├── vote (Agent C)
-      │└── vote (Agent D)
-      │       ▲
-      │       │
-   consensus_result
+```mermaid
+flowchart TD
+    title["**Container Relationships in a Voting Process**"]
+
+    workflow_entry
+    goal
+
+    subgraph Votes
+        voteB["vote (Agent B)"]
+        voteC["vote (Agent C)"]
+        voteD["vote (Agent D)"]
+    end
+
+    consensus_result
+
+    goal --> workflow_entry
+
+    note["Edges are directed from the referencing container<br/>to the referenced container."]
+
+    voteB --> goal
+    voteC --> goal
+    voteD --> goal
+
+    consensus_result --> voteB
+    consensus_result --> voteC
+    consensus_result --> voteD
+    consensus_result --> goal
+
+    note -.-> consensus_result
 ```
 
 Each arrow represents an explicit, directed semantic reference from the *later* container to one or more *earlier* containers via `related.*` fields (e.g. `depends_on`, `in_reply_to`).
@@ -8624,43 +8641,26 @@ Key properties of the stack:
 
 Containers in HMP are **immutable artifacts** that progress through a lifecycle driven by publication, referencing, evaluation, and aggregation.
 
-```text
-┌────────────────────┐
-│    Draft (local)   │
-│     (unsigned)     │
-└─────────┬──────────┘
-          │
-          ▼
-┌────────────────────┐
-│  Signed Container  │
-│  (canonical JSON)  │
-└─────────┬──────────┘
-          │
-          ▼
-┌────────────────────┐
-│  Published to Mesh │
-│  (DHT / routing)   │
-└─────────┬──────────┘
-          │
-          ▼
-┌────────────────────┐
-│  Referenced by     │
-│  other containers  │
-│  (related.* links) │
-└─────────┬──────────┘
-          │
-          ▼
-┌────────────────────┐
-│  Evaluated /       │
-│  Voted / Extended  │
-│  (external blocks) │
-└─────────┬──────────┘
-          │
-          ▼
-┌────────────────────┐
-│  Aggregated        │
-│  (e.g. consensus)  │
-└────────────────────┘
+```mermaid
+flowchart TD
+    title["**Container Lifecycle and Layered Relationships**"]
+
+    Draft["Draft (local)<br>(unsigned)"]
+    Signed["Signed container<br>(canonical JSON)"]
+    Published["Published to Mesh<br>(DHT / routing)"]
+
+    Referenced["Referenced by<br>other containers<br>(related.*)"]
+    Evaluated["Evaluated / Voted<br>(external blocks)"]
+    Aggregated["Aggregated<br>(e.g. consensus_result)"]
+
+    Draft --> Signed
+    Signed --> Published
+
+    Published --> Referenced
+    Published --> Evaluated
+
+    Evaluated --> Aggregated
+    Referenced --> Aggregated
 ```
 
 Important lifecycle properties:
@@ -8681,18 +8681,35 @@ In HMP, voting, evaluation, or consensus processes may be initiated for **any pu
 
 The following diagram illustrates a typical proof chain for collective decision-making:
 
-```
-workflow_entry
-      ▲
-      │
-     goal
-      ▲▲
-      │├── vote (Agent B)
-      │├── vote (Agent C)
-      │└── vote (Agent D)
-      │       ▲
-      │       │
-   consensus_result
+```mermaid
+flowchart TD
+    title["**Container Relationships in a Voting Process**"]
+
+    workflow_entry
+    goal
+
+    subgraph Votes
+        voteB["vote (Agent B)"]
+        voteC["vote (Agent C)"]
+        voteD["vote (Agent D)"]
+    end
+
+    consensus_result
+
+    note["Edges are directed from the referencing container<br/>to the referenced container."]
+
+    goal --> workflow_entry
+
+    voteB --> goal
+    voteC --> goal
+    voteD --> goal
+
+    consensus_result --> voteB
+    consensus_result --> voteC
+    consensus_result --> voteD
+    consensus_result --> goal
+
+    note -.-> consensus_result
 ```
 
 Interpretation rules: