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

# Risk Management

Risk parameters affect the actions guardians authorise and validators interpret. They do not guarantee that collateral remains sufficient through every market move or infrastructure outage.

The [published parameter reference](https://docs.ducatprotocol.com/how-ducat-works/protocol-parameters.md) identifies the anchor and values used in these explanations. Use that reference rather than treating an undated percentage as a universal constant.

### Decisions and their effects

| Area                                      | Effect of a change                                                                                                    |
| ----------------------------------------- | --------------------------------------------------------------------------------------------------------------------- |
| Borrowing ratio                           | Changes required collateral for risk-increasing actions. A higher floor can reduce borrowing and withdrawal capacity. |
| Liquidation thresholds and oracle buckets | Changes the commitments selected for affected vault actions and when their liquidation paths can be enabled.          |
| Liquidation tax and rebate                | Changes reserve revenue, collateral available to liquidators and the BTC needed to recapitalise assumed debt.         |
| Minimum debt and BTC outputs              | Changes which small positions and residual outputs can be constructed.                                                |
| Oracle and guardian configuration         | Changes accepted identities and signing dependencies for the applicable profile.                                      |
| Treasury or application fees              | Requires its own defined accounting and authority; it should not be inferred from unrelated anchor terms.             |

### Existing vaults

A confirmed vault output commits to concrete keys and hashlocks. Publishing a new oracle key or voting for a different guardian does not rewrite that output.

The implementation carries version and historical-profile information so earlier transactions can be interpreted in context. The effect of an upgrade on an existing vault must still be specified for each action and migration path. Neither "all old vaults immediately use the new terms" nor "only newly opened vaults can ever be affected" is a sufficient general rule.

A change proposal should identify the publication, activation height, compatible software, historical rules and any transaction required from existing users.

### Emergency actions

There is no verified operational 51% emergency-vote mechanism in the documented deployment. A service refusing to sign new borrowing is an operational restriction; it is not the same as a Bitcoin consensus rule or proof that token governance has frozen issuance everywhere.

Emergency procedures must also account for repayment, closure and signer availability. Replacing configuration alone does not recover funds locked under unavailable keys.

### Limits of parameter policy

Deposits and repayments can improve a position, but they need an unspent vault and valid signatures. Liquidation requires an available preimage, guardian participation, liquidator capital and Bitcoin confirmation. Rapid price changes or delays can leave collateral below debt despite the configured thresholds.
