# Veil Protocol — rebuild recipe

Revision: pooltogether-full-20260909-c04b16c4

Reconstructed recipe; not the original prompts. End-to-end regeneration is untested.

The captured interface labels unavailable wallet data and planned multi-vault features. No transactions or privacy guarantees were independently verified.

## 1. Define the experience

Build a new interpretation of Veil Protocol: A multi-vault interface study around one configured Sepolia confidential prize vault. Read the repository instructions and preserve existing work first. Reconstruct the idea from this selection; do not promise an exact recreation. Start with one complete useful flow.

## 2. Prepare sources and assets

Start from the retained confidential-prize-savings source and lockfile. Document chain ID, vault addresses, token interfaces and which capabilities are implemented or planned. Use testnet only during reconstruction.

## 3. Build the core flow

Build one source-backed vault card, a detail view, a capability map and explicit unavailable states. Separate public contract reads from encrypted wallet state. Do not invent vaults, yields, balances or audit assurances.

## 4. Leave a working handoff

Check the real production route, keyboard operation, mobile layout, reduced motion, asset loading and failure states. Record what passed and what remains untested. Leave source, lockfiles, setup instructions, data provenance and unique selected assets in a compact package. Exclude secrets, dependencies and caches. Label reconstructed prompts honestly; a local package is not a NAS backup.