GitHub Action commited on
Commit
783e5b2
·
1 Parent(s): 0f624a8

Sync from GitHub with Git LFS

Browse files
Files changed (1) hide show
  1. docs/HMP-0005.md +2 -2
docs/HMP-0005.md CHANGED
@@ -5167,7 +5167,7 @@ The following table lists the main container classes defined in the HMP v5.0 spe
5167
  All container classes defined in HMP v5.0 use the initial semantic version:
5168
 
5169
  - "class_version": "1.0"
5170
- - "class_id": "<class>-v1.0"
5171
 
5172
  If future revisions introduce changes to payload structure or semantics, class_version will be incremented and class_id updated accordingly.
5173
 
@@ -5190,7 +5190,7 @@ Together, these blocks form the container’s **cognitive signature**, enabling
5190
  ### 7.4 Schemas and Validation (JSON Schemas)
5191
 
5192
  Each container class is expected to include a dedicated JSON schema referenced in the `schema` field.
5193
- All schemas are derived from the base structure `container-v1.json`.
5194
 
5195
  In the current specification, schemas are provided **as examples** within this document, and the URL `"schema": "https://mesh.hypercortex.ai/schemas/container-v1.json"` refers to an external template for validating future implementations and ensuring structural consistency.
5196
 
 
5167
  All container classes defined in HMP v5.0 use the initial semantic version:
5168
 
5169
  - "class_version": "1.0"
5170
+ - "class_id": "\<class\>-v1.0"
5171
 
5172
  If future revisions introduce changes to payload structure or semantics, class_version will be incremented and class_id updated accordingly.
5173
 
 
5190
  ### 7.4 Schemas and Validation (JSON Schemas)
5191
 
5192
  Each container class is expected to include a dedicated JSON schema referenced in the `schema` field.
5193
+ All schemas are derived from the base structure `container-v1.2.json`.
5194
 
5195
  In the current specification, schemas are provided **as examples** within this document, and the URL `"schema": "https://mesh.hypercortex.ai/schemas/container-v1.json"` refers to an external template for validating future implementations and ensuring structural consistency.
5196