> For the complete documentation index, see [llms.txt](https://coordination-play.gitbook.io/coordinationlab/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://coordination-play.gitbook.io/coordinationlab/overview/stack/attribution-stack.md).
# Attribution stack
The attribution stack is the centrepiece of the coordination stack. Nothing works without it. The goal of the attribution stack is to store the relative value of contributions for all contributors onchain in an organisation across different guilds/teams/skills.
## **How does attribution stack work?**
An organisation distributes points to its contributors for completing any work every month. These points are uploaded onchain and become immutable.
Then, that organisation can use these immutable points to distribute governance power using[Governance stack](/coordinationlab/overview/stack/governance-stack.md) and reward the contributor using the [Financial stack](/coordinationlab/overview/stack/financial-stack.md)
## What are guilds?
When an organisation assigns points to a contributor, it chooses a category for which it assigns them. These categories are called guilds.
Some examples of guilds
* guilds similar to teams in an organisation like a dev team, design team, etc
* guilds for a dev team like a java team, solidity team
Guilds can be in the form of sub-guilds as well by creating an organisation for the top guild.
## Visual representation of points for an organisation in a specific guild
By having points onchain, anyone can see and verify the contribution history of a contributor to a particular org in a specific guild. The attribution stack creates a coordination DNA for organisations and contributors, creating graph-like data for individuals and organisations.
This data is then used to experiment and create financial reward and governance models for the organisations. CoordinationLab is creating basic premitives in the form of [Financial stack](/coordinationlab/overview/stack/financial-stack.md) and [Governance stack](/coordinationlab/overview/stack/governance-stack.md) using this graph-like data.
---
# 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://coordination-play.gitbook.io/coordinationlab/overview/stack/attribution-stack.md?ask=&goal=
```
`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.