> 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/aspan-mechanics/system-rebalancing.md).

# System Rebalancing

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.

System rebalancing is part of ASPAN’s stability design. When collateral conditions weaken, reducing apUSD liabilities can improve the collateral ratio while changing the assets held by the staking vault.

### Conceptual flow

1. Stability conditions are evaluated using the configured collateral valuation and thresholds.
2. A portion of apUSD held by the Stability Pool can be used to reduce protocol liabilities.
3. The vault receives residual xBNB exposure under the applicable accounting and contract rules.

Rebalancing changes the allocation of existing economic risk. Issuing xBNB does not create new external collateral or guarantee recovery from a shortfall.

### What changes for s-apUSD holders

A vault that previously held apUSD can hold a mixture of apUSD and xBNB after a stability operation. Redemptions during stability mode can therefore include both assets.

xBNB is a leveraged residual claim whose value can fall to zero. This conversion should be understood as risk transfer, not a guaranteed opportunity to buy a market bottom.

### Implications for agent payments

A scheduled payment requires the appropriate liquid token. An operator cannot assume the full accounting value of s-apUSD will be available immediately as apUSD.

The proposed operating-balance workflow therefore separates eligible idle funds from liquid payment reserves and must account for withdrawal delays and changes in redemption assets.

### Deployment details

The actual trigger, callable functions, permissions, timing, and conversion calculation depend on the deployed version and configuration. Historical threshold examples do not establish current production parameters. The current interactive prototype does not verify production execution.
