> For the complete documentation index, see [llms.txt](https://token-engineering-commons.gitbook.io/tec-handbook/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://token-engineering-commons.gitbook.io/tec-handbook/tec-agreements-1.md).

# TEC Collective Agreements

- [Introduction](https://token-engineering-commons.gitbook.io/tec-handbook/tec-agreements-1/why-do-we-need-agreements.md)
- [Collective Agreements](https://token-engineering-commons.gitbook.io/tec-handbook/tec-agreements-1/collective-agreements.md)
- [Hatch DAO](https://token-engineering-commons.gitbook.io/tec-handbook/tec-agreements-1/collective-agreements/hatch-dao.md): Temporary DAO with a Dandelion Voting instance that will be fully migrated once the hatch phase is over.‌
- [Gravity](https://token-engineering-commons.gitbook.io/tec-handbook/tec-agreements-1/collective-agreements/gravity.md): Conflict Management
- [Advice Process](https://token-engineering-commons.gitbook.io/tec-handbook/tec-agreements-1/collective-agreements/advice-process.md): Gathering perspective before executing a proposal
- [Forum Voting](https://token-engineering-commons.gitbook.io/tec-handbook/tec-agreements-1/collective-agreements/forum-voting.md): Off-chain decision making process dedicated to cultural agreements and signaling polls.
- [Conviction Voting](https://token-engineering-commons.gitbook.io/tec-handbook/tec-agreements-1/collective-agreements/conviction-voting.md): On chain decision making process dedicated to funds allocation
- [Disputable Voting](https://token-engineering-commons.gitbook.io/tec-handbook/tec-agreements-1/collective-agreements/dandelion-voting.md): On chain Moloch-like voting instance
- [SourceCred](https://token-engineering-commons.gitbook.io/tec-handbook/tec-agreements-1/collective-agreements/sourcecred.md): Quantitative system for rewarding contributions
- [Praise](https://token-engineering-commons.gitbook.io/tec-handbook/tec-agreements-1/collective-agreements/praise.md): Our culture of gratitude - qualitative system for rewarding contributions
- [Github](https://token-engineering-commons.gitbook.io/tec-handbook/tec-agreements-1/collective-agreements/github.md): Tech and Cultural coordination
- [Forum](https://token-engineering-commons.gitbook.io/tec-handbook/tec-agreements-1/collective-agreements/forum.md): Resources - Voting - Discussions
- [Discord](https://token-engineering-commons.gitbook.io/tec-handbook/tec-agreements-1/collective-agreements/discord.md): Co-working space
- [Content Ownership Agreement](https://token-engineering-commons.gitbook.io/tec-handbook/tec-agreements-1/content-ownership-agreement.md)
- [Code of Conduct](https://token-engineering-commons.gitbook.io/tec-handbook/tec-agreements-1/code-of-conduct.md): This aims to serve as a guideline for how to relate healthily with one another when participating in the Token Engineering Commons.


---

# 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://token-engineering-commons.gitbook.io/tec-handbook/tec-agreements-1.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.