> 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/help-center/readme.md). # Help Center ## Help Center ### Overview HPEC is a **living, evolving decentralized network**. Because the network, services, and governance continue to evolve, **static documentation alone is not sufficient** for operator support. For this reason, the primary Help Center for HPEC is our **community Discord**. > Support, coordination, and governance happen where the network lives: with the operators. *** ### Primary Support Channel: Discord All support, questions, and coordination are handled through the **HPEC Discord server**. In Discord you can: * Ask technical and operational questions * Get help from core contributors and fellow node runners * Raise support tickets * Participate in governance discussions * Join live voice meetings This ensures: * Transparency * Peer-to-peer support * Shared learning across the network *** ### How to Get Help #### 1. Join the Discord 👉 **Join the HPEC Discord**\ Once inside, please: * Read the welcome and rules channels * Introduce yourself as a HyperAIBox node runner * Follow the instructions to raise a support ticket if needed *** #### 2. Raise a Ticket For: * Node issues * Bootstrap problems * Network participation questions * Service eligibility questions Open a **support ticket** in Discord so the right contributors can assist you. Tickets help us: * Track recurring issues * Improve documentation * Identify network-level improvements *** ### Live Support & Community Calls #### Weekly Operator Call We host a **weekly community meeting every Thursday** on Discord (voice chat). These sessions are used for: * Network updates * Governance discussions * Operator questions * Open technical conversations * Roadmap alignment No preparation required — just join and listen or participate. *** #### Peer-to-Peer Meetings For more complex topics, we may: * Schedule **1:1 or small group P2P calls** * Use Google Meet or Discord voice * Coordinate directly through Discord tickets These sessions are collaborative, not hierarchical. *** ### Support Philosophy HPEC support follows a simple principle: > **The network is built by operators, for operators.** There is no private support desk, no hidden escalation paths, and no privileged operators. If an issue matters, it is discussed **in the open**, documented, and improved collectively. *** ### Summary * 📍 **Discord is the Help Center** * 🎫 Tickets are handled openly * 🗣 Weekly live calls every Thursday * 🤝 Peer-to-peer support by design * 🧠 Documentation evolves from real conversations Welcome to a network that grows by participation, not tickets alone. --- # 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/help-center/readme.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.