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

# Task Weights

Task weights are how we keep things fair and focused. Each task is given a value from 1 to 10 based on how important or demanding it is, decided collectively by the community. Higher weights don’t mean favoritism they simply make sure that the toughest or most impactful work gets a bigger share of the pool. \
\
This system helps us direct effort where it matters most each sprint, without turning work into a race or a grind. Everyone knows the value upfront, and every contribution counts toward something real.

* Each task gets a weight from 1 to 5 by community vote
* A higher weight means a larger share of the epoch pool

If $ORG wins we all win.


---

# 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://organic-1.gitbook.io/organic-docs/contributors/task-weights.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.
