# 3. Problem statement **IP Creators** * enhanced access to capital, development tools, and distribution channels * development structure that improves the likelihood of creating IP properties capable of achieving long-term creative and financial sustainability, underpinned by a positive-sum incentives system * access to community of early adopters **Consumer Investors** * access to a curated pipeline of scouted and vetted early-stage entertainment IP properties * robust legal and governance framework for asset purchase and ownership * assets designed for interoperability and liquidity to enable participation in global markets **Content consumers / Fandom** * access to IP properties that better reflect various cultures and market segments * more direct engagement with creators, offering insights into creative processes and behind-the-scenes development * IPs that are more deeply grounded in audience needs and interests **Industry** * access to market-tested creators, properties and early audience data * de-risked pool of diverse creators, with broader geographical and cultural representation * opportunities to connect with and access new audiences Read more on: [ACCESS](/3rd-unit-litepaper-december-2024/3.-problem-statement/problem-1-access.md) - [REPRESENTATION](/3rd-unit-litepaper-december-2024/3.-problem-statement/problem-2-representation.md) - [VALUE SHARING](/3rd-unit-litepaper-december-2024/3.-problem-statement/problem-3-value-sharing.md) --- # Agent Instructions: 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: ``` GET https://3rdunit.gitbook.io/3rd-unit-litepaper-december-2024/3.-problem-statement.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.