> For the complete documentation index, see [llms.txt](https://committees.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://committees.docs.intersectmbo.org/intersect-product-committee/committee-outcomes/2025-cardanos-roadmap.md).

# 2025 Cardano's roadmap

The Cardano Product Committee is facilitating a process to create a shared set of goals and priorities for Cardano.

## 2025 Broad Cardano Goals

To achieve this, the Product Committee was formed in August 2024. With the support of an initial group of 3 voting seats and 20+ SMEs from the broader Cardano community, it brainstormed an **initial set of proposed draft goals**.

To **refine, expand, and adjust** these draft goals, the committee has since then been **collecting input and feedback** from focus groups (dApps builders, SPOs, Builders on Cardano, Builders on Cardano, and more), Intersect committees and Intersect working groups and the broader Cardano community.

The outcome of this process is [here](/intersect-product-committee/committee-outcomes/2025-cardanos-roadmap/2025-proposed-cardano-goals.md). This was used by the Intersect committees to align their budget requests to a common direction.

## 2025 Cardano Roadmap

To provide a more detailed roadmap to Cardano in 2025, the Product Committee, with feedback from other committees and the broader community, has created a draft proposal that is currently open for consultation and that aligns with the 2025 Cardano budget.

More details [here](/intersect-product-committee/committee-outcomes/2025-cardanos-roadmap/2025-proposed-cardano-roadmap.md)


---

# 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://committees.docs.intersectmbo.org/intersect-product-committee/committee-outcomes/2025-cardanos-roadmap.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.