# PoWeb — rebuild recipe

Revision: poweb-20260909-4e887583

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

The original advertises five-hour hosted job and ZIP retention. This selection does not contain user exports or prove archive correctness.

## 1. Define the experience

Build a new interpretation of PoWeb: A POAP preservation utility that packages badge records, artwork and ownership evidence. 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

Define normalized POAP records, raw source responses, media hashes, chain/block provenance and a versioned manifest. Use the retained source as a starting point and document API and temporary storage dependencies.

## 3. Build the core flow

Implement discovery, ownership verification, packaging and offline verification as separate steps. Verify one authorized public collection end to end, including partial-source failures and reopening the downloaded archive after hosted expiry.

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