> For the complete documentation index, see [llms.txt](https://saga-mobile-dao.gitbook.io/codex/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://saga-mobile-dao.gitbook.io/codex/core-team/core-funds.md).

# Core Funds

### **Operations Fund**

* **Purpose:** Covers subscriptions, platform costs, contributor stipends, marketing and ongoing DAO operations.
* **Source of Assets:** Normally from approved budgets via Revenue Staging, Reserve Fund, or the Main Treasury.
* **Management:** Handled by the Core Team. May be divided into sub-accounts by team.

### Revenue Staging

* **Purpose:** Hold incoming revenues and route them as they arrive. May pursue yield strategies.
* **Inflows:** Validator revenue and other Core project revenue.
* **Routing:** When validator revenue arrives, a portion is routed to current destinations; the remainder stays in Revenue Staging and is allocated in the next budget ([see validator rev. flow](/codex/core-team/projects/sagadao-validator.md#validator-revenue-flow)).
* **Spend Rule:** No expenses allowed from this wallet, except validator-related fees.
* **Movement:** Transfers out occur on receipt (for the routed portion) or during the next budget allocation.

### **Reserve Fund**

* **What it is:** Leftover balance from prior budgets; not a locked pool.
* **Use:** Covers gaps and urgent needs.
* **Access:** **Per request**. Each request includes a short budget (scope, amount, justification, expected timeline).
* **Approval:** Reviewed and confirmed by Core before release.
* **Replenish:** Topped up in the next budget cycle if needed.