Share mobility

Torq vault shares are permissioned financial state. Share mobility can depend on investor identity, wallet status, trusted recipients, transfer guards, allowances, vault policy, pause state, and lifecycle synchronization. The maintained adapters remain Developer Preview.

Integration surfaces

• role.asset_manager.vaultShareMobilityManagerAction for approved manager-side policy and status actions.
• role.lender.vaultShareMobilityInvestorAction for approved investor-side mobility actions.
• role.lender.investorRequestRedeem and role.lender.investorFulfillRedeem for controlled exits.
• Canonical wallet, position, allowance, trusted-recipient, personal-guard, adapter, and vault state through the current resource and GraphQL references.

Prepare from current state

Every mobility action must bind the current wallet, vault, network, actor role, identity evidence, policy state, and destination. Do not cache eligibility or mobility status across wallet, network, identity, vault, or chain changes.

Completion and failure

An emitted event or successful receipt is insufficient for customer-visible mobility. Wait for the tracked workflow and canonical readback of the exact resulting state. Frame unrelated balances, allowances, recipients, and mobility policy as unchanged in the product's own reconciliation.

Fingerprint drift, revoked eligibility, an untrusted recipient, stale status, a paused vault, and a blocked personal guard must fail closed. Do not silently replace transfer with redemption or route around the configured mobility adapter.

Continue with Embed Torq Earn, Typed workflows, and Security.