Redemption Workflow

A redemption moves through four explicit handoffs: the investor records a business request, the manager prices and approves it after checking liquidity, the investor submits the on-chain requestRedeem, and the manager fulfills the confirmed Vault request before the investor claims the payout.

Manager approval must not jump directly to fulfillment. Until scanner confirmation records the request effect, the manager state is Awaiting investor redemption request and fulfillRedeem is not ready.

The Fund Treasury Vault redemption operations also describe a delegated manager or platform alternative. That alternative is valid only when prior investor authorization and a compatible execution path exist. The current interactive workflow below keeps investor signing explicit.

Manager And Investor Sequence

Manager Flow

The manager action depends on the current milestone:

• Pending: review the request, set the price and payout, verify liquidity, and approve.
• Approved without a request effect: show Awaiting investor redemption request. Do not offer fulfillment or fulfillment retry.
• Confirmed requestRedeem: prepare and authorize fulfillRedeem with the fund wallet.
• Fulfillment submitted: wait for chain-backed confirmation.
• Claimable: wait for the investor claim.
• Claimed: show the redemption as completed.

Investor Flow

The critical handoff order is:

Manager approval
    -> investor requestRedeem
        -> manager fulfillRedeem
            -> investor claim

Implementation Flow

See Redemption Operations: Potential Issues for authorization, liquidity, interruption recovery, and batch-accounting requirements.