[study] (1h) Migration playbook for critical bugs — deploy-v2 + user withdraw-redeposit

[ozpool]

Goal

Understand what happens when a critical bug is found in v1.

Time estimate

1h (single focused session)

Prerequisites

• [study] (2h) Immutable core — no-proxy philosophy, governance as attack surface #114 (P15) — Immutable core — no-proxy philosophy, governance as attack surface

Study plan (in order)

1. [15 min] PRISM_PRD_v1.0.html §13 + PRISM CLAUDE.md migration section
2. [15 min] Playbook: deploy v2 → dApp shows v1 as deprecated → users withdraw from v1, redeposit into v2
3. [15 min] Invariants that survive: withdraw-never-pausable guarantee (P7) means users can always exit
4. [15 min] Cost to users: 2 txs (withdraw + deposit), possible slippage, lost accrued fees on closed v1 vault

Total: 60 min

After studying, you can

• Describe deploy-v2 + deprecate-v1-UI + support communication
• Identify which invariants survive migration
• Articulate the cost to users
• Sketch automation: migration bot, one-click 'move to v2' in dApp

Tradeoff prompt for the architectural review

What automation could make migration painless?

References

• PRISM_PRD_v1.0.html §13
• PRISM CLAUDE.md