> For the complete documentation index, see [llms.txt](https://docs.catalystcontributors.org/funding-categorisation-analysis/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.catalystcontributors.org/funding-categorisation-analysis/historical-analysis-and-comparisons/funding-access-for-each-focus-area/fund-7.md).
# Fund 7
### Funding access for different focus areas
### **Funding categories equivalent**
After reviewing the [data covered in the methodology](/funding-categorisation-analysis/historical-analysis-and-comparisons/funding-access-for-each-focus-area/methodology-data-and-feedback.md) for fund 7 a similar funding categorisation outcome could have been achieved with funding categories as an alternative categorisation approach by applying the following budget weightings:
* **Community & Outreach** - 15%
* **Products & Integrations** - 30%
* **Governance & Identity** - 30%
* **Development & Infrastructure** - 25%
### Observations
**Restrictive funding access**
Fund 7 had far much more limiting access to funding for a number of proposal focus areas. The funding categories equivalent achieves more access for all of the proposal focus areas to a fairly significant degree. This could have helped with both competition and better variation of the proposals submitted to give the voter more options to choose from.
**Few broad categorisations**
The only main broad categorisations were [Open Source Developer Ecosystem](http://app.ideascale.com/t/UM5UZBnCM) and [DApps & Integrations](http://app.ideascale.com/t/UM5UZBoNV) however there total budget was still low. This contributed towards the lack of much funding being available for many of the areas that could be covered in the ecosystem.
**Large usage of specific categorisations**
There were a number of specific categorisations that meant limiting the types of proposals that could be submitted such as [Boosting Cardano's DeFi](http://app.ideascale.com/t/UM5UZBnJW), [Lobbying for favorable legislation](http://app.ideascale.com/t/UM5UZBnJd), [Connecting Japan/日本 Community](http://app.ideascale.com/t/UM5UZBnVu), [Gamers On-Chained](http://app.ideascale.com/t/UM5UZBnPQ), [Seeding Cardano's Grassroots DeFi](http://app.ideascale.com/t/UM5UZBnWs), [A.I. & SingularityNet a $5T market](http://app.ideascale.com/t/UM5UZBnKN), [Nation Building Dapps](http://app.ideascale.com/t/UM5UZBmrP), [Multilingual resources](http://app.ideascale.com/t/UM5UZBneK), [Improve and Grow Auditability](http://app.ideascale.com/t/UM5UZBneL) and [Catalyst Accelerator & Mentors](https://cardano.ideascale.com/c/campaigns/26255/about).
**Categorisation interpretation is needed**
Some categorisations such as [Miscellaneous Challenge](http://app.ideascale.com/t/UM5UZBnH5) invite proposals based off them not being able to be submitted elsewhere. This adds large complexity as the proposer and voter need to be aware of which proposals should be in what categorisations amongst all the options to fulfil that requirement.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.catalystcontributors.org/funding-categorisation-analysis/historical-analysis-and-comparisons/funding-access-for-each-focus-area/fund-7.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.