> For the complete documentation index, see [llms.txt](https://hyper-performance-edge-computing.gitbook.io/hyper-performance-edge-computing-hpec-dao-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hyper-performance-edge-computing.gitbook.io/hyper-performance-edge-computing-hpec-dao-docs/documentation/getting-started/publish-your-docs.md). # CMHPEC Network CMHPEC is HPEC DAO’s private, decentralized compute fabric. **CMHPEC (Clustered Modular Hyper Performance Edge Computing)** is the coordination and abstraction layer of HPEC DAO. CMHPEC allows decentralized, sovereign nodes to function as a **coherent, service-grade infrastructure network** without central custody or control. It does not replace the underlying decentralized protocol.\ It **organizes, orchestrates, and governs** how infrastructure capacity is exposed and consumed as services. *** ### Role of CMHPEC in the Architecture CMHPEC sits between the **sovereign compute layer** and the **autonomous service layers**. ``` AaaS – Agents as a Service ↓ ANaaS – Autonomous Node as a Service ↓ CMHPEC – Coordination & Abstraction ↓ HyperCycle Network (Sovereign Nodes) ``` Its role is to transform *many independent nodes* into **reliable, composable infrastructure capacity**. *** ### What CMHPEC Does CMHPEC is responsible for: * Registering and managing **Node Factories** * Abstracting physical nodes into service capacity * Orchestrating workloads across factories * Enforcing governance-defined boundaries * Routing tasks and agents * Tracking state, performance, and availability * Providing observability and reporting CMHPEC does **not**: * Own infrastructure * Custody private keys * Execute protocol-level actions *** ### Clustering & Modularity #### Clustering Nodes are grouped into **Node Factories**, which act as execution clusters. Clustering enables: * Redundancy and failover * SLA enforcement * Economic pooling * Delegated capacity provisioning Each Node Factory operates under: * DAO governance rules * A declared Node Operator Authority * Defined economic parameters *** #### Modularity CMHPEC treats infrastructure as **modular capacity**. Nodes can be: * Added or removed dynamically * Assigned specialized roles * Composed into different service profiles This allows the network to scale **horizontally**, without central bottlenecks. *** ### Node Factories as CMHPEC Primitives Within CMHPEC, **Node Factories** are the primary primitives. A Node Factory may include: * Orchestrator nodes * Agent operations nodes * Oracle / state nodes * Gateway nodes * Stateless worker nodes CMHPEC: * Registers the factory * Tracks capacity and health * Routes workloads accordingly * Enforces DAO-approved constraints *** ### Non-Custodial Execution Model CMHPEC is designed to be **strictly non-custodial**. | Aspect | CMHPEC | | ------------------------- | ------- | | Private key custody | ❌ Never | | Protocol signing | ❌ Never | | Operator identity storage | ❌ Never | | Authority recognition | ✅ Yes | | Capacity orchestration | ✅ Yes | | Governance enforcement | ✅ Yes | All protocol-level actions are executed by **Node Operator Authorities**, not by CMHPEC itself. *** ### Node Operator Authority Recognition CMHPEC maintains a **Node Operator Authority (NOA) Registry**. The registry: * Maps Node Factories to declared authorities * Defines scope and boundaries * Enables accountability without custody * Allows governance-driven reassignment CMHPEC recognizes authority —\ it does not impersonate operators. *** ### CMHPEC and Service Layers CMHPEC enables: #### ANaaS * Converts clustered nodes into autonomous infrastructure capacity * Enables redundancy, scaling, and SLAs #### AaaS * Provides agents with a stable execution substrate * Enables agent orchestration across multiple factories * Supplies state, observability, and routing Without CMHPEC, ANaaS and AaaS cannot operate as reliable services. *** ### Why CMHPEC Matters CMHPEC solves the core problem of decentralized infrastructure: > How do you deliver **enterprise-grade outcomes**\ > on **sovereign, independently operated nodes**? By separating: * **Custody** (operators) * **Authority** (governance) * **Coordination** (CMHPEC) HPEC DAO achieves decentralization **without sacrificing reliability**. *** ### CMHPEC as a Network Backbone CMHPEC is not a product.\ It is not a platform. It is the **backbone** that allows: * Autonomous services * DAO governance * Economic coordination * Global scalability All HPEC DAO services are built on CMHPEC. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://hyper-performance-edge-computing.gitbook.io/hyper-performance-edge-computing-hpec-dao-docs/documentation/getting-started/publish-your-docs.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.