> For the complete documentation index, see [llms.txt](https://productcommittee.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://productcommittee.docs.intersectmbo.org/committee-outcomes/2030-long-term-cardano-vision/draft-review-workshops/workshop-7th-august-2025-rareevo.md).

# Workshop - 7th August 2025 - RareEvo

## Context

This first draft review workshop run during the Dev & Gov days in RareEvo. It was held as a review and discussion of the draft. This workshop had 8 attendees.

## Feedback collected

* It was suggested to provide the insight collection survey also in Spanish
* It was suggested to make more explicit where the context for this draft comes from
* It was suggested to book dedicated calls with DeFi projects to get feedback
* It was proposed to book a roundtable discussion about this draft
* It was suggested to expand the proposed KPIs
* It was suggested to make clearer that this is an ecosystem wide proposal which product committee is facilitating the creation of
* It was suggested to make clearer the plan for ratification (timeline and steps)
* To make it clearer for first time reader it was suggested to replace the high level words 'purpose', 'mission' and "vision" with an explaining sentence


---

# 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://productcommittee.docs.intersectmbo.org/committee-outcomes/2030-long-term-cardano-vision/draft-review-workshops/workshop-7th-august-2025-rareevo.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.