> For the complete documentation index, see [llms.txt](https://turboflow.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://turboflow.gitbook.io/whitepaper/turboflow/growth.md). # GROWTH TurboFlow’s growth layer is designed to support broader participation across the platform — not only through user activity, but also through referrals, partnerships, and campaign-based expansion. This section brings together the main programs that help users, communities, and partners grow alongside Turboflow. ### What you’ll find here #### Referral Program A user growth program that allows participants to invite others to TurboFlow and earn based on eligible platform activity. #### Affiliate Program A broader collaboration framework for agents, communities, partners, and growth channels interested in building with TurboFlow. #### Campaigns Platform activities and special initiatives designed to drive participation, visibility, and community engagement over time. ### Why it matters TurboFlow’s growth programs are designed to make platform expansion more open, more collaborative, and more participation-driven. Whether through referrals, partnerships, or campaigns, these programs help connect user growth with broader ecosystem momentum. --- # 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://turboflow.gitbook.io/whitepaper/turboflow/growth.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.