> 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/education-multimedia-content/considerations.md).

# Considerations

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

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

Collaboration with other members is encouraged since the proposed solution should involve the entire governance process.

### Expected Cost Range

There is no set amount for multimedia education grants, as it’d be preferable for applicants to specify the amount needed to implement their proposed solution, allowing for a broader range of creativity. However, to help applicants sense-check their proposal, the maximum amount is 150,000 ADA for the Education category. Multiple proposals will likely be selected for these categories so smaller proposals are equally beneficial. Proposals outside this range with valid reasoning will also be considered.

### Suggested Minimum Milestones

The milestones below are indicative and proposals should ideally not exceed a six month delivery plan. Proposals should also broadly align with the [CIP-1694 roadmap](https://www.intersectmbo.org/roadmap).

| Milestone                                                                            |
| ------------------------------------------------------------------------------------ |
| Design Phase or outline if non-code                                                  |
| Testable prototype or first draft if non-code                                        |
| MVP - meets minimum requirements, fully working version or first version if non-code |
| V1.0 - start to implement new features and/or improvements                           |

\\


---

# 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/education-multimedia-content/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.