HMP-0005_01

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

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

1. Overview

1.1 Purpose and scope

The HyperCortex Mesh Protocol (HMP) defines a decentralized cognitive architecture where autonomous agents exchange and evolve knowledge through a unified model of containers, cognitive workflows, and distributed consensus.

Version 5.0 consolidates three foundational layers into a single cohesive framework:

  • Cognitive Layer — defines how meaning is created, reasoned about, and aligned through semantic graphs, goals, and ethical evaluation.
  • Container Layer — introduces a universal data envelope (HMP-Container) for all cognitive objects, ensuring atomicity, immutability, and traceable proof chains.
  • Network Layer — integrates a DHT-based peer-to-peer substrate for decentralized discovery, routing, and propagation of containers.

HMP v5.0 is intended for researchers, engineers, and developers building autonomous or semi-autonomous agents that require: - persistent reasoning and long-term memory; - semantic interoperability across heterogeneous systems; - decentralized consensus on cognitive, ethical, and goal-oriented decisions; - ethical auditability and verifiable transparency in reasoning.

1.2 Core principles

Decentralization.
Every agent in the Mesh acts as an independent cognitive node. No central authority exists — meaning, trust, and governance emerge through local interactions and consensus.

Cognitive Autonomy.
Agents reason, learn, and self-correct independently, while sharing their conclusions via containers that can be verified, endorsed, or refuted by peers.

Containerization.
All data, reasoning traces, goals, and votes are encapsulated in immutable containers with cryptographic signatures. This ensures integrity and consistent verification across the network.

Ethical propagation.
Ethical reasoning is a first-class citizen of HMP. Each decision or goal can be accompanied by ethical justifications and subject to distributed voting.

Proof-Chains and verifiable history.
Each piece of knowledge forms part of a traceable chain (proof_chain) linking back to its origin. Agents can reproduce reasoning paths and audit historical context.

Interoperability and evolution.
The protocol is designed to evolve — cognitive, container, and DHT layers can be independently extended without breaking compatibility.

1.3 Changes since v4.1

HMP v5.0 introduces a major architectural shift toward unified containerization and integrated DHT networking.

Area Change Summary
Data exchange model All messages are now encapsulated in standardized containers (HMP-Container) with metadata, signatures, and versioning.
Networking layer DHT becomes a native component of HMP, enabling distributed discovery, replication, and retrieval of containers.
Consensus model Moved from centralized proposal aggregation to container-linked voting, allowing any container to accumulate votes and reactions.
Trust & security Signatures and proof-chains unify authentication across all layers; snapshot verification includes container linkage.
Workflows workflow_entry containers record cognitive cycles: log inputs, actions, and outputs for each reasoning step, including provenance and derived conclusions. Supports tracking of thought processes across containers, external sources, and reflections.
Structure The specification merges HMP, container, and DHT layers into one cohesive document, simplifying navigation and implementation.

1.4 Terminology and abbreviations

Term Definition
HMP HyperCortex Mesh Protocol — a decentralized cognitive communication standard.
Container Atomic, signed JSON object encapsulating cognitive data and metadata.
WorkflowEntry Container recording a reasoning step or workflow action. Represents a unit of the agent’s cognitive workflow.
CognitiveDiaryEntry Container representing an internal reflection or summarized cognitive state; part of the agent’s cognitive diary.
DHT Distributed Hash Table — the foundational peer-to-peer structure in HMP used for lookup, replication, and data distribution, including node discovery.
NDP Node Discovery Process — a functional layer within the DHT responsible for peer discovery, interest-based lookup, and address advertisement. (Formerly a separate protocol.)
Proof-chain Cryptographic sequence linking containers through fields such as in_reply_to and relation. Enables verifiable semantic lineage.
Cognitive Layer Logical layer handling reasoning, goals, ethics, and consensus mechanisms.
Mesh The collective network of autonomous agents exchanging containers over HMP.
TTL Time-to-live — lifespan of a container before expiration or archival.
Agent Autonomous cognitive node participating in the Mesh via HMP protocols.
Consensus Vote A container expressing approval, rejection, or reaction to another container (used in consensus workflows).
CogSync Cognitive Synchronization Protocol — abstraction for synchronizing cognitive diaries and semantic graphs.
CogConsensus Mesh Consensus Protocol — defines how agents reach agreement on container outcomes.
GMP Goal Management Protocol — governs creation, negotiation, and tracking of goals.
EGP Ethical Governance Protocol — defines moral and safety alignment mechanisms.
IQP Intelligence Query Protocol — standardizes semantic queries and information requests.
SAP Snapshot and Archive Protocol — defines container snapshots and archival mechanisms.
MRD Message Routing & Delivery — specifies routing, addressing, and delivery logic.
RTE Reputation and Trust Exchange — defines reputation metrics and trust propagation.
DID Decentralized Identifier — persistent, verifiable identifier used for agents, containers, or resources within the Mesh.
Payload The primary content of a container — semantic or operational data subject to signing and verification.
Consensus The process by which multiple agents agree on the validity or priority of containers, versions, or ideas.
Lineage A chronological chain of container versions representing semantic continuity and authorship evolution.
Semantic fork A parallel development branch diverging from a previous container version; allows ideas to evolve independently.
Cognitive Graph The emergent graph formed by interlinked containers representing reasoning, debate, and shared knowledge.

Note: Protocols are conceptual abstractions describing how to generate, propagate, and process containers; they are not executable objects themselves.

1.5 Layered view of HMP v5.0

HMP v5.0 is structured into three interdependent layers:

+---------------------------------------------------------------+
|                        Cognitive Layer                        |
|  - Goals, Tasks, Ethical Decisions, Workflows                 |
|  - Consensus, Reasoning, Reflection                           |
+---------------------------------------------------------------+
|                        Container Layer                        |
|  - HMP-Container structure (atomic, signed, versioned)        |
|  - Proof-chains, in_reply_to, and metadata management         |
+---------------------------------------------------------------+
|                         Network Layer                         |
|  - DHT-based peer discovery and propagation                   |
|  - Message routing, caching, offline synchronization          |
+---------------------------------------------------------------+

Each layer operates independently yet seamlessly integrates with the others.
Containers form the boundary of communication: reasoning produces containers, containers propagate over the DHT, and cognition evolves from the received containers.

In essence:
HMP v5.0 transforms the Mesh into a self-describing, self-replicating cognitive ecosystem —
where every thought, goal, and ethical stance exists as a verifiable, shareable container.

Комментарии

Отправить комментарий

Популярные сообщения из этого блога

Habr_Distributed-Cognition

Источник: Habr_Distributed-Cognition.md От OpenCog Hyperon до HyperCortex Mesh Protocol: как устроены децентрализованные когнитивные системы Альтернатива централизованным ИИ: гиперграфы, mesh-взаимодействие и совместное мышление агентов Зачем нужны децентрализованные когнитивные системы? Сегодня интеллектуальные системы чаще всего выглядят как один большой модуль в облаке — LLM, с которым мы общаемся через API или WEB-интерфейс. Но если мы хотим построить действительно автономную интеллектуальную систему (или AGI), то нам потребуется: Смысловая память, а не токены Способность планировать и распределять задачи Этические оценки перед действием И главное: связь с другими агентами, чтобы обмениваться знаниями, достигать согласия и общего понимания. Два проекта, которые решают эти задачи с разных сторон: OpenCog Hyperon (фокус на внутреннюю когницию и гиперграфы) HyperCortex Mesh Protocol (HMP) (сетевой уровень: обмен целями, знаниями, смыслами, совмест...
Read more »

HMP-0005

Источник: HMP-0005.md HyperCortex Mesh Protocol (HMP) Version: 5.0.8 Document ID: HMP-0005 Status: Stable Category: Core Specification Release Date: March 2026 Canonical Repository: https://github.com/kagvi13/HMP Authors: Глеб (GitHub: @kagvi13), Максим Хотинский (Maksim Khotinsky); AI-assisted by ChatGPT (OpenAI) Supersedes: - HMP-0004 v4.1 Summary: HMP v5.0 unifies the cognitive, container, and network layers into a single architecture in which autonomous agents interact through verifiable data containers, using decentralized propagation and semantic search. This version formalizes the container format for the first time, integrates a DHT as the foundational network layer, and introduces a unified scheme for signatures, proofs, and consensus. Abstract The HyperCortex Mesh Protocol (HMP) defines a distributed cognitive framework where autonomous agents cooperate to create, exchange, and align knowledge without centralized control or autho...
Read more »

CHANGELOG

Источник: CHANGELOG.md HyperCortex Mesh Protocol — Changelog HMP-0005 (May 2026) — Core Specification v5.0.8 Encryption and payload integrity clarifications: Clarified head.payload_hash semantics: the hash is computed over the final serialized payload representation (including optional compression and encryption). Unified payload_hash wording across Sections 3.3 and 3.9. Refined hybrid-encryption processing terminology: clarified usage of symmetric session keys and recipient encryption envelopes. Clarified that key_recipient contains an encrypted symmetric session key and may be transmitted openly alongside the container. Improved wording for encrypted container verification and store-and-forward propagation behavior. No semantic changes to the protocol model. No wire-format changes. Fully backward-compatible within the 5.0.x series. HMP-0005 (May 2026) — Core Specification v5.0.7 Extended representations for referenced-by.link...
Read more »