> 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.5/diamond-core-facets.md).

# Diamond Core Facets

## Diamond Core Facets

Facets are a core component of the Diamond architecture. They let functions execute logic against the Diamond's storage. Each facet contract is paired with an implementation contract that holds the facet's logic.

***

#### Overview

Facets are modular units within the Diamond architecture. They allow isolated updates to specific parts of the system without redeploying the entire contract.

***

#### Functionality and Implementation

Each facet manages a distinct segment of the system's functionality. The implementation contract handles the logic, so that:

* Facets can modify the Diamond's storage in a targeted way.
* Updates stay isolated, reducing the risk of system-wide impact during changes.
* Separating logic from storage simplifies development and troubleshooting.

The following sections cover SYMM's facet contracts, 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.5/diamond-core-facets.md?ask=<question>&goal=<user_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.