> For the complete documentation index, see [llms.txt](https://3rdunit.gitbook.io/3rd-unit-litepaper-december-2024/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://3rdunit.gitbook.io/3rd-unit-litepaper-december-2024/3.-problem-statement/problem-1-access.md).
# Problem 1: Access
**Problem**
For creators, building an IP that has franchise potential is extremely challenging without access to finance, networks and talent. It demands money, time, institutional support, and often a bit of luck.
Geography also matters. Starting in cities like London, New York, Los Angeles, or Tokio with established entertainment industries provides a much greater advantage compared to Buenos Aires, Riyadh, or Lagos. Many creators in less connected locations struggle to get their projects off the ground due to these access imbalances.
The disparity also affects individual investors. Early stage IP is sold on private markets and without connections to producers or access to exclusive deals, even those with the financial resources and enthusiasm are often excluded from investment opportunities.
**Solution**
We aim to address some of these challenges by creating an environment where promising early-stage IPs from non-mainstream markets have a display, audience, legal framework, and process to convert promising IPs into digital assets that make them "investable" long-term.
Our process filters and vets incoming creators and intellectual properties. We balance between expert assessments, audience judgment and data-based tools. We stay attuned to market trends and seek opportunities for new entrants, while maintaining our baseline high quality.
Once vetted, new IP opportunities are presented at the 3RD UNIT, allowing both creators and investors to discover and transact with them.
---
# 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://3rdunit.gitbook.io/3rd-unit-litepaper-december-2024/3.-problem-statement/problem-1-access.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.