> 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/affiliate-partnerships-and-license-distribution.md). # Affiliate Partnerships & License Distribution HPEC DAO operates as an **affiliate and ecosystem partner of HyperCycle**. This enables HPEC DAO and its HPEC regional DAOs to: * Onboard Web2 companies and institutions into HyperCycle * Facilitate the acquisition of HyperCycle node licenses and software * Support infrastructure deployment through Active Ambassadors and NOAs * Provide ongoing operational and service-layer integration **How It Works** * Licenses are sold **directly by Active Ambassadors of HPEC** * HPEC DAO does **not** custody licenses, hardware, or infrastructure * Clients may: * Operate their own Node Factories * Delegate operation to [Active Ambassadors](/hyper-performance-edge-computing-hpec-dao-docs/documentation/basics-execution-layer/integrations/participation-roles/active-ambassadors.md) / NOAs * Participate through CMHPEC or DAO-aligned services * A predefined **affiliate fee** is returned to the HPEC DAO treasury **Why This Matters** This model: * Bridges Web2 demand into decentralized infrastructure * Creates a sustainable, non-inflationary DAO revenue stream * Aligns growth incentives between HyperCycle, operators, and governance * Avoids speculative dependency while funding long-term expansion Affiliate revenues are subject to: * DAO transparency standards * Treasury reporting * Governance oversight --- # 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/affiliate-partnerships-and-license-distribution.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.