# Proposals

Proposals can vary broadly in their stated goals and requests.

* They may ask the community to endorse a specific policy and procedure (e.g. “Should Gitcoin Grants allow VC backed projects?”), or ask the community to build something (e.g. “Building a new software tool” or “Writing improved documentation”).
* They may have no funding requests attached (e.g. “Should we adopt a new Foundation for the DAO”), or make an explicit request for funding (e.g. “We would like to create a workstream focused on building a decentralized architecture for Gitcoin Grants”).

Typically, proposals will fall into one of several categories:

1. Funding proposals : A workstream requests funding from the Gitcoin DAO treasury.
2. Ratification proposals: The community or a workstream asks the community to approve something it wants to do, like issuing matching funds to Gitcoin Grantees at the end of a Grants round.
3. Governance proposals: The community is asked to ratify proposed changes to policy or procedures, like updating the Gitcoin Governance Process document, adopting the Foundation, etc. or the community is asked to vote on structural changes to how the DAO operates.
4. Reallocation proposals: A previously-funded project/Workstream may want to use their approved funds toward net new objectives that were not approved when funding was initially requested. In this case, the project/Workstream would need to receive approval from the community to do so. In the case they are not approved, funds should be sent back to the DAO treasury.

There is currently no discintion between regular proposals and Gitcoin Community Proposals.


---

# Agent Instructions: 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://manual.gitcoin.co/governance-processes/proposals.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.