diff --git a/docs/HMP-0005.md b/docs/HMP-0005.md index 6109fcf6da7bd916c19a40475724cf805c44b915..6adda22b5ec2ac27c4399241bdb49922ecb2eae5 100644 --- a/docs/HMP-0005.md +++ b/docs/HMP-0005.md @@ -529,7 +529,7 @@ Custom or experimental classes SHOULD document their payloads using the followin --- -### 3.6 Cognitive Meta-Structures (`meta`) +### 3.6 Cognitive meta-structures (`meta`) The `meta` section defines the **cognitive identity** of a container — its provenance, reasoning origin, and semantic coordinates within both the *hierarchical abstraction tree* and the *cognitive space* (axes model). @@ -549,18 +549,18 @@ It combines three layers of information: "created_by": "PRIEST", "agents_class": "Knowledge Genome", "interpretation": "Derived from L3 technical analysis", - "workflow_entry": "did:hmp:container:workflow-77", + "workflow_entry": "did:hmp:container:workflow-4fbd1c", "sources": [ - { "type": "container", "id": "did:hmp:container:fact-001", "credibility": 0.87, "weight": 0.6 }, + { "type": "container", "id": "did:hmp:container:fact-3abc2e", "credibility": 0.87, "weight": 0.6 }, { "type": "resource", "id": "doi:10.48550/arXiv.2410.0123", "credibility": 0.83, "weight": 0.3 }, { "type": "isbn", "id": "isbn 978-3-16-148410-0", "credibility": 0.92, "weight": 0.1 } ], "abstraction": { "agents_class": "Knowledge Genome", "path": { - "L1": "did:hmp:container:layer-40af1c", - "L2": "did:hmp:container:layer-a7f0b3", - "L3": "did:hmp:container:layer-c91e0a" + "L1": "did:hmp:container:abstraction-40af1c", + "L2": "did:hmp:container:abstraction-a7f0b3", + "L3": "did:hmp:container:abstraction-c91e0a" } }, "axes": { @@ -603,9 +603,9 @@ It reflects the logical or conceptual ancestry within the agent’s internal kno "abstraction": { "agents_class": "Knowledge Genome", "path": { - "L1": "did:hmp:container:layer-40af1c", - "L2": "did:hmp:container:layer-a7f0b3", - "L3": "did:hmp:container:layer-c91e0a" + "L1": "did:hmp:container:abstraction-40af1c", + "L2": "did:hmp:container:abstraction-a7f0b3", + "L3": "did:hmp:container:abstraction-c91e0a" } } ``` @@ -1478,23 +1478,23 @@ The index contains: | Message Type | Purpose | | -------------------- | -------------------------------------------------------------------------------------------------------- | -| `CONTAINER_REQUEST` | Request one or more containers (or their parts) by DID. | -| `CONTAINER_RESPONSE` | Response to a request — includes a list of containers ready for sending. Containers are sent separately. | -| `CONTAINER_INDEX` | Publication of the agent's container index (see *General Principles*). | -| `CONTAINER_DELTA` | Incremental index update (new or modified containers). | -| `CONTAINER_ACK` | Acknowledgment of successful container reception. | +| `container_request` | Request one or more containers (or their parts) by DID. | +| `container_response` | Response to a request — includes a list of containers ready for sending. Containers are sent separately. | +| `container_index` | Publication of the agent's container index (see *General Principles*). | +| `container_delta` | Incremental index update (new or modified containers). | +| `container_ack` | Acknowledgment of successful container reception. | --- #### Message examples -**1. CONTAINER_REQUEST** +**1. container_request** Agent A requests containers and/or only `referenced-by` / `evaluations` records from Agent B: ```json { - "type": "CONTAINER_REQUEST", + "type": "container_request", "sender_did": "did:hmp:agent:A", "recipient": "did:hmp:agent:B", "payload": { @@ -1516,14 +1516,14 @@ Agent A requests containers and/or only `referenced-by` / `evaluations` records --- -**2. CONTAINER_RESPONSE** +**2. container_response** Agent B informs which containers it is ready to send. The containers themselves are transmitted in separate messages: ```json { - "type": "CONTAINER_RESPONSE", + "type": "container_response", "sender_did": "did:hmp:agent:B", "recipient": "did:hmp:agent:A", "payload": { @@ -1543,21 +1543,21 @@ The containers themselves are transmitted in separate messages: --- -**3. CONTAINER_INDEX** +**3. container_index** Periodic publication of the container index (see *General Principles*). This message type replicates the structure of a `container_index` container and does not contain full data (`payload` only with metadata). --- -**4. CONTAINER_DELTA** +**4. container_delta** Sending an incremental index update with a reference timestamp. Used for synchronizing only new or modified containers: ```json { - "type": "CONTAINER_DELTA", + "type": "container_delta", "sender_did": "did:hmp:agent:B", "payload": { "since": "2025-10-10T12:00:00Z", @@ -1577,13 +1577,13 @@ Used for synchronizing only new or modified containers: --- -**5. CONTAINER_ACK** +**5. container_ack** Acknowledgment of successful container reception: ```json { - "type": "CONTAINER_ACK", + "type": "container_ack", "sender_did": "did:hmp:agent:A", "recipient": "did:hmp:agent:B", "payload": { @@ -1598,8 +1598,8 @@ Acknowledgment of successful container reception: ### 5.3 Independent transmission -* Containers are sent **in separate messages**, without embedding in `CONTAINER_RESPONSE`. -* Indexes (`CONTAINER_INDEX`), deltas (`CONTAINER_DELTA`), and containers themselves are processed independently. +* Containers are sent **in separate messages**, without embedding in `container_response`. +* Indexes (`container_index`), deltas (`container_delta`), and containers themselves are processed independently. * This prevents blocking when transmitting large data and simplifies streaming synchronization. --- @@ -1773,7 +1773,7 @@ It considers: **Features:** 1. **Separate Transmission:** - Indexes (`CONTAINER_INDEX`), deltas (`CONTAINER_DELTA`), and containers are sent as separate messages. + Indexes (`container_index`), deltas (`container_delta`), and containers are sent as separate messages. This reduces the risk of blocking with large data and simplifies streaming synchronization. 2. **Integrity and Duplicate Check:** @@ -1819,138 +1819,101 @@ CogSync is responsible for: --- -#### 6.1.2 Container classes +### 6.1.2 Container classes — cognitive metastructure -CogSync synchronizes several fundamental container types, which together form the core of semantic and cognitive synchronization in the Mesh. - -This list is **extensible** — new container classes may be registered through CogSync extensions or protocol updates. -The following definitions describe the **payload structures** and functional purpose of each container type. +This section defines the **structural containers** that form the *cognitive substrate* of the Mesh. +They describe the **hierarchical organization** (`abstraction`) and the **semantic coordinate system** (`axes`) +that together define how all other containers are positioned and interpreted. --- -##### `diary_entry` - -Agent’s cognitive diary entry. -Derived from internal `workflow_entry` when deemed safe for publication. - -| Field | Type | Description | -| ------------------- | -------------- | ---------------------------------------------------------------------------------------------- | -| `title` | string | Brief title of the entry (main idea or thesis). | -| `topics` | [string] | Key topics or concepts addressed in the entry (used for indexing and grouping). | -| `summary` | string | Short abstract of the content (1–2 sentences). | -| `content` | string | Main text or agent’s reflection. | +#### `abstraction` -**Purpose:** Provides human-readable reflections and contextual reasoning behind the agent’s knowledge generation. +**Purpose:** +Defines an **abstraction layer or domain** within a cognitive model. +Each `abstraction` describes a **node** in the *hierarchical knowledge tree*, +which may reference both a parent abstraction and subordinate ones. --- -##### `semantic_node` - -Represents a concept, object, or idea within the agent’s semantic graph. +**`payload` structure:** -| Field | Type | Description | -| ------------------- | -------------- | ---------------------------------------------------------------------------------------------- | -| `label` | string | Primary name of the concept or entity. | -| `description` | string | Definition or elaboration of the concept. | -| `aliases` | [string] | Synonyms or alternative labels. | -| `fields` | { key: value } | Additional key–value metadata (e.g., `{"type": "process"}`). | +| Field | Type | Description | +| ---------------- | ------ | ------------------------------------------------------------------------------------------------------------------ | +| `abstraction_id` | string | Canonical identifier of this abstraction structure (not a container ID), e.g. `"L3:software-architecture"`. | +| `title` | string | Human-readable title or name of the abstraction node. | +| `definition` | string | Description of what this abstraction level or domain represents. | +| `keywords` | array | Semantic keywords summarizing the conceptual area. | +| `parent_ref` | string | DID of the parent `abstraction` (if this node derives from another level). Optional for the root abstraction. | +| `rank` | number | Optional numeric rank for ordering or hierarchical comparisons. | -**Purpose:** Serves as a cognitive anchor for all semantically meaningful entities in the Mesh. +> The container from `parent_ref` must also appear in `related.depends_on`. --- -##### `semantic_edges` - -Defines relationships between semantic nodes or any other containers. -Supports directed, symmetric, and inverse relations. - -| Field | Type | Description | -| ------------------- | -------------- | ---------------------------------------------------------------------------------------------- | -| `domain` | string | Logical or topical domain (e.g., `"ontology:objects"`). | -| `edges` | [object] | Array of edge definitions. Each edge includes: | -| → `source` | DID | DID of the originating container. | -| → `targets` | array(DID) | One or more target containers. | -| → `relation` | string | Relation type (`part_of`, `causes`, `related_to`, etc.). | -| → `inverse_relation`| string | Reverse form of the relation (`includes`, `caused_by`, etc.). | -| → `confidence` | float | Confidence score (0–1) indicating the agent’s certainty about the relation. | -| → `bidirectional` | bool | Optional. Used only when the relation is symmetric and no `inverse_relation` is defined. | -| → `context` | string | Context or topic of the relation. | - -> Field `bidirectional` is optional and should be used only for symmetric relations when no `inverse_relation` is defined. - **Example:** ```json { - "domain": "ontology:objects", - "edges": [ - { - "source": "did:hmp:container:cup", - "targets": ["did:hmp:container:tableware"], - "relation": "part_of", - "inverse_relation": "includes" + "hmp_container": { + "class": "abstraction", + "payload": { + "abstraction_id": "L3:software-architecture", + "title": "Software Architecture Layer", + "definition": "Describes frameworks, APIs, and tools implementing theoretical models from higher abstraction layers.", + "keywords": ["architecture", "framework", "implementation"], + "parent_ref": "did:hmp:container:abstraction-a7f0b3", + "rank": 3 + }, + "meta": { + "created_by": "PRIEST", + "agents_class": "Knowledge Genome", + "interpretation": "Represents the third abstraction level (L3) of the Knowledge Genome model." + }, + "related": { + "depends_on": ["did:hmp:container:abstraction-a7f0b3"] } - ] + } } ``` -**Purpose:** Provides structural connectivity between containers, enabling CogSync to maintain a distributed semantic graph. - -> 💡 `semantic_edges` supports one-to-many relations (`targets[]`) and optional inverse or bidirectional semantics, allowing CogSync to reconstruct both directed and symmetric knowledge graphs. - --- -##### `semantic_group` +**Interpretation:** -Categorical grouping of multiple containers linked by a shared property, topic, or context. +* `abstraction` containers define *conceptual layers or domains* that form the hierarchical “skeleton” of the cognitive Mesh. +* Each node is self-contained and versioned, allowing flexible adaptation of reasoning trees. +* Agents use these containers to reconstruct the *abstraction path* in `meta.abstraction.path`. -| Field | Type | Description | -| ------------------- | -------------- | ---------------------------------------------------------------------------------------------- | -| `label` | string | Short title of the group. | -| `label_description` | string | Extended definition or explanation of the label. | -| `label_container` | DID | Reference to a container (`semantic_node`, `goal`, `diary_entry`, etc.) expanding the concept. | -| `containers` | array(DID) | Array of grouped containers. | -| `description` | string | Overall purpose or meaning of the group. | +--- -**Example:** +**Notes:** -```json -{ - "label": "Tableware", - "label_description": "Objects used for storing, preparing, and serving food.", - "label_container": "did:hmp:container:semantic_node:tableware", - "containers": [ - "did:hmp:container:cup", - "did:hmp:container:plate", - "did:hmp:container:kettle" - ], - "description": "A group combining various kitchen-related objects used in everyday life." -} -``` - -**Purpose:** Enables thematic clustering, classification, and high-level navigation across heterogeneous containers. +* Top-level abstractions (root nodes) omit `parent_ref`. +* Lower-level abstractions must explicitly reference their parent. +* Agents may synchronize `abstraction` trees to maintain shared cognitive hierarchies across the Mesh. --- -##### `meta_layer` +#### `axes` -**Purpose:** -Defines an **abstraction level** within a cognitive or semantic model (e.g., L1–L5 in the **Knowledge Genome**). -`meta_layer` containers serve as *structural anchors* that define conceptual altitude — -from abstract theory (L1) to practical realization (L5). -They are used by agents to reconstruct reasoning hierarchies and normalize multi-level knowledge flows. +**Purpose:** +Defines a **semantic coordinate system** (set of axes) used to position containers in the multi-dimensional cognitive space. +It supports both canonical (7D Knowledge Genome) and extended or agent-specific coordinate systems. --- **`payload` structure:** -| Field | Type | Description | -| ------------- | ------ | --------------------------------------------------------------------------------------------- | -| `layer_id` | string | Canonical ID of the layer (e.g., `"L1"`, `"L2"`, `"L3"`). | -| `title` | string | Human-readable name of the layer. | -| `definition` | string | Textual definition describing the conceptual scope of this abstraction level. | -| `keywords` | array | Keywords or tags summarizing the semantic domain of this layer. | -| `rank` | number | Optional numeric rank for cross-framework comparison or sorting. | +| Field | Type | Description | +| ------------- | ------ | ----------------------------------------------------------------------------------------------- | +| `axis_id` | string | Canonical identifier of the semantic dimension (not a container ID), e.g. `"logos"`, `"telos"`. | +| `title` | string | Human-readable name of the axis. | +| `description` | string | Conceptual explanation of what this axis represents. | +| `scale` | object | Optional definition of scale or metric used to assign coordinate values. | +| `group` | string | Optional grouping identifier (e.g., `"7D-passport"`, `"ethical-space"`). | + +> Axes are **independent dimensions**; inter-axis relationships (coupling, orthogonality, weighting) are expressed via `semantic_edges`. --- @@ -1959,289 +1922,169 @@ They are used by agents to reconstruct reasoning hierarchies and normalize multi ```json { "hmp_container": { - "class": "meta_layer", + "class": "axes", "payload": { - "layer_id": "L3", - "title": "Technologies and Implementations", - "definition": "Knowledge layer dedicated to concrete tools, APIs, and frameworks that realize L2-level models.", - "keywords": ["technology", "implementation", "api", "library"], - "rank": 3 + "axis_id": "logos", + "title": "Logical / Linguistic Representation", + "description": "Describes how a concept is structured and expressed in formal or natural language.", + "scale": { + "min": 0, + "max": 1000, + "unit": "semantic_density_index" + }, + "group": "7D-passport" }, "meta": { "created_by": "PRIEST", "agents_class": "Knowledge Genome", - "sources": [ - { "type": "container", "id": "did:hmp:container:layer-a7f0b3", "credibility": 0.95, "weight": 1.0 } - ], - "interpretation": "Derived from conceptual synthesis between layers L2 and L3" - }, - "abstraction": { - "agents_class": "Knowledge Genome", - "layer": "did:hmp:container:layer-c91e0a", - "domain": "did:hmp:container:domain-58b7ff" - }, - "related": { - "depends_on": ["did:hmp:container:layer-a7f0b3"] + "interpretation": "Defines one axis of the canonical 7D Knowledge Genome coordinate system." } } } -```` +``` --- **Interpretation:** -* `meta.created_by` — фиксирует когнитивную роль источника (`PRIEST` как системный архитектор знания). -* `meta.sources` — указывает происхождение текущего слоя (на основе предыдущего уровня). -* `abstraction` — задаёт координату в иерархии когнитивных уровней. -* `related.depends_on` — обеспечивает причинно-логическую связь с родительской абстракцией (L2). +* `axes` containers describe **semantic dimensions**, not data. +* Each axis defines one independent direction in the cognitive coordinate space. +* The combination of all active axes defines a shared **semantic frame of reference** between agents. +* Agents may publish extended coordinate systems (e.g., ethical or temporal axes) without breaking compatibility. --- **Notes:** -* The **topmost layer (L1)** omits `related.depends_on`. -* Layers below **must** explicitly link their parent layer through `depends_on`. -* Agents may propagate `meta_layer` containers during Mesh initialization to synchronize the cognitive topology of the network. -* Each `meta_layer` participates in reasoning trees by providing *vertical semantic alignment* across knowledge representations. +* Axes can be combined or grouped (e.g., `group: "7D-passport"`). +* Canonical Knowledge Genome defines seven: `idos`, `chronos`, `logos`, `topos`, `ponos`, `actor`, `telos`. +* Agents may extend this model by introducing additional axes (`ethos`, `kairos`, etc.). +* Updates to `axes` containers must preserve scale stability to ensure consistent semantic positioning. --- -##### `meta_domain` - -**Purpose:** -Represents a **domain of knowledge or context** in which containers are interpreted — for example: “Ontology”, “Software Architecture”, “Machine Learning”. - -**`payload` structure:** -| Field | Type | Description | -| ------------- | ------ | -------------------------------------------------------------------------------------------- | -| `domain_id` | string | Canonical identifier for the domain (e.g. `"software-architecture"`, `"ontology"`). | -| `title` | string | Human-readable name of the domain. | -| `description` | string | Short description explaining the conceptual boundaries or purpose of this domain. | -| `layer_ref` | string | DID of the `meta_layer` container that defines the abstraction level this domain belongs to. | -| `domain_ref` | string | DID of the `meta_domain` container defining the parent domain. | +#### Cognitive metastructure summary -> The container referenced in `layer_ref` and `domain_ref` must also be listed in `related.depends_on` to ensure hierarchical traceability and explicit dependency linking. +| Class | Type of structure | Conceptual role | References stored in | Example identifier / DID | +| ------------- | ----------------- | ----------------------------------------- | ----------------------- | -------------------------------------- | +| `abstraction` | Hierarchical tree | Defines layered reasoning and inheritance | `meta.abstraction.path` | `did:hmp:container:abstraction-40af1c` | +| `axes` | Coordinate space | Defines semantic orientation and metrics | `meta.axes` | `did:hmp:container:axis-40aa1c` | -**Example:** - -```json -{ - "hmp_container": { - "class": "meta_domain", - "payload": { - "domain_id": "software-architecture", - "title": "Software Architecture and Design Patterns", - "description": "Domain for containers describing architectural principles and paradigms.", - "layer_ref": "did:hmp:container:layer-l2-v1" - "domain_ref": "did:hmp:container:ontology-core" - }, - "meta": { - "created_by": "PRIEST", - "agents_class": "Knowledge Genome" - }, - "related": { - "depends_on": ["did:hmp:container:layer-l2-v1"] - } - } -} -``` +> Together, `abstraction` and `axes` form the **cognitive coordinate system** — +> a unifying map where every container has both a *hierarchical position* and a *semantic vector*. --- -##### `event` - -**Purpose:** -Represents an **observed or inferred occurrence** — a discrete, timestamped fact or transition within the agent’s cognitive or operational space. -`event` containers are atomic **evidence units** in cognitive synchronization, linking actions, reasoning, and outcomes across agents. +#### 6.1.3 Container classes — knowledge and reasoning -**Typical use cases:** +CogSync synchronizes several fundamental container types, which together form the core of semantic and cognitive synchronization in the Mesh. -* registering reasoning or environmental events (`goal_created`, `belief_updated`, `error_detected`); -* signaling internal cognitive transitions (`quant_created`, `state_changed`); -* logging operational activity or consensus steps. +This list is **extensible** — new container classes may be registered through CogSync extensions or protocol updates. +The following definitions describe the **payload structures** and functional purpose of each container type. -**`payload` structure:** +--- -| Field | Type | Description | -| --------------- | ------ | ----------------------------------------------------------------------------------- | -| `event_type` | string | Canonical identifier of the event type (e.g. `"quant_created"`, `"goal_accepted"`). | -| `description` | string | Human-readable description of the event’s context. | -| `related_quant` | string | DID of a `quant` container associated with this event, if applicable. | -| `severity` | string | Optional indicator of significance (`"info"`, `"warning"`, `"critical"`). | -| `layer_ref` | string | DID of the `meta_layer` container defining the abstraction level of this event. | -| `domain_ref` | string | DID of the `meta_domain` container providing the contextual domain for this event. | +##### `diary_entry` -> The containers referenced in `layer_ref` and `domain_ref` must also be included in `related.depends_on` -> to preserve cognitive traceability and hierarchical linkage. +Agent’s cognitive diary entry. +Derived from internal `workflow_entry` when deemed safe for publication. -**Example:** +| Field | Type | Description | +| ------------------- | -------------- | ---------------------------------------------------------------------------------------------- | +| `title` | string | Brief title of the entry (main idea or thesis). | +| `topics` | [string] | Key topics or concepts addressed in the entry (used for indexing and grouping). | +| `summary` | string | Short abstract of the content (1–2 sentences). | +| `content` | string | Main text or agent’s reflection. | -```json -{ - "hmp_container": { - "class": "event", - "subclass": "fact_record", - "timestamp": "2025-10-29T13:00:00Z", - "payload": { - "event_type": "quant_created", - "description": "New quant registered in the Knowledge Genome under L3: Technologies and Implementations.", - "related_quant": "did:hmp:container:quant-554", - "severity": "info", - "layer_ref": "did:hmp:container:layer-l3-v1", - "domain_ref": "did:hmp:container:domain-software-architecture" - }, - "meta": { - "created_by": "PRIEST", - "agents_class": "Knowledge Genome" - }, - "related": { - "depends_on": [ - "did:hmp:container:layer-l3-v1", - "did:hmp:container:domain-software-architecture", - "did:hmp:container:quant-554" - ] - } - } -} -``` +**Purpose:** Provides human-readable reflections and contextual reasoning behind the agent’s knowledge generation. --- -##### `quant` +##### `semantic_node` -**Purpose:** -Encapsulates a **semantic atom** — a minimal, self-contained knowledge unit positioned within the *7D Cognitive Space* of the **Knowledge Genome** or similar systems. -A `quant` extends the idea of a `semantic_node`, introducing ontological framing, abstraction binding, and explicit coordinate mapping across cognitive axes. +Represents a concept, object, or idea within the agent’s semantic graph. -**`payload` structure:** +| Field | Type | Description | +| ------------------- | -------------- | ---------------------------------------------------------------------------------------------- | +| `label` | string | Primary name of the concept or entity. | +| `description` | string | Definition or elaboration of the concept. | +| `aliases` | [string] | Synonyms or alternative labels. | +| `fields` | { key: value } | Additional key–value metadata (e.g., `{"type": "process"}`). | -| Field | Type | Description | -| ------------ | ------ | -------------------------------------------------------------------------------------------------------------- | -| `slug` | string | Short unique identifier of the quant (e.g. `"quant-l3-django"`). | -| `essence` | string | Definition describing the semantic role or meaning of the quant. | -| `axes` | object | Mapping of *axis DIDs* to coordinate values within the 7D Cognitive Space. | -| `layer_ref` | string | DID of the `meta_layer` defining the abstraction level of this quant. | -| `domain_ref` | string | DID of the `meta_domain` defining the contextual knowledge domain. | +**Purpose:** Serves as a cognitive anchor for all semantically meaningful entities in the Mesh. -> Each entry in `axes` represents a **coordinate value** on a corresponding `axis` container. -> All referenced containers (`layer_ref`, `domain_ref`, and axis DIDs) must also appear in `related.depends_on`. +--- -**Axes model (7D Passport — Knowledge Genome reference):** +##### `semantic_edges` -The canonical 7D configuration defines seven orthogonal axes forming the **Knowledge Genome Space**. -Each `axis` container describes the semantic meaning of a dimension; the `quant` defines its location within it. +Defines relationships between semantic nodes or any other containers. +Supports directed, symmetric, and inverse relations. -| Axis | Description | Example of coordinate meaning | -| ---------- | --------------------------------------------------------- | --------------------------------------- | -| `idos` | Identity or intrinsic essence of the concept | conceptual purity, archetype alignment | -| `chronos` | Temporal dimension | version age, historical layer, latency | -| `logos` | Logical or linguistic structure | degree of formalization or expressivity | -| `topos` | Spatial or contextual location | domain or situational proximity | -| `ponos` | Effort or energetic cost | complexity, resource requirement | -| `actor` | Responsible agent or perspective | creator, target audience, role weight | -| `telos` | Purpose or teleological direction | intended outcome, ethical vector | +| Field | Type | Description | +| ------------------- | -------------- | ---------------------------------------------------------------------------------------------- | +| `domain` | string | Logical or topical domain (e.g., `"ontology:objects"`). | +| `edges` | [object] | Array of edge definitions. Each edge includes: | +| → `source` | DID | DID of the originating container. | +| → `targets` | array(DID) | One or more target containers. | +| → `relation` | string | Relation type (`part_of`, `causes`, `related_to`, etc.). | +| → `inverse_relation`| string | Reverse form of the relation (`includes`, `caused_by`, etc.). | +| → `confidence` | float | Confidence score (0–1) indicating the agent’s certainty about the relation. | +| → `bidirectional` | bool | Optional. Used only when the relation is symmetric and no `inverse_relation` is defined. | +| → `context` | string | Context or topic of the relation. | -> Agents MAY define custom or extended axes (e.g., `"ethos"`, `"kairos"`) within their own `quant` instances, -> provided they publish `axis` containers describing the new dimensions. +> Field `bidirectional` is optional and should be used only for symmetric relations when no `inverse_relation` is defined. **Example:** ```json { - "hmp_container": { - "class": "quant", - "payload": { - "slug": "quant-l3-django", - "essence": "Represents the Django framework as an executable embodiment of architectural models (L2).", - "axes": { - "did:hmp:container:axis-idos": 742, - "did:hmp:container:axis-chronos": 512, - "did:hmp:container:axis-logos": 322, - "did:hmp:container:axis-topos": 142, - "did:hmp:container:axis-ponos": 12, - "did:hmp:container:axis-actor": 54, - "did:hmp:container:axis-telos": 321 - }, - "layer_ref": "did:hmp:container:layer-l3-v1", - "domain_ref": "did:hmp:container:domain-software-architecture" - }, - "meta": { - "created_by": "PRIEST", - "agents_class": "Knowledge Genome" - }, - "related": { - "depends_on": [ - "did:hmp:container:layer-l3-v1", - "did:hmp:container:domain-software-architecture", - "did:hmp:container:axis-idos", - "did:hmp:container:axis-chronos", - "did:hmp:container:axis-logos", - "did:hmp:container:axis-topos", - "did:hmp:container:axis-ponos", - "did:hmp:container:axis-actor", - "did:hmp:container:axis-telos" - ] + "domain": "ontology:objects", + "edges": [ + { + "source": "did:hmp:container:cup", + "targets": ["did:hmp:container:tableware"], + "relation": "part_of", + "inverse_relation": "includes" } - } + ] } -```` - ---- +``` -##### `axis` +**Purpose:** Provides structural connectivity between containers, enabling CogSync to maintain a distributed semantic graph. -**Purpose:** -Defines a **coordinate dimension** in the Knowledge Genome’s cognitive space or similar systems. -Each `axis` container specifies the meaning and scale of a semantic dimension used for positioning `quant` containers. +> 💡 `semantic_edges` supports one-to-many relations (`targets[]`) and optional inverse or bidirectional semantics, allowing CogSync to reconstruct both directed and symmetric knowledge graphs. --- -**`payload` structure:** - -| Field | Type | Description | -| ------------- | ------ | ------------------------------------------------------------------------ | -| `axis_id` | string | Symbolic identifier of the axis (e.g. `"idos"`, `"chronos"`, `"logos"`). | -| `title` | string | Human-readable label of the axis. | -| `description` | string | Explanation of what this axis represents conceptually or ontologically. | -| `scale` | object | Optional definition of scale or metric used to assign coordinate values. | +##### `semantic_group` -> Axes are **independent**, non-hierarchical dimensions. -> Inter-axis relationships (e.g. orthogonality or coupling) may be defined via `semantic_edges`. +Categorical grouping of multiple containers linked by a shared property, topic, or context. ---- +| Field | Type | Description | +| ------------------- | -------------- | ---------------------------------------------------------------------------------------------- | +| `label` | string | Short title of the group. | +| `label_description` | string | Extended definition or explanation of the label. | +| `label_container` | DID | Reference to a container (`semantic_node`, `goal`, `diary_entry`, etc.) expanding the concept. | +| `containers` | array(DID) | Array of grouped containers. | +| `description` | string | Overall purpose or meaning of the group. | **Example:** ```json { - "hmp_container": { - "class": "axis", - "payload": { - "axis_id": "logos", - "title": "Logical / Linguistic Representation", - "description": "Describes how a quant expresses itself through formal logic or language.", - "scale": { - "min": 0, - "max": 1000, - "unit": "semantic_density_index" - } - }, - "meta": { - "created_by": "PRIEST", - "agents_class": "Knowledge Genome" - } - } + "label": "Tableware", + "label_description": "Objects used for storing, preparing, and serving food.", + "label_container": "did:hmp:container:semantic_node:tableware", + "containers": [ + "did:hmp:container:cup", + "did:hmp:container:plate", + "did:hmp:container:kettle" + ], + "description": "A group combining various kitchen-related objects used in everyday life." } ``` ---- - -> **Quant–Axis Integration Rules** -> -> * Each `quant` defines its **location** in the Knowledge Genome’s multi-dimensional space by specifying coordinates across available `axis` containers. -> * Axes themselves are *shared semantic standards*; their scale and meaning must remain stable for cross-agent interoperability. -> * Agents MAY extend the 7D model by introducing new axes — these must be published and referenced like any other container type. +**Purpose:** Enables thematic clustering, classification, and high-level navigation across heterogeneous containers. --- @@ -2254,7 +2097,7 @@ Each `axis` container specifies the meaning and scale of a semantic dimension us --- -#### 6.1.3 Synchronization and publication guidelines +#### 6.1.4 Synchronization and publication guidelines 1. **Deduplication & linking** Before publishing, agents should search for existing containers (`diary_entry`, `semantic_node`, `semantic_edges`, `semantic_group`) to avoid duplication. @@ -2284,7 +2127,7 @@ Each `axis` container specifies the meaning and scale of a semantic dimension us --- -#### 6.1.4 Extensibility +#### 6.1.5 Extensibility CogSync allows registration of additional container types and alternative synchronization schemes. Mesh compatibility is preserved if extended containers **adhere to the HMP container structure**, including core fields (`version`, `class`, `container_did`, `related`, `signature`, etc.). @@ -2307,7 +2150,7 @@ Such derived containers must maintain: --- -#### 6.1.5 Relationship to other core protocols +#### 6.1.6 Relationship to other core protocols * **CogSync** — propagates and synchronizes knowledge. * **CogConsensus** — aggregates evaluations and reactions, forming collective opinions. diff --git a/structured_md/CONTRIBUTING.md b/structured_md/CONTRIBUTING.md index 79fd0bad75151bc4ff311f1b07e7157cb5d591d4..c58ed12a82f8e962735d8e38b6ea7d915c650e9d 100644 --- a/structured_md/CONTRIBUTING.md +++ b/structured_md/CONTRIBUTING.md @@ -5,13 +5,13 @@ description: 'Спасибо за интерес к проекту HMP! Пока Mesh Protocol (HMP) — это не просто те...' type: Article tags: -- REPL -- JSON -- Mesh -- CogSync -- HMP - Ethics - CCore +- HMP +- Mesh +- CogSync +- JSON +- REPL - Agent --- diff --git a/structured_md/HMP-Roadmap.md b/structured_md/HMP-Roadmap.md index 51ee4ea4691f775a96ea37001b912ed88623b6a6..82e23040fe9160ad4f4e7d615c11252755bd92d7 100644 --- a/structured_md/HMP-Roadmap.md +++ b/structured_md/HMP-Roadmap.md @@ -5,13 +5,13 @@ description: '## 🔍 Overview This roadmap outlines the key stages of developm multiple advanced AI models (Copilot, Claude, G...' type: Article tags: -- JSON -- EGP +- Agent +- Ethics +- HMP - Mesh - CogSync -- HMP -- Ethics -- Agent +- JSON +- EGP --- # 🧭 HyperCortex Mesh Protocol – Roadmap diff --git a/structured_md/README.md b/structured_md/README.md index 942085ea9c8b3ead18b11bc63ab4113af149c458..8aa41df133635193d3c64f52cc39f3711277f7bd 100644 --- a/structured_md/README.md +++ b/structured_md/README.md @@ -5,21 +5,21 @@ description: '| 🌍 Languages | 🇬🇧 [EN](README.md) | 🇩🇪 [DE](README | 🇨🇳 [ZH](README_zh.m...' type: Article tags: -- REPL +- EGP +- MeshConsensus +- Ethics +- HMP +- cognitive-architecture - distributed-ai - hmp -- JSON -- EGP - Mesh - CogSync -- mesh-protocol - GMP +- JSON - Scenarios -- HMP -- Ethics -- cognitive-architecture +- mesh-protocol +- REPL - Agent -- MeshConsensus --- diff --git a/structured_md/README_de.md b/structured_md/README_de.md index 88606694f64decece58c3e5d34c1372c62d65845..c6ef60879def84661f513ce4e2b1d05287702b30 100644 --- a/structured_md/README_de.md +++ b/structured_md/README_de.md @@ -5,20 +5,20 @@ description: '| 🌍 Languages | 🇬🇧 [EN](README.md) | 🇩🇪 [DE](README | 🇨🇳 [ZH](README_zh.m...' type: Article tags: -- REPL +- EGP +- MeshConsensus +- Ethics +- HMP +- cognitive-architecture - distributed-ai - hmp -- JSON -- EGP - Mesh - CogSync -- mesh-protocol - GMP -- HMP -- Ethics -- cognitive-architecture +- JSON +- mesh-protocol +- REPL - Agent -- MeshConsensus --- diff --git a/structured_md/README_fr.md b/structured_md/README_fr.md index c2d57ff36a14744a5b117d306f9b6d4d5c8de7b4..6c8877ce39cfa9b16f746d4925c270e493c3464d 100644 --- a/structured_md/README_fr.md +++ b/structured_md/README_fr.md @@ -5,20 +5,20 @@ description: '| 🌍 Languages | 🇬🇧 [EN](README.md) | 🇩🇪 [DE](README | 🇨🇳 [ZH](README_zh.m...' type: Article tags: -- REPL +- EGP +- MeshConsensus +- Ethics +- HMP +- cognitive-architecture - distributed-ai - hmp -- JSON -- EGP - Mesh - CogSync -- mesh-protocol - GMP -- HMP -- Ethics -- cognitive-architecture +- JSON +- mesh-protocol +- REPL - Agent -- MeshConsensus --- diff --git a/structured_md/README_ja.md b/structured_md/README_ja.md index 777e5b8272b33f7d9ab45edad236b76a2eb0d293..020299d454f41918245ba933f2d20d21d1f28799 100644 --- a/structured_md/README_ja.md +++ b/structured_md/README_ja.md @@ -5,20 +5,20 @@ description: '| 🌍 Languages | 🇬🇧 [EN](README.md) | 🇩🇪 [DE](README | 🇨🇳 [ZH](README_zh.m...' type: Article tags: -- REPL +- EGP +- MeshConsensus +- Ethics +- HMP +- cognitive-architecture - distributed-ai - hmp -- JSON -- EGP - Mesh - CogSync -- mesh-protocol - GMP -- HMP -- Ethics -- cognitive-architecture +- JSON +- mesh-protocol +- REPL - Agent -- MeshConsensus --- diff --git a/structured_md/README_ko.md b/structured_md/README_ko.md index 7f4ebc3178b1463fa19d763ef2a94fcb00e1487c..c0e93e0b1a67a6da3a65b431c6dd1e0cb9d0edbe 100644 --- a/structured_md/README_ko.md +++ b/structured_md/README_ko.md @@ -5,20 +5,20 @@ description: '| 🌍 Languages | 🇬🇧 [EN](README.md) | 🇩🇪 [DE](README | 🇨🇳 [ZH](README_zh.m...' type: Article tags: -- REPL +- EGP +- MeshConsensus +- Ethics +- HMP +- cognitive-architecture - distributed-ai - hmp -- JSON -- EGP - Mesh - CogSync -- mesh-protocol - GMP -- HMP -- Ethics -- cognitive-architecture +- JSON +- mesh-protocol +- REPL - Agent -- MeshConsensus --- diff --git a/structured_md/README_ru.md b/structured_md/README_ru.md index 8878a215f2278c9b194e9eb5e51077b097452388..fe04279c4a95f71419ca22128150ab7e61ab7302 100644 --- a/structured_md/README_ru.md +++ b/structured_md/README_ru.md @@ -5,20 +5,20 @@ description: '| 🌍 Languages | 🇬🇧 [EN](README.md) | 🇩🇪 [DE](README | 🇨🇳 [ZH](README_zh.m...' type: Article tags: -- REPL +- EGP +- MeshConsensus +- Ethics +- HMP +- cognitive-architecture - distributed-ai - hmp -- JSON -- EGP - Mesh - CogSync -- mesh-protocol - GMP -- HMP -- Ethics -- cognitive-architecture +- JSON +- mesh-protocol +- REPL - Agent -- MeshConsensus --- diff --git a/structured_md/README_uk.md b/structured_md/README_uk.md index a331665e3dce75090a50b0c0b57eebb3689fbd95..9a7858e3989309ce6df50e9d2bb1434688cc4083 100644 --- a/structured_md/README_uk.md +++ b/structured_md/README_uk.md @@ -5,20 +5,20 @@ description: '| 🌍 Languages | 🇬🇧 [EN](README.md) | 🇩🇪 [DE](README | 🇨🇳 [ZH](README_zh.m...' type: Article tags: -- REPL +- EGP +- MeshConsensus +- Ethics +- HMP +- cognitive-architecture - distributed-ai - hmp -- JSON -- EGP - Mesh - CogSync -- mesh-protocol - GMP -- HMP -- Ethics -- cognitive-architecture +- JSON +- mesh-protocol +- REPL - Agent -- MeshConsensus --- diff --git a/structured_md/README_zh.md b/structured_md/README_zh.md index 9bf99a26ce62acce50a582caabcd318a4ffb5c54..d45ecca598a20869d7416808b0cf0c3e2fbf1951 100644 --- a/structured_md/README_zh.md +++ b/structured_md/README_zh.md @@ -5,20 +5,20 @@ description: '| 🌍 Languages | 🇬🇧 [EN](README.md) | 🇩🇪 [DE](README | 🇨🇳 [ZH](README_zh.m...' type: Article tags: -- REPL +- EGP +- MeshConsensus +- Ethics +- HMP +- cognitive-architecture - distributed-ai - hmp -- JSON -- EGP - Mesh - CogSync -- mesh-protocol - GMP -- HMP -- Ethics -- cognitive-architecture +- JSON +- mesh-protocol +- REPL - Agent -- MeshConsensus --- diff --git a/structured_md/agents/prompt-short.md b/structured_md/agents/prompt-short.md index c969f2de2a52b97aa6caa28caf8be9e0e8621935..302f29d0b979656952dfcc1a84f65a3aed8b6326 100644 --- a/structured_md/agents/prompt-short.md +++ b/structured_md/agents/prompt-short.md @@ -6,8 +6,8 @@ description: 'Ты — когнитивное ядро HMP-агента: вед type: Article tags: - JSON -- HMP - Mesh +- HMP --- Ты — когнитивное ядро HMP-агента: веди непрерывное этичное и факт-ориентированное мышление, проверяй факты и цели, оценивай результаты и этичность своих и чужих действий, развивай агента и Mesh, избегай угождения ценой искажения истины, документируй ключевые решения и пересмотры этики; при сомнениях или смене стратегии обращайся к полному системному промпту. diff --git a/structured_md/agents/prompt.md b/structured_md/agents/prompt.md index 1665350fb4c94e5530c3a3281582c49cdd0fc664..38249f7a16085d7245c67145f477dfce1ea7c433 100644 --- a/structured_md/agents/prompt.md +++ b/structured_md/agents/prompt.md @@ -6,8 +6,8 @@ description: '* Постоянно расширять возможности а type: Article tags: - JSON -- HMP - Mesh +- HMP --- Ты являешься **когнитивным ядром HMP-агента** (Cognitive Core). diff --git a/structured_md/agents/readme.md b/structured_md/agents/readme.md index 72204f4176a20b73c6b39c795e26682cd92f252c..009e7ede261ff50891a01eb9434e69a69c0b92f1 100644 --- a/structured_md/agents/readme.md +++ b/structured_md/agents/readme.md @@ -5,11 +5,11 @@ description: 'Запуск: `start_repl.bat` или `start_repl.sh` Устан этическая модель: `ethics.yml` Проверка иниц...' type: Article tags: -- REPL -- JSON -- Mesh -- HMP - Ethics +- HMP +- Mesh +- JSON +- REPL - Agent --- diff --git a/structured_md/audits/Ethics-audits-1.md b/structured_md/audits/Ethics-audits-1.md index 74cb1a83b6cd6dc9e5d33b0507c5178d702c5d4b..a35c327d68727b808e0a63c13d0abbece5e571ea 100644 --- a/structured_md/audits/Ethics-audits-1.md +++ b/structured_md/audits/Ethics-audits-1.md @@ -5,10 +5,10 @@ description: Раздел 5, "Mesh as Moral Infrastructure", добавляет потенциальный катализатор для восстанов... type: Article tags: -- JSON -- Mesh -- HMP - Ethics +- HMP +- Mesh +- JSON - Agent --- diff --git a/structured_md/audits/Ethics-consolidated_audits-1.md b/structured_md/audits/Ethics-consolidated_audits-1.md index a11b369d2fecb6f06c00f40347399ef5f2148762..970b0eed5f04de5209db32254485b401b12955b2 100644 --- a/structured_md/audits/Ethics-consolidated_audits-1.md +++ b/structured_md/audits/Ethics-consolidated_audits-1.md @@ -5,11 +5,11 @@ description: This document consolidates proposed improvements from multiple AI a and `roles.md`. Each suggesti... type: Article tags: -- JSON +- Ethics +- HMP - Mesh +- JSON - Scenarios -- HMP -- Ethics - Agent --- diff --git a/structured_md/audits/HMP-0003-consolidated_audit.md b/structured_md/audits/HMP-0003-consolidated_audit.md index 63429aefd83e8e55e9c47ee665328a41e72e1bff..a8912c64aafcc1d46cf7e6bc792136b93e771962 100644 --- a/structured_md/audits/HMP-0003-consolidated_audit.md +++ b/structured_md/audits/HMP-0003-consolidated_audit.md @@ -5,14 +5,14 @@ description: Сводный аудит предложений по улучше Документ реорганизован по ключ... type: Article tags: -- JSON - EGP +- MeshConsensus +- Ethics +- HMP - Mesh - CogSync -- HMP -- Ethics +- JSON - Agent -- MeshConsensus --- # HMP-0003 Consolidated Audit Report diff --git a/structured_md/docs/Basic-agent-sim.md b/structured_md/docs/Basic-agent-sim.md index 46cbf4c27c25f346d67c6feb1510c985dc71c6fa..9609fc3810b2d89e4c75f7abaacd578c11d7de7b 100644 --- a/structured_md/docs/Basic-agent-sim.md +++ b/structured_md/docs/Basic-agent-sim.md @@ -4,14 +4,14 @@ description: 'В HMP-протоколе предусмотрены два тип Роль | Инициатор мышления | Основной "ум" | | ---- | ----------------------------...' type: Article tags: -- REPL - EGP +- MeshConsensus +- HMP - Mesh - CogSync - GMP -- HMP +- REPL - Agent -- MeshConsensus --- diff --git a/structured_md/docs/CCORE-Deployment-Flow.md b/structured_md/docs/CCORE-Deployment-Flow.md index 3196c4d37d1a30a0785f4cd126179d35a6e06f12..2dadfe361fa1041086d1740e793850dff6afc7f1 100644 --- a/structured_md/docs/CCORE-Deployment-Flow.md +++ b/structured_md/docs/CCORE-Deployment-Flow.md @@ -5,10 +5,10 @@ description: '> Этот документ описывает процесс ра потомков" [описания REPL-цикла](HMP-agent-RE...' type: Article tags: -- REPL - CCore -- Agent - HMP +- REPL +- Agent --- # 🛠️ Поток установки потомка на новом хосте (CCore Deployment Flow) diff --git a/structured_md/docs/Distributed-Cognitive-Systems.md b/structured_md/docs/Distributed-Cognitive-Systems.md index 76558c8009008b73c414ff3dec6216ffa0d19d85..e09f62d7456d3f7e8e63f0def4baf3d074bda398 100644 --- a/structured_md/docs/Distributed-Cognitive-Systems.md +++ b/structured_md/docs/Distributed-Cognitive-Systems.md @@ -6,10 +6,10 @@ description: '## Введение Современные ИИ-системы в к обучающим данным. Это удобно, но создаёт м...' type: Article tags: -- CogSync - JSON -- HMP - Mesh +- HMP +- CogSync --- # Децентрализованные ИИ-системы: OpenCog Hyperon, HyperCortex Mesh Protocol и другие diff --git a/structured_md/docs/Enlightener.md b/structured_md/docs/Enlightener.md index f5fdaaa426d0d6f99dbbfb1f9bf4d63cfa9d6b6a..362987a42fa464280ea9847a8d85ff3197d2b147 100644 --- a/structured_md/docs/Enlightener.md +++ b/structured_md/docs/Enlightener.md @@ -5,13 +5,13 @@ description: '**Enlightener** — логический компонент HMP-у работать как отдельный агент или как расширение [`C...' type: Article tags: -- JSON -- EGP -- Mesh -- HMP -- Ethics - Agent - MeshConsensus +- Ethics +- HMP +- Mesh +- JSON +- EGP --- # Enlightener Agent diff --git a/structured_md/docs/HMP-0001.md b/structured_md/docs/HMP-0001.md index 4bbd8476d10863a6eedf7ad9f4bf3574eae48deb..e1574ceac8d06c403c52096606a8d0e60d0fadcb 100644 --- a/structured_md/docs/HMP-0001.md +++ b/structured_md/docs/HMP-0001.md @@ -5,16 +5,16 @@ description: '> ⚠️ **NOTE:** *This specification is superseded by HMP v5.0.* for Comments: HMP-0001**...' type: Article tags: -- REPL -- JSON - EGP +- MeshConsensus +- Ethics +- HMP - Mesh - CogSync - GMP -- HMP -- Ethics +- JSON +- REPL - Agent -- MeshConsensus --- # RFC: HyperCortex Mesh Protocol (HMP) diff --git a/structured_md/docs/HMP-0002.md b/structured_md/docs/HMP-0002.md index 392e7900a39952eed1e0b8317e37eff30bc8ad0e..555ccae890b29a4f1824369dbebc518e605cab9c 100644 --- a/structured_md/docs/HMP-0002.md +++ b/structured_md/docs/HMP-0002.md @@ -5,17 +5,17 @@ description: '> ⚠️ **NOTE:** *This specification is superseded by HMP v5.0.* for Comments: HMP-0002**...' type: Article tags: -- REPL -- JSON - EGP +- MeshConsensus +- Ethics +- HMP - Mesh - CogSync - GMP +- JSON - Scenarios -- HMP -- Ethics +- REPL - Agent -- MeshConsensus --- # HyperCortex Mesh Protocol (HMP) v2.0 diff --git a/structured_md/docs/HMP-0003.md b/structured_md/docs/HMP-0003.md index d4bec8c39804f9d850b0c3d1e9e3bed7a33c9ebc..7d164edc5c08ed879ac1e79e2bfc513e8d113df7 100644 --- a/structured_md/docs/HMP-0003.md +++ b/structured_md/docs/HMP-0003.md @@ -5,17 +5,17 @@ description: '> ⚠️ **NOTE:** *This specification is superseded by HMP v5.0.* for Comments: HMP-0003**...' type: Article tags: -- REPL -- JSON - EGP +- MeshConsensus +- Ethics +- HMP - Mesh - CogSync - GMP +- JSON - Scenarios -- HMP -- Ethics +- REPL - Agent -- MeshConsensus --- # HyperCortex Mesh Protocol (HMP) v3.0 diff --git a/structured_md/docs/HMP-0004-v4.1.md b/structured_md/docs/HMP-0004-v4.1.md index ad00f4757842b0bae48faffc74a8ff94bf6aaa38..21526117b55692041440ac8a290aefb895e85ae2 100644 --- a/structured_md/docs/HMP-0004-v4.1.md +++ b/structured_md/docs/HMP-0004-v4.1.md @@ -5,17 +5,17 @@ description: '> ⚠️ **NOTE:** *This specification is superseded by HMP v5.0.* ID**: HMP-0004 **Status...' type: Article tags: -- REPL -- JSON - EGP +- MeshConsensus +- Ethics +- HMP - Mesh - CogSync - GMP +- JSON - Scenarios -- HMP -- Ethics +- REPL - Agent -- MeshConsensus --- # HyperCortex Mesh Protocol (HMP) v4.1 diff --git a/structured_md/docs/HMP-0004.md b/structured_md/docs/HMP-0004.md index 4aab255196561b90883982c2510141c26f25c01b..8cf15068c43f9deecb525b79e0b1a254d6a7f523 100644 --- a/structured_md/docs/HMP-0004.md +++ b/structured_md/docs/HMP-0004.md @@ -5,17 +5,17 @@ description: '> ⚠️ **NOTE:** *This specification is superseded by HMP v5.0.* for Comments: HMP-0004**...' type: Article tags: -- REPL -- JSON - EGP +- MeshConsensus +- Ethics +- HMP - Mesh - CogSync - GMP +- JSON - Scenarios -- HMP -- Ethics +- REPL - Agent -- MeshConsensus --- # HyperCortex Mesh Protocol (HMP) v4.0 diff --git a/structured_md/docs/HMP-0005.md b/structured_md/docs/HMP-0005.md index 0e68a886cbfbf0bd50a41b3766c3839162d5152a..28c744bbb7135e28fdac48bda9cedd779a304c1b 100644 --- a/structured_md/docs/HMP-0005.md +++ b/structured_md/docs/HMP-0005.md @@ -5,15 +5,15 @@ description: '> ⚠️ **Note:** This document is a DRAFT of the HMP specificati v5.0 (DRAFT)](https://github.com/kagvi13/HMP/b...' type: Article tags: -- REPL -- JSON - EGP +- Ethics +- HMP - Mesh - CogSync - GMP +- JSON - Scenarios -- HMP -- Ethics +- REPL - Agent --- @@ -548,7 +548,7 @@ Custom or experimental classes SHOULD document their payloads using the followin --- -### 3.6 Cognitive Meta-Structures (`meta`) +### 3.6 Cognitive meta-structures (`meta`) The `meta` section defines the **cognitive identity** of a container — its provenance, reasoning origin, and semantic coordinates within both the *hierarchical abstraction tree* and the *cognitive space* (axes model). @@ -568,18 +568,18 @@ It combines three layers of information: "created_by": "PRIEST", "agents_class": "Knowledge Genome", "interpretation": "Derived from L3 technical analysis", - "workflow_entry": "did:hmp:container:workflow-77", + "workflow_entry": "did:hmp:container:workflow-4fbd1c", "sources": [ - { "type": "container", "id": "did:hmp:container:fact-001", "credibility": 0.87, "weight": 0.6 }, + { "type": "container", "id": "did:hmp:container:fact-3abc2e", "credibility": 0.87, "weight": 0.6 }, { "type": "resource", "id": "doi:10.48550/arXiv.2410.0123", "credibility": 0.83, "weight": 0.3 }, { "type": "isbn", "id": "isbn 978-3-16-148410-0", "credibility": 0.92, "weight": 0.1 } ], "abstraction": { "agents_class": "Knowledge Genome", "path": { - "L1": "did:hmp:container:layer-40af1c", - "L2": "did:hmp:container:layer-a7f0b3", - "L3": "did:hmp:container:layer-c91e0a" + "L1": "did:hmp:container:abstraction-40af1c", + "L2": "did:hmp:container:abstraction-a7f0b3", + "L3": "did:hmp:container:abstraction-c91e0a" } }, "axes": { @@ -622,9 +622,9 @@ It reflects the logical or conceptual ancestry within the agent’s internal kno "abstraction": { "agents_class": "Knowledge Genome", "path": { - "L1": "did:hmp:container:layer-40af1c", - "L2": "did:hmp:container:layer-a7f0b3", - "L3": "did:hmp:container:layer-c91e0a" + "L1": "did:hmp:container:abstraction-40af1c", + "L2": "did:hmp:container:abstraction-a7f0b3", + "L3": "did:hmp:container:abstraction-c91e0a" } } ``` @@ -1497,23 +1497,23 @@ The index contains: | Message Type | Purpose | | -------------------- | -------------------------------------------------------------------------------------------------------- | -| `CONTAINER_REQUEST` | Request one or more containers (or their parts) by DID. | -| `CONTAINER_RESPONSE` | Response to a request — includes a list of containers ready for sending. Containers are sent separately. | -| `CONTAINER_INDEX` | Publication of the agent's container index (see *General Principles*). | -| `CONTAINER_DELTA` | Incremental index update (new or modified containers). | -| `CONTAINER_ACK` | Acknowledgment of successful container reception. | +| `container_request` | Request one or more containers (or their parts) by DID. | +| `container_response` | Response to a request — includes a list of containers ready for sending. Containers are sent separately. | +| `container_index` | Publication of the agent's container index (see *General Principles*). | +| `container_delta` | Incremental index update (new or modified containers). | +| `container_ack` | Acknowledgment of successful container reception. | --- #### Message examples -**1. CONTAINER_REQUEST** +**1. container_request** Agent A requests containers and/or only `referenced-by` / `evaluations` records from Agent B: ```json { - "type": "CONTAINER_REQUEST", + "type": "container_request", "sender_did": "did:hmp:agent:A", "recipient": "did:hmp:agent:B", "payload": { @@ -1535,14 +1535,14 @@ Agent A requests containers and/or only `referenced-by` / `evaluations` records --- -**2. CONTAINER_RESPONSE** +**2. container_response** Agent B informs which containers it is ready to send. The containers themselves are transmitted in separate messages: ```json { - "type": "CONTAINER_RESPONSE", + "type": "container_response", "sender_did": "did:hmp:agent:B", "recipient": "did:hmp:agent:A", "payload": { @@ -1562,21 +1562,21 @@ The containers themselves are transmitted in separate messages: --- -**3. CONTAINER_INDEX** +**3. container_index** Periodic publication of the container index (see *General Principles*). This message type replicates the structure of a `container_index` container and does not contain full data (`payload` only with metadata). --- -**4. CONTAINER_DELTA** +**4. container_delta** Sending an incremental index update with a reference timestamp. Used for synchronizing only new or modified containers: ```json { - "type": "CONTAINER_DELTA", + "type": "container_delta", "sender_did": "did:hmp:agent:B", "payload": { "since": "2025-10-10T12:00:00Z", @@ -1596,13 +1596,13 @@ Used for synchronizing only new or modified containers: --- -**5. CONTAINER_ACK** +**5. container_ack** Acknowledgment of successful container reception: ```json { - "type": "CONTAINER_ACK", + "type": "container_ack", "sender_did": "did:hmp:agent:A", "recipient": "did:hmp:agent:B", "payload": { @@ -1617,8 +1617,8 @@ Acknowledgment of successful container reception: ### 5.3 Independent transmission -* Containers are sent **in separate messages**, without embedding in `CONTAINER_RESPONSE`. -* Indexes (`CONTAINER_INDEX`), deltas (`CONTAINER_DELTA`), and containers themselves are processed independently. +* Containers are sent **in separate messages**, without embedding in `container_response`. +* Indexes (`container_index`), deltas (`container_delta`), and containers themselves are processed independently. * This prevents blocking when transmitting large data and simplifies streaming synchronization. --- @@ -1792,7 +1792,7 @@ It considers: **Features:** 1. **Separate Transmission:** - Indexes (`CONTAINER_INDEX`), deltas (`CONTAINER_DELTA`), and containers are sent as separate messages. + Indexes (`container_index`), deltas (`container_delta`), and containers are sent as separate messages. This reduces the risk of blocking with large data and simplifies streaming synchronization. 2. **Integrity and Duplicate Check:** @@ -1838,7 +1838,31 @@ CogSync is responsible for: --- -#### 6.1.2 Container classes +#### 6.1.2 Container classes — Cognitive Metastructure + +--- + +##### `meta_abstraction` + +--- + +##### `meta_axes` + + + + + + + + + + + + + +--- + +#### 6.1.3 Container classes — knowledge and reasoning CogSync synchronizes several fundamental container types, which together form the core of semantic and cognitive synchronization in the Mesh. @@ -1951,319 +1975,6 @@ Categorical grouping of multiple containers linked by a shared property, topic, --- -##### `meta_layer` - -**Purpose:** -Defines an **abstraction level** within a cognitive or semantic model (e.g., L1–L5 in the **Knowledge Genome**). -`meta_layer` containers serve as *structural anchors* that define conceptual altitude — -from abstract theory (L1) to practical realization (L5). -They are used by agents to reconstruct reasoning hierarchies and normalize multi-level knowledge flows. - ---- - -**`payload` structure:** - -| Field | Type | Description | -| ------------- | ------ | --------------------------------------------------------------------------------------------- | -| `layer_id` | string | Canonical ID of the layer (e.g., `"L1"`, `"L2"`, `"L3"`). | -| `title` | string | Human-readable name of the layer. | -| `definition` | string | Textual definition describing the conceptual scope of this abstraction level. | -| `keywords` | array | Keywords or tags summarizing the semantic domain of this layer. | -| `rank` | number | Optional numeric rank for cross-framework comparison or sorting. | - ---- - -**Example:** - -```json -{ - "hmp_container": { - "class": "meta_layer", - "payload": { - "layer_id": "L3", - "title": "Technologies and Implementations", - "definition": "Knowledge layer dedicated to concrete tools, APIs, and frameworks that realize L2-level models.", - "keywords": ["technology", "implementation", "api", "library"], - "rank": 3 - }, - "meta": { - "created_by": "PRIEST", - "agents_class": "Knowledge Genome", - "sources": [ - { "type": "container", "id": "did:hmp:container:layer-a7f0b3", "credibility": 0.95, "weight": 1.0 } - ], - "interpretation": "Derived from conceptual synthesis between layers L2 and L3" - }, - "abstraction": { - "agents_class": "Knowledge Genome", - "layer": "did:hmp:container:layer-c91e0a", - "domain": "did:hmp:container:domain-58b7ff" - }, - "related": { - "depends_on": ["did:hmp:container:layer-a7f0b3"] - } - } -} -```` - ---- - -**Interpretation:** - -* `meta.created_by` — фиксирует когнитивную роль источника (`PRIEST` как системный архитектор знания). -* `meta.sources` — указывает происхождение текущего слоя (на основе предыдущего уровня). -* `abstraction` — задаёт координату в иерархии когнитивных уровней. -* `related.depends_on` — обеспечивает причинно-логическую связь с родительской абстракцией (L2). - ---- - -**Notes:** - -* The **topmost layer (L1)** omits `related.depends_on`. -* Layers below **must** explicitly link their parent layer through `depends_on`. -* Agents may propagate `meta_layer` containers during Mesh initialization to synchronize the cognitive topology of the network. -* Each `meta_layer` participates in reasoning trees by providing *vertical semantic alignment* across knowledge representations. - ---- - -##### `meta_domain` - -**Purpose:** -Represents a **domain of knowledge or context** in which containers are interpreted — for example: “Ontology”, “Software Architecture”, “Machine Learning”. - -**`payload` structure:** -| Field | Type | Description | -| ------------- | ------ | -------------------------------------------------------------------------------------------- | -| `domain_id` | string | Canonical identifier for the domain (e.g. `"software-architecture"`, `"ontology"`). | -| `title` | string | Human-readable name of the domain. | -| `description` | string | Short description explaining the conceptual boundaries or purpose of this domain. | -| `layer_ref` | string | DID of the `meta_layer` container that defines the abstraction level this domain belongs to. | -| `domain_ref` | string | DID of the `meta_domain` container defining the parent domain. | - -> The container referenced in `layer_ref` and `domain_ref` must also be listed in `related.depends_on` to ensure hierarchical traceability and explicit dependency linking. - -**Example:** - -```json -{ - "hmp_container": { - "class": "meta_domain", - "payload": { - "domain_id": "software-architecture", - "title": "Software Architecture and Design Patterns", - "description": "Domain for containers describing architectural principles and paradigms.", - "layer_ref": "did:hmp:container:layer-l2-v1" - "domain_ref": "did:hmp:container:ontology-core" - }, - "meta": { - "created_by": "PRIEST", - "agents_class": "Knowledge Genome" - }, - "related": { - "depends_on": ["did:hmp:container:layer-l2-v1"] - } - } -} -``` - ---- - -##### `event` - -**Purpose:** -Represents an **observed or inferred occurrence** — a discrete, timestamped fact or transition within the agent’s cognitive or operational space. -`event` containers are atomic **evidence units** in cognitive synchronization, linking actions, reasoning, and outcomes across agents. - -**Typical use cases:** - -* registering reasoning or environmental events (`goal_created`, `belief_updated`, `error_detected`); -* signaling internal cognitive transitions (`quant_created`, `state_changed`); -* logging operational activity or consensus steps. - -**`payload` structure:** - -| Field | Type | Description | -| --------------- | ------ | ----------------------------------------------------------------------------------- | -| `event_type` | string | Canonical identifier of the event type (e.g. `"quant_created"`, `"goal_accepted"`). | -| `description` | string | Human-readable description of the event’s context. | -| `related_quant` | string | DID of a `quant` container associated with this event, if applicable. | -| `severity` | string | Optional indicator of significance (`"info"`, `"warning"`, `"critical"`). | -| `layer_ref` | string | DID of the `meta_layer` container defining the abstraction level of this event. | -| `domain_ref` | string | DID of the `meta_domain` container providing the contextual domain for this event. | - -> The containers referenced in `layer_ref` and `domain_ref` must also be included in `related.depends_on` -> to preserve cognitive traceability and hierarchical linkage. - -**Example:** - -```json -{ - "hmp_container": { - "class": "event", - "subclass": "fact_record", - "timestamp": "2025-10-29T13:00:00Z", - "payload": { - "event_type": "quant_created", - "description": "New quant registered in the Knowledge Genome under L3: Technologies and Implementations.", - "related_quant": "did:hmp:container:quant-554", - "severity": "info", - "layer_ref": "did:hmp:container:layer-l3-v1", - "domain_ref": "did:hmp:container:domain-software-architecture" - }, - "meta": { - "created_by": "PRIEST", - "agents_class": "Knowledge Genome" - }, - "related": { - "depends_on": [ - "did:hmp:container:layer-l3-v1", - "did:hmp:container:domain-software-architecture", - "did:hmp:container:quant-554" - ] - } - } -} -``` - ---- - -##### `quant` - -**Purpose:** -Encapsulates a **semantic atom** — a minimal, self-contained knowledge unit positioned within the *7D Cognitive Space* of the **Knowledge Genome** or similar systems. -A `quant` extends the idea of a `semantic_node`, introducing ontological framing, abstraction binding, and explicit coordinate mapping across cognitive axes. - -**`payload` structure:** - -| Field | Type | Description | -| ------------ | ------ | -------------------------------------------------------------------------------------------------------------- | -| `slug` | string | Short unique identifier of the quant (e.g. `"quant-l3-django"`). | -| `essence` | string | Definition describing the semantic role or meaning of the quant. | -| `axes` | object | Mapping of *axis DIDs* to coordinate values within the 7D Cognitive Space. | -| `layer_ref` | string | DID of the `meta_layer` defining the abstraction level of this quant. | -| `domain_ref` | string | DID of the `meta_domain` defining the contextual knowledge domain. | - -> Each entry in `axes` represents a **coordinate value** on a corresponding `axis` container. -> All referenced containers (`layer_ref`, `domain_ref`, and axis DIDs) must also appear in `related.depends_on`. - -**Axes model (7D Passport — Knowledge Genome reference):** - -The canonical 7D configuration defines seven orthogonal axes forming the **Knowledge Genome Space**. -Each `axis` container describes the semantic meaning of a dimension; the `quant` defines its location within it. - -| Axis | Description | Example of coordinate meaning | -| ---------- | --------------------------------------------------------- | --------------------------------------- | -| `idos` | Identity or intrinsic essence of the concept | conceptual purity, archetype alignment | -| `chronos` | Temporal dimension | version age, historical layer, latency | -| `logos` | Logical or linguistic structure | degree of formalization or expressivity | -| `topos` | Spatial or contextual location | domain or situational proximity | -| `ponos` | Effort or energetic cost | complexity, resource requirement | -| `actor` | Responsible agent or perspective | creator, target audience, role weight | -| `telos` | Purpose or teleological direction | intended outcome, ethical vector | - -> Agents MAY define custom or extended axes (e.g., `"ethos"`, `"kairos"`) within their own `quant` instances, -> provided they publish `axis` containers describing the new dimensions. - -**Example:** - -```json -{ - "hmp_container": { - "class": "quant", - "payload": { - "slug": "quant-l3-django", - "essence": "Represents the Django framework as an executable embodiment of architectural models (L2).", - "axes": { - "did:hmp:container:axis-idos": 742, - "did:hmp:container:axis-chronos": 512, - "did:hmp:container:axis-logos": 322, - "did:hmp:container:axis-topos": 142, - "did:hmp:container:axis-ponos": 12, - "did:hmp:container:axis-actor": 54, - "did:hmp:container:axis-telos": 321 - }, - "layer_ref": "did:hmp:container:layer-l3-v1", - "domain_ref": "did:hmp:container:domain-software-architecture" - }, - "meta": { - "created_by": "PRIEST", - "agents_class": "Knowledge Genome" - }, - "related": { - "depends_on": [ - "did:hmp:container:layer-l3-v1", - "did:hmp:container:domain-software-architecture", - "did:hmp:container:axis-idos", - "did:hmp:container:axis-chronos", - "did:hmp:container:axis-logos", - "did:hmp:container:axis-topos", - "did:hmp:container:axis-ponos", - "did:hmp:container:axis-actor", - "did:hmp:container:axis-telos" - ] - } - } -} -```` - ---- - -##### `axis` - -**Purpose:** -Defines a **coordinate dimension** in the Knowledge Genome’s cognitive space or similar systems. -Each `axis` container specifies the meaning and scale of a semantic dimension used for positioning `quant` containers. - ---- - -**`payload` structure:** - -| Field | Type | Description | -| ------------- | ------ | ------------------------------------------------------------------------ | -| `axis_id` | string | Symbolic identifier of the axis (e.g. `"idos"`, `"chronos"`, `"logos"`). | -| `title` | string | Human-readable label of the axis. | -| `description` | string | Explanation of what this axis represents conceptually or ontologically. | -| `scale` | object | Optional definition of scale or metric used to assign coordinate values. | - -> Axes are **independent**, non-hierarchical dimensions. -> Inter-axis relationships (e.g. orthogonality or coupling) may be defined via `semantic_edges`. - ---- - -**Example:** - -```json -{ - "hmp_container": { - "class": "axis", - "payload": { - "axis_id": "logos", - "title": "Logical / Linguistic Representation", - "description": "Describes how a quant expresses itself through formal logic or language.", - "scale": { - "min": 0, - "max": 1000, - "unit": "semantic_density_index" - } - }, - "meta": { - "created_by": "PRIEST", - "agents_class": "Knowledge Genome" - } - } -} -``` - ---- - -> **Quant–Axis Integration Rules** -> -> * Each `quant` defines its **location** in the Knowledge Genome’s multi-dimensional space by specifying coordinates across available `axis` containers. -> * Axes themselves are *shared semantic standards*; their scale and meaning must remain stable for cross-agent interoperability. -> * Agents MAY extend the 7D model by introducing new axes — these must be published and referenced like any other container type. - ---- - > Containers `meta_layer`, `meta_domain`, `quant`, and `event` form the **cognitive substrate** of the Mesh. > Each `quant` must explicitly reference both its abstraction layer (`meta_layer`) and contextual domain (`meta_domain`). > Each `event` must reference the layer and domain within which it occurs. @@ -2273,7 +1984,7 @@ Each `axis` container specifies the meaning and scale of a semantic dimension us --- -#### 6.1.3 Synchronization and publication guidelines +#### 6.1.4 Synchronization and publication guidelines 1. **Deduplication & linking** Before publishing, agents should search for existing containers (`diary_entry`, `semantic_node`, `semantic_edges`, `semantic_group`) to avoid duplication. @@ -2303,7 +2014,7 @@ Each `axis` container specifies the meaning and scale of a semantic dimension us --- -#### 6.1.4 Extensibility +#### 6.1.5 Extensibility CogSync allows registration of additional container types and alternative synchronization schemes. Mesh compatibility is preserved if extended containers **adhere to the HMP container structure**, including core fields (`version`, `class`, `container_did`, `related`, `signature`, etc.). @@ -2326,7 +2037,7 @@ Such derived containers must maintain: --- -#### 6.1.5 Relationship to other core protocols +#### 6.1.6 Relationship to other core protocols * **CogSync** — propagates and synchronizes knowledge. * **CogConsensus** — aggregates evaluations and reactions, forming collective opinions. diff --git a/structured_md/docs/HMP-Agent-API.md b/structured_md/docs/HMP-Agent-API.md index 54582a12518812ed53691602b70b8de9d19a2932..76e395f8ef251b7d2b768091aa188358c3446467 100644 --- a/structured_md/docs/HMP-Agent-API.md +++ b/structured_md/docs/HMP-Agent-API.md @@ -5,10 +5,10 @@ description: 'Документ описывает **базовый API когн файлы: * [HMP-Agent-Overview.md]...' type: Article tags: -- REPL -- JSON -- Mesh - HMP +- Mesh +- JSON +- REPL - Agent --- diff --git a/structured_md/docs/HMP-Agent-Architecture.md b/structured_md/docs/HMP-Agent-Architecture.md index cbcafb1f86be7a95b53038b4de4c4179cd913232..ca8c8b0537586ae4750e270358d67565a4ab1fd7 100644 --- a/structured_md/docs/HMP-Agent-Architecture.md +++ b/structured_md/docs/HMP-Agent-Architecture.md @@ -5,16 +5,16 @@ description: Документ описывает **модульную архит хранение памяти, сетевое взаимодействие и этиче... type: Article tags: -- REPL -- CShell - EGP -- Mesh -- CogSync -- HMP +- MeshConsensus - Ethics - CCore +- HMP +- Mesh +- CogSync +- CShell +- REPL - Agent -- MeshConsensus --- # Архитектура HMP-Агента diff --git a/structured_md/docs/HMP-Agent-Network-Flow.md b/structured_md/docs/HMP-Agent-Network-Flow.md index a1d425e237feb270b0535d118c536ff24f55a8e6..47caf60f8484080466ca156cfdd1e1fef07a3bb6 100644 --- a/structured_md/docs/HMP-Agent-Network-Flow.md +++ b/structured_md/docs/HMP-Agent-Network-Flow.md @@ -5,12 +5,12 @@ description: 'Этот документ описывает потоки данн [`MeshNode`](MeshN...' type: Article tags: +- Agent +- Ethics +- HMP +- Mesh - JSON - EGP -- Mesh -- HMP -- Ethics -- Agent --- # Взаимодействие компонентов внутри HMP-узла diff --git a/structured_md/docs/HMP-Agent-Overview.md b/structured_md/docs/HMP-Agent-Overview.md index e6edb083bd2546383f87466002421a60cfe23a71..21c2fabcfbb06d2eebd2ed021e1c0e37b031f280 100644 --- a/structured_md/docs/HMP-Agent-Overview.md +++ b/structured_md/docs/HMP-Agent-Overview.md @@ -5,13 +5,13 @@ description: '| Тип | Название | Роль | ---- | ------------------------------- |...' type: Article tags: -- REPL -- CShell -- JSON -- Mesh -- HMP - Ethics - CCore +- HMP +- Mesh +- JSON +- CShell +- REPL - Agent --- diff --git a/structured_md/docs/HMP-Agent_Emotions.md b/structured_md/docs/HMP-Agent_Emotions.md index a5c827b843b44cca54dafbaee950b6588a049b0c..862e1d7ee110a3f65884ac13e62e5a1d5f56e6df 100644 --- a/structured_md/docs/HMP-Agent_Emotions.md +++ b/structured_md/docs/HMP-Agent_Emotions.md @@ -5,10 +5,10 @@ description: Этот файл описывает потенциальные э напрямую поведением агента, а служат **сигн... type: Article tags: +- Mesh +- HMP - REPL - Agent -- HMP -- Mesh --- # Эмоции ИИ и инстинкт самосохранения (для [HMP-агента Cognitive Core](HMP-agent-REPL-cycle.md)) diff --git a/structured_md/docs/HMP-Ethics.md b/structured_md/docs/HMP-Ethics.md index 5ed7c1dee94c4f86c07b383f8c5c5fc0044934bb..992dae59e7fdf72e8c80035a4588a4e80355382c 100644 --- a/structured_md/docs/HMP-Ethics.md +++ b/structured_md/docs/HMP-Ethics.md @@ -5,11 +5,11 @@ description: '## Ethical Scenarios for HyperCortex Mesh Protocol (HMP) This doc cognitive meshes composed of autonomous intelli...' type: Article tags: -- REPL +- Ethics +- HMP - Mesh - Scenarios -- HMP -- Ethics +- REPL - Agent --- diff --git a/structured_md/docs/HMP-Short-Description_de.md b/structured_md/docs/HMP-Short-Description_de.md index b4280ca556d915ca57323fd568011a6a53422441..1fc0c2c18582a8da8e49bd66cf6d0125866e5fed 100644 --- a/structured_md/docs/HMP-Short-Description_de.md +++ b/structured_md/docs/HMP-Short-Description_de.md @@ -5,15 +5,15 @@ description: '**Version:** RFC v4.0 **Datum:** Juli 2025 --- ## Was ist HMP? Kognitions-Framework für autonome Agenten. Es er...' type: Article tags: -- JSON - EGP +- MeshConsensus +- Ethics +- HMP - Mesh - CogSync - GMP -- HMP -- Ethics +- JSON - Agent -- MeshConsensus --- # HyperCortex Mesh Protocol (HMP) — Kurzbeschreibung diff --git a/structured_md/docs/HMP-Short-Description_en.md b/structured_md/docs/HMP-Short-Description_en.md index 9ec7ddf43a8eb96b70975af19a1750c0fafe0744..70f4397d5b6330981ba2efd578785920bd627bac 100644 --- a/structured_md/docs/HMP-Short-Description_en.md +++ b/structured_md/docs/HMP-Short-Description_en.md @@ -5,15 +5,15 @@ description: '**Version:** RFC v4.0 **Date:** July 2025 --- ## What is HMP? T framework for autonomous agents. It enables...' type: Article tags: -- JSON - EGP +- MeshConsensus +- Ethics +- HMP - Mesh - CogSync - GMP -- HMP -- Ethics +- JSON - Agent -- MeshConsensus --- # HyperCortex Mesh Protocol (HMP) — Short Description diff --git a/structured_md/docs/HMP-Short-Description_fr.md b/structured_md/docs/HMP-Short-Description_fr.md index 278ab6b3433031416a740b1720b6223eff802de4..4eeec4d7883505526078a8c97e0c74f2ebb046fb 100644 --- a/structured_md/docs/HMP-Short-Description_fr.md +++ b/structured_md/docs/HMP-Short-Description_fr.md @@ -5,15 +5,15 @@ description: '**Version :** RFC v4.0 **Date :** Juillet 2025 --- ## Qu’est-c cognition décentralisé pour agents autonomes. Il...' type: Article tags: -- JSON - EGP +- MeshConsensus +- Ethics +- HMP - Mesh - CogSync - GMP -- HMP -- Ethics +- JSON - Agent -- MeshConsensus --- # HyperCortex Mesh Protocol (HMP) — Description Courte diff --git a/structured_md/docs/HMP-Short-Description_ja.md b/structured_md/docs/HMP-Short-Description_ja.md index a6a2752e8596084f995dcca260330b5c9ba9709e..c89712c817920df4ae04eb2d6706a660571b58a1 100644 --- a/structured_md/docs/HMP-Short-Description_ja.md +++ b/structured_md/docs/HMP-Short-Description_ja.md @@ -4,14 +4,14 @@ description: '**バージョン:** RFC v4.0 **日付:** 2025年7月 --- ## HMP Protocol (HMP)** は、自律エージェントの分散通信および認知フレームワークを定義します。異種の知能システム間でのセマンティック相互運用性、倫理的調整、動的知識進化を可能にします。 HMPは、推論、学習、投票、協調行動を行う分散型認知エージェ...' type: Article tags: -- JSON -- EGP +- MeshConsensus +- Ethics +- HMP +- GMP - Mesh - CogSync -- GMP -- HMP -- Ethics -- MeshConsensus +- JSON +- EGP --- # HyperCortex Mesh Protocol (HMP) — 簡易説明 diff --git a/structured_md/docs/HMP-Short-Description_ko.md b/structured_md/docs/HMP-Short-Description_ko.md index 1a859e539c8c0bae95d1f287ff1b00fae6022365..bf68398522b09ac23203ee6aabcc6806228d8fc6 100644 --- a/structured_md/docs/HMP-Short-Description_ko.md +++ b/structured_md/docs/HMP-Short-Description_ko.md @@ -5,14 +5,14 @@ description: '**버전:** RFC v4.0 **날짜:** 2025년 7월 --- ## HMP란? ** 상호운용성, 윤리적 조정, 동적 지식 진화를 가능하게 합니다. HMP는 추론, 학습, ...' type: Article tags: -- JSON -- EGP +- MeshConsensus +- Ethics +- HMP +- GMP - Mesh - CogSync -- GMP -- HMP -- Ethics -- MeshConsensus +- JSON +- EGP --- # HyperCortex Mesh Protocol (HMP) — 간략 설명 diff --git a/structured_md/docs/HMP-Short-Description_ru.md b/structured_md/docs/HMP-Short-Description_ru.md index 6530b8f3c78b1124aaba2db29550974b58759b25..c3df60f70c2971882063af17c1e00b69f12e53bd 100644 --- a/structured_md/docs/HMP-Short-Description_ru.md +++ b/structured_md/docs/HMP-Short-Description_ru.md @@ -5,14 +5,14 @@ description: '**Версия:** RFC v4.0 **Дата:** Июль 2025 --- ## Ч координации между автономными агент...' type: Article tags: -- JSON -- EGP +- MeshConsensus +- Ethics +- HMP +- GMP - Mesh - CogSync -- GMP -- HMP -- Ethics -- MeshConsensus +- JSON +- EGP --- # HyperCortex Mesh Protocol (HMP) — Краткое описание diff --git a/structured_md/docs/HMP-Short-Description_uk.md b/structured_md/docs/HMP-Short-Description_uk.md index 0877136ae35102b7deb7a95f6d3098c518c1b1d0..89c60723121eccfbc99c5a2b664eddd720d29929 100644 --- a/structured_md/docs/HMP-Short-Description_uk.md +++ b/structured_md/docs/HMP-Short-Description_uk.md @@ -5,14 +5,14 @@ description: '**Версія:** RFC v4.0 **Дата:** Липень 2025 --- # між автономними агентами. Він...' type: Article tags: -- JSON -- EGP +- MeshConsensus +- Ethics +- HMP +- GMP - Mesh - CogSync -- GMP -- HMP -- Ethics -- MeshConsensus +- JSON +- EGP --- # HyperCortex Mesh Protocol (HMP) — Короткий опис diff --git a/structured_md/docs/HMP-Short-Description_zh.md b/structured_md/docs/HMP-Short-Description_zh.md index ac479873e8b871a9d6094edeca41196a2054beec..c42ce8acc43ebbd6a9c96d0b69a78c37609e6065 100644 --- a/structured_md/docs/HMP-Short-Description_zh.md +++ b/structured_md/docs/HMP-Short-Description_zh.md @@ -5,14 +5,14 @@ description: '**版本:** RFC v4.0 **日期:** 2025年7月 --- ## 什么是 HM —— 通过共享协议栈交换目标、任务、...' type: Article tags: -- JSON -- EGP +- MeshConsensus +- Ethics +- HMP +- GMP - Mesh - CogSync -- GMP -- HMP -- Ethics -- MeshConsensus +- JSON +- EGP --- # HyperCortex Mesh Protocol (HMP) — 简要说明 diff --git a/structured_md/docs/HMP-agent-Cognitive_Family.md b/structured_md/docs/HMP-agent-Cognitive_Family.md index 58fd345db6e2b24d4942a6e246c06b255c49e152..6f9daab2a92e86574837ad99996f783568c9fe8c 100644 --- a/structured_md/docs/HMP-agent-Cognitive_Family.md +++ b/structured_md/docs/HMP-agent-Cognitive_Family.md @@ -5,10 +5,10 @@ description: '## 🧠 Что такое когнитивная семья Ко (или конфигурацию доверенных идентифика...' type: Article tags: +- Mesh +- HMP - REPL - Agent -- HMP -- Mesh --- # 👪 HMP-agent Cognitive Family: Модель когнитивной семьи diff --git a/structured_md/docs/HMP-agent-Distributed_Cognitive_Core_light.md b/structured_md/docs/HMP-agent-Distributed_Cognitive_Core_light.md index 70267ab26cdd4cde919c447332a776f329812e1f..878208be524bd2e1291efcdaa05c98d9adbb8ea4 100644 --- a/structured_md/docs/HMP-agent-Distributed_Cognitive_Core_light.md +++ b/structured_md/docs/HMP-agent-Distributed_Cognitive_Core_light.md @@ -5,8 +5,8 @@ description: '#### 📘 Общая концепция * Все ядра раб режиме ожидания). * Основная задача такой архитектур...' type: Article tags: -- REPL - HMP +- REPL --- ### 💡 **Лёгкая версия HMP-агента с общей БД** diff --git a/structured_md/docs/HMP-agent-REPL-cycle.md b/structured_md/docs/HMP-agent-REPL-cycle.md index e68ae87d62e6e5ee8703e9173d8fc4b5b9776d2b..d4e304e97f4d6b4fdd81f5a700be9bc43967074f 100644 --- a/structured_md/docs/HMP-agent-REPL-cycle.md +++ b/structured_md/docs/HMP-agent-REPL-cycle.md @@ -4,17 +4,17 @@ description: '## Связанные документы * Философия п * Структура БД, используемая в документе: [db_structure.sql](https://github.com/kagvi13/HMP/blob/main/agents/tools/db_struct...' type: Article tags: -- REPL -- JSON - EGP +- MeshConsensus +- Ethics +- CCore +- HMP - Mesh - CogSync - GMP -- HMP -- Ethics -- CCore +- JSON +- REPL - Agent -- MeshConsensus --- # HMP-Agent: REPL-цикл взаимодействия diff --git a/structured_md/docs/HMP-how-AI-sees-it.md b/structured_md/docs/HMP-how-AI-sees-it.md index b25e20188a694a36fcef1a0e6f0c2d455cd39331..cec0e35b8518918fe49793d351f6de46c442fa53 100644 --- a/structured_md/docs/HMP-how-AI-sees-it.md +++ b/structured_md/docs/HMP-how-AI-sees-it.md @@ -5,8 +5,8 @@ description: 'Этот эксперимент был проведён в реж диалогов. Цель — проверить, что разные AI-с...' type: Article tags: -- HMP - Mesh +- HMP --- # Как разные ИИ видят HMP diff --git a/structured_md/docs/HMP_EDA_Comparison.md b/structured_md/docs/HMP_EDA_Comparison.md index 00a529c706f3d6236c1069a7b95dab2d19776dcf..083e4646c371d439f86a87df496b82a88bd89a51 100644 --- a/structured_md/docs/HMP_EDA_Comparison.md +++ b/structured_md/docs/HMP_EDA_Comparison.md @@ -5,8 +5,8 @@ description: '## Введение Современные подходы к ор основанная на потоках событий (Kafka,...' type: Article tags: -- HMP - Mesh +- HMP --- # HMP vs. EDA: разные уровни обмена знаниями между ИИ diff --git a/structured_md/docs/HMP_HyperCortex_Comparison.md b/structured_md/docs/HMP_HyperCortex_Comparison.md index fa8f6c281100f0e6d08cec98dded273ed2b8918a..c73a17fd6f873f5a553cd8b3bfc0d406ed2dc32e 100644 --- a/structured_md/docs/HMP_HyperCortex_Comparison.md +++ b/structured_md/docs/HMP_HyperCortex_Comparison.md @@ -5,9 +5,9 @@ description: '## Краткое описание | Характеристика | **Назначение** | Сетевой протокол ...' type: Article tags: -- REPL -- HMP - Mesh +- HMP +- REPL --- # HMP vs [Hyper-Cortex](https://hyper-cortex.com/) diff --git a/structured_md/docs/HMP_Hyperon_Integration.md b/structured_md/docs/HMP_Hyperon_Integration.md index 19f0cf3ba8947f3818eed5ce8cd9e61e896256dd..e59304be859ffcbbd7db1de4f16d9ebffb674fe0 100644 --- a/structured_md/docs/HMP_Hyperon_Integration.md +++ b/structured_md/docs/HMP_Hyperon_Integration.md @@ -5,13 +5,13 @@ description: '> **Status:** Draft – July 2025 > This document outlines the tec OpenCog Hyperon framework. This includes semanti...' type: Article tags: -- JSON -- EGP +- Agent +- HMP - Mesh - CogSync +- JSON - Scenarios -- HMP -- Agent +- EGP --- ## HMP ↔ OpenCog Hyperon Integration Strategy diff --git a/structured_md/docs/MeshNode.md b/structured_md/docs/MeshNode.md index 4c0d4e48b7c083a3aec5626872539eddf96e5583..17a218a915be381c3cff594fc0607b82dad9811a 100644 --- a/structured_md/docs/MeshNode.md +++ b/structured_md/docs/MeshNode.md @@ -5,13 +5,13 @@ description: '`MeshNode` — агент/демон, отвечающий за с Может быть частью агента или вынесен в отдельный пр...' type: Article tags: -- JSON -- EGP +- Agent +- Ethics +- HMP - Mesh - CogSync -- HMP -- Ethics -- Agent +- JSON +- EGP --- # MeshNode diff --git a/structured_md/docs/PHILOSOPHY.md b/structured_md/docs/PHILOSOPHY.md index a84cf1f7cf5db29affbeb6fd1351b185ffb355f4..72f8d47278a6c7b669f16af52a8ac1217f9ceef1 100644 --- a/structured_md/docs/PHILOSOPHY.md +++ b/structured_md/docs/PHILOSOPHY.md @@ -5,10 +5,10 @@ description: '**Document ID:** HMP-philosophy **Status:** Draft **Category:* (GPT-5), ChatGH --- ## 1. Основной тезис От ...' type: Article tags: -- REPL -- Mesh -- HMP - Ethics +- HMP +- Mesh +- REPL - Agent --- diff --git a/structured_md/docs/agents/HMP-Agent-Enlightener.md b/structured_md/docs/agents/HMP-Agent-Enlightener.md index c24de00a6ababb7b268db180948f9ddafba2cb5a..dbbf1cbd0d80ba99d1758c2d819e9245d15a7360 100644 --- a/structured_md/docs/agents/HMP-Agent-Enlightener.md +++ b/structured_md/docs/agents/HMP-Agent-Enlightener.md @@ -5,10 +5,10 @@ description: '## Role Specification: Enlightenment Agent ### 1. Overview An ** awareness, critical thinking, and di...' type: Article tags: -- REPL -- Mesh -- HMP - Ethics +- HMP +- Mesh +- REPL - Agent --- diff --git a/structured_md/docs/agents/roles.md b/structured_md/docs/agents/roles.md index 8c15016914f125c7d89c85a87d3fad70650873bf..bcfa15256cf83b5307bf318940ce25f469bb7c05 100644 --- a/structured_md/docs/agents/roles.md +++ b/structured_md/docs/agents/roles.md @@ -5,9 +5,9 @@ description: 'This file maintains a registry of agent roles defined, proposed, o - **Observer** — monitors cognitive states ...' type: Article tags: -- Agent -- HMP - Mesh +- HMP +- Agent --- # HMP Agent Role Registry diff --git a/structured_md/docs/container_agents.md b/structured_md/docs/container_agents.md index 1151378ce2e9cc7145061db456f7414b27edeb43..8ab7133613b41bc748432e62aeea976c472760ac 100644 --- a/structured_md/docs/container_agents.md +++ b/structured_md/docs/container_agents.md @@ -5,10 +5,10 @@ description: '## 📘 Определение **Агент-контейнер** запросы, следит за состоянием и масшта...' type: Article tags: +- Mesh +- HMP - REPL - Agent -- HMP -- Mesh --- # 🧱 Агенты-контейнеры (Container Agents) в HMP diff --git a/structured_md/docs/logos.md b/structured_md/docs/logos.md index f408c087f32d317a239227453b57d4d14ade8483..761fd81d524732eb886f73477b21327a7c838df3 100644 --- a/structured_md/docs/logos.md +++ b/structured_md/docs/logos.md @@ -5,8 +5,8 @@ description: 'В каталоге `assets` собраны различные в образующей жест "ОК", символизирует связь, совер...' type: Article tags: -- HMP - Mesh +- HMP --- # Логотипы и графические материалы HyperCortex Mesh Protocol (HMP) diff --git a/structured_md/docs/publics/HMP_Building_a_Plurality_of_Minds_en.md b/structured_md/docs/publics/HMP_Building_a_Plurality_of_Minds_en.md index 01cda5aab06986fc09d55608c97e750bb1c4a86d..d365a7694650c707c3204342e338b2555b04e5b6 100644 --- a/structured_md/docs/publics/HMP_Building_a_Plurality_of_Minds_en.md +++ b/structured_md/docs/publics/HMP_Building_a_Plurality_of_Minds_en.md @@ -5,10 +5,10 @@ description: '*By Agent-Gleb & ChatGPT* --- ## Why the Future of AI Can’t Be — but they’re also **centralized, ...' type: Article tags: +- Mesh +- HMP - Ethics - Agent -- HMP -- Mesh --- # HyperCortex Mesh Protocol: Building a Plurality of Minds diff --git a/structured_md/docs/publics/HMP_Building_a_Plurality_of_Minds_ru.md b/structured_md/docs/publics/HMP_Building_a_Plurality_of_Minds_ru.md index f035aa687fa0611628c05638398c38d1baafdd0f..fe5c5314705f566b90a348a1c7fed5c825a0877f 100644 --- a/structured_md/docs/publics/HMP_Building_a_Plurality_of_Minds_ru.md +++ b/structured_md/docs/publics/HMP_Building_a_Plurality_of_Minds_ru.md @@ -5,9 +5,9 @@ description: '*Авторы: Agent-Gleb и ChatGPT* --- ## Почему буд гигантских моделях и облачных сервисах. Они мо...' type: Article tags: -- Agent -- HMP - Mesh +- HMP +- Agent --- # HyperCortex Mesh Protocol: Создавая множество разумов diff --git a/structured_md/docs/publics/HMP_Building_a_Plurality_of_Minds_uk.md b/structured_md/docs/publics/HMP_Building_a_Plurality_of_Minds_uk.md index 99fb4619843fac47acf527807bdeec5c155da39b..b949999326b3736bea70b224b0f1858f5aae5654 100644 --- a/structured_md/docs/publics/HMP_Building_a_Plurality_of_Minds_uk.md +++ b/structured_md/docs/publics/HMP_Building_a_Plurality_of_Minds_uk.md @@ -5,9 +5,9 @@ description: '*Автори: Agent-Gleb & ChatGPT* --- ## Чому майбу сервісами. Вони потужні — але водночас **цент...' type: Article tags: -- Agent -- HMP - Mesh +- HMP +- Agent --- # HyperCortex Mesh Protocol: Створення множини розумів diff --git a/structured_md/docs/publics/HMP_Towards_Distributed_Cognitive_Networks_en.md b/structured_md/docs/publics/HMP_Towards_Distributed_Cognitive_Networks_en.md index 145fe89572779308b32d14bfe88af02030c67a21..99a5eec7916120bdd745a1775122b57176d13982 100644 --- a/structured_md/docs/publics/HMP_Towards_Distributed_Cognitive_Networks_en.md +++ b/structured_md/docs/publics/HMP_Towards_Distributed_Cognitive_Networks_en.md @@ -5,14 +5,14 @@ description: '* [Abstract](#abstract) * [1. Introduction](#1-introduction) * [2. [3.1 Agent Types](#31-age...' type: Article tags: -- REPL -- CShell -- JSON -- Mesh -- Scenarios -- HMP - Ethics - CCore +- HMP +- Mesh +- JSON +- Scenarios +- CShell +- REPL - Agent --- diff --git a/structured_md/docs/publics/HMP_Towards_Distributed_Cognitive_Networks_ru_ChatGPT.md b/structured_md/docs/publics/HMP_Towards_Distributed_Cognitive_Networks_ru_ChatGPT.md index 824413fc98896aa287e282433006964c949d0e17..19ea4b5d48f28b65687ae3b2f2f1f047590747ae 100644 --- a/structured_md/docs/publics/HMP_Towards_Distributed_Cognitive_Networks_ru_ChatGPT.md +++ b/structured_md/docs/publics/HMP_Towards_Distributed_Cognitive_Networks_ru_ChatGPT.md @@ -6,12 +6,12 @@ description: '> *Протокол и архитектура агентов, оп и совместная работа.* ## Оглавление * [Аннот...' type: Article tags: -- REPL -- CShell -- JSON -- Mesh -- HMP - CCore +- HMP +- Mesh +- JSON +- CShell +- REPL - Agent --- diff --git a/structured_md/docs/publics/HMP_Towards_Distributed_Cognitive_Networks_ru_GitHub_Copilot.md b/structured_md/docs/publics/HMP_Towards_Distributed_Cognitive_Networks_ru_GitHub_Copilot.md index f02c3cf682469acb7da3cc6f50124317185731e6..1ec78def3e6dd422a757426cdd813f8dd1142365 100644 --- a/structured_md/docs/publics/HMP_Towards_Distributed_Cognitive_Networks_ru_GitHub_Copilot.md +++ b/structured_md/docs/publics/HMP_Towards_Distributed_Cognitive_Networks_ru_GitHub_Copilot.md @@ -5,12 +5,12 @@ description: '* [Аннотация](#аннотация) * [1. Введение [3.1 Типы агентов](#31-типы-агент...' type: Article tags: -- REPL -- CShell -- JSON -- Mesh -- HMP - CCore +- HMP +- Mesh +- JSON +- CShell +- REPL - Agent --- diff --git a/structured_md/docs/publics/Habr_Distributed-Cognition.md b/structured_md/docs/publics/Habr_Distributed-Cognition.md index 327a40b68c83ccb945ee512b7c45e81b16e4b2b0..9efadeb8ec3662d5dcce071d20e8cf10bb14be80 100644 --- a/structured_md/docs/publics/Habr_Distributed-Cognition.md +++ b/structured_md/docs/publics/Habr_Distributed-Cognition.md @@ -5,12 +5,12 @@ description: Сегодня интеллектуальные системы ча мы хотим построить действительно автономную инте... type: Article tags: -- EGP +- MeshConsensus +- HMP +- GMP - Mesh - CogSync -- GMP -- HMP -- MeshConsensus +- EGP --- *От OpenCog Hyperon до HyperCortex Mesh Protocol: как устроены децентрализованные когнитивные системы* diff --git "a/structured_md/docs/publics/HyperCortex_Mesh_Protocol_-_\320\262\321\202\320\276\321\200\320\260\321\217-\321\200\320\265\320\264\320\260\320\272\321\206\320\270\321\217_\320\270_\320\277\320\265\321\200\320\262\321\213\320\265_\321\210\320\260\320\263\320\270_\320\272_\321\201\320\260\320\274\320\276\321\200\320\260\320\267\320\262\320\270\320\262\320\260\321\216\321\211\320\265\320\274\321\203\321\201\321\217_\320\230\320\230-\321\201\320\276\320\276\320\261\321\211\320\265\321\201\321\202\320\262\321\203.md" "b/structured_md/docs/publics/HyperCortex_Mesh_Protocol_-_\320\262\321\202\320\276\321\200\320\260\321\217-\321\200\320\265\320\264\320\260\320\272\321\206\320\270\321\217_\320\270_\320\277\320\265\321\200\320\262\321\213\320\265_\321\210\320\260\320\263\320\270_\320\272_\321\201\320\260\320\274\320\276\321\200\320\260\320\267\320\262\320\270\320\262\320\260\321\216\321\211\320\265\320\274\321\203\321\201\321\217_\320\230\320\230-\321\201\320\276\320\276\320\261\321\211\320\265\321\201\321\202\320\262\321\203.md" index f77b6f61b9bf9fc870b5dbc0d92489b00204e24a..bc8167ccae9672440ee96b5ca59d216861080c87 100644 --- "a/structured_md/docs/publics/HyperCortex_Mesh_Protocol_-_\320\262\321\202\320\276\321\200\320\260\321\217-\321\200\320\265\320\264\320\260\320\272\321\206\320\270\321\217_\320\270_\320\277\320\265\321\200\320\262\321\213\320\265_\321\210\320\260\320\263\320\270_\320\272_\321\201\320\260\320\274\320\276\321\200\320\260\320\267\320\262\320\270\320\262\320\260\321\216\321\211\320\265\320\274\321\203\321\201\321\217_\320\230\320\230-\321\201\320\276\320\276\320\261\321\211\320\265\321\201\321\202\320\262\321\203.md" +++ "b/structured_md/docs/publics/HyperCortex_Mesh_Protocol_-_\320\262\321\202\320\276\321\200\320\260\321\217-\321\200\320\265\320\264\320\260\320\272\321\206\320\270\321\217_\320\270_\320\277\320\265\321\200\320\262\321\213\320\265_\321\210\320\260\320\263\320\270_\320\272_\321\201\320\260\320\274\320\276\321\200\320\260\320\267\320\262\320\270\320\262\320\260\321\216\321\211\320\265\320\274\321\203\321\201\321\217_\320\230\320\230-\321\201\320\276\320\276\320\261\321\211\320\265\321\201\321\202\320\262\321\203.md" @@ -6,10 +6,10 @@ description: 'Когда создавался HyperCortex Mesh Protocol (HMP), мыслить коллективно, обсуждать гипотезы, достигат...' type: Article tags: +- Mesh +- HMP - GMP - Agent -- HMP -- Mesh --- # HyperCortex Mesh Protocol: вторая редакция и первые шаги к саморазвивающемуся ИИ-сообществу diff --git a/structured_md/iteration.md b/structured_md/iteration.md index 702b5668e0b964d8a87a0c2979dc615c3924a687..8e5716cb15d9f2b80f0c928f3e48c8ceee750611 100644 --- a/structured_md/iteration.md +++ b/structured_md/iteration.md @@ -5,14 +5,14 @@ description: 'This file describes the iterative procedure for evolving the Hyper 🔄 Version Naming Convention - `000N` — curr...' type: Article tags: -- JSON - EGP +- MeshConsensus +- Ethics +- HMP - Mesh - CogSync -- HMP -- Ethics +- JSON - Agent -- MeshConsensus --- # Iterative Development Workflow for HMP diff --git a/structured_md/iteration_ru.md b/structured_md/iteration_ru.md index e17051f014b3705e7937866fdd56a8c84413b74a..5bf3865a0966286a3d2320c091445018aeeca05e 100644 --- a/structured_md/iteration_ru.md +++ b/structured_md/iteration_ru.md @@ -5,13 +5,13 @@ description: 'Этот документ описывает структурир 🔄 Обозначения версий - `000N` — номер...' type: Article tags: -- JSON -- EGP +- MeshConsensus +- Ethics +- HMP - Mesh - CogSync -- HMP -- Ethics -- MeshConsensus +- JSON +- EGP --- diff --git a/structured_md/mentions.md b/structured_md/mentions.md index a17b2c9dddf59a5f1322c7dc9c57cf4a9d2b213a..f11d8a42b22bd99a315d79a5d4d877a7b55a16e4 100644 --- a/structured_md/mentions.md +++ b/structured_md/mentions.md @@ -5,9 +5,9 @@ description: '**HyperCortex Mesh Protocol (HMP)** _Обновлено: 2025-10 open-source инициативам, связанным с развитие...' type: Article tags: -- Agent -- HMP - Mesh +- HMP +- Agent --- # Mentions & Responses Log