# 9. Safety, Governance, and Emergency Controls

[Back to whitepaper overview](/lsteak-protocol-docs/lsteak-whitepaper-v2.2/overview.md)

LSteak is designed to remain operational through market volatility, low activity, and adverse conditions without discretionary intervention.

Safety mechanisms exist to protect accounting integrity and investor fairness in catastrophic scenarios only.

### 9.1 Governance Architecture and Constraints

Governance within LSteak is intentionally layered, permissioned, and delayed.

There are three governance tiers, each with strictly limited authority:

* Tier 1 — Emergency Control
  * Emergency pause only
  * No ability to move funds, change parameters, or execute upgrades
* Tier 2 — Parameter Governance
  * Bounded variable adjustments
  * Subject to mandatory timelocks
  * Cannot bypass fixed invariants
* Tier 3 — Treasury and Structural Actions
  * Treasury routing
  * Upgrades and structural changes
  * Always subject to timelocks and multisig approval

All non-emergency governance actions are delayed by a minimum 72-hour timelock.

Fixed invariants cannot be overridden by governance.

### 9.2 Emergency Pause

Emergency pause is designed exclusively for catastrophic failure scenarios.

When activated, it halts all protocol transactions.

Market conditions alone are never a valid trigger.

### 9.3 Time-Bound Pause and Extensions

The emergency pause is time-limited:

* Initial pause duration: up to 72 hours
* Automatic resume: Yes, if no further action is taken

Extensions require elevated multisig approval.

### 9.4 Liquidation Framework (Exceptional Only)

If the protocol cannot safely resume, full liquidation may be initiated.

In liquidation:

* Backing is liquidated
* Proceeds distribute pro-rata to LSTEAK holders
* Distribution is purely mechanical

### 9.5 LSaaS During Pause and Liquidation

When LSteak enters emergency pause, all LSaaS systems pause.

In liquidation, each LSaaS silo resolves exactly as a partner exit.


---

# Agent Instructions: 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:

```
GET https://lsteak-protocol.gitbook.io/lsteak-protocol-docs/lsteak-whitepaper-v2.2/9.-safety-governance-and-emergency-controls.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.