# Kohakool — rebuild recipe

Revision: kohakool-20260909-677ad156

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

The router uses mock pools. The original wallet targets Sepolia and alpha, unaudited SDKs. Transaction references are historical project records; wallet recovery, balances and private withdrawals were not verified for this selection.

## 1. Define the experience

Build a new interpretation of Kohakool: a study of the Kohaku privacy-plugin interface, with a clearly labelled concept router and a separate Sepolia wallet boundary. Read repository instructions first. Treat these prompts as a reconstruction, not the original conversation or an exact restoration. Start with the public explanatory and concept-demo flow.

## 2. Prepare sources and assets

Preserve the engine, plugin-standard provenance, router, React/Vite interface, lockfile and selected public circuit/WASM assets. Record the exact SDK and circuit versions and their licenses. Keep the public transaction references as historical project evidence. Never include wallet mnemonics, private keys, browser storage or endpoint credentials in the project archive.

## 3. Build the core flow

Build a labelled mock-pool router with amount input, balanced/privacy-first ranking, protocol cards and a public-to-shielded visualization. Keep the real wallet in a separate flow. If restoring wallet functionality, constrain it to the documented test network, make recovery/export explicit, and distinguish relayed private withdrawal from the non-private ragequit exit. Do not claim that mock routing chooses routes for real funds.

## 4. Leave a working handoff

Verify the public demo, About and roadmap routes on desktop and mobile without opening a wallet. Record untested wallet, proving and transaction behavior honestly. Preserve the public runtime assets and upstream provenance with the source archive. Before retiring an original wallet origin, obtain owner confirmation that no wallet state requires preservation or that independent recovery is complete; a same-browser encrypted save and a source archive do not prove recovery.