# Ethweekly — rebuild recipe

Revision: ethweekly-20260909-a224d667

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

Captured issues are historical editorial artifacts. Headlines and protocol claims have not been independently revalidated. Rebuilding the workflow does not authorize publishing or emailing new issues.

## 1. Define the experience

Build a new interpretation of Ethweekly: A weekly Ethereum reading experiment with source-linked issues and an archive. 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

Preserve published issue artifacts, citation URLs, source registries, dates and editorial revisions. Separate local crawling from public serving, and retain human review before publication.

## 3. Build the core flow

Build a readable issue page, topic sections, archive and RSS. Keep generated drafts separate from published issues. Test citation integrity, date windows and stale-source behavior; enable scheduling and email only with explicit operating authorization.

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