> 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/illuminance-technological-architecture/how-the-system-works-internally.md). # How the System Works Internally To fully understand Illuminance, it is important to move beyond the economic model and examine what underpins it — the technological architecture. It is the technology that enables everything else: * processing large volumes of data * identifying market inefficiencies * making decisions without human involvement * scaling the system without loss of efficiency If the economic layer answers the question of where value comes from, the technological layer explains why the system is able to function at all. Illuminance is not a single server or a standalone program.\ It is a distributed system composed of multiple interconnected layers, each performing a specific role within a unified structure. This architecture allows the system to operate continuously, adapt to increasing scale, and maintain performance under growing demand. *** The technological architecture forms the foundation of the entire ecosystem, enabling efficiency, scalability, and consistent system performance. --- # 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/illuminance-technological-architecture/how-the-system-works-internally.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.