> ## Documentation Index
> Fetch the complete documentation index at: https://docs.accumulate.supply/llms.txt
> Use this file to discover all available pages before exploring further.

# Governance and Control

> Safeguard the system, not actively manage strategy

Accumulate is designed to execute a fixed strategy while allowing limited governance over protocol operations and long-term maintenance.

<img src="https://mintcdn.com/lemonlaunch/2QOconk9czqE3yGM/images/governance.png?fit=max&auto=format&n=2QOconk9czqE3yGM&q=85&s=dc78ed6b7b087deee921845672f574fa" alt="governance.png" width="1920" height="1080" data-path="images/governance.png" />

<Note>
  Governance exists to **safeguard the system**, not to actively manage
  strategy.
</Note>

## Governance Scope

Governance applies to:

* Protocol operations
* Upgrades within predefined bounds
* Parameter management (where permitted)

<Warning>
  Governance does **not** direct day-to-day execution or respond to market
  conditions. The core strategy runs by default and does not require governance
  input to function.
</Warning>

***

## DAO Governance

<Card title="$ACCU Token Governance" icon="users">
  Accumulate uses a DAO-based governance system where \$ACCU holders may propose
  and vote on governance actions according to defined rules and thresholds.
</Card>

Governance decisions are executed onchain where applicable.

<Info>
  The DAO provides **collective oversight and coordination**, not active
  strategy control.
</Info>

***

## Treasury Custody

Bitcoin accumulated by the protocol is held using a **Safe multisig treasury wallet**.

<AccordionGroup>
  <Accordion title="Purpose of the Multisig" icon="shield">
    The multisig exists for secure custody of treasury assets and operational
    safety. It does **not** intervene in protocol execution or strategy logic.
  </Accordion>

  <Accordion title="Signer Structure" icon="key">
    Signers are limited in number and subject to predefined permissions. The
    structure prioritizes security while preventing single points of failure.
  </Accordion>

  <Accordion title="What the Multisig Cannot Do" icon="ban">
    The multisig cannot sell treasury Bitcoin, alter protocol logic, or override
    smart contract execution. Its role is strictly custodial.
  </Accordion>
</AccordionGroup>

***

## Separation of Responsibilities

<Steps>
  <Step title="Execution" icon="microchip">
    Enforced by smart contracts. No human intervention in core protocol flow.
  </Step>

  <Step title="Governance" icon="gavel">
    Defines allowed operational changes. Bound by predefined scope and
    limitations.
  </Step>

  <Step title="Treasury Custody" icon="vault">
    Handled through multisig security. Focused on asset protection, not
    strategy.
  </Step>
</Steps>

<Card title="Key Principle" icon="lock" color="#10b981">
  **No single component has unilateral control over the system.**
</Card>

***

## Upgrade Boundaries

Protocol upgrades are limited to:

* 🔐 Security improvements
* 🔧 Maintenance and bug fixes
* ⚙️ Operational enhancements

<Warning>
  Upgrades do **not** alter the accumulation mandate or introduce active
  treasury management.
</Warning>

### What Can Never Change

<AccordionGroup>
  <Accordion title="The Core Strategy" icon="compass">
    The fundamental rule accumulate Bitcoin and never sell cannot be modified
    through governance.
  </Accordion>

  <Accordion title="Treasury Mandate" icon="bitcoin">
    Governance cannot authorize selling, lending, or deploying treasury Bitcoin.
  </Accordion>

  <Accordion title="Fee Destination" icon="route">
    The routing of fees to Bitcoin accumulation and token burns is fixed.
  </Accordion>
</AccordionGroup>