> 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-open-source-committee/about/paid-open-source-model-posm/tooling-sustainability/signed-contracts.md).

# Signed Contracts

Below are copies of the signed Contracts and relevant Milestone Acceptance Forms received by the Open Source Committee. 

**Cicerium:** Hydra-Based feedback tool, originally designed for the 2026 Cardano Budget Process, revised for use in other decentralized governance decisions, delivered as an option for use to the Civics Committee. 

{% file src="/files/Rq1FQ8pQdi9tseCwXSsA" %}

{% hint style="info" %}
Cicerium was the first tool to be funded under TSP. It therefore served as a test. The tooling was approved initially in quick format under the assumption that it would be utilized in the 2026 Cardano Budget Process. After review and contract completion, the OSC determined that future Tooling Projects to be funded, will undergo a more detailed review specifically targeting explicit delivery and improvement. While this tool was funded without proven and active use/adoption, a higher focus on adoption was added by the OSC for future TSP funding requests. 
{% endhint %}

**Milestone 1:** Meet with the Civics committee and necessary working groups under Civics. Go over current tool capabilities and create a delta of work to meet the specific needs of the committee.

{% file src="/files/TxLxvs0aAEVlYOIPJ3jj" %}

**Milestone 2:** Pre-production deployment of tool, usability testing with the Civics committee and SMEs. Provide usability reports, provide any updates needed.

{% file src="/files/06uwpwfGtxWU5iKRQ02z" %}

**Milestone 3:** Production deployment of tool. Monitor the tool for the initial usage (Cardano Constitution Amendment Process).

{% file src="/files/mHi015d9Ooi7yuypLJ9g" %}


---

# 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-open-source-committee/about/paid-open-source-model-posm/tooling-sustainability/signed-contracts.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.