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

# Four-Tier Defense System

Technical reference for native ASPAN DeFi, an optional strategy within ASPAN Account. These mechanics do not describe all account assets or the planned external-strategy ASPAN Vaults.

This framework describes four categories of protocol risk response. It is a conceptual guide; it does not certify that every mechanism, threshold, or reserve is active in a particular deployment.

### 1. Economic incentives

Dynamic mint and redemption fees can encourage transactions that improve collateral balance and discourage actions that weaken it. Their effectiveness depends on market participation, executable pricing, and available capital.

### 2. System rebalancing

Stability operations can reduce apUSD liabilities and change the staking vault’s asset mix. This may transfer xBNB exposure to s-apUSD holders. It can improve an accounting ratio without eliminating losses or ensuring uninterrupted redemption.

### 3. Recapitalization

Recapitalization requires actual external capital or available reserves, a defined authorization process, and an executable mechanism. No automatic treasury rescue, debt-token issuance, or lender-of-last-resort guarantee is established by these docs.

### 4. Emergency controls

Appropriate pause and failure-handling controls can limit further exposure when pricing, collateral, or contracts malfunction. The scope, authorized roles, and effect on minting and redemption must be verified for the deployed version.

### Additional requirements for payments

The proposed payment layer introduces separate risks: agent authorization, spending limits, acceptance evidence, cancellation, refunds, and disputes. A core DeFi defense mechanism does not establish security for those payment functions.

Production permissions, payment contracts, provider adapters, and independent security review remain part of the launch work. Simulated approvals in the current demo are not an enforcement guarantee.
