> 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/5.-product/standardized-tokenized-ip-assets.md). # Standardized (tokenized) IP assets The digital assets IP contract covers several critical aspects: * **Concept authorship and copyright:** credits the original authorship and copyright from the inception stage honoring the initial creators and giving space for new contributors * **Future development rules:** outlines the initial rules and guidelines for IP property development, including financial resource allocation for pre-production stage * **Governance, oversight and accountability structure:** details the governance model and executive production framework, outlines scenarios for IP success, plateau or sunsetting * **IP rights framework:** defines the rights for acquiring value from new co-creators, shared authorship, royalties and fractional ownership * **Growth and reward framework:** sets the terms for financial incentives (royalties, and rewards) We plan to offer a range of digital assets with various utilities, which may include, but are not limited to: * Fractional ownership (securitized royalties) * Membership passes * Collectible assets * Playable assets (experience-enhancing) * Consumer products in digital form Additionally, we plan to operate as a **multi-chain ecosystem**, which means adjusting to the specific opportunities that each IP property or blockchain ecosystem offer at a given time. --- # 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/5.-product/standardized-tokenized-ip-assets.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.