> For the complete documentation index, see [llms.txt](https://veme-master.gitbook.io/dao/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://veme-master.gitbook.io/dao/3.-organizational-structure/3.2-proposals.md).

# 3.2 Proposals

The above actors can vote on a variety of proposals submitted by community members, VEME the company, contractors, or the sub DAOs, which govern different parts of the ecosystem to keep the ecosystem moving with agility. Below are some of the relevant proposals needed in order to govern a DAO such as the VEME DAO at scale.

**Treasury & monetary policy proposals**

* Bringing in the capital by selling VEME NFTs to aligned investors or partners; effectively diluting the shares in the VEME ecosystem.&#x20;
* Rebalancing of assets in the treasury to decrease market risk.&#x20;
* Proposed monetary policy adjustment for VeFi staking/bonding, Voltage fee mechanisms, or DAO Launchpad fee mechanisms. These proposals are signed off to The Development DAO for review, implementation, and final signage of the VEME DAO.

**Business opportunity execution proposals**

If a company, another DAO, or a pod in the VEME ecosystem encounters an opportunity involving the VEME ecosystem, one can submit a proposal to receive initial funding, grant, or loan, to act upon that opportunity. This brings value back either functionally and/or monetarily.

Examples of business opportunities could be:

* Applying ecosystem mechanics like Voltage to solve a specific legal problem in a niche sector.&#x20;
* Applying VeFi to collateralize a specific NFT collection.&#x20;
* Assisting a startup to launch their DAO through VEME’s DAO Launchpad.

Depending on whether it's a grant or loan, the DAO executes the contract accordingly. A pitch is suggested to the VEME DAO to increase a successful funding round.

In VEMEs DAO future advancements, a specific pod could take over this function to fund and pro-actively curate potential business opportunities eligible for funding.

**Marketing or management related proposals**

Since the DAO is basically a business-oriented organization, it needs to secure interest in the projects it's governing and involved in to increase exposure and drive on top of organic adoption. The marketing proposals are related to events, exposing use cases to certain industries, and bringing the community together. Management proposals are focused on optimizing the HR levels that operate on the DAO; further streamlining its organizational operations.

**Protocol integration & advancement proposals**

Ecosystem integrations can be submitted and executed by any partner looking to expand upon the already existing tech stack in VEME’s product suite.

Examples of protocol integrations can be:

* Bridging to different protocols/chains.&#x20;
* Integrating with particular DEX infrastructure.&#x20;
* Building specific interfaces for VeFi, Voltage, and the DAO Launchpad.

Core ecosystem components of VEME’s product suite are governed by The Development DAO: a pod taking ownership of curating grander ecosystem-level advancements. The community, partners, or VEME, or the company itself, can submit protocol-level advancements to the pod. The pod holds the keys to the core infrastructure. The Development DAO expands through development community participation over time. More about The Development DAO in the next section.

Examples of protocol level proposals can be:

* Re-architecturing blockchain level tech stack to optimize performance, i.e. ZK-Snarks.&#x20;
* New VeFi bonding, staking mechanics.&#x20;
* Voltage improvements on the smart-contract layer, allowing for new use cases to be fulfilled.


---

# 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://veme-master.gitbook.io/dao/3.-organizational-structure/3.2-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.
