> For the complete documentation index, see [llms.txt](https://postthread.gitbook.io/postthread-wiki/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://postthread.gitbook.io/postthread-wiki/tokenomics/subblockits.md). # SubPostThreads For now, when a user mints a post, they will specify which category they want the post to be under. This will allow for easier searching and grouping of posts, but there will not be designated subblockit communities at the start. There is a main page with all posts and a filter by category button. In the future, as the community grows, it will want to segment into smaller groups with their own moderation, rules and potentially economy. We are open to this and would like to allow for it, but feel it is not needed at the start. Some ideas for the future however are to allow users to mint a subblockit and create their own DAO and token. This would allow them to make and enforce their own rules --- # 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://postthread.gitbook.io/postthread-wiki/tokenomics/subblockits.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.