# POPE — rebuild recipe

Revision: pope-20260909-source-review

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

Research prototype with local and Sepolia paths. Screenshots do not certify cryptographic security or successful issuance. The original hosts remain available while credential and organizer recovery is unresolved.

## 1. Define the experience

Build a new interpretation of POPE: an attendance-proof prototype with attendee, organizer, staff and verifier roles. Read repository instructions and preserve existing work first. Treat these as reconstructed instructions, not the original prompt history. Keep local demonstrations visibly separate from real event operations.

## 2. Prepare sources and artifacts

Use the retained attendance-zk-pwa monorepo, workspace lockfile, protocol and crypto packages, circuits, proving artifacts and public event manifests. Record artifact hashes, circuit versions and Sepolia configuration. Keep attendee credentials, organizer keys and passphrases outside the showcase and source package. Independent security review remains a prerequisite for a real attendance pilot.

## 3. Build the connected flow

Reconstruct event setup, signed invite, attendee commitment QR, staff capability validation, organizer issuance request signing, local credential import, proof generation and verification. The staff device creates a scoped issuance request; the organizer signs the credential. Preserve explicit local-versus-on-chain results and require deliberate wallet approval for chain operations.

## 4. Prove recovery before moving origins

Check keyboard and mobile operation, malformed payloads and failure states. Use isolated test credentials to verify encrypted attendee export/import and organizer key plus manifest restoration on a replacement origin. Keep original origins available until each relevant device has a verified private recovery path. Do not copy private recovery material into logs or this recipe. Preserve selected source, lockfiles and artifact provenance; record untested boundaries and label the package as a local selection, not a complete mirror or NAS backup.
