> For the complete documentation index, see [llms.txt](https://docs.ternoa.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ternoa.network/learn/caps-token/governance-and-proposals.md).

# Governance & Proposals

CAPS plays a role in Ternoa blockchain governance.

The **Democracy module** manages the administration of the general stakeholders' vote. Ternoa allows CAPS holders to be custodians of the network and to have decision-making power regarding blockchain governance. Blockchain governance includes developments, partners, protocols, etc.

There are two different queues to which a proposal can be added before it becomes a referendum:

1. **The proposal queue,** which comprises all public proposals
2. **The external queue** is comprised of a single proposal that comes from one of the external origins (such as a collective group).

At each launch period, a referendum is created from a proposal taken in turn from the proposal queue or from the external queue. Any CAPS holder in the system can vote on referendums. The voting system uses a fixed-time vote by allowing the token holder to fix his or her conviction behind the vote. The conviction dictates how long the tokens are locked for, as well as the multiplier that scales the power of the vote.


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.ternoa.network/learn/caps-token/governance-and-proposals.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.