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

# Governance Principles

## Primer on Principles-based Governance

The Principles listed in this Framework are designed to provide a functional reference point, and act as checks and balances, for cheqd community members and Network Users voting on the Network.

These Principles are specifically designed to govern [Major Network Changes](/product/learning-docs/governance/participate/network-changes/major.md) and ‘on-chain’ governance activities. They should serve as the foundation and baseline for the Network to build upon as it iterates and becomes increasingly decentralised.

Regulating through Principles-based Governance, as explained in [Introduction to Governance](/product/learning-docs/governance/start/introduction-to-governance.md), means that these are not hard rules. There is no single entity that can impose a punishment for failure to comply with these Principles. Instead these are suggestions to nudge Users on the Network to act within the best interests of the community, to be inclusive and to keep the Network secure. The Principles can be interpreted broadly, or narrowly, this is up to the discretion of the User and the community.

If the general consensus of the Network believes a Network Proposal is contrary to a Principle, they SHOULD feel inclined to reject or veto such as Proposal. This SHOULD keep the Network in check and within a set of boundaries to keep it developing in a healthy way. A decision by Network consensus MAY also incur a financial penalty on the User acting contrary to a Principle. In this way, the Network regulates behaviour through Principles as well as Economics using the Network's Architecture.

This type of Regulation, through norms and Principles is also flexible and can change quickly, as society and the Network develops. This is Unlike Laws and Guidelines which are far more static.

Updates, amendments or revisions to this Principles list can be made through the process explained in the section [Major Network Changes](/product/learning-docs/governance/participate/network-changes/major.md).

## cheqd Network Principles

Familiarise yourself with our set of principles for interacting with the network.

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><mark style="color:blue;"><strong>Foundational Principles</strong></mark></td><td>Learn about the three Foundational Principles guiding the cheqd governance framework.</td><td><a href="/pages/xQOo0cC9U4uWYAQihVw9">/pages/xQOo0cC9U4uWYAQihVw9</a></td></tr><tr><td><mark style="color:blue;"><strong>General Principles</strong></mark></td><td>Learn about the ten General Principles accompanying the Foundational Principles. </td><td><a href="/pages/l5dGqDXuigqR2Is9fTEo">/pages/l5dGqDXuigqR2Is9fTEo</a></td></tr></tbody></table>


---

# 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.cheqd.io/product/learning-docs/governance/start/governance-principles.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.