> For the complete documentation index, see [llms.txt](https://docs.mosaic-program.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mosaic-program.org/5.-risks.md).

# 5. Risks

* Adoption: Network effects keep researchers on closed platforms. Even where MOSAIC succeeds at the individual level, new contribution and reputation signals may take longer than the program timeline to earn trust from traditional institutions and funders.
* Sustainability: Usage may not reach the scale needed to generate self-sustaining revenue, and the underlying economics remain unproven.
* Programmatic: Many interdependent developments — attribution, standards, novel publishing tools — must each work and integrate with the others. Bottlenecks in one area can cascade across the system.
* AI displacement: If AI capabilities advance faster than expected, infrastructure designed for human-AI collaboration may become redundant in domains where AI can operate autonomously. Mitigation: AI agents need a structured substrate to contribute into just as humans do, so MOSAIC's value persists across a wide range of AI futures, even if the balance of human and AI contribution shifts.


---

# 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://docs.mosaic-program.org/5.-risks.md?ask=<question>&goal=<endgoal>
```

`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.