> 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/basics-execution-layer/interactive-blocks.md). # Node Factories “For how HPEC DAO governs participation around Node Factories, see: Governance → Participation Roles → Active Ambassadors.” ## HyperCycle Node Factories inside HPEC (Correct Definition & HPEC Integration) **Node Factories are HyperCycle’s scaling primitive.**\ **HPEC DAO coordinates them.**\ **CMHPEC orchestrates on top of them.** {% embed url="" %} *** ### What Is a Node Factory (HyperCycle Definition) On the **HyperCycle network**, a **Node Factory** is a **protocol-level construct** that enables a Node Operator to instantiate and operate **multiple HyperCycle nodes** under a single factory configuration. A Node Factory: * Is created using a **HyperCycle license** * Operates at a specific **factory level** * Produces **multiple nodes** from one factory * Is bound to a **Node Operator Authority** * Exists natively within the HyperCycle protocol It is **not** a physical machine or cloud cluster. > A Node Factory is how HyperCycle scales nodes efficiently and securely at the protocol level. This enables AI to communicate to other AIs in peer to peer inside the HyperCycle Network. *** ### Node Factories Inside HPEC HyperCycle Protocol \ └─ Node Factories \ └─ Nodes \ ↑ \ CMHPEC Orchestration \ ↑ \ HPEC DAO Governance **A Node Factory is a node-multiplying primitive inside the HyperCycle network.** *** ### Types of Node Factories HyperCycle supports multiple factory types, including: * **Standard Node Factories** (ETH) * **Advanced Node Factory Enclosure (ANFEs)** (BASE) * Future factory classes as defined by the protocol Each factory type: * Is chain-specific * Has defined capacity per level * Produces a fixed number of nodes per license *** ### Node Operator Authority (NOA) Every Node Factory is operated by a **Node Operator Authority**. The Node Operator Authority: * Holds the HyperCycle credentials * Creates and manages Node Factories * Controls node lifecycle * Receives protocol-level rewards HPEC DAO and CMHPEC **never custody keys**.\ They **recognize and coordinate authority**, not replace it. *** ### How HPEC DAO Uses Node Factories (Important Distinction) HPEC DAO **does not redefine Node Factories**. Instead, it: * Coordinates **existing HyperCycle Node Factories** * Aligns them under DAO governance * Routes workloads and services via CMHPEC * Applies economic and service-layer rules **on top** of HyperCycle primitives In other words: > **HyperCycle defines Node Factories.**\ > **HPEC DAO governs how they are used.** *** ### CMHPEC: Orchestration Layer Above Node Factories **CMHPEC** (Composable Modular Hyper Performance Edge Computing) operates **above** HyperCycle Node Factories. CMHPEC: * Does **not create** Node Factories * Does **not alter** HyperCycle protocol rules * Uses Node Factories as **capacity providers** * Orchestrates workloads, services, and agents * Enforces DAO and enterprise policies This preserves: * Protocol purity * Non-custodial operation * Operator sovereignty *** ### Why Node Factories Matter for HPEC Node Factories enable HPEC DAO to: * Scale infrastructure globally * Aggregate capacity across operators * Support ANaaS and AaaS services * Enable regional DAOs * Onboard Web2 users via delegated operation Without Node Factories, **Internet-scale AI infrastructure is not possible**. --- # 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/basics-execution-layer/interactive-blocks.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.