> For the complete documentation index, see [llms.txt](https://budgetcommittee.docs.intersectmbo.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://budgetcommittee.docs.intersectmbo.org/archive/drep-knowledge-journey/stage-2-drep-role-in-the-budget-process.md).

# Stage 2: DRep Role in the Budget Process

Objective: Learn the specific responsibilities of DReps within the budget cycle.

## Content:

#### DRep Role in the budget process

In the Cardano budget process, DReps (Delegated Representatives) play a crucial role in budget approval and oversight. Their responsibilities include:

1. **Reviewing Budget Proposals**: DReps examine proposed budgets, ensuring alignment with Cardano’s strategic goals and community priorities.
2. **Providing Feedback**: They engage in feedback cycles with the Budget Committee to refine proposals, particularly during socialization stages.
3. **Voting on Final Approval**: DReps participate in voting to approve or reject budgets and other financial actions.
4. **Monitoring Quarterly Reports**: DReps review quarterly financial reports to maintain accountability and transparency for approved spending.

This process ensures that DReps represent community interests and uphold the transparency of Cardano’s financial planning.


---

# 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://budgetcommittee.docs.intersectmbo.org/archive/drep-knowledge-journey/stage-2-drep-role-in-the-budget-process.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.