> For the complete documentation index, see [llms.txt](https://docs.symm.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.symm.io/contract-documentation/symmio-perps-v0.8.4/facets.md). # Facets ### Overview Facets serve as modular units within the Diamond architecture. Their design allows for isolated updates to specific areas of the system without necessitating a full redeployment of the contract. This modularity is key to maintaining system flexibility and ensuring that enhancements can be applied with minimal disruption. *** ### Functionality and Implementation Each facet is responsible for managing a distinct segment of the system’s functionality. The corresponding implementation contract handles the logic, ensuring that: * Facets can adjust the Diamond’s storage in a targeted manner. * Isolated updates are made possible, reducing the risk of widespread system impact during modifications. * The separation of logic and storage responsibilities streamlines both development and troubleshooting. The following sections will delve into the specifics of SYMM’s facet contracts, outlining the functions within each and how they interact with the Diamond’s core architecture. *** --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.symm.io/contract-documentation/symmio-perps-v0.8.4/facets.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.