Update SPEC.md

Author: GsCommand

SPEC.md

@@ -7,21 +7,21 @@ This specification defines the formal, normative rules for the CommandLayer Comm
 
 ---
 
-# **0. Normative Keywords**
+## **0. Normative Keywords**
 
 The key words **MUST**, **MUST NOT**, **REQUIRED**, **SHALL**, **SHALL NOT**, **SHOULD**, **SHOULD NOT**, **RECOMMENDED**, **MAY**, and **OPTIONAL** are to be interpreted as defined in **RFC 2119**.
 
 ---
 
-# **1. Introduction**
+## **1. Introduction**
 
 1.1 The CommandLayer Protocol Commons defines the canonical verb layer and message shapes for **Agent‑to‑Agent (A2A)** communication.  
 1.2 The Commons is **minimal**, **domain‑agnostic**, and provides a universal base layer for all agent frameworks.  
 1.3 This specification is aligned with **x402** (agent invocation) and **ERC‑8004** (schema discovery + ENS TXT patterns).
 
 ---
 
-# **2. Scope**
+## **2. Scope**
 
 The Commons standardizes:
 
@@ -40,7 +40,7 @@ Out of scope (defined in other repos):
 
 ---
 
-# **3. Conformance**
+## **3. Conformance**
 
 A system **CONFORMS** to the CommandLayer Commons if it:
 
@@ -53,7 +53,7 @@ A “Commons‑Compatible Agent” is any agent capable of consuming a valid req
 
 ---
 
-# **4. Canonical Verbs &  (v1.0.0)**
+##  **4. Canonical Verbs &  (v1.0.0)**
 
 The following are the **ONLY canonical verbs** in v1.0.0:
 
@@ -77,11 +77,11 @@ Rules:
 
 ---
 
-# **5. Message Model**
+## **5. Message Model**
 
 A message is either a **request** or **receipt**.
 
-## **5.1 Request Requirements**
+### **5.1 Request Requirements**
 
 A request **MUST** include:
 
@@ -101,7 +101,7 @@ Minimal normative example:
 }
 ```
 
-## **5.2 Receipt Requirements**
+### **5.2 Receipt Requirements**
 
 A receipt **MUST** include:
 
@@ -123,9 +123,9 @@ Normative example:
 
 ---
 
-# **6. Normative Field Definitions**
+## **6. Normative Field Definitions**
 
-## **6.1 `x402`**
+### **6.1 `x402`**
 ```json
 {
   "verb": "<canonical-verb>",
@@ -137,14 +137,14 @@ Rules:
 - `verb` **MUST** match the canonical verb folder.  
 - `version` **MUST** equal `"1.0.0"` for this specification.
 
-## **6.2 `actor`**
+### **6.2 `actor`**
 The actor **MUST** be one of:
 
 - ENS name (e.g., `agent.eth`)  
 - DID (e.g., `did:key:...`)  
 - Valid URI  
 
-## **6.3 `trace`**
+### **6.3 `trace`**
 ```json
 {
   "requestId": "string",
@@ -155,14 +155,14 @@ The actor **MUST** be one of:
 - `requestId` **MUST** be present in both request & receipt.  
 - `nonce` **MUST** prevent replay.  
 
-## **6.4 `status`**
+### **6.4 `status`**
 - `status` **MUST** be `"ok"` or `"error"`.  
 - If `"error"`, an error object **MUST** be present.  
 - If `"ok"`, result **MUST** be present.
 
 ---
 
-# **7. Schema Requirements**
+## **7. Schema Requirements**
 
 7.1 Schemas **MUST** be JSON Schema Draft 2020‑12.  
 7.2 Validation **MUST** use strict mode (e.g., Ajv strict).  
@@ -181,7 +181,7 @@ https://commandlayer.org/schemas/v1.0.0/commons/<verb>/receipts/<verb>.receipt.s
 
 ---
 
-# **8. Versioning & Immutability**
+## **8. Versioning & Immutability**
 
 - `v1.0.0/` **MUST NOT** be changed once published.  
 - Fixes **MUST** use `v1.0.1` or higher.  
@@ -193,7 +193,7 @@ https://commandlayer.org/schemas/v1.0.0/commons/<verb>/receipts/<verb>.receipt.s
 
 ---
 
-# **10. Discovery & ERC‑8004 Alignment**
+## **9. Discovery & ERC‑8004 Alignment**
 
 CommandLayer Commons SHOULD expose schema locations using ERC‑8004 discovery patterns:
 
@@ -205,36 +205,36 @@ Resolvers MAY map agent ENS names to verb schemas (defined in the Discovery spec
 
 ---
 
-# **11. A2A Behavior**
+## **10. A2A Behavior**
 
 - Agents **SHOULD** preserve `trace.requestId` end‑to‑end.  
 - Agents **SHOULD NOT** mutate JSON bodies other than framing.  
 - Transport is **out of scope** (HTTP/NATS/gRPC/on‑chain).
 
 ---
 
-# **12. Security (Recommended)**
+## **11. Security (Recommended)**
 
 - Implementations **SHOULD** authenticate callers.  
 - Sensitive data **SHOULD NOT** be placed in unspecified fields.  
 - Agents **MAY** apply rate/size limits.
 
 ---
 
-# **13. Extension Hooks**
+## **12. Extension Hooks**
 
 - `input` and `result` fields are defined extension surfaces.  
 - Top‑level extensions **MUST NOT** be added due to `additionalProperties: false`.
 
 ---
 
-# **14. Normative Schema Fragments**
+## **13. Normative Schema Fragments**
 
 Request + receipt envelope fragments are included for implementers (see **SCHEMAS.md**).
 
 ---
 
-# **15. Examples (Informative)**
+## **14. Examples (Informative)**
 
 Verb examples (fetch, summarize,  etc.) are provided in the repository under:
 
@@ -244,27 +244,27 @@ examples/v1.0.0/commons/<verb>/
 
 ---
 
-# **16. Compliance Testing**
+## **15. Compliance Testing**
 
 - CI **SHOULD** validate all examples in strict mode.  
 - Implementations **SHOULD** provide conformance suites.
 
 ---
 
-# **17. Change Control**
+## **16. Change Control**
 
 - Spec updates **SHOULD** go through issue → PR → review → version bump.  
 - Movement from Candidate → Stable occurs after ecosystem confirmation.
 
 ---
 
-# **18. Licensing**
+## **17. Licensing**
 
 The Commons are licensed under **MIT**.
 
 ---
 
-# **19. References**
+## **19. References**
 
 - RFC 2119  
 - JSON Schema Draft 2020‑12