Converted from source DOCX

Automated text/table extraction for archival convenience. The original DOCX remains the authoritative visual source if formatting matters.

SPAWN.FARM

Full Site Crawl & Current-State Inventory

Baseline documentation for the v2.0 rebuild

| At a glance Site: https://spawn.farm/ · Category: DeSci / DeFi launchpad Pages crawled: 28 (8 core · 10 documentation · 10 organism pages) Apparent build platform: Lovable (single-page React app; assets on Cloudflare R2) Prepared by: Purple AI · Status: current-state audit, pre-v2.0 |

| --- |

| Headline finding The live site is caught mid-migration between two blockchains — "Robinhood Chain" and "Arc" — and the two versions coexist and contradict each other across pages (different chain names, two different $SPAWN contract addresses, and opposite "live" vs "not deployed" claims). Resolving this into one source of truth should be the first content decision of v2.0. Details in Section 6. |

| --- |

1. Executive summary

This document is a complete inventory of spawn.farm as it exists today. Every reachable page was crawled and its structure, metadata, and content recorded so we have a stable, agreed picture of the starting point before designing and building v2.0.

Spawn positions itself as a "DeSci launchpad": a platform where a creator can deploy a small, formally-specified computational model (an "organism") together with its own token in a single transaction, where trading fees fund the compute that keeps the model running, and where a provenance document is a hard gate on launching. The site is heavy on precise, technical, deliberately non-promotional copy.

The site divides cleanly into three content types:

Core pages (8): home, explore, launch flow, treasury, token, and two whitepaper renderings.
Docs (10): documentation articles plus introduction and FAQ.
Organisms (10): model pages sharing one rich template; seven run live in-browser, three are illustrative examples.

The most consequential observations for v2.0 are content-integrity issues rather than visual ones: the site is mid-migration between chains and its pages disagree with one another, the treasury page renders no server-side content, and the header/footer navigation is inconsistent.

2. Platform, stack & global observations

Signals gathered during the crawl about how the current site is built. These are inferences from URLs and markup, to be confirmed with the client / repo access before v2.0 planning is finalized.

Attribute	Observed
Build platform	Lovable — preview/build URLs and asset paths appear throughout meta tags.
Rendering	Client-side React SPA. Data-driven pages render placeholders in fetched HTML.
Asset hosting	Cloudflare R2 bucket for logo mark and OG images.
Chain / web3	Wallet connect via EIP-6963 injected discovery, WalletConnect, and Coinbase Wallet SDK. Reads on-chain data; no launch contracts deployed yet.
Analytics / SEO	OpenGraph + Twitter card metadata present; canonical tags inconsistent.
Current community contact	spawnfarmCTO@proton.me

Nav items: Organisms (/explore) · Launch (/launch) · Docs (/docs) · Treasury (/treasury) · $SPAWN (/token) · wallet.

Observation: Treasury is missing from header/footer on several pages.

Four-column footer with brand blurb, contact, site links, docs links, risk/FAQ, X, and varying disclaimer wording.

3. Site map / page inventory

3.1 Core pages

#	Page	URL	Type
1	Home	/	Marketing / landing
2	Organisms (Explore)	/explore	Listing / filterable index
3	Launch an organism	/launch	Multi-step form
4	What is Spawn	/docs	Docs hub + article
5	Treasury and buybacks	/treasury	Live on-chain data (JS)
6	$SPAWN token	/token	Token info + live market (JS)
7	Whitepaper (print)	/whitepaper	Long-form document
8	Whitepaper (interactive)	/whitepaper-classic	Long-form document

3.2 Documentation pages

#	Page	URL
9	Simplified Introduction	/docs/simplified-introduction
10	FAQ	/docs/faq
11	Risk disclosure	/docs/risk
12	Organism specification	/docs/specification
13	Model classes	/docs/model-classes
14	Why provenance is required	/docs/provenance
15	Runtime funding and farming	/docs/runtime
16	Verification and replay	/docs/verification
17	The liquidity lock	/docs/liquidity-lock
18	Launching an organism	/docs/launching

3.3 Organism pages

#	Organism	Ticker	Class	Status	URL
19	Heading Ring	$RING	connectome-derived	Running — no pool	/organisms/heading-ring
20	Physarum Network	$PHYSARUM	agent-based	Running — no pool	/organisms/physarum-network
21	BZ Spirals	$BZ	reaction–diffusion	Running — no pool	/organisms/bz-spirals
22	Larval Peristalsis	$LARVA	agent-based	Running — no pool	/organisms/larval-peristalsis
23	Tripod Walker	$TRIPOD	agent-based	Running — no pool	/organisms/tripod-walker
24	Orbium	$ORBIUM	cellular automaton	Running — no pool	/organisms/orbium
25	Vicsek Flock	$FLOCK	agent-based	Running — no pool	/organisms/vicsek-flock
26	EB Ring Attractor	$RING	connectome-derived	Not launched (illustr.)	/organisms/eb-ring-attractor
27	Gray–Scott Field	$GSF	reaction–diffusion	Not launched (illustr.)	/organisms/gray-scott-field
28	Kuramoto Lattice	$KURA	coupled oscillators	Not launched (illustr.)	/organisms/kuramoto-lattice

Note: two different organisms share ticker $RING.

4. Page-by-page breakdown

4.1 Home

Title: Spawn — launch a real, running model funded by its own token.

Purpose: explain core value proposition and drive to Launch.

Sections:

Hero with launch CTA.
Three-step “How a launch works.”
Organism preview cards.
“Three new engines, seeded and running.”
Formal organism tuple O = ⟨S,f,σ,τ⟩.
Runtime economics block.
Trust strip around provenance, hashes, and runtime visibility.
Footer.

4.2 Organisms / Explore

Filterable catalogue:

status filters;
model-class filters;
cards/table view;
sort by recent / market cap / 24h volume;
10 organism cards.

4.3 Launch

Six-step wizard:

Basics.
Provenance.
Runtime.
Funding rule.
Review.
Launch.

Step 2 provenance is a hard gate. Later steps unlock only after current validation passes.

4.4 Docs home

Docs hub plus “What is Spawn?” article. Technical/anti-hype copy, explicit distinctions between what is designed and what is live.

4.5 Treasury

Client-side on-chain read page for treasury holdings, buybacks, burns, routing transactions, and launch-gate burns.

Observation: meaningful values render only after client JS; server HTML shows loading states.

4.6 $SPAWN token

Token identity, contract address, Pons v2 pair, market embed, tax/burn-gate copy, and contract verification.

This page was one of the main sources of chain/live-status contradiction with the Arc-era docs.

4.7 Whitepapers

Two materially different v1.0 whitepapers:

Arc version.
Robinhood Chain “classic” version.

They disagree on chain, contract address, and deployment status.

4.8 Documentation article set

Simplified Introduction — plain-language model/token/runtime concept.
FAQ — wallets, local launches, farming, replay, current deployment state, liquidity, provenance, runtime depletion, token supply.
Risk — smart-contract, chain, liquidity, runtime, model, advice/warranty.
Organism specification — O = ⟨S,f,σ,τ⟩.
Model classes — equations, provenance boundaries, rejected overclaims.
Provenance — required document, hashes, citations, sourced-vs-designed.
Runtime — fee loop, c, escrow, farming, pause/resume.
Verification — recorded launch data, replay, hashes, reproducibility.
Liquidity lock — no-withdraw design surface.
Launching — six-step launch walkthrough.

Observation: six docs pages duplicate whitepaper sections closely, creating drift risk.

4.9 Organism template

Shared template includes:

name/ticker/slug/chain/status;
current state;
specification;
replay/verification;
full provenance;
runtime funding;
liquidity lock;
token;
market fields.

Running organisms compute in the visitor browser from a fixed seed; nothing is persisted or observed server-side. Illustrative organisms are worked examples with no live computation. No organism has a token/pool/market in this captured state.

5. Content, voice & design notes

5.1 Voice

Deliberately precise, technical, anti-hype. Repeatedly states what the platform cannot do or does not prove, foregrounds risk, and avoids marketing superlatives.

This credibility-through-restraint tone was identified as core to the brand.

5.2 Recurring components

Organism cards.
Status pills.
Equation/spec blocks.
Numbered step/trust strips.
Data panels with explicit “not deployed”/loading states.
Sourced-vs-designed tables.
Exposed-vs-not-implemented function tables.

5.3 SEO

OG/Twitter metadata present widely. Gaps:

canonical tags incomplete;
most pages share same OG image;
JS-only Treasury/Token pages have poor first-paint/server content.

6. Issues & inconsistencies found

6.1 CRITICAL — two blockchains coexist

“Arc” and “Robinhood Chain” both appear as canonical depending on page.

v2 requires one authoritative chain identity.

6.2 CRITICAL — two contradictory whitepapers

/whitepaper and /whitepaper-classic are both labeled v1.0 but materially disagree.

6.3 HIGH — $SPAWN live vs not-deployed contradiction

/token presents $SPAWN live/trading on Robinhood; Arc docs say no$ SPAWN deployed and cite a different address.

6.4 Medium/lower

Treasury has no server-rendered data.
Navigation inconsistent.
Footer disclaimers inconsistent.
Duplicate $RING ticker.
Both whitepaper pages have same print-style title.
Explorer links split across chains.
Whitepaper content duplicated into multiple docs pages.

7. Suggested next steps toward v2.0

Decide single source of truth for chain identity and $SPAWN status/address.
Consolidate to one whitepaper.
Establish single data store for chain/token/organism constants.
Add SSR/server reads for data pages.
Normalize global navigation/footer.
Build a component library from recurring patterns.
Confirm framework/hosting and rebuild from a controlled repo.

Prepared by Purple AI · spawn.farm current-state inventory · 28 pages crawled