# ETH Front Desk — rebuild recipe

Revision: ethcc-20260909-fc00948a

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

This is a prototype, not an operating support service. The source form is explicitly non-delivering; no requests or messages were sent.

## 1. Define the experience

Build a new interpretation of ETH Front Desk: A prototype for routing Ethereum founders to practical ecosystem support. 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

Use support categories, eligibility and capacity rules supplied by an actual operator. Keep prototype contacts and routing examples clearly labeled; do not imply real people have agreed to help.

## 3. Build the core flow

Build structured intake and a visible routing/status flow. Keep the first version a non-delivering prototype. Add a real inbox or Telegram integration only after explicit operator authorization and delivery testing.

## 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.