> For the complete documentation index, see [llms.txt](https://flint-rwa.gitbook.io/flintrwa-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://flint-rwa.gitbook.io/flintrwa-docs/technical-architecture/roles.md).

# Roles & Responsibilities

The vault operates with a clear separation of duties across five roles. No single actor controls the full system, which is the point.

## Summary

| Role               | Responsibility                        |
| ------------------ | ------------------------------------- |
| Vault Admin        | Governance and configuration          |
| Curator            | Strategy execution and settlement     |
| Valuation Provider | NAV calculation and submission        |
| Access Manager     | Whitelist / blacklist / compliance    |
| Security Council   | Independent price guardrail oversight |

## Vault Admin

Governs configuration and safety controls. Doesn't run the strategy, sets the parameters within which the Curator operates. Manages fee structures (within on-chain caps), upgrade delays, and proxy settings.

## Curator

The operational brain of the vault. For Flint, this is **9 Summits**.

They deploy capital into lend.xyz / opLend bond positions, accept NAV proposals from the Valuation Provider, call `settleDeposit()` and `settleRedeem()` to process pending batches, and monitor ongoing exposure. Allocation decisions sit with them.

## Valuation Provider

Submits NAV proposals that drive all settlement calculations. Accuracy matters directly here because a wrong NAV affects how many shares are minted, how much users redeem, and how fees are applied. The provider can't push a valuation through alone, it has to be accepted by the Curator first.

## Access Manager

Controls who can interact with the vault. Three modes:

| Mode           | Behavior                                                 |
| -------------- | -------------------------------------------------------- |
| Whitelist      | Only approved addresses can deposit or redeem            |
| Blacklist      | Open to all except explicitly blocked addresses          |
| Sanctions list | Automated compliance screening regardless of active mode |

A Super Operator role exists that bypasses all access restrictions, used for specific operational needs.

## Security Council

Acts as independent oversight. Manages the price-per-share guardrails: on-chain bounds that limit how much the NAV can move between two consecutive updates. If a proposed valuation exceeds those bounds, it's automatically rejected. The Security Council can also propose emergency valuations that bypass guardrails when a legitimate extreme move happens.

***

*Next:* [*Fees*](/flintrwa-docs/technical-architecture/fees.md)


---

# 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:

```
GET https://flint-rwa.gitbook.io/flintrwa-docs/technical-architecture/roles.md?ask=<question>
```

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.