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

# Governance and transparency

Lockups, on-chain visibility, and progressive decentralization.

## Governance and transparency

Cybertig positions governance around locked allocations, transparent reporting, and progressive decentralization.

### Core principles

#### Hard-locked allocations

Initial developer and team tokens are hard-locked by smart contract for a full **1-year period**.

#### On-chain transparency

Treasury activity, buybacks, burns, and IoT-linked reporting are intended to remain publicly verifiable.

#### Progressive decentralization

Governance can evolve toward a community-driven DAO as the network scales.

#### Execution-first culture

The project emphasizes deployed infrastructure over symbolic roadmap claims.

### Intended outcome

The design aims to increase trust by making capital use, supply changes, and operating performance visible over time.


---

# 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.cybertig.com/readme/governance-and-transparency.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.