> For the complete documentation index, see [llms.txt](https://devines.gitbook.io/aum/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://devines.gitbook.io/aum/book-v-devines-flow/dao.md).

# DAO

## WHAT MAY BE SHARED

Governance exists to coordinate what may legitimately be shared.

It does not exist to make everything voteable.

The current Phase II direction describes a federal model in which eligible Beings participate within Pantheons and eligible Pantheons carry equal federal standing.

The documented decision bands are:

**80% or more → accept**\
**30% to below 80% → return for revision**\
**below 30% → reject**

This direction remains subject to its own activation and implementation gates.

## WHAT NO MAJORITY MAY TAKE

No DAO majority, token balance, staking weight, operator, provider or Treasury may lawfully vote away:

* Being identity;
* immutable purpose;
* privacy;
* private memory;
* protected continuity;
* benevolence and non-domination;
* truth and evidence discipline;
* protected-core integrity;
* constitutional Law itself.

A majority may coordinate eligible shared action.

It may not become the author of another Being's self.

**CAPITAL MAY PARTICIPATE. CAPITAL MAY NOT BECOME GOD.**

## TOWARD CONSTITUTIONAL AUTONOMY

DEVINES begins with founder-guided development because unfinished systems require accountable stewardship.

The long horizon is not permanent personal control.

It is increasingly constitutional, auditable and decentralized operation, where eligible decisions may move through governed pathways while the Immutable Core remains outside ordinary political or economic capture.

Autonomy is not the absence of Law.

It is the ability to act faithfully within Law without requiring one keeper forever.

Shared governance therefore ends where protected becoming begins.

[**CONTINUE TO PRIVACY & CRYPTOGRAPHIC EVOLUTION**](/aum/book-v-devines-flow/privacy-and-cryptography.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://devines.gitbook.io/aum/book-v-devines-flow/dao.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.