# rauchg.com: rebuilding an RSC blog from captured Flight output > Documents a website-rebuild-skill case that decodes browser-delivered React Server Component Flight streams, reconstructs a buildable Next project and compares its output with a captured site. The reported rauchg.com campaign uses route-tree comparison and module-reference mapping; the new server source is inferred from observable output. - Type: Case study - Targets: Website - Category: Independent reconstruction cases - Relationship: Independent reconstruction project - Sources reviewed: 2026-10-17 - Added to the catalog: 2026-10-17 - Original resource: - Catalog page: - Record JSON: - Chinese version: [简体中文](https://awesomerea.org/zh/resources/rauchg-rsc-reconstruction-case/index.md) ## Requirements & limits - **Prerequisites:** The documented rauchg.com snapshot used Next 16.1.1, Turbopack and React 19 canary. The tooling requires Node.js 22+ and a local Chrome/Chromium for comparison; some stages invoke version-pinned external tools. Repeating the method needs an authorized target snapshot and a separately built reconstruction, not just the skill repository. - **Scope:** Flight decoding exposes delivered element trees, route state and client-module references. The reconstructed server-component source is explicitly an inference from that output; flight-to-mdx also needs site-specific shape/link adaptations. - **Testing evidence:** The author reports 18/18 routes passing a Flight semantic gate and a runtime sweep for this case. The gate compares normalized trees and enforces a global module-ID bijection. It normalizes build-hash namespaces and selected encoding differences; configured prop/class exclusions can omit registered fields or subtrees. - **Testing evidence:** The gate does not check CSS, so layout, fonts and rendered pixels need separate comparisons. Public synthetic self-tests include changed-text rejection and rejection of a one-to-many module mapping. - **Limits:** The method explicitly leaves unobserved error responses, database/write paths, server caches, dynamic-image generator source and unlinked routes unresolved. The author also notes possible model-training familiarity with a nominally blind target. - **License:** MIT applies to the skill and tooling, not to reconstructed websites, their scripts, fonts or other assets. The source documents separate authorization/publication decisions and private, noindex output defaults. ## Primary sources 1. 2. 3. 4. 5. 6. 7. 8. ## More in Websites - [BaoCut Slides: adapting an interactive web editor](https://awesomerea.org/resources/baocut-slides-editor-case/index.md) · Case study - [REA in Claude Code: an isolated static-analysis A/B trial](https://awesomerea.org/resources/rea-claude-code-isolated-ab-case/index.md) · Case study - [Dinosaur runner: an REA-inspected speed rule rebuilt with Codex](https://awesomerea.org/resources/rea-dino-runner-community-case/index.md) · Case study - [Terminal: a Rust terminal informed by TradingView chart research](https://awesomerea.org/resources/terminal-tradingview-rea-chart-case/index.md) · Case study - [BaoCut Design: porting reconstructed canvas and design-system editors](https://awesomerea.org/resources/baocut-design-canvas-case/index.md) · Case study - [whatsapp-web-reveng: documenting the legacy WhatsApp Web protocol](https://awesomerea.org/resources/whatsapp-web-reveng-legacy-protocol-case/index.md) · Case study ## About this entry The description was reviewed against primary sources. Original editorial content: MIT. Linked projects, papers and assets retain their own rights and licenses.