> For the complete documentation index, see [llms.txt](https://kizunai.gitbook.io/kizuna-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kizunai.gitbook.io/kizuna-docs/02.-the-problem.md). # 02. The Problem ## The Problem ### Project Knowledge Is Scattered Projects create and maintain a large amount of information for their communities. This information can exist across: * Websites * GitBooks * Documentation * FAQs * Other trusted project resources The knowledge is available, but it is often distributed across different places. For a community member, finding the correct information can require leaving the conversation, searching through documentation, and identifying which source contains the answer. ### Repetitive Community Questions Project teams regularly receive questions about information that may already exist in their official resources. The same questions can appear repeatedly across the community. This creates a simple gap: **THE INFORMATION EXISTS.**\ **THE COMMUNITY STILL NEEDS AN ANSWER.** Teams have to spend time providing answers that could otherwise be accessible directly from the project's existing knowledge. ### Communities Are Always Moving Telegram communities are active environments where conversations happen continuously. Project teams cannot realistically be available every minute of every day. When a team member is unavailable, community members may have to wait for an answer or search for the information themselves. KIZUNA is designed to address this gap by bringing project knowledge directly into the community. ### The Missing Layer The problem is not simply a lack of information. The problem is the distance between **project knowledge** and **community access**. Today, the flow often looks like: **PROJECT KNOWLEDGE → DOCUMENTATION → COMMUNITY MEMBER SEARCHES → ANSWER** KIZUNA is designed to simplify this: **PROJECT KNOWLEDGE → KIZUNA → COMMUNITY** This creates an intelligent layer between the information a project already has and the people who need it. ### The Opportunity Projects already have the foundation required to answer many community questions: their own knowledge. KIZUNA connects that knowledge to an AI community manager so that community members can interact with project-specific information directly inside Telegram. The goal is not to replace the project team. The goal is to make the project's existing knowledge more accessible to the community. --- # 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://kizunai.gitbook.io/kizuna-docs/02.-the-problem.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.