> 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/economic-framework/regional-dao-framework.md). # Regional DAO Framework Regional HPEC DAOs own and operate Node Factories by delegation — not by centralization. ### Role of Regional HPEC DAOs Regional HPEC DAOs exist to **bridge Web2 users into the Internet of AI**. They act as: * **Infrastructure operators** * **Active Ambassadors** * **Node Operators** * **Regional representatives of HPEC DAO** This allows individuals and organizations to participate **without needing to understand or operate HyperCycle infrastructure directly**. *** ### What Regional HPEC DAOs *Do* Regional HPEC DAOs may: * **Create, own, and operate HyperCycle Node Factories** * Act as **Node Operators** under HPEC DAO governance * Operate Node Factories **on behalf of clients** * Aggregate multiple users into shared infrastructure * Provide onboarding, support, and education * Hold legal responsibility where required * Participate in global HPEC DAO governance In this role, Regional DAOs function as **trusted operators**, not centralized custodians. *** ### Delegated Operation Model (Web2 → Web3 Bridge) For many participants: * Running nodes directly is not feasible * Managing protocol operations is too complex * Legal clarity is required Regional HPEC DAOs solve this by: * Operating Node Factories **by mandate** * Acting as **Active Ambassadors** inside HPEC DAO * Representing client interests transparently * Routing rewards and outcomes according to DAO rules Clients do not lose sovereignty — they **delegate execution**, not ownership of outcomes. *** ### What Regional HPEC DAOs *Do Not* Do Regional HPEC DAOs: * ❌ Do not custody **client private keys** without mandate * ❌ Do not override HPEC DAO governance * ❌ Do not centralize protocol decision-making Authority is **granted, scoped, and revocable** by governance. *** ### Relationship to Node Operator Authority (NOA) When operating Node Factories on [CMHPEC Network](/hyper-performance-edge-computing-hpec-dao-docs/documentation/getting-started/publish-your-docs.md), a Regional DAO: * Is registered as a **Node Operator Authority** * Acts under a defined scope * Is accountable to HPEC DAO governance * Can be audited, reassigned, or revoked This preserves: * Decentralization * Accountability * Human responsibility * Network integrity *** ### Why This Model Matters This structure enables: * Web2 users to join the Internet of AI * Infrastructure growth without technical barriers * Regional legal compliance * Scalable global expansion * DAO-aligned execution at every layer HPEC DAO does not exclude non-technical participants.\ It **absorbs them safely through delegated operation**. --- # 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/economic-framework/regional-dao-framework.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.