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

# Emergency Procedures

Use this template for emergency governance actions such as pausing contracts, activating emergency controls, upgrading critical modules operations.

### **When to Use**

Emergency actions may be required during:

* Security vulnerabilities
* Exploit attempts or suspicious network activity
* Infrastructure failures
* Critical bugs in Participation, bridge, or governance systems

### **Proposal Title**

Provide a clear, specific title.

**Example:**\
Emergency Pause on Bridge Operations (24 Hours)

### **Summary**

Explain the emergency situation and the immediate action being requested.

### **Reason for Emergency**

Provide clear evidence or a brief case summary such as:

* Logs or diagnostic data
* Unusual network behavior
* Reported vulnerability

### **Proposed Action**

Describe exactly what action should be taken.

**Examples:**

* Pause a contract
* Temporarily pause operations
* Trigger a forced upgrade
* Adjust a critical system parameter

### **Duration**

State precisely how long the emergency measure should remain active.

### **Mitigation Steps**

Describe the steps that will follow after the emergency action:

* Patch development
* Auditor or security review
* Final incident report

### **Execution Payload**

Include any required governance payload or contract call.

### **Voting Options**

* **Accept**— Approve the action
* **Reject**— Reject the action
* **Neutral** —  Skip Voting