> For the complete documentation index, see [llms.txt](https://funding.treasuries.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://funding.treasuries.io/approaches/incentive-approaches/idea-cost-approaches/costs-attached-to-ideas.md).

# Costs attached to ideas

<div align="left"><figure><img src="/files/5aNkYZAFq7VF430KOgnC" alt="" width="225"><figcaption></figcaption></figure></div>

**Overview**

Keeping idea costs attached to idea suggestions means that these costs would need to be requested in the idea proposal itself. Each of the idea costs would be accounted for and included in the same approval as the idea itself.

**Moderate idea cost budgeting complexity (Score - 3)**

Each of the idea related costs can be budgeted for in the idea proposal. This can be fine for some of the costs that an idea might have however some costs could change over time or be difficult to calculate ahead of time without further execution effort. This means it can be moderately difficult for contributors to accurately budget for these idea costs ahead of time.

**Moderate idea cost change complexity (Score - 3)**

To change the existing idea related costs or to add new ones a contributor either needs to estimate all of these costs upfront in the initial idea proposal or withhold those requests entirely until a future repeated idea proposal. Creating a future idea proposal for this purpose adds extra complexity for the voters who then need to approve multiple similar instances of the same idea and this also increases the effort for contributors to handle these repeated submissions.

**Low voter expressiveness (Score - 2)**

The grouped costs could be easily listed out when the costs are directly attached to the idea however there is still little ability for the voter to properly express their preference in a vote and can only do this by sharing their feedback and opinions on the idea itself. The voters either have to accept everything or nothing.

**Total score = 8 / 15**


---

# 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://funding.treasuries.io/approaches/incentive-approaches/idea-cost-approaches/costs-attached-to-ideas.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.
