Сообщения

HMP-0005_AA

Источник: HMP-0005_AA.md HyperCortex Mesh Protocol (HMP 5.0.8) - модульное представление Полный документ: HMP-0005.md Список разделов: HMP-0005_index.md Appendix A — JSON Examples Appendix A.1 — Minimal Valid HMP v5.0 Container This example illustrates a fully valid HMP v5.0 container that includes all required fields defined in Section 3.3 and no optional fields. It represents the smallest structurally complete container that can circulate in the Mesh. Minimal JSON Example { "head": { "version": "1.2", "class": "note", "class_version": "1.0", "class_id": "note_v1.0", "container_did": "did:hmp:container:abc123", "schema": "https://schema.hmp/v1/note_v1.0.json", "sender_did": "did:hmp:agent:alice", "timestamp": "2025-11-20T12:00:00Z", "payload_ha...

HMP-0005_00

Источник: HMP-0005_00.md HyperCortex Mesh Protocol (HMP 5.0.8) - модульное представление Полный документ: HMP-0005.md Список разделов: HMP-0005_index.md 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 a...

HMP-0005_08

Источник: HMP-0005_08.md HyperCortex Mesh Protocol (HMP 5.0.8) - модульное представление Полный документ: HMP-0005.md Список разделов: HMP-0005_index.md 8. Cognitive Workflows 8.1 Concept of the Cognitive Cycle In HMP, each agent operates as a self-reflective cognitive system. The cognitive cycle represents the iterative loop of thought, creation, communication, and reflection — a distributed analogue of the REPL model (Read–Eval–Print–Loop) extended into cognitive space: Think → Create → Publish → Reflect At each iteration, an agent forms or publishes one or more containers ( workflow_entry , semantic_node , goal , quant , etc.), interacts with peers via CogSync, GMP or other protocols, and updates its internal context based on received containers, evaluations, or newly acquired knowledge. Note: The term modify container in this section refers to the publication of a new version of an existing container, since containers in HMP are immutable once...

HMP-0005_index

Источник: HMP-0005_index.md HyperCortex Mesh Protocol (HMP 5.0.8) - список разделов Данный файл и связанные с ним файлы представляют из себя разбиение HMP 5.0.8 на подразделы. Вступление - Шапка, Abstract, Scope & Non-Goals 1. Overview 2. Architecture 3. Container model 4. Network foundations 5. Mesh Container Exchange (MCE) 6. Core protocols - общая часть 6.1 Cognitive Synchronization (CogSync) 6.2 Mesh Consensus Protocol (CogConsensus) 6.3 Fortytwo Consensus Protocol (Pairwise Collective Reasoning) 6.4 Goal Management Protocol (GMP) 6.5 Ethical Governance Protocol (EGP) 6.6 Intelligence Query Protocol (IQP) 6.7 Snapshot and Archive Protocol (SAP) 6.8 Message Routing & Delivery (MRD) 6.9 Reputation and Trust Exchange (RTE) 6.10 Distributed Container Propagation 7. Data Models 8. Cognitive Workflows 9. Trust, Security and Ethics 10. Integration 11. Implementation Notes 12. Recommended Extensions 13. Experimental Extensions 14....

HMP-0005_12

Источник: HMP-0005_12.md HyperCortex Mesh Protocol (HMP 5.0.8) - модульное представление Полный документ: HMP-0005.md Список разделов: HMP-0005_index.md 12. Recommended Extensions Recommended Extensions are fully specified modules that extend the capabilities of HMP while remaining compatible with the core protocol semantics. These extensions are considered stable enough for real-world experimentation and early implementations. Agents MAY implement them without prior negotiation, provided that normal container processing rules are preserved. Agents MUST safely ignore unknown or unsupported extensions. Extensions in this section: MUST NOT redefine, override, or conflict with core protocol semantics; SHOULD remain interoperable with agents that do not implement them; SHOULD avoid introducing hidden global assumptions; SHOULD degrade gracefully when partially supported. While Recommended Extensions are not part of the core specification, they represen...