> 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-budget-archive/intersect-operational-services/2024-intersect-cdh-and-grant-contracts/2024-cdh-grants/closed-grants/proposal-discussion-forum/considerations.md).

# Considerations

Consider the below before submitting your application

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

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

When thinking about applying for this grant, responses to the brief should consider how the Proposal Discussion Forum could surface proposals before they become governance actions. Stages such as:

1. Proposal submission
2. Proposal discussion
3. Proposal polling

The features that you could include under each area is under your creative direction. To help, [this is an overall flow map](https://drive.google.com/file/d/1LtwxQ9it_8yb10LS2kd4jPIq2Locq5FB/view?usp=sharing), highlighting the key steps that the Proposal Discussion Forum will need to support.

### Expected cost range

There is no set amount for this grant, as we would prefer applicants to specify the amount needed to implement their proposed solution, allowing for a broader range of creativity and ambition. However, as a steer, we expect the costs to fall between 90,000 - 180,000 ADA. *Note that you may still propose outside of this range with strong rationale.*

### Timings and milestones

This grant will follow a milestone reporting approach and your application should note the expectations below. This will help with scope and various other parts to your application.

The timelines below are indicative, and broadly align with the [CIP-1694 roadmap](https://www.intersectmbo.org/roadmap).

<table data-header-hidden><thead><tr><th width="452"></th><th></th></tr></thead><tbody><tr><td><strong>Milestone</strong></td><td><strong>Due Date</strong></td></tr><tr><td>Design Phase (System Architecture + UX/UI design)</td><td>Dec 15, 2023</td></tr><tr><td>Testable prototype</td><td>Jan 31, 2024</td></tr><tr><td>MVP - meets minimum requirements, fully working version</td><td>Mar 31, 2024</td></tr><tr><td>V1.0 - start to implement new features (may be based from the nice to have list) and/or improvements</td><td>May 31, 2024</td></tr></tbody></table>

\
\
\\


---

# 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-budget-archive/intersect-operational-services/2024-intersect-cdh-and-grant-contracts/2024-cdh-grants/closed-grants/proposal-discussion-forum/considerations.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.