> For the complete documentation index, see [llms.txt](https://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://docs.intersectmbo.org/intersect-knowledge-base/archive/cardano-governance-archive/key-terms/ratification.md).

# Ratification

{% hint style="danger" %}
**ARCHIVED**

This page has been archived. It's content might be outdated.
{% endhint %}

Ratification refers to a [Governance Action](/intersect-knowledge-base/archive/cardano-governance-archive/key-terms/governance-action.md). A Governance Action gets approved (or ratified) if it reaches the defined [thresholds](/intersect-knowledge-base/archive/cardano-governance-archive/key-terms/threshold.md).

Governance actions are ratified through on-chain voting actions. While different kinds of governance actions have different requirements, ratification always involves two of the three governance bodies (DReps, Constitutional Committee and SPOs), with the exception of a hard-fork initiation, which requires ratification by all governance bodies.

Depending on the type of governance action, an action will be ratified when a combination of the following occurs:

* the Constitutional Committee (CC) approves of the action (the number of 'Yes' votes meets the CC’s threshold)
* the DReps approve of the action (the stake controlled by the DReps who vote 'Yes' meets a certain threshold of the total active voting stake)
* the SPOs approve of the action (the stake controlled by the SPOs who vote 'Yes' meets a certain threshold over the total registered voting stake)

\
The ratification period is the time that elapses between a governance action being submitted and its ratification.


---

# 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://docs.intersectmbo.org/intersect-knowledge-base/archive/cardano-governance-archive/key-terms/ratification.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.