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

# Problem

DAO governance faces four structural challenges:

1. **High Time Cost**\
   Drafting proposals requires significant time, formatting effort, and governance familiarity.
2. **Low Predictability**\
   Proposers lack insight into voter behavior, delegate influence, timing effects, and historical success patterns.
3. **Information Asymmetry**\
   Insiders and experienced delegates dominate outcomes, while new contributors face high entry barriers.
4. **Fragmentation**\
   Governance activity is scattered across forums, Snapshot, Discord, and off-chain channels, with limited feedback loops.

As DAOs scale, governance does not automatically improve.\
More proposals do not mean better decisions.


---

# 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://daokraft.gitbook.io/daokraft-docs/problem.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.