> 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/functional-requirements.md).

# Functional requirements

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

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

## Minimum functional requirements

Must have (in no particular proirity order)

* Community members log-in via email address and/or wallet connect
* Proposal submission form - (details below)
* Proposal comments form - (details below)
* Single choice opinion Poll (Yes/No) to test consensus on a proposal
* The author of proposals should be able to edit and update their proposal
* Generates an anchor - URL that points to an off-chain JSON file containing all the information generated for a specified proposal within the Proposal Discussion Forum
* Open APIs allow other services to query proposal information alongside public endpoint with JSON structured data containing all information generated for a specified proposal
* Proposal search and filtering
* Moderator role, to keep the forum clean (neutralizing spam and spambots, profanity check and ability to remove, hide, delete, or flag inappropriate content)

### Minimum required fields for the Proposal Submission Form:

The list below should align with what is decided in the [governance metadata CIP. ](https://github.com/cardano-foundation/CIPs/pull/556)\\

<table data-header-hidden><thead><tr><th width="205"></th><th></th></tr></thead><tbody><tr><td><strong>Form fields</strong></td><td><strong>Description</strong></td></tr><tr><td>Author ID</td><td><p>ID of author:</p><ul><li>A way for the users to identify the author of the proposal</li><li>A way to allow the platform to identify which proposal belongs to who - permissions control</li><li>Nice to have: Possibly a way to allow this platform to connect the off-chain and the on-chain author</li></ul></td></tr><tr><td>Proposal ID</td><td>Auto generated unique identifier for the proposal</td></tr><tr><td>GA Type</td><td>Indicate which type of GA this proposal represents</td></tr><tr><td>Title</td><td>The proposal name should give an indication of the Governance action that community members are trying to achieve. Keep it simple and informative.</td></tr><tr><td>Abstract</td><td>A concise summary of your proposal that provides the essential information such as the problems, implications (200-character limit including spaces)</td></tr><tr><td>Motivation/problem</td><td>Detailed description of the motivation/problem</td></tr><tr><td>Solution</td><td>The proposed solution. Explain how it is aligned with the motivation/problem.</td></tr><tr><td>Supporting links</td><td>Allows proposer to share links to different resources (e.g. PDFs, images, website/ GitHub and additional URLs).</td></tr><tr><td>Tags</td><td>Nice to have: Tags with keywords related to the proposal</td></tr></tbody></table>

### Minimum required fields for the Proposal Comment Form:

<table data-header-hidden><thead><tr><th width="211"></th><th></th></tr></thead><tbody><tr><td><strong>Form fields</strong></td><td><strong>Description</strong></td></tr><tr><td>Author ID</td><td>ID of the comment’s author</td></tr><tr><td>Comment</td><td>Once a proposal is submitted the discussion starts by users adding comments</td></tr><tr><td>Supporting links</td><td>Allow users to share additional information. e.g. PDFs, images, Website/ GitHub and additional URLs</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/functional-requirements.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.