Spawn.farm — captured content archive ([all docs])

Captured from the live site during the crawl. This folder is the content and functional reference for the v2 / $RESPAWN rebuild.

Straight answer: do we have everything?

You asked for…	Do we have it?	What we actually have
The whitepaper	✅ Yes	Full text of both versions — the "Arc" print version and the older "Robinhood Chain" (classic) version. They differ materially. See `whitepaper-*.md`.
All docs from /docs	✅ Yes	All 11 documentation pages, full body text. Files `01`–`11`.
The source code of each page	❌ No	We have the rendered content of each page, not its source. A React SPA's component/style source can't be recovered from rendered HTML, and the deployed token is compiled bytecode. This has to come from the client's repo / Lovable export (front-end) and the verified contract on the explorer (token).
Understanding of the UI + what users fill out	✅ Yes (functional)	Full field-by-field launch flow captured in `launch-and-burn-to-mint-flow.md` — from the live Step-1 form + the official step-by-step walkthrough.
How to burn 100k to mint an organism	✅ Yes (documented flow)	The full burn-to-register process is in `launch-and-burn-to-mint-flow.md`. Note: this is the documented flow; the backend code that verifies the burn is not in our hands (see source-code row).

Bottom line: we have all the content, copy, and functional flows — enough to design and rebuild v2. We do not have the underlying source code. For a fresh v2 build that's usually fine (you rebuild the front-end anyway), but you should know the gap exists so nobody assumes we're "porting" existing code we don't actually hold.

The two real gaps to close before building

Front-end source → get the repo or Lovable export from the client. Without it, v2 is a fresh build (reproducing structure + content from this archive), not a port.
Contract source → pull the verified source of the deployed token from the "Contract" tab on robinhoodchain.blockscout.com. If it isn't verified, only the client/deployer has the real source. This matters more for $RESPAWN than for the site.

A minor content note: the two whitepapers contradict each other (chain, token address, live-status). That's captured, not resolved — the v2 launch spec covers consolidating them.

Folder contents

all-docs/
  00-README-inventory.md            ← this file
  launch-and-burn-to-mint-flow.md   ← UI fields + 6-step flow + 100k burn mechanics
  whitepaper.md                     ← full text; both /whitepaper (Arc) and
                                       /whitepaper-classic (Robinhood) captured, with
                                       the diverging sections flagged inline
  01-what-is-spawn.md               ← /docs
  02-simplified-introduction.md     ← /docs/simplified-introduction
  03-organism-specification.md      ← /docs/specification
  04-model-classes.md               ← /docs/model-classes
  05-why-provenance.md              ← /docs/provenance
  06-runtime-funding.md             ← /docs/runtime
  07-verification-replay.md         ← /docs/verification
  08-liquidity-lock.md              ← /docs/liquidity-lock
  09-launching.md                   ← /docs/launching
  10-risk.md                        ← /docs/risk
  11-faq.md                         ← /docs/faq

Repeated site chrome (header nav, footer columns) has been trimmed from each file — that's documented separately in the site-inventory doc. Each file keeps the page's real body content.