Define the recovery path
Managed Resolution V1 is designed but not active in the published deployment. It specifies recovery authority, pricing, investor rights, and settlement rules at origination.
Managed Resolution V1 is inactive.
Review the recovery design.
Set the policy.
In the recovery design, record the sale floor and decision authority at origination so sale proposals follow terms set before a draw.
Review a proposed sale.
Review proposed sale terms against the recorded floor, with below-floor proposals opening the investor veto path before settlement.
Apply recovered cash.
Follow how realized recovery proceeds are allocated to recorded claims under the specified payout order and each investor’s entitlement.
Claims survive a later exit.
Recovery entitlements are recorded against funding positions. A later exit does not erase an earlier loss claim.
Readiness to act is built before a crisis, not during one…
Understand recovery responsibilities.
- A veto has limits. A veto can stop a below-floor proposal under the design. It does not guarantee another buyer, a better price, or timing.
- Responsibilities stay assigned. The design assigns the recovery operator, approvers, and recipients before they need to act.
Credit risk at industry scale.
$76.3T
Assets in the FSB narrow nonbank measure
12%
Narrow-measure asset growth in 2024
29
Jurisdictions in the FSB monitoring exercise
FSB, 16 DEC 2025. 2024 data across 29 jurisdictions. The narrow measure covers nonbank credit activities with bank-like financial stability risks, beyond private credit alone.
Recovery guides.
Recovery rules at origination.
Review the valuation requirements, recovery authority, sale conditions and investor loss allocation recorded at origination before a borrower draws funds.
Read guide
Credit recovery rights and responsibilities.
Review recovery authority, investor protections and beneficiary records to understand who can act on impaired credit and receive later proceeds.
Read guide
Recovery questions.
Read documentationManaged Resolution V1 is a separate specified extension. It is not activated in the published deployment. Availability needs confirmation for any proposed facility.