> For the complete documentation index, see [llms.txt](https://nexon-3.gitbook.io/nexon-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nexon-3.gitbook.io/nexon-docs/part-v-economics/06-governance.md).

# Governance

How parameters are administered today, and what ecosystem governance for XO has to define before it becomes a real right.

Governance is one of the functions of XO (Roadmap). The current mechanism defines XO as the Staking Principal Token and EXON as the Core Value Token; the specific rules for proposals, voting and execution are published together with the governance framework.

The narrative positions XO as the Value Anchor, associated with staking, participation, governance and long-term value. Until the governance framework is published, parameters are **administered** by accountable project operators under disclosed controls.

## How parameters are administered today

The project team currently administers a set of configurable parameters, which may include staking settings, reward payout ranges, round terms and operating controls. **Every production change carries six things:**

{% stepper %}
{% step %}

### An effective time and a unique parameter version

So a user can answer "which version governed my order?"
{% endstep %}

{% step %}

### The exact fields changed, and why

Not "parameters were adjusted," but which field went from what to what.
{% endstep %}

{% step %}

### Scope

New orders, existing orders, or both.
{% endstep %}

{% step %}

### Advance notice

Through an official channel, wherever it is practical.
{% endstep %}

{% step %}

### An auditable record

Which prevents silent retroactive changes to closed epochs.
{% endstep %}

{% step %}

### An emergency process

With named approvers and a post-incident report where normal notice is impossible.
{% endstep %}
{% endstepper %}

**Interfaces should show the version governing a user's order.** Saying "parameters are adjustable" is not enough if the user cannot find out which values applied when their order executed.

## What governance has to answer first

XO governance is Roadmap. Before it can go live, the project has to define **where governance ends**. A published design covers at least:

| Dimension                   | Must be specified                                                    |
| --------------------------- | -------------------------------------------------------------------- |
| Scope                       | What is governable, and what is not                                  |
| Proposal and voting         | Proposal eligibility, voting or signaling method, quorum, thresholds |
| Delegation and timelocks    | Delegation rules, execution timelocks, who holds execution authority |
| Interests and concentration | Conflict-of-interest handling, limits on concentrated holdings       |
| Emergency and correction    | Emergency powers, appeals, correction procedures                     |

Some decisions stay with regulated providers or contractual operators regardless of community preference. **A token vote cannot direct a card issuer to breach a legal obligation, change a merchant's fulfillment duty, override custody terms or waive jurisdictional eligibility.** Economic parameter changes likewise need risk, legal and technical review — not just a popularity signal.

## Disclosure discipline

Execution rates for leadership bonuses V1 – V12 are published externally as ranges, set by market stage and recorded by parameter version; the switch to 1:1 pairing after listing and the thresholds and scope of XO governance are listed under [Open Parameters](/nexon-docs/appendix/open-parameters.md).

When a future written decision takes effect, it updates the authority registry, both language trees, the user interfaces and the calculation tests **together**. Conflicting historical material stays archived and is not reused as current copy.

## Independence and accountability

NEXON is the first flagship project on the NEX exchange. NEX exchange status, licences or personnel do not approve or guarantee Staking Platform outcomes or future NEXON product governance. **Responsibility is named per operating entity and per product.**

*Previous:* [*Value Flows*](/nexon-docs/part-v-economics/05-tokenomics/value-flows.md) *· Next:* [*Security & Risk*](/nexon-docs/part-vi-assurance/07-security-and-risk.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 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://nexon-3.gitbook.io/nexon-docs/part-v-economics/06-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.