Governance & Safety
Use this page when you need the safety model: what governance may control, what should remain explicit, and what must not be silently rewritten.
OmegaX needs governance and safety controls that are strong enough for real capital, but narrow enough that settlement truth does not become discretionary.
Core principle
Governance should coordinate the network.
Governance should not silently rewrite:
- already accrued obligations
- already finalized claim outcomes
- already funded reserve requirements
- historical settlement truth
Governance layers
| Layer | Controls | Should not do |
|---|---|---|
| Protocol governance | Global configuration, fee policy, upgrades, emergency behavior | Rewrite historical settlement truth |
| Plan-level control | Plan policy, sponsor/operator settings, metadata, scoped operations | Hide reserve or liability behavior |
| Class or product controls | Capital entry, redemptions, claim intake, rails | Change capital priority casually after activation |
Protocol governance
Protocol governance is for:
- global configuration
- fee policy
- upgrade path
- protocol-wide emergency behavior
- ecosystem standards around schemas, oracle policy, and public goods
Plan-level control
Plan-level authority is for:
- plan configuration
- sponsor and operator policy within protocol rules
- plan-specific metadata and series setup
- scoped operational controls
Class or product-level controls
Some plans may also need narrower controls for:
- capital entry
- redemptions
- claim intake
- specific rails
- specific regulated modes
Safety controls
OmegaX should favor scoped controls over blunt global freezes.
Typical safety tools include:
- protocol emergency pause
- plan operational pause
- claim intake pause
- capital subscription pause
- redemption queue-only mode
- oracle-finality hold
- impaired-state escalation
Each control should have:
- explicit authority
- explicit scope
- a visible audit trail
- a clear unwind path
Protected invariants
Some rules should be treated as especially protected:
- obligations do not disappear silently
- reserve changes reconcile explicitly
- historical settlement remains visible
- emergency actions leave a trace
- capital priorities do not change casually after the fact
Why this matters
Without enough control, OmegaX is unsafe.
With too much discretionary control, OmegaX stops looking like public infrastructure.
The right answer is narrow, explicit, auditable governance.