# Core Architecture The foundation of Fightly AI is built on three interconnected layers that work together to deliver security, computing, and economic value. The first layer is the **Compute Layer**, which aggregates CPU resources contributed by participants. Machines of all sizes, from personal computers to large enterprise servers, connect to the network through lightweight clients. These clients verify workloads, allocate resources, and ensure that every transaction is recorded transparently. The second layer is the **Security Layer**, powered by artificial intelligence. This layer acts as a real-time defense system, monitoring all workloads and traffic for suspicious activity. It is designed to act autonomously, preventing malicious processes from spreading across the network. Data from every interaction feeds back into the AI, which refines its detection models continuously. The third layer is the **Economic Layer**, which governs incentives and payments through the $FIGAI token. This layer ensures that contributors are rewarded fairly, that usage fees are distributed efficiently, and that governance decisions can be made transparently by the community. Together, these three layers form the backbone of Fightly AI, creating a structure that is resilient, adaptive, and economically sustainable. --- # Agent Instructions: 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: ``` GET https://fightly-ai.gitbook.io/fightly-ai-whitepaper/core-architecture.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.