> 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/integrations/participation-roles/editor.md). # Node Operator Authorities | NOA Are you a HyperAIBox Node Runner ? Check the Role of Node Operators Authorities inside HPEC. A **Node Operator Authority (NOA)** is an individual or DAO-mandated entity responsible for operating infrastructure within the HPEC DAO network. Node Operators provide the **human authority** required to run decentralized infrastructure safely, autonomously, and accountably. HPEC DAO is non-custodial by design.\ As a result, **Node Operators retain control of protocol credentials** while operating under DAO-defined rules. *** ## Are you a Hyper AI Box Node Runner? We Started as HyperAIBox Node Runners inside HPEC . {% embed url="" %} ### Why Node Operators Exist Decentralized infrastructure cannot rely on: * Centralized DevOps teams * Platform-custodied keys * Automated protocol signing Node Operators AUthorities inside HPEC exist to: * Maintain sovereignty of infrastructure * Preserve human accountability * Execute protocol-level actions safely * Act under explicit DAO or regional mandate They are **operators by authority**, not owners by default. *** ### NOA | Responsibilities Node Operators may be responsible for: * Operating HyperCycle nodes * Maintaining uptime and availability * Managing node health and lifecycle * Executing protocol-level actions * Declaring and maintaining Node Factories * Enforcing governance boundaries * Responding to escalations from agents Actual scope depends on the **Node Operator Authority** granted. *** ### NOA vs Infrastructure Provider These roles may overlap, but they are distinct. #### Infrastructure Providers Provide: * Physical or virtual nodes * Capital and licenses * Capacity and reliability Examples: * Ambassadors (Node Factory owners) * Delegators (HyperAIBox owners) #### NOA | Node Operators Authorities Provide: * Operational authority * Protocol execution * Governance compliance A single entity may act as both — but the roles are **logically separated**. *** ### Dual-Role Node Doctrine HPEC DAO supports **Dual-Role Nodes**. A Dual-Role Node is a HyperAIBox that simultaneously: * Operates as a **sovereign HyperCycle node** * Provides **delegated capacity** to CMHPEC services These roles: * Share physical hardware * Remain operationally and logically separated * Are governed independently CMHPEC orchestrates capacity —\ it does **not** custody keys or impersonate operators. *** ### Node Operator Authority (NOA) A **Node Operator Authority (NOA)** is a formally recognized mandate that allows a Node Operator to act on behalf of a CMHPEC domain. #### What an NOA Defines * Which Node Factories may be operated * Scope of protocol-level actions * Applicable governance body * Authority status (active, paused, revoked) #### What an NOA Does Not Do * Transfer ownership * Grant custody to CMHPEC * Override DAO governance Authority is **declared and governed**, not embedded in software. *** ### Authority Recognition Model CMHPEC maintains a **Node Operator Authority Registry** that: * Records declared authorities * Maps authorities to Node Factories * Enforces scope boundaries * Enables governance-driven reassignment CMHPEC recognizes authority —\ all execution is performed by the operator. *** ### Custody & Accountability | Aspect | Node Operator | CMHPEC | | ---------------------- | --------------------- | ------- | | Private keys | ✅ Held by operator | ❌ Never | | Protocol signing | ✅ Manual or delegated | ❌ Never | | Infrastructure custody | ✅ Operator / provider | ❌ Never | | Capacity orchestration | ❌ | ✅ | | Governance enforcement | Shared | Shared | This model ensures: * Zero protocol custody risk * Clear human accountability * DAO-enforced boundaries *** ### Governance & Revocation Node Operator Authority: * Is granted by DAO or regional governance * Can be modified, suspended, or revoked * Does not imply permanent control * Exists solely as an operational mandate Operators act **on behalf of the DAO or domain**, not as platform agents. *** ### Summary Node Operators are the **human execution layer** of HPEC DAO. They: * Retain sovereignty * Act under governance * Enable autonomous systems to function safely * Provide accountability without centralization > CMHPEC governs authority, not keys.\ > Operators act by mandate, not by platform custody. --- # 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/integrations/participation-roles/editor.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.