> For the complete documentation index, see [llms.txt](https://docs.engma.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.engma.io/ravid/overview.md). # Overview RAVID is not a single algorithm. It is a coordination framework where multiple independent algorithms run concurrently, each governing a different dimension of the system (networking, routing, rotation, placement, storage, proofs), and are synchronized through shared state and timing.\ \ RAVID does not assume infrastructure is fixed or centrally controlled. Network routes, running workloads, and where data is stored are expected to change over time. Coordination focuses on managing identity, access, and movement across these parts without relying on static endpoints or permanent roles. RAVID is designed to layer into existing systems gradually, avoiding full replacements or forcing every participant to adopt the same setup. RAVID keeps day-to-day coordination separate from verification and settlement. High-volume coordination and execution happen off chain, while verification and economic enforcement are handled by an external trust system. In Ethereum-aligned deployments, Ethereum is used to verify cryptographic results, record commitments, and apply incentives or penalties, without taking part in coordination or execution. This separation allows the system to stay flexible and private, while relying on a stable and neutral layer to enforce outcomes when needed. --- # 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://docs.engma.io/ravid/overview.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.