> For the complete documentation index, see [llms.txt](https://docs.szns.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.szns.io/core-components/governance.md).

# sznsDAO

## **What does the sznsDAO govern?**

While the sznsDAO will continue to evolve, initial governance includes decisions around the SZNS treasury, the Album Factory parameters, and Album voting arbitration.

### **Governance Arbitration**

The sznsDAO provides an important role as backstop for a Collection DAO's governance decisions. If somehow an oracle verifies an inaccurate outcome, the sznsDAO can halt an action from being committed to chain.

The sznsDAO can also be invoked by the community to pass a proposal quickly.

### **Treasury Management**

The sznsDAO will be responsible for deciding how to use assets in the treasury to create value for the network. These decisions include managing Collection Tokens to support the community and broader network.

### **Album Factory**&#x20;

The Album Factory defines the sensible default parameters given to each Collection at launch. This determines the way communities vote to add new NFTs and members, or coordinate a Collection buyout using the SZNS governance stack. SZNS holders will be able to propose new default parameters for the factory as the protocol evolves.


---

# 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://docs.szns.io/core-components/governance.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.
