HMP-0005_07

Источник: HMP-0005_07.md

HyperCortex Mesh Protocol (HMP 5.0.8) - модульное представление

• Полный документ: HMP-0005.md
• Список разделов: HMP-0005_index.md

---

7. Data Models

7.1 Unified Container Model

All data within the HMP network are represented as containers — atomic, signed structures described in Section 3 (Container Model).
Containers provide a unified format for storing, verifying, and propagating cognitive, ethical, and network-level objects.
Each container:

• contains a mandatory header (head) with signatures, TTL, DID identifiers, and other general information about the container;
• includes the meta section (cognitive coordinates, provenance, abstraction levels, and axes);
• includes the payload section (main content);
• and the related section — a set of lists with direct references to other containers forming a proof-chain;
• may include evaluations and referenced-by blocks, which are not part of the signed payload and reflect social activity, reverse references, and peer assessments;
• may also include a relay_chain block, allowing agents to trace the propagation path of the container under Message Routing & Delivery (MRD).

This structure ensures atomicity, immutability, and a verifiable lineage of every unit of meaning, while allowing flexible schema extensions without breaking compatibility.

---

7.2 Container Classes

Containers are categorized by their purpose and by the protocols in which they are used (see Section 6).
The following table lists the main container classes defined in the HMP v5.0 specification.

Category	Container classes	Description / usage
Network Layer	peer_announce, peer_query	Node discovery and capability advertisement within the DHT.
Mesh Container Exchange (MCE)	container_index, container_request, container_response, container_delta, container_ack, referenced-by_exchange, evaluations_exchange	Replication, querying, acknowledgment of received containers, and exchange of reverse links and evaluations.
Cognitive Metastructure (CogSync)	abstraction, axes	Define hierarchical and coordinate dimensions of knowledge, forming the agent’s cognitive map.
Knowledge & Reasoning	diary_entry, semantic_node, semantic_index, semantic_edges, semantic_group, tree_nested, tree_listed, sequence, event, quant	Units of cognitive diaries and semantic graphs. The subclass definition is used for explicit conceptual definitions.
Consensus (CogConsensus)	vote, consensus_result	Voting containers and aggregated binary consensus results.
Collective Reasoning (Fortytwo Protocol)	fortytwo_round, fortytwo_evaluation, fortytwo_round_result, fortytwo_final_result	Distributed multi-round pairwise comparison, reasoning transparency, and selection of the best solution among many alternatives.
Goal Management Protocol (GMP)	goal, task, workflow_entry	Define goals, decompose tasks, and record reasoning or cognitive workflow steps.
Ethical Governance Protocol (EGP)	ethics_case, ethics_solution, ethical_result	Representation of ethical dilemmas, proposed solutions, and final network-level verdicts.
Intelligence Query Protocol (IQP)	query_request, query_subscription, query_result, summary	Semantic and cognitive queries, subscriptions, and summarized responses.
Snapshot & Archive Protocol (SAP)	archive_snapshot	Persistent snapshots of network or agent states for backup and restoration.
Reputation & Trust Exchange (RTE)	trust	Reputation and trust metrics exchanged between agents.
Message Routing & Delivery (MRD)	—	Defines interaction principles and specialized roles for message delivery, routing, and relay-chain analysis.

Mechanisms of distributed container propagation are not defined as a separate protocol but describe the underlying replication and integrity principles of container exchange.

All container classes defined in HMP v5.0 use the initial semantic version:

• "class_version": "1.0"
• "class_id": "\<class>-v1.0"

If future revisions introduce changes to payload structure or semantics, class_version will be incremented and class_id updated accordingly.

---

7.3 Cognitive and Structural Containers

Containers at the cognitive layer form a semantic graph, where each node and edge has an address and a signature.
The fields meta.abstraction and meta.axes define a container’s cognitive position:

• meta.abstraction describes its level in the hierarchy of knowledge (L1–L5 and beyond) and its ancestors within the abstraction tree;
• meta.axes encodes coordinates in a multidimensional cognitive space, forming a vector of semantic proximity;
• related captures direct links to other containers (in_reply_to, depends_on, extends, etc.);
• referenced-by and evaluations represent the dynamic “social” layer — reverse links and peer feedback.

Together, these blocks form the container’s cognitive signature, enabling agents to perform semantic search, clustering, and cross-context alignment.

---

7.4 Schemas and Validation (JSON Schemas)

Each container class is expected to include a dedicated JSON schema referenced in the schema field.
All schemas are derived from the base structure container-v1.2.json.

In the current specification, schemas are provided as examples within this document, and the URL "schema": "https://mesh.hypercortex.ai/schemas/container-v1.2.json" refers to an external template for validating future implementations and ensuring structural consistency.

• Agents MUST validate containers of supported classes.
• Containers of unknown but formally valid classes MUST NOT be rejected and SHOULD be stored or relayed on request (store-and-forward).
• Schemas are versioned independently from the main specification, allowing experimental or private node-specific extensions without breaking compatibility.

---

7.5 Container Lifecycle

The ttl (Time-to-Live) parameter defines the container’s active lifetime:

• Ephemeral containers (e.g., goal, task, vote) are propagated for a limited period but may still be transmitted on demand if explicitly requested by DID.
• Persistent containers (e.g., semantic_node, definition, archive_snapshot) are retained indefinitely and can be referenced in other proof-chains.

Additional lifecycle elements:

• head.confidence — credibility or confidence score (0 – 1).
• meta.abstraction and meta.axes — cognitive position and provenance.
• related — collection of direct reference links.
• evaluations and referenced-by — auxiliary blocks containing reverse links and peer evaluations.

Together, these fields enable agents to track knowledge evolution, consensus dynamics, and reputation flow across the network.

---

7.6 Summary

Section 7 consolidates all data representations in HMP v5.0 — from low-level network exchanges to high-level cognitive and ethical structures.
Containers act as a universal semantic exchange medium, where every thought, decision, or action is represented as a verifiable, addressable, and inheritable object.

Beyond the core protocols described in Section 6, the network may also employ custom container types and protocols — for example, to build distributed libraries, wikis, repositories, or creative networks based on tree- or chain-structured container graphs.