> For the complete documentation index, see [llms.txt](https://illuminance.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://illuminance.gitbook.io/docs/the-role-of-the-participant-in-the-ecosystem/what-a-person-does-in-illuminance/general-principle-of-participation.md). # General Principle of Participation The Illuminance ecosystem is designed to provide participants with different levels of involvement, allowing each person to choose a role that aligns with their goals and experience. There is no fixed path.\ Instead, the system offers a structured progression where each level builds on the previous one. #### The Investor Level The investor is the entry point into the system. At this stage, the participant: * funds their balance * activates capital * connects to the system * observes how the infrastructure operates * receives results The focus here is not on theory, but on practical experience. The participant does not: * trade manually * analyze the market * make trading decisions * manage strategies All operational processes are handled by the system. At this level, the participant develops understanding, builds trust, and gains their first experience with the ecosystem. *** #### The Active Participant After gaining experience, some participants begin to engage more actively. This typically happens when a person: * understands how the system works * sees consistent results * gains confidence At this stage, the participant may: * share their experience * explain the system to others * invite new participants * build an initial network This is not a requirement, but a natural extension for those who want to grow within the ecosystem. Activity unlocks additional opportunities, including access to growth programs and expanded income potential. *** #### The Leader Level At the leadership level, the participant moves beyond individual activity and begins to build a structured team. The leader: * guides and supports others * helps participants understand the system * develops and manages a team * works with growing volume and structure Leadership is based on clarity, understanding, and personal example, rather than pressure or sales tactics. At this stage, the participant gains access to: * career infrastructure * bonus programs * management tools * scalable income through team growth *** #### The Regional Level At the highest level, participation becomes strategic. A regional leader: * develops the ecosystem within a specific region * works with large structures * interacts with the company * contributes to overall system expansion Here, growth is no longer personal — it becomes systemic and large-scale. The participant takes on a role within the broader architecture of the ecosystem. *** This structure allows each participant to progress naturally within the system, moving from initial involvement to scalable growth based on their level of engagement and ambition. --- # 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://illuminance.gitbook.io/docs/the-role-of-the-participant-in-the-ecosystem/what-a-person-does-in-illuminance/general-principle-of-participation.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.