> 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/archive/archived-content/smart-contract-layer-and-tools/tokenlog.md).

# Tokenlog

[Tokenlog](https://tokenlog.xyz/) is a new governance tool that creates token-weighted backlogs and rankings. It allows projects to continuously gather feedback from their token-holders and allows token-holders to signal which items matter to them rather than just vote on single proposals. The Token Engineering Commons is using this tool in tandem with the [Hatch Configuration Dashboard](https://params.tecommons.org/hatch) to vote on parameter configurations submitted by community members. It is also used in the cultural layer as a general signaling tool.                                    

**Voting Type:** Weighted with TEC token holdings\
\
**Signalling Interval:** Discrete<br>


---

# 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/archive/archived-content/smart-contract-layer-and-tools/tokenlog.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.