> For the complete documentation index, see [llms.txt](https://myros.gitbook.io/bp/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://myros.gitbook.io/bp/challenges.md).
# Challenges
#### Knowledge Has Become Fragmented
Every project accumulates knowledge.
Some of it lives in official documentation.\
Some of it lives in blog posts.\
Some of it lives in GitHub repositories.\
Some of it lives in Discord, Telegram, Notion, GitBook, Medium, X, or internal documents.
Over time, the knowledge base becomes fragmented. Users do not know where to look. Teams do not know which source is current. Newcomers struggle to understand the project. Contributors waste time asking questions that have already been answered somewhere else.
The problem is not that knowledge does not exist.
The problem is that knowledge is no longer easily accessible.
***
#### Static Documentation Cannot Keep Up
Traditional documentation is important, but it has limits.
Documentation requires users to search manually.\
It assumes users know the right keywords.\
It becomes outdated when teams move quickly.\
It does not adapt to the user’s context.\
It does not explain itself conversationally.
For fast-moving industries such as AI, Web3, gaming, and open-source software, static documentation often becomes a bottleneck.
A user may not want to read five pages to find one answer.\
A community member may not know which page contains the answer.\
A developer may need immediate guidance while building.\
A support team may be overwhelmed by repeated questions.
Static information is useful, but it is not enough.
Modern users expect knowledge to be instant, contextual, and conversational.
***
#### Communities Need Always-On Intelligence
Communities are active across time zones. Questions appear at any hour. New users arrive continuously. Projects launch updates, features, partnerships, patches, governance proposals, and technical changes.
Human teams cannot answer everything instantly.
This creates gaps in user experience:
| Problem | Result |
| --------------------- | ---------------------------------------------------- |
| Repeated questions | Community fatigue and inefficient support |
| Outdated answers | Confusion and loss of trust |
| Scattered sources | Poor onboarding |
| Manual support burden | Slower team productivity |
| Lack of context | Generic answers instead of project-specific guidance |
The next generation of online communities will not rely only on static pages and human moderators.
They will use intelligent agents that understand the project, retrieve current information, and respond in real time.
This is the gap Myros is designed to fill.
---
# 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:
```
GET https://myros.gitbook.io/bp/challenges.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.