> For the complete documentation index, see [llms.txt](https://support.ayahq.com/user/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.ayahq.com/user/community/eligibility-guidelines.md). # Eligibility Guidelines ### **Introduction** To uphold the highest standards of participation, we meticulously evaluate community eligibility to ensure meaningful contributions and engagement. This document provides comprehensive guidance for communities to assess their eligibility before submitting an application to AyaLabs. We encourage prospective communities to carefully review these criteria to ensure alignment with our mission and operational framework. *** ### **πŸš€ 1. Mandatory Eligibility Criteria** A community must satisfy all of the following five fundamental requirements to qualify for participation. #### **1.1 Active Engagement & Meaningful Contributions** A robust technology community is characterized by continuous engagement, collaborative interactions, and substantial contributions. βœ… **Requirements:** * Regular and **high-quality technical discussions, knowledge sharing, and problem-solving engagements**. * Demonstrated contributions to **code development, research, or open-source projects**. * Engagement spanning multiple platforms such as **Discord, GitHub, forums, twitter and the official platform**. ❌ **Disqualifiers:** * Minimal or infrequent participation from members. * One-directional communication dominated by administrators with little interaction. * Focus primarily on hype-driven discussions rather than substantive technical collaboration. #### **1.2 Technical Expertise & Knowledge Exchange** We prioritizes communities with a solid technical foundation that actively support learning and knowledge dissemination. βœ… **Requirements:** * Routine **technical deep-dives, AMAs, and workshops** covering relevant topics. * Members actively share **code, research papers, technical blogs, and analytical insights**. * Established history of **open-source contributions, prototype development, and real-world implementations**. ❌ **Disqualifiers:** * Discussions lack depth and revolve around non-technical or superficial content. * No evidence of real-world application, experimentation, or deployment. #### **1.3 Integration with the Broader Ecosystem** A credible community does not operate in isolation but engages meaningfully within the wider technology landscape. βœ… **Requirements:** * Active collaboration with **DAOs, developer networks, research institutions, or technology consortiums**. * Members participate in **external projects, hackathons, conferences, and public repositories**. * Presence of respected **engineers, industry leaders, or researchers** within the community. ❌ **Disqualifiers:** * Limited to a single communication channel without broader industry engagement. * No established partnerships, affiliations, or interactions with external stakeholders. #### **1.4 Well-Defined Contribution Pathways** Communities must facilitate an inclusive, transparent, and structured approach for members to participate and contribute. βœ… **Requirements:** * Comprehensive **onboarding guides, technical documentation, and contribution guidelines**. * Clearly delineated roles for various contributors, including **developers, designers, researchers, and product strategists**. * Defined frameworks for **contribution tracking, project assignments, and member recognition**. ❌ **Disqualifiers:** * No structured approach to welcoming and integrating new contributors. * Lack of clear documentation, participation guidelines, or mentorship structures. #### **1.5 Longevity & Sustainability** We value communities with a track record of resilience and long-term commitment to innovation. βœ… **Requirements:** * Proven operational history of **at least one year** with a consistent engagement trajectory. * Demonstrated adaptability through **market cycles, leadership transitions, or technological shifts**. * A **roadmap, financial sustainability plan, or structured operational model** to ensure continuity. ❌ **Disqualifiers:** * Recently formed communities with minimal track record. * Existence primarily tied to hype cycles (e.g., NFT speculation, airdrop incentives). * No long-term strategic plan for growth and sustainability. *** ### **πŸš€ 1.6 Governance, Leadership, & Mission Integrity** A strong community must have credible leadership and a well-defined governance model to ensure sustainability and long-term success. βœ… **Requirements:** * Clearly established **governance model**, which may be either centralized or decentralized, ensuring leadership credibility and mission integrity. * Leadership, whether centralized or decentralized, must demonstrate a **clear mission, transparency, and credibility** in decision-making processes. * Founding members or leadership teams should have a **proven track record** of commitment to the community’s objectives and long-term vision. ❌ **Disqualifiers:** * Leadership lacks credibility, transparency, or fails to communicate a clear mission. * Lack of financial transparency and strategic oversight. *** ### **πŸ›  2. Additional Evaluation Factors (Highly Recommended)** While the following criteria are not mandatory, communities exhibiting these attributes significantly enhance their credibility and competitive edge. #### **2.1 Innovation & Demonstrated Impact** * A track record of **successful research initiatives, technical implementations, or open-source contributions**. * Projects emerging from the community have **achieved real-world adoption, external funding, or scalability**. * Contributions are **recognized, cited, or extended by external communities or industry stakeholders**. 🚨 **Red Flags:** * No tangible output from community initiatives. * Engagement centered solely on theoretical discussions without execution. #### **2.2 Cross-Community Collaboration** * Active participation in **partnerships with DAOs, research organizations, startups, institutions or global technology initiatives**. * Regular involvement in **joint events and interdisciplinary projects**. * Attraction of domain experts, advisors, or thought leaders from various sectors. 🚨 **Red Flags:** * Limited external visibility and isolated ecosystem presence. * No history of collaboration or participation in broader technology forums. #### **2.3 Financial Support & Incentive Structures** * Access to **grants, sponsorships, or treasury funds** to support project development. * Well-defined **career advancement opportunities** for members and contributors. * Incentive models designed to **retain active members and sustain long-term contributions**. 🚨 **Red Flags:** * No structured incentive framework for rewarding contributions. * Absence of financial planning for sustainability and growth. *** To qualify for AyaLabs, a community **must satisfy all five mandatory criteria**. A strong application is further reinforced by demonstrating excellence in the **additional evaluation factors**. Communities meeting these standards are encouraged to apply and join AyaLabs’ network of forward-thinking developers, researchers, and innovators. πŸš€ --- # 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://support.ayahq.com/user/community/eligibility-guidelines.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.