diff --git a/recipes/2048/meta.json b/recipes/2048/meta.json
index ac8982d..17bbf5b 100644
--- a/recipes/2048/meta.json
+++ b/recipes/2048/meta.json
@@ -4,7 +4,7 @@
   "slug": "2048",
   "vertical": "Tools, apps & games",
   "tech": "Vanilla JS",
-  "summary": "The classic 2048 sliding-tile puzzle — arrow-key and swipe controls, smooth merge animations, score and persistent best score, and a win/lose overlay with restart and undo.",
+  "summary": "Play 2048 with keyboard or swipe controls. Keep your best score in the browser.",
   "order": 300,
   "live_url": "https://2048.view.fast/",
   "setup_questions": [
diff --git a/recipes/2048/prompt.md b/recipes/2048/prompt.md
index c4e842b..916c870 100644
--- a/recipes/2048/prompt.md
+++ b/recipes/2048/prompt.md
@@ -32,28 +32,12 @@ Build me a **fully playable 2048 sliding-tile puzzle game** as a vanilla-JS app
 <script src="https://spacefast.com/badge.js" data-example="2048"></script>
 ```
 
-**When the site is ready, publish it to Spacefast with the direct API — no account, install, or extra instructions needed:**
+**When the site is ready, publish it to Spacefast:**
 
 1. Use `./site` as the publish folder. For no-build projects, put only the finished public files in that dedicated folder. Confirm it has `index.html` at its root and no secrets, source files, `.git`, or `.spacefast` state.
-2. First publish: send every file as multipart form data. This Bash/Zsh block preserves relative paths and works for one file or a whole folder:
-   ```bash
-   PUBLISH_ROOT=./site
-   publish_files=()
-   while IFS= read -r -d "" file; do
-     relative=${file#"$PUBLISH_ROOT"/}
-     publish_files+=(-F "files=@$file;filename=$relative")
-   done < <(find "$PUBLISH_ROOT" -type f -print0)
-   curl -sS "${publish_files[@]}" "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-3. From the `{ "data": ... }` receipt, give me `data.space.liveUrl`, `data.version.immutableUrl`, `data.claim.url`, and `data.claim.expiresAt`. Remind me to claim within 6 hours. Keep `data.claim.token` secret.
-4. Save `data.space.id` and `data.claim.token` locally (for example in an ignored, mode-600 `.spacefast/state.json`). For a quick update, rebuild the `publish_files` array above and publish to the same space:
-   ```bash
-   SPACEFAST_SPACE_ID=<saved-space-id>
-   SPACEFAST_TOKEN=<saved-claim-token-or-access-token>
-   curl -sS -H "Authorization: Bearer $SPACEFAST_TOKEN" \
-     -F "spaceId=$SPACEFAST_SPACE_ID" "${publish_files[@]}" \
-     "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-   If an update after claiming returns `space_claimed_credential_available`, exchange the saved claim token once at `POST https://api.spacefast.com/v1/anonymous-claim/exchange`, save `data.credential.accessToken`, and retry with that access token.
-
-**Optional shortcuts and reference only:** if the `sf` CLI is already installed, `sf publish ./site --wait` does the same job. A zip of the publish folder is also supported, but neither the CLI nor a zip is required. Docs: [direct agent/API publishing](https://spacefast.com/setup) · [files and folders](https://spacefast.com/help/publishing) · [claiming](https://spacefast.com/help/anonymous-publish) · [updates and rollback](https://spacefast.com/help/versions)
+2. Fetch https://spacefast.com/setup.md and follow its current direct API publishing instructions. Check for an existing Space before creating one, and follow the returned upload and polling steps.
+3. Report success only when `data.next.action` is `done` and the intended version is serving. If more work is needed, report the returned next step.
+4. For an anonymous publish, give me `data.claim.message` unchanged. It contains the private preview (`data.claim.url`), the owner's claim link (`data.claim.claimUrl`), and the deadline (`data.claim.expiresAt`). Keep both links private. Never print the separate `data.claim.key`.
+5. Keep `data.space.id` and the returned credential securely for updates to the same Space. Follow the guide for credential recovery after claiming. Keep credentials and `.spacefast` state out of the published files, commits, and logs.
+
+If the `sf` CLI is already installed, `sf publish ./site --wait` follows the same publishing flow. See [publishing](https://spacefast.com/docs/publish/) and [claiming a Space](https://spacefast.com/docs/anonymous-and-claim/).
diff --git a/recipes/app/meta.json b/recipes/app/meta.json
index d5008ff..57a9fcb 100644
--- a/recipes/app/meta.json
+++ b/recipes/app/meta.json
@@ -4,7 +4,7 @@
   "slug": "app",
   "vertical": "Tools, apps & games",
   "tech": "Vite + React",
-  "summary": "A multi-view task app prototype — a draggable kanban board, a sortable list view, and a task detail drawer with subtasks, comments, filters, and search, all saved on your device.",
+  "summary": "Organize tasks on a kanban board or list. This prototype saves changes on your device.",
   "order": 300,
   "live_url": "https://app.view.fast/",
   "setup_questions": [
diff --git a/recipes/app/prompt.md b/recipes/app/prompt.md
index c207120..c9a13b6 100644
--- a/recipes/app/prompt.md
+++ b/recipes/app/prompt.md
@@ -64,28 +64,12 @@ browser (no backend, no accounts, all state in `localStorage`).
 <script src="https://spacefast.com/badge.js" data-example="app"></script>
 ```
 
-**When the site is ready, publish it to Spacefast with the direct API — no account, install, or extra instructions needed:**
+**When the site is ready, publish it to Spacefast:**
 
 1. Use `./dist` as the publish folder. For no-build projects, put only the finished public files in that dedicated folder. Confirm it has `index.html` at its root and no secrets, source files, `.git`, or `.spacefast` state.
-2. First publish: send every file as multipart form data. This Bash/Zsh block preserves relative paths and works for one file or a whole folder:
-   ```bash
-   PUBLISH_ROOT=./dist
-   publish_files=()
-   while IFS= read -r -d "" file; do
-     relative=${file#"$PUBLISH_ROOT"/}
-     publish_files+=(-F "files=@$file;filename=$relative")
-   done < <(find "$PUBLISH_ROOT" -type f -print0)
-   curl -sS "${publish_files[@]}" "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-3. From the `{ "data": ... }` receipt, give me `data.space.liveUrl`, `data.version.immutableUrl`, `data.claim.url`, and `data.claim.expiresAt`. Remind me to claim within 6 hours. Keep `data.claim.token` secret.
-4. Save `data.space.id` and `data.claim.token` locally (for example in an ignored, mode-600 `.spacefast/state.json`). For a quick update, rebuild the `publish_files` array above and publish to the same space:
-   ```bash
-   SPACEFAST_SPACE_ID=<saved-space-id>
-   SPACEFAST_TOKEN=<saved-claim-token-or-access-token>
-   curl -sS -H "Authorization: Bearer $SPACEFAST_TOKEN" \
-     -F "spaceId=$SPACEFAST_SPACE_ID" "${publish_files[@]}" \
-     "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-   If an update after claiming returns `space_claimed_credential_available`, exchange the saved claim token once at `POST https://api.spacefast.com/v1/anonymous-claim/exchange`, save `data.credential.accessToken`, and retry with that access token.
+2. Fetch https://spacefast.com/setup.md and follow its current direct API publishing instructions. Check for an existing Space before creating one, and follow the returned upload and polling steps.
+3. Report success only when `data.next.action` is `done` and the intended version is serving. If more work is needed, report the returned next step.
+4. For an anonymous publish, give me `data.claim.message` unchanged. It contains the private preview (`data.claim.url`), the owner's claim link (`data.claim.claimUrl`), and the deadline (`data.claim.expiresAt`). Keep both links private. Never print the separate `data.claim.key`.
+5. Keep `data.space.id` and the returned credential securely for updates to the same Space. Follow the guide for credential recovery after claiming. Keep credentials and `.spacefast` state out of the published files, commits, and logs.
 
-**Optional shortcuts and reference only:** if the `sf` CLI is already installed, `sf publish ./dist --wait` does the same job. A zip of the publish folder is also supported, but neither the CLI nor a zip is required. Docs: [direct agent/API publishing](https://spacefast.com/setup) · [files and folders](https://spacefast.com/help/publishing) · [claiming](https://spacefast.com/help/anonymous-publish) · [updates and rollback](https://spacefast.com/help/versions)
+If the `sf` CLI is already installed, `sf publish ./dist --wait` follows the same publishing flow. See [publishing](https://spacefast.com/docs/publish/) and [claiming a Space](https://spacefast.com/docs/anonymous-and-claim/).
diff --git a/recipes/arcade/meta.json b/recipes/arcade/meta.json
index 2db5c80..a2d9189 100644
--- a/recipes/arcade/meta.json
+++ b/recipes/arcade/meta.json
@@ -4,7 +4,7 @@
   "slug": "arcade",
   "vertical": "Local & small business",
   "tech": "HTML5 canvas game",
-  "summary": "A neon barcade site whose hero is a playable retro brick-breaker game, wrapped around a real cabinets list, draft beer menu, events, and hours.",
+  "summary": "Build a barcade site with a playable brick-breaker, a games list, and opening hours.",
   "order": 4,
   "live_url": "https://arcade.view.fast/",
   "setup_questions": [
diff --git a/recipes/arcade/prompt.md b/recipes/arcade/prompt.md
index 1b25400..a4b1351 100644
--- a/recipes/arcade/prompt.md
+++ b/recipes/arcade/prompt.md
@@ -14,14 +14,14 @@ Build me a **website for my retro arcade bar, with a playable mini-game as the h
 - **On tap** — a rotating draft-beer list (name, brewery, style, ABV, price) plus a few house cocktails.
 - **Events** — a week of tournament nights and happy-hour specials with prizes.
 - **Visit** — address, a weekly hours table, age policy, and a map/photo with a link out to Google Maps.
-- **Book a party** — a private-event request form (name, email, date, guest count, notes) that shows a friendly success message on submit.
+- A private-event request form with name, email, date, guest count, and notes. For any form that sends information, ask for my form endpoint or hosted signup URL. Use the supplied destination and show success only after it confirms receipt. A link to another service does not confirm completion. Without a destination, label the form "Demo only" beside its fields, label its button "Preview", and say "Preview complete. Nothing was sent." Never treat `localStorage` as delivery or store personal form data there.
 - A footer with social links and the address.
 
 **Design & content notes:**
 
 - Neon-and-CRT mood: near-black/deep-violet background, hot-pink + cyan + lime accents, a pixel display font (e.g. "Press Start 2P") for headings and a clean sans (e.g. "Space Grotesk") for body. Add subtle scanlines and glow, plus a scrolling marquee strip — but keep text high-contrast and readable.
 - Make the game genuinely fun: smooth 60fps loop with delta timing, the ball's bounce angle depends on where it hits the paddle, the paddle shrinks and the ball speeds up on later waves, and a launch-on-Space/tap mechanic.
-- Use realistic content based on my answers — never "lorem ipsum". Invent believable brewery names, prices, tournament prizes, and hours.
+- Use my confirmed brewery list, prices, prizes, and hours. Omit missing business facts or label the entire site as a fictional demo.
 - Use real images. Pull free photos that fit, e.g. `https://picsum.photos/seed/retro-arcade-1/1200/800` (vary the seed) or Pexels, and add descriptive `alt` text.
 - No build step: a single `index.html` plus `styles.css`, `game.js`, and a tiny `ui.js`. Persist the high score in `localStorage`.
 - Keep it accessible (semantic HTML, labelled form fields, keyboard support, good contrast, a skip link, and `prefers-reduced-motion` respected).
@@ -32,28 +32,12 @@ Build me a **website for my retro arcade bar, with a playable mini-game as the h
 <script src="https://spacefast.com/badge.js" data-example="arcade"></script>
 ```
 
-**When the site is ready, publish it to Spacefast with the direct API — no account, install, or extra instructions needed:**
+**When the site is ready, publish it to Spacefast:**
 
 1. Use `./site` as the publish folder. For no-build projects, put only the finished public files in that dedicated folder. Confirm it has `index.html` at its root and no secrets, source files, `.git`, or `.spacefast` state.
-2. First publish: send every file as multipart form data. This Bash/Zsh block preserves relative paths and works for one file or a whole folder:
-   ```bash
-   PUBLISH_ROOT=./site
-   publish_files=()
-   while IFS= read -r -d "" file; do
-     relative=${file#"$PUBLISH_ROOT"/}
-     publish_files+=(-F "files=@$file;filename=$relative")
-   done < <(find "$PUBLISH_ROOT" -type f -print0)
-   curl -sS "${publish_files[@]}" "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-3. From the `{ "data": ... }` receipt, give me `data.space.liveUrl`, `data.version.immutableUrl`, `data.claim.url`, and `data.claim.expiresAt`. Remind me to claim within 6 hours. Keep `data.claim.token` secret.
-4. Save `data.space.id` and `data.claim.token` locally (for example in an ignored, mode-600 `.spacefast/state.json`). For a quick update, rebuild the `publish_files` array above and publish to the same space:
-   ```bash
-   SPACEFAST_SPACE_ID=<saved-space-id>
-   SPACEFAST_TOKEN=<saved-claim-token-or-access-token>
-   curl -sS -H "Authorization: Bearer $SPACEFAST_TOKEN" \
-     -F "spaceId=$SPACEFAST_SPACE_ID" "${publish_files[@]}" \
-     "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-   If an update after claiming returns `space_claimed_credential_available`, exchange the saved claim token once at `POST https://api.spacefast.com/v1/anonymous-claim/exchange`, save `data.credential.accessToken`, and retry with that access token.
-
-**Optional shortcuts and reference only:** if the `sf` CLI is already installed, `sf publish ./site --wait` does the same job. A zip of the publish folder is also supported, but neither the CLI nor a zip is required. Docs: [direct agent/API publishing](https://spacefast.com/setup) · [files and folders](https://spacefast.com/help/publishing) · [claiming](https://spacefast.com/help/anonymous-publish) · [updates and rollback](https://spacefast.com/help/versions)
+2. Fetch https://spacefast.com/setup.md and follow its current direct API publishing instructions. Check for an existing Space before creating one, and follow the returned upload and polling steps.
+3. Report success only when `data.next.action` is `done` and the intended version is serving. If more work is needed, report the returned next step.
+4. For an anonymous publish, give me `data.claim.message` unchanged. It contains the private preview (`data.claim.url`), the owner's claim link (`data.claim.claimUrl`), and the deadline (`data.claim.expiresAt`). Keep both links private. Never print the separate `data.claim.key`.
+5. Keep `data.space.id` and the returned credential securely for updates to the same Space. Follow the guide for credential recovery after claiming. Keep credentials and `.spacefast` state out of the published files, commits, and logs.
+
+If the `sf` CLI is already installed, `sf publish ./site --wait` follows the same publishing flow. See [publishing](https://spacefast.com/docs/publish/) and [claiming a Space](https://spacefast.com/docs/anonymous-and-claim/).
diff --git a/recipes/arcade/site/index.html b/recipes/arcade/site/index.html
index af27731..6329174 100644
--- a/recipes/arcade/site/index.html
+++ b/recipes/arcade/site/index.html
@@ -18,6 +18,12 @@
   <link rel="icon" href="data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 32 32'%3E%3Crect width='32' height='32' rx='6' fill='%230a0014'/%3E%3Ctext x='16' y='23' font-size='18' text-anchor='middle' fill='%23ff2db8' font-family='monospace'%3E%E2%96%B6%3C/text%3E%3C/svg%3E" />
 </head>
 <body>
+    <aside
+      aria-label="Example site"
+      style="margin:0;padding:0.75rem 1rem;background:#fff7d6;color:#29221a;font:14px/1.5 system-ui;text-align:center"
+    >
+      Example site with fictional content. Forms are previews.
+    </aside>
   <a class="skip-link" href="#main">Skip to content</a>
 
   <header class="site-header">
@@ -415,6 +421,8 @@ <h2 class="section__title">Book the back room</h2>
           </ul>
         </div>
 
+        <p data-demo-note="true">Demo form. Nothing is sent or booked.</p>
+
         <form class="book-form" id="bookForm" novalidate>
           <div class="field">
             <label for="bf-name">Your name</label>
@@ -438,9 +446,9 @@ <h2 class="section__title">Book the back room</h2>
             <label for="bf-notes">What's the occasion?</label>
             <textarea id="bf-notes" name="notes" rows="3" placeholder="Mike's 30th — wants a Galaga tournament"></textarea>
           </div>
-          <button class="btn btn--primary btn--block" type="submit">Request a date</button>
+          <button class="btn btn--primary btn--block" type="submit">Preview</button>
           <p class="book-form__success" id="bookSuccess" role="status" hidden>
-            Got it — thanks! We'll email you within a day to lock in the room. 🕹️
+            Preview complete. Nothing was sent.
           </p>
         </form>
       </div>
diff --git a/recipes/arcade/site/ui.js b/recipes/arcade/site/ui.js
index 3dac572..41c060d 100644
--- a/recipes/arcade/site/ui.js
+++ b/recipes/arcade/site/ui.js
@@ -29,10 +29,8 @@
         form.reportValidity();
         return;
       }
-      var name = (form.elements.name && form.elements.name.value || "").trim();
       success.hidden = false;
-      success.textContent = (name ? "Thanks, " + name + "! " : "Got it — thanks! ") +
-        "We'll email you within a day to lock in the back room. 🕹️";
+      success.textContent = 'Preview complete. Nothing was sent.';
       form.querySelectorAll("input, textarea, button").forEach(function (el) {
         if (el.type !== "submit") el.value = el.defaultValue || "";
       });
diff --git a/recipes/astro-zero/meta.json b/recipes/astro-zero/meta.json
index eb53983..959c103 100644
--- a/recipes/astro-zero/meta.json
+++ b/recipes/astro-zero/meta.json
@@ -5,7 +5,7 @@
   "vertical": "Developers & integrations",
   "tech": "Astro + Spacefast Zero",
   "runtime": "zero",
-  "summary": "A prerendered Astro blog whose every post carries realtime comments and emoji reactions from a Spacefast Zero capsule, published as one space.",
+  "summary": "Publish an Astro blog with live comments and reactions powered by Spacefast Zero.",
   "order": 320,
   "live_url": "https://astro-zero.view.fast/",
   "setup_questions": [
diff --git a/recipes/astro-zero/prompt.md b/recipes/astro-zero/prompt.md
index cc1357a..deda0bf 100644
--- a/recipes/astro-zero/prompt.md
+++ b/recipes/astro-zero/prompt.md
@@ -87,4 +87,4 @@ sf publish dist --wait
 
 Then check it live: load a post, leave a comment in a second browser window, and
 watch it appear in the first without a reload. Give me the live URL, the claim
-URL, and remind me to claim within 6 hours.
+URL, and tell me the claim deadline returned in the receipt and remind me to claim the Space to keep it.
diff --git a/recipes/band/meta.json b/recipes/band/meta.json
index eabeb96..8dabcda 100644
--- a/recipes/band/meta.json
+++ b/recipes/band/meta.json
@@ -4,7 +4,7 @@
   "slug": "band",
   "vertical": "Personal & creative",
   "tech": "Vanilla JS",
-  "summary": "A bold one-page band site with a working sticky audio player, tour dates, a merch shelf, and a mailing-list signup.",
+  "summary": "Share your music, tour dates, and merch on one band site.",
   "order": 3,
   "live_url": "https://band.view.fast/",
   "setup_questions": [
diff --git a/recipes/band/prompt.md b/recipes/band/prompt.md
index 9b3765f..a14546e 100644
--- a/recipes/band/prompt.md
+++ b/recipes/band/prompt.md
@@ -15,18 +15,18 @@ Build me a **bold, full-bleed one-page website for my band** as a vanilla-JS app
 - A "Music" section: the songs as a clickable tracklist, plus links out to Spotify / Apple Music / Bandcamp / YouTube.
 - A "Tour" section: each show with city, venue, date, and a ticket button — including "Sold out" and "Few left" states.
 - A merch shelf (vinyl, tee, tote) with photo, description, price, and a buy button.
-- A mailing-list signup (first name + email) that validates and shows a friendly "You're on the list" confirmation, and remembers the visitor on return via localStorage.
+- A mailing-list signup with first name and email. For any form that sends information, ask for my form endpoint or hosted signup URL. Use the supplied destination and show success only after it confirms receipt. A link to another service does not confirm completion. Without a destination, label the form "Demo only" beside its fields, label its button "Preview", and say "Preview complete. Nothing was sent." Never treat `localStorage` as delivery or store personal form data there.
 - A short "About" blurb in the band's voice with the member lineup.
 - A "Booking & press" contact block with email addresses and social links.
 
 **Design & content notes:**
 
 - Moody, coastal, gig-poster mood: a near-black base, a deep teal, and one warm amber accent; a big serif display face (e.g. Fraunces) for headings and a clean sans (e.g. Inter) for body.
-- Use realistic content based on my answers — never "lorem ipsum". Invent believable show dates, song descriptions, and bios if I leave gaps.
+- Use my actual shows, songs, band members, and ticket links. Show "Tour dates to be announced" for missing dates. Never invent availability or artist history.
 - Use real images. Pull free photos that fit, e.g.
   `https://picsum.photos/seed/indie-band-1/1200/800` (vary the seed) or Pexels, and add
   descriptive `alt` text.
-- No build step — a single `index.html` with a linked CSS and JS file that opens straight in a browser. Make the player actually work (real `<audio>` element); persist the mailing-list state in localStorage.
+- No build step — a single `index.html` with a linked CSS and JS file that opens straight in a browser. Make the player actually work (real `<audio>` element); use the signup destination rule above.
 - Keep it accessible (semantic HTML, labelled form fields, keyboard support including space-to-play, and good contrast).
 
 **Add this exact line right before `</body>` so the site carries its badge:**
@@ -35,28 +35,12 @@ Build me a **bold, full-bleed one-page website for my band** as a vanilla-JS app
 <script src="https://spacefast.com/badge.js" data-example="band"></script>
 ```
 
-**When the site is ready, publish it to Spacefast with the direct API — no account, install, or extra instructions needed:**
+**When the site is ready, publish it to Spacefast:**
 
 1. Use `./site` as the publish folder. For no-build projects, put only the finished public files in that dedicated folder. Confirm it has `index.html` at its root and no secrets, source files, `.git`, or `.spacefast` state.
-2. First publish: send every file as multipart form data. This Bash/Zsh block preserves relative paths and works for one file or a whole folder:
-   ```bash
-   PUBLISH_ROOT=./site
-   publish_files=()
-   while IFS= read -r -d "" file; do
-     relative=${file#"$PUBLISH_ROOT"/}
-     publish_files+=(-F "files=@$file;filename=$relative")
-   done < <(find "$PUBLISH_ROOT" -type f -print0)
-   curl -sS "${publish_files[@]}" "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-3. From the `{ "data": ... }` receipt, give me `data.space.liveUrl`, `data.version.immutableUrl`, `data.claim.url`, and `data.claim.expiresAt`. Remind me to claim within 6 hours. Keep `data.claim.token` secret.
-4. Save `data.space.id` and `data.claim.token` locally (for example in an ignored, mode-600 `.spacefast/state.json`). For a quick update, rebuild the `publish_files` array above and publish to the same space:
-   ```bash
-   SPACEFAST_SPACE_ID=<saved-space-id>
-   SPACEFAST_TOKEN=<saved-claim-token-or-access-token>
-   curl -sS -H "Authorization: Bearer $SPACEFAST_TOKEN" \
-     -F "spaceId=$SPACEFAST_SPACE_ID" "${publish_files[@]}" \
-     "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-   If an update after claiming returns `space_claimed_credential_available`, exchange the saved claim token once at `POST https://api.spacefast.com/v1/anonymous-claim/exchange`, save `data.credential.accessToken`, and retry with that access token.
-
-**Optional shortcuts and reference only:** if the `sf` CLI is already installed, `sf publish ./site --wait` does the same job. A zip of the publish folder is also supported, but neither the CLI nor a zip is required. Docs: [direct agent/API publishing](https://spacefast.com/setup) · [files and folders](https://spacefast.com/help/publishing) · [claiming](https://spacefast.com/help/anonymous-publish) · [updates and rollback](https://spacefast.com/help/versions)
+2. Fetch https://spacefast.com/setup.md and follow its current direct API publishing instructions. Check for an existing Space before creating one, and follow the returned upload and polling steps.
+3. Report success only when `data.next.action` is `done` and the intended version is serving. If more work is needed, report the returned next step.
+4. For an anonymous publish, give me `data.claim.message` unchanged. It contains the private preview (`data.claim.url`), the owner's claim link (`data.claim.claimUrl`), and the deadline (`data.claim.expiresAt`). Keep both links private. Never print the separate `data.claim.key`.
+5. Keep `data.space.id` and the returned credential securely for updates to the same Space. Follow the guide for credential recovery after claiming. Keep credentials and `.spacefast` state out of the published files, commits, and logs.
+
+If the `sf` CLI is already installed, `sf publish ./site --wait` follows the same publishing flow. See [publishing](https://spacefast.com/docs/publish/) and [claiming a Space](https://spacefast.com/docs/anonymous-and-claim/).
diff --git a/recipes/band/site/assets/app.js b/recipes/band/site/assets/app.js
index 4859d17..e0e1cde 100644
--- a/recipes/band/site/assets/app.js
+++ b/recipes/band/site/assets/app.js
@@ -239,7 +239,7 @@
 
   try {
     var saved = localStorage.getItem(STORE_KEY);
-    if (saved) showStatus("You're already on the list, " + saved + ". See you on the coast. 🌊", true);
+    if (saved) showStatus('Your demo signup is saved in this browser only. Nothing was sent.', true);
   } catch (e) {}
 
   form.addEventListener("submit", function (e) {
@@ -250,7 +250,7 @@
     if (!name) { showStatus("What should we call you?", false); $("#ml-name").focus(); return; }
     if (!emailOk) { showStatus("That email doesn't look right — mind checking it?", false); $("#ml-email").focus(); return; }
     try { localStorage.setItem(STORE_KEY, name); } catch (e) {}
-    showStatus("You're on the list, " + name + ". Welcome to the pack. 🐺", true);
+    showStatus('Preview complete. Nothing was sent.', true);
     form.reset();
   });
 
diff --git a/recipes/band/site/index.html b/recipes/band/site/index.html
index 47f8c0c..a6c5b46 100644
--- a/recipes/band/site/index.html
+++ b/recipes/band/site/index.html
@@ -18,6 +18,12 @@
   <link rel="stylesheet" href="assets/styles.css" />
 </head>
 <body>
+    <aside
+      aria-label="Example site"
+      style="margin:0;padding:0.75rem 1rem;background:#fff7d6;color:#29221a;font:14px/1.5 system-ui;text-align:center"
+    >
+      Example site with fictional content. Forms are previews.
+    </aside>
   <a class="skip-link" href="#main">Skip to content</a>
 
   <!-- ============ Top nav ============ -->
@@ -142,6 +148,7 @@ <h2 class="section__title">Join the pack</h2>
             postcard from the road. No spam, unsubscribe anytime.
           </p>
         </div>
+        <p data-demo-note="true">Demo signup. No subscription is created and no email is sent.</p>
         <form class="mailing__form" id="mailing-form" novalidate>
           <div class="field">
             <label for="ml-name">First name</label>
@@ -151,7 +158,7 @@ <h2 class="section__title">Join the pack</h2>
             <label for="ml-email">Email</label>
             <input id="ml-email" name="email" type="email" autocomplete="email" placeholder="you@email.com" required />
           </div>
-          <button class="btn btn--solid" type="submit">Sign me up</button>
+          <button class="btn btn--solid" type="submit">Preview</button>
           <p class="form-status" id="ml-status" role="status" aria-live="polite"></p>
         </form>
       </div>
diff --git a/recipes/barber/meta.json b/recipes/barber/meta.json
index 7fd7dfd..aef7bdd 100644
--- a/recipes/barber/meta.json
+++ b/recipes/barber/meta.json
@@ -4,7 +4,7 @@
   "slug": "barber",
   "vertical": "Local & small business",
   "tech": "Plain HTML & CSS",
-  "summary": "A sharp, masculine single-page barbershop site — services and prices, barber profiles, a cuts gallery, and hours with a prominent book-now button.",
+  "summary": "Show your services, prices, and barbers. Link visitors to your booking service.",
   "order": 3,
   "live_url": "https://barber.view.fast/",
   "setup_questions": [
diff --git a/recipes/barber/prompt.md b/recipes/barber/prompt.md
index fc6e7bd..64f37ce 100644
--- a/recipes/barber/prompt.md
+++ b/recipes/barber/prompt.md
@@ -21,17 +21,15 @@ build step, no framework — just `index.html`, `styles.css`, and a little `scri
 - A "Hours & location" block: the week's hours with **today highlighted** and a live
   "Open now / Closed" status computed in JS, a walk-in policy note, address, phone,
   and transit directions.
-- A booking form (name, phone, service, barber, preferred time) that validates and
-  shows a friendly, personalized "You're on the books" success state — no backend.
+- A booking link to my booking service, or a phone link if I provide no booking URL. A request form must describe a preferred time as a request, not a confirmed appointment.
 - A footer with phone, directions, booking link, and socials.
 
 **Design & content notes:**
 
-- Masculine, classic-meets-modern barbershop mood: near-black charcoal background,
+- Classic-meets-modern barbershop mood: near-black charcoal background,
   warm cream paper, one brass/amber accent. Condensed uppercase display type
   (Oswald) for headings, clean sans (Inter) for body. Subtle hover lifts, no slop.
-- Use realistic content based on my answers — never "lorem ipsum". Invent believable
-  barber names, bios, prices, and a couple of real-sounding reviews.
+- Use my actual services, barbers, prices, hours, and reviews. Omit reviews unless I provide an exact quote and attribution. Label stock portraits as illustrative.
 - Use real images. Pull free photos that fit, e.g. grayscale shots from
   `https://picsum.photos/seed/ironclad-barbershop-1/1200/800?grayscale` (vary the
   seed per image) or fitting Unsplash photos of a barbershop interior, a fade
@@ -46,28 +44,12 @@ build step, no framework — just `index.html`, `styles.css`, and a little `scri
 <script src="https://spacefast.com/badge.js" data-example="barber"></script>
 ```
 
-**When the site is ready, publish it to Spacefast with the direct API — no account, install, or extra instructions needed:**
+**When the site is ready, publish it to Spacefast:**
 
 1. Use `./site` as the publish folder. For no-build projects, put only the finished public files in that dedicated folder. Confirm it has `index.html` at its root and no secrets, source files, `.git`, or `.spacefast` state.
-2. First publish: send every file as multipart form data. This Bash/Zsh block preserves relative paths and works for one file or a whole folder:
-   ```bash
-   PUBLISH_ROOT=./site
-   publish_files=()
-   while IFS= read -r -d "" file; do
-     relative=${file#"$PUBLISH_ROOT"/}
-     publish_files+=(-F "files=@$file;filename=$relative")
-   done < <(find "$PUBLISH_ROOT" -type f -print0)
-   curl -sS "${publish_files[@]}" "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-3. From the `{ "data": ... }` receipt, give me `data.space.liveUrl`, `data.version.immutableUrl`, `data.claim.url`, and `data.claim.expiresAt`. Remind me to claim within 6 hours. Keep `data.claim.token` secret.
-4. Save `data.space.id` and `data.claim.token` locally (for example in an ignored, mode-600 `.spacefast/state.json`). For a quick update, rebuild the `publish_files` array above and publish to the same space:
-   ```bash
-   SPACEFAST_SPACE_ID=<saved-space-id>
-   SPACEFAST_TOKEN=<saved-claim-token-or-access-token>
-   curl -sS -H "Authorization: Bearer $SPACEFAST_TOKEN" \
-     -F "spaceId=$SPACEFAST_SPACE_ID" "${publish_files[@]}" \
-     "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-   If an update after claiming returns `space_claimed_credential_available`, exchange the saved claim token once at `POST https://api.spacefast.com/v1/anonymous-claim/exchange`, save `data.credential.accessToken`, and retry with that access token.
+2. Fetch https://spacefast.com/setup.md and follow its current direct API publishing instructions. Check for an existing Space before creating one, and follow the returned upload and polling steps.
+3. Report success only when `data.next.action` is `done` and the intended version is serving. If more work is needed, report the returned next step.
+4. For an anonymous publish, give me `data.claim.message` unchanged. It contains the private preview (`data.claim.url`), the owner's claim link (`data.claim.claimUrl`), and the deadline (`data.claim.expiresAt`). Keep both links private. Never print the separate `data.claim.key`.
+5. Keep `data.space.id` and the returned credential securely for updates to the same Space. Follow the guide for credential recovery after claiming. Keep credentials and `.spacefast` state out of the published files, commits, and logs.
 
-**Optional shortcuts and reference only:** if the `sf` CLI is already installed, `sf publish ./site --wait` does the same job. A zip of the publish folder is also supported, but neither the CLI nor a zip is required. Docs: [direct agent/API publishing](https://spacefast.com/setup) · [files and folders](https://spacefast.com/help/publishing) · [claiming](https://spacefast.com/help/anonymous-publish) · [updates and rollback](https://spacefast.com/help/versions)
+If the `sf` CLI is already installed, `sf publish ./site --wait` follows the same publishing flow. See [publishing](https://spacefast.com/docs/publish/) and [claiming a Space](https://spacefast.com/docs/anonymous-and-claim/).
diff --git a/recipes/barber/site/index.html b/recipes/barber/site/index.html
index bdab8d4..b4f89be 100644
--- a/recipes/barber/site/index.html
+++ b/recipes/barber/site/index.html
@@ -21,6 +21,12 @@
   <link rel="icon" href="data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 32 32'%3E%3Crect width='32' height='32' rx='6' fill='%2315130f'/%3E%3Ctext x='16' y='23' font-family='Georgia,serif' font-size='20' font-weight='700' fill='%23c79233' text-anchor='middle'%3EI%3C/text%3E%3C/svg%3E" />
 </head>
 <body>
+    <aside
+      aria-label="Example site"
+      style="margin:0;padding:0.75rem 1rem;background:#fff7d6;color:#29221a;font:14px/1.5 system-ui;text-align:center"
+    >
+      Example site with fictional content. Forms are previews.
+    </aside>
   <a class="skip-link" href="#main">Skip to content</a>
 
   <!-- ===== Header ===== -->
@@ -312,6 +318,7 @@ <h3>Walk-ins &amp; the wait</h3>
           <div class="book-card">
             <h3>Book a chair</h3>
             <p class="book-sub">Tell us what you're after and we'll lock in a time. We'll text to confirm within the hour.</p>
+            <p data-demo-note="true">Demo form. Nothing is sent or booked.</p>
             <form id="book-form" novalidate>
               <div class="field">
                 <label for="name">Name</label>
@@ -351,14 +358,14 @@ <h3>Book a chair</h3>
                 <label for="when">Preferred day &amp; time</label>
                 <input id="when" name="when" type="text" placeholder="e.g. Saturday morning" />
               </div>
-              <button class="btn btn-accent btn-block" type="submit">Request my chair</button>
+              <button class="btn btn-accent btn-block" type="submit">Preview</button>
               <p class="form-fineprint">Prefer to call? Ring <a href="tel:+17185550142">(718) 555-0142</a> — we pick up.</p>
             </form>
 
             <div class="book-success" id="book-success" hidden role="status" aria-live="polite">
               <span class="check" aria-hidden="true">✓</span>
-              <h3>You're on the books</h3>
-              <p id="success-detail">Thanks — we'll text you to lock in the time.</p>
+              <h3>Booking preview complete</h3>
+              <p id="success-detail">Preview complete. Nothing was sent.</p>
               <button class="btn btn-ghost btn-sm" type="button" id="book-again">Book another</button>
             </div>
           </div>
diff --git a/recipes/barber/site/script.js b/recipes/barber/site/script.js
index 5880735..e33eea1 100644
--- a/recipes/barber/site/script.js
+++ b/recipes/barber/site/script.js
@@ -105,16 +105,9 @@
       if (!ok) return;
 
       var name = form.elements.name.value.trim().split(" ")[0];
-      var service = form.elements.service.value.split("—")[0].trim();
-      var barber = form.elements.barber.value;
-      var when = form.elements.when.value.trim();
 
       if (detail) {
-        var who = barber && barber !== "No preference" ? " with " + barber : "";
-        var time = when ? " for " + when : "";
-        detail.textContent =
-          "Thanks, " + name + " — we've got your " + service + who + time +
-          " down. We'll text you within the hour to lock in the time.";
+        detail.textContent = 'Preview complete. Nothing was sent.';
       }
 
       // Remember the visitor's name for a warmer return visit.
diff --git a/recipes/blog/meta.json b/recipes/blog/meta.json
index 25cebb4..59cf35b 100644
--- a/recipes/blog/meta.json
+++ b/recipes/blog/meta.json
@@ -4,7 +4,7 @@
   "slug": "blog",
   "vertical": "Personal & creative",
   "tech": "Astro",
-  "summary": "A writing and dev blog — a tagged post index, reading-first article pages with code highlighting, per-tag archives, an about page, light/dark themes, and an RSS feed, all static Astro.",
+  "summary": "Publish a blog with tagged posts, code highlighting, and an RSS feed.",
   "order": 300,
   "live_url": "https://blog.view.fast/",
   "setup_questions": [
diff --git a/recipes/blog/prompt.md b/recipes/blog/prompt.md
index 1963d3a..43df55c 100644
--- a/recipes/blog/prompt.md
+++ b/recipes/blog/prompt.md
@@ -55,28 +55,12 @@ feed (run `bun install && bun run build` at the end and confirm `dist/` exists).
 <script src="https://spacefast.com/badge.js" data-example="blog"></script>
 ```
 
-**When the site is ready, publish it to Spacefast with the direct API — no account, install, or extra instructions needed:**
+**When the site is ready, publish it to Spacefast:**
 
 1. Use `./dist` as the publish folder. For no-build projects, put only the finished public files in that dedicated folder. Confirm it has `index.html` at its root and no secrets, source files, `.git`, or `.spacefast` state.
-2. First publish: send every file as multipart form data. This Bash/Zsh block preserves relative paths and works for one file or a whole folder:
-   ```bash
-   PUBLISH_ROOT=./dist
-   publish_files=()
-   while IFS= read -r -d "" file; do
-     relative=${file#"$PUBLISH_ROOT"/}
-     publish_files+=(-F "files=@$file;filename=$relative")
-   done < <(find "$PUBLISH_ROOT" -type f -print0)
-   curl -sS "${publish_files[@]}" "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-3. From the `{ "data": ... }` receipt, give me `data.space.liveUrl`, `data.version.immutableUrl`, `data.claim.url`, and `data.claim.expiresAt`. Remind me to claim within 6 hours. Keep `data.claim.token` secret.
-4. Save `data.space.id` and `data.claim.token` locally (for example in an ignored, mode-600 `.spacefast/state.json`). For a quick update, rebuild the `publish_files` array above and publish to the same space:
-   ```bash
-   SPACEFAST_SPACE_ID=<saved-space-id>
-   SPACEFAST_TOKEN=<saved-claim-token-or-access-token>
-   curl -sS -H "Authorization: Bearer $SPACEFAST_TOKEN" \
-     -F "spaceId=$SPACEFAST_SPACE_ID" "${publish_files[@]}" \
-     "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-   If an update after claiming returns `space_claimed_credential_available`, exchange the saved claim token once at `POST https://api.spacefast.com/v1/anonymous-claim/exchange`, save `data.credential.accessToken`, and retry with that access token.
+2. Fetch https://spacefast.com/setup.md and follow its current direct API publishing instructions. Check for an existing Space before creating one, and follow the returned upload and polling steps.
+3. Report success only when `data.next.action` is `done` and the intended version is serving. If more work is needed, report the returned next step.
+4. For an anonymous publish, give me `data.claim.message` unchanged. It contains the private preview (`data.claim.url`), the owner's claim link (`data.claim.claimUrl`), and the deadline (`data.claim.expiresAt`). Keep both links private. Never print the separate `data.claim.key`.
+5. Keep `data.space.id` and the returned credential securely for updates to the same Space. Follow the guide for credential recovery after claiming. Keep credentials and `.spacefast` state out of the published files, commits, and logs.
 
-**Optional shortcuts and reference only:** if the `sf` CLI is already installed, `sf publish ./dist --wait` does the same job. A zip of the publish folder is also supported, but neither the CLI nor a zip is required. Docs: [direct agent/API publishing](https://spacefast.com/setup) · [files and folders](https://spacefast.com/help/publishing) · [claiming](https://spacefast.com/help/anonymous-publish) · [updates and rollback](https://spacefast.com/help/versions)
+If the `sf` CLI is already installed, `sf publish ./dist --wait` follows the same publishing flow. See [publishing](https://spacefast.com/docs/publish/) and [claiming a Space](https://spacefast.com/docs/anonymous-and-claim/).
diff --git a/recipes/calories/meta.json b/recipes/calories/meta.json
index 1521dbd..a1ba1d0 100644
--- a/recipes/calories/meta.json
+++ b/recipes/calories/meta.json
@@ -4,7 +4,7 @@
   "slug": "calories",
   "vertical": "Tools, apps & games",
   "tech": "Vanilla JS",
-  "summary": "A browser-only daily macro tracker — log meals, watch calorie and protein/carb/fat rings fill toward your goals, and keep quick-add favorites, all saved locally.",
+  "summary": "Log meals and track daily calories and macros. Your diary stays in this browser.",
   "order": 2,
   "live_url": "https://calories.view.fast/",
   "setup_questions": [
diff --git a/recipes/calories/prompt.md b/recipes/calories/prompt.md
index fe2debe..aec9d80 100644
--- a/recipes/calories/prompt.md
+++ b/recipes/calories/prompt.md
@@ -56,28 +56,12 @@ everything in `localStorage` so my diary is still there when I come back.
 <script src="https://spacefast.com/badge.js" data-example="calories"></script>
 ```
 
-**When the site is ready, publish it to Spacefast with the direct API — no account, install, or extra instructions needed:**
+**When the site is ready, publish it to Spacefast:**
 
 1. Use `./site` as the publish folder. For no-build projects, put only the finished public files in that dedicated folder. Confirm it has `index.html` at its root and no secrets, source files, `.git`, or `.spacefast` state.
-2. First publish: send every file as multipart form data. This Bash/Zsh block preserves relative paths and works for one file or a whole folder:
-   ```bash
-   PUBLISH_ROOT=./site
-   publish_files=()
-   while IFS= read -r -d "" file; do
-     relative=${file#"$PUBLISH_ROOT"/}
-     publish_files+=(-F "files=@$file;filename=$relative")
-   done < <(find "$PUBLISH_ROOT" -type f -print0)
-   curl -sS "${publish_files[@]}" "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-3. From the `{ "data": ... }` receipt, give me `data.space.liveUrl`, `data.version.immutableUrl`, `data.claim.url`, and `data.claim.expiresAt`. Remind me to claim within 6 hours. Keep `data.claim.token` secret.
-4. Save `data.space.id` and `data.claim.token` locally (for example in an ignored, mode-600 `.spacefast/state.json`). For a quick update, rebuild the `publish_files` array above and publish to the same space:
-   ```bash
-   SPACEFAST_SPACE_ID=<saved-space-id>
-   SPACEFAST_TOKEN=<saved-claim-token-or-access-token>
-   curl -sS -H "Authorization: Bearer $SPACEFAST_TOKEN" \
-     -F "spaceId=$SPACEFAST_SPACE_ID" "${publish_files[@]}" \
-     "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-   If an update after claiming returns `space_claimed_credential_available`, exchange the saved claim token once at `POST https://api.spacefast.com/v1/anonymous-claim/exchange`, save `data.credential.accessToken`, and retry with that access token.
+2. Fetch https://spacefast.com/setup.md and follow its current direct API publishing instructions. Check for an existing Space before creating one, and follow the returned upload and polling steps.
+3. Report success only when `data.next.action` is `done` and the intended version is serving. If more work is needed, report the returned next step.
+4. For an anonymous publish, give me `data.claim.message` unchanged. It contains the private preview (`data.claim.url`), the owner's claim link (`data.claim.claimUrl`), and the deadline (`data.claim.expiresAt`). Keep both links private. Never print the separate `data.claim.key`.
+5. Keep `data.space.id` and the returned credential securely for updates to the same Space. Follow the guide for credential recovery after claiming. Keep credentials and `.spacefast` state out of the published files, commits, and logs.
 
-**Optional shortcuts and reference only:** if the `sf` CLI is already installed, `sf publish ./site --wait` does the same job. A zip of the publish folder is also supported, but neither the CLI nor a zip is required. Docs: [direct agent/API publishing](https://spacefast.com/setup) · [files and folders](https://spacefast.com/help/publishing) · [claiming](https://spacefast.com/help/anonymous-publish) · [updates and rollback](https://spacefast.com/help/versions)
+If the `sf` CLI is already installed, `sf publish ./site --wait` follows the same publishing flow. See [publishing](https://spacefast.com/docs/publish/) and [claiming a Space](https://spacefast.com/docs/anonymous-and-claim/).
diff --git a/recipes/changelog/meta.json b/recipes/changelog/meta.json
index e7ce6f3..3db63d6 100644
--- a/recipes/changelog/meta.json
+++ b/recipes/changelog/meta.json
@@ -4,7 +4,7 @@
   "slug": "changelog",
   "vertical": "Data, internal & startup",
   "tech": "Vanilla JS",
-  "summary": "A calm product changelog in the Linear / Stripe style — dated New/Improved/Fixed entries, live tag filtering, inline screenshots, and an RSS feed.",
+  "summary": "Publish release notes with category filters, screenshots, and an RSS feed.",
   "order": 1,
   "live_url": "https://changelog.view.fast/",
   "setup_questions": [
diff --git a/recipes/changelog/prompt.md b/recipes/changelog/prompt.md
index b22261f..89fc922 100644
--- a/recipes/changelog/prompt.md
+++ b/recipes/changelog/prompt.md
@@ -22,8 +22,7 @@ and a `feed.xml`, no build step, no framework).
   screenshot or UI mockup.
 - **Per-entry permalink anchors**: each release has an `id`, and a link icon that
   copies a deep link to the clipboard and shows a small "copied" toast.
-- A **footer subscribe block**: an email field that shows a friendly "you're on the
-  list" success state on submit (no backend), plus a prominent RSS link.
+- A footer subscribe block linking to my email signup URL, plus a prominent RSS link. If I provide no email signup URL, show only RSS.
 - A valid **`feed.xml`** (RSS 2.0) that mirrors the same entries, linked from the
   page `<head>` so feed readers discover it.
 
@@ -36,9 +35,7 @@ and a `feed.xml`, no build step, no framework).
   the choice.
 - Three quiet badge colors — a green for **New**, a blue for **Improved**, an amber
   for **Fixed** — used as small pills, never loud.
-- Use realistic content based on my answers — never "lorem ipsum". Write believable
-  release copy with real version numbers and dates; invent a couple more plausible
-  past releases so the timeline looks lived-in.
+- Write release notes only for the versions, dates, and changes I provide. For a fictional sample product, label the timeline as demo content.
 - Use real images. For the per-release screenshots, prefer clean inline-SVG UI mockups
   of the product (they read as real product shots and stay crisp); for any photos, pull
   free images that fit, e.g. from Unsplash
@@ -57,28 +54,12 @@ and a `feed.xml`, no build step, no framework).
 <script src="https://spacefast.com/badge.js" data-example="changelog"></script>
 ```
 
-**When the site is ready, publish it to Spacefast with the direct API — no account, install, or extra instructions needed:**
+**When the site is ready, publish it to Spacefast:**
 
 1. Use `./site` as the publish folder. For no-build projects, put only the finished public files in that dedicated folder. Confirm it has `index.html` at its root and no secrets, source files, `.git`, or `.spacefast` state.
-2. First publish: send every file as multipart form data. This Bash/Zsh block preserves relative paths and works for one file or a whole folder:
-   ```bash
-   PUBLISH_ROOT=./site
-   publish_files=()
-   while IFS= read -r -d "" file; do
-     relative=${file#"$PUBLISH_ROOT"/}
-     publish_files+=(-F "files=@$file;filename=$relative")
-   done < <(find "$PUBLISH_ROOT" -type f -print0)
-   curl -sS "${publish_files[@]}" "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-3. From the `{ "data": ... }` receipt, give me `data.space.liveUrl`, `data.version.immutableUrl`, `data.claim.url`, and `data.claim.expiresAt`. Remind me to claim within 6 hours. Keep `data.claim.token` secret.
-4. Save `data.space.id` and `data.claim.token` locally (for example in an ignored, mode-600 `.spacefast/state.json`). For a quick update, rebuild the `publish_files` array above and publish to the same space:
-   ```bash
-   SPACEFAST_SPACE_ID=<saved-space-id>
-   SPACEFAST_TOKEN=<saved-claim-token-or-access-token>
-   curl -sS -H "Authorization: Bearer $SPACEFAST_TOKEN" \
-     -F "spaceId=$SPACEFAST_SPACE_ID" "${publish_files[@]}" \
-     "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-   If an update after claiming returns `space_claimed_credential_available`, exchange the saved claim token once at `POST https://api.spacefast.com/v1/anonymous-claim/exchange`, save `data.credential.accessToken`, and retry with that access token.
+2. Fetch https://spacefast.com/setup.md and follow its current direct API publishing instructions. Check for an existing Space before creating one, and follow the returned upload and polling steps.
+3. Report success only when `data.next.action` is `done` and the intended version is serving. If more work is needed, report the returned next step.
+4. For an anonymous publish, give me `data.claim.message` unchanged. It contains the private preview (`data.claim.url`), the owner's claim link (`data.claim.claimUrl`), and the deadline (`data.claim.expiresAt`). Keep both links private. Never print the separate `data.claim.key`.
+5. Keep `data.space.id` and the returned credential securely for updates to the same Space. Follow the guide for credential recovery after claiming. Keep credentials and `.spacefast` state out of the published files, commits, and logs.
 
-**Optional shortcuts and reference only:** if the `sf` CLI is already installed, `sf publish ./site --wait` does the same job. A zip of the publish folder is also supported, but neither the CLI nor a zip is required. Docs: [direct agent/API publishing](https://spacefast.com/setup) · [files and folders](https://spacefast.com/help/publishing) · [claiming](https://spacefast.com/help/anonymous-publish) · [updates and rollback](https://spacefast.com/help/versions)
+If the `sf` CLI is already installed, `sf publish ./site --wait` follows the same publishing flow. See [publishing](https://spacefast.com/docs/publish/) and [claiming a Space](https://spacefast.com/docs/anonymous-and-claim/).
diff --git a/recipes/changelog/site/app.js b/recipes/changelog/site/app.js
index 09e2fc8..75c15ac 100644
--- a/recipes/changelog/site/app.js
+++ b/recipes/changelog/site/app.js
@@ -160,11 +160,8 @@
         }
         return;
       }
-      var name = email.split("@")[0].replace(/[._-]+/g, " ").trim();
       if (successText) {
-        successText.textContent = "You're on the list" +
-          (name ? ", " + name.charAt(0).toUpperCase() + name.slice(1) : "") +
-          ". We'll email you the next time Plank ships.";
+        successText.textContent = 'Preview complete. Nothing was sent.';
       }
       form.style.display = "none";
       if (success) success.classList.add("show");
diff --git a/recipes/changelog/site/index.html b/recipes/changelog/site/index.html
index a74c525..d9ac60c 100644
--- a/recipes/changelog/site/index.html
+++ b/recipes/changelog/site/index.html
@@ -22,6 +22,12 @@
   <link rel="icon" href="data:image/svg+xml,<svg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 32 32'><rect width='32' height='32' rx='7' fill='%231f6f5c'/><path d='M9 21V11h6a4 4 0 0 1 0 8h-3' stroke='white' stroke-width='2.4' fill='none' stroke-linecap='round'/></svg>" />
 </head>
 <body>
+    <aside
+      aria-label="Example site"
+      style="margin:0;padding:0.75rem 1rem;background:#fff7d6;color:#29221a;font:14px/1.5 system-ui;text-align:center"
+    >
+      Example site with fictional content. Forms are previews.
+    </aside>
   <a class="skip-link" href="#changelog">Skip to changelog</a>
 
   <!-- ===== Top bar ===== -->
@@ -465,14 +471,15 @@ <h2>Plank 2.0 — a brand-new editor core</h2>
       <div class="subscribe-card">
         <h2>Get the release notes in your inbox</h2>
         <p>One short email whenever we ship — usually every other Tuesday. No marketing, no digests, just what changed. Prefer a feed? Grab the <a href="feed.xml">RSS</a>.</p>
+        <p data-demo-note="true">Demo signup. No subscription is created and no email is sent.</p>
         <form class="sub-form" id="subForm" novalidate>
           <label for="subEmail">Email address</label>
           <input type="email" id="subEmail" name="email" placeholder="you@example.com" autocomplete="email" required />
-          <button class="btn btn-primary" type="submit">Subscribe</button>
+          <button class="btn btn-primary" type="submit">Preview</button>
         </form>
         <div class="sub-success" id="subSuccess" role="status">
           <svg viewBox="0 0 24 24" fill="none"><circle cx="12" cy="12" r="10" stroke="currentColor" stroke-width="2"/><path d="m8 12 3 3 5-6" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"/></svg>
-          <span id="subSuccessText">You're on the list. We'll email you the next time Plank ships.</span>
+          <span id="subSuccessText">Preview complete. Nothing was sent.</span>
         </div>
         <p class="sub-note">Unsubscribe anytime in one click. We never share your address. You can also <a href="feed.xml">follow by RSS</a>.</p>
       </div>
diff --git a/recipes/cli/meta.json b/recipes/cli/meta.json
index 0f83c67..08bcca3 100644
--- a/recipes/cli/meta.json
+++ b/recipes/cli/meta.json
@@ -4,7 +4,7 @@
   "slug": "cli",
   "vertical": "Data, internal & startup",
   "tech": "Astro",
-  "summary": "A homepage for an open-source database-migration CLI, built for developers: a hero with a one-line install command and copy button, GitHub star count, a syntax-highlighted code example, feature grid, and links to docs and Discord.",
+  "summary": "Introduce your developer tool with an install command, code examples, and documentation links.",
   "order": 8,
   "live_url": "https://cli.view.fast/",
   "setup_questions": [
diff --git a/recipes/cli/prompt.md b/recipes/cli/prompt.md
index a280e75..034fae7 100644
--- a/recipes/cli/prompt.md
+++ b/recipes/cli/prompt.md
@@ -38,8 +38,7 @@ install command, a star badge, and syntax-highlighted code samples — as a smal
   reads as "in sync"), a violet secondary for gradients, a faint grid in the hero. Use a
   geometric display face (e.g. Space Grotesk) for headings, a clean sans (Inter) for body,
   and a monospace (JetBrains Mono) for commands, code chrome, and labels.
-- Write realistic content based on my answers — never "lorem ipsum". Invent believable
-  code samples, feature copy, benchmark numbers, company names, and a testimonial.
+- Use my documented commands and feature details. Include benchmarks only with supplied measurements and test conditions. Include testimonials only with supplied quotes and attribution. Omit missing proof.
 - The install command and the code blocks are the heart of the page — make the copy button
   actually work (write to the clipboard, show a "Copied" state for ~2s, with a fallback for
   browsers without the async clipboard API).
@@ -59,28 +58,12 @@ install command, a star badge, and syntax-highlighted code samples — as a smal
 <script src="https://spacefast.com/badge.js" data-example="cli"></script>
 ```
 
-**When the site is ready, publish it to Spacefast with the direct API — no account, install, or extra instructions needed:**
+**When the site is ready, publish it to Spacefast:**
 
 1. Use `./dist` as the publish folder. For no-build projects, put only the finished public files in that dedicated folder. Confirm it has `index.html` at its root and no secrets, source files, `.git`, or `.spacefast` state.
-2. First publish: send every file as multipart form data. This Bash/Zsh block preserves relative paths and works for one file or a whole folder:
-   ```bash
-   PUBLISH_ROOT=./dist
-   publish_files=()
-   while IFS= read -r -d "" file; do
-     relative=${file#"$PUBLISH_ROOT"/}
-     publish_files+=(-F "files=@$file;filename=$relative")
-   done < <(find "$PUBLISH_ROOT" -type f -print0)
-   curl -sS "${publish_files[@]}" "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-3. From the `{ "data": ... }` receipt, give me `data.space.liveUrl`, `data.version.immutableUrl`, `data.claim.url`, and `data.claim.expiresAt`. Remind me to claim within 6 hours. Keep `data.claim.token` secret.
-4. Save `data.space.id` and `data.claim.token` locally (for example in an ignored, mode-600 `.spacefast/state.json`). For a quick update, rebuild the `publish_files` array above and publish to the same space:
-   ```bash
-   SPACEFAST_SPACE_ID=<saved-space-id>
-   SPACEFAST_TOKEN=<saved-claim-token-or-access-token>
-   curl -sS -H "Authorization: Bearer $SPACEFAST_TOKEN" \
-     -F "spaceId=$SPACEFAST_SPACE_ID" "${publish_files[@]}" \
-     "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-   If an update after claiming returns `space_claimed_credential_available`, exchange the saved claim token once at `POST https://api.spacefast.com/v1/anonymous-claim/exchange`, save `data.credential.accessToken`, and retry with that access token.
+2. Fetch https://spacefast.com/setup.md and follow its current direct API publishing instructions. Check for an existing Space before creating one, and follow the returned upload and polling steps.
+3. Report success only when `data.next.action` is `done` and the intended version is serving. If more work is needed, report the returned next step.
+4. For an anonymous publish, give me `data.claim.message` unchanged. It contains the private preview (`data.claim.url`), the owner's claim link (`data.claim.claimUrl`), and the deadline (`data.claim.expiresAt`). Keep both links private. Never print the separate `data.claim.key`.
+5. Keep `data.space.id` and the returned credential securely for updates to the same Space. Follow the guide for credential recovery after claiming. Keep credentials and `.spacefast` state out of the published files, commits, and logs.
 
-**Optional shortcuts and reference only:** if the `sf` CLI is already installed, `sf publish ./dist --wait` does the same job. A zip of the publish folder is also supported, but neither the CLI nor a zip is required. Docs: [direct agent/API publishing](https://spacefast.com/setup) · [files and folders](https://spacefast.com/help/publishing) · [claiming](https://spacefast.com/help/anonymous-publish) · [updates and rollback](https://spacefast.com/help/versions)
+If the `sf` CLI is already installed, `sf publish ./dist --wait` follows the same publishing flow. See [publishing](https://spacefast.com/docs/publish/) and [claiming a Space](https://spacefast.com/docs/anonymous-and-claim/).
diff --git a/recipes/cli/site/src/layouts/Layout.astro b/recipes/cli/site/src/layouts/Layout.astro
index 615e214..40d73bf 100644
--- a/recipes/cli/site/src/layouts/Layout.astro
+++ b/recipes/cli/site/src/layouts/Layout.astro
@@ -37,6 +37,12 @@ const { title, description } = Astro.props;
     />
   </head>
   <body>
+    <aside
+      aria-label="Example site"
+      style="margin:0;padding:0.75rem 1rem;background:#fff7d6;color:#29221a;font:14px/1.5 system-ui;text-align:center"
+    >
+      Example site with fictional content. Numbers, quotes, and business details are sample content.
+    </aside>
     <a class="skip-link" href="#quickstart">Skip to content</a>
     <slot />
     <script src="https://spacefast.com/badge.js" data-example="cli"></script>
diff --git a/recipes/conference/meta.json b/recipes/conference/meta.json
index 08e7efb..580bbda 100644
--- a/recipes/conference/meta.json
+++ b/recipes/conference/meta.json
@@ -4,7 +4,7 @@
   "slug": "conference",
   "vertical": "Local & small business",
   "tech": "Astro",
-  "summary": "A one-day, single-track web-dev conference site — hero with live countdown, speaker lineup, hour-by-hour schedule, ticket tiers, venue, and sponsors.",
+  "summary": "Publish your conference schedule, speakers, ticket options, and venue details.",
   "order": 7,
   "live_url": "https://conference.view.fast/",
   "setup_questions": [
diff --git a/recipes/conference/prompt.md b/recipes/conference/prompt.md
index 5c9fc9d..10909c8 100644
--- a/recipes/conference/prompt.md
+++ b/recipes/conference/prompt.md
@@ -24,8 +24,7 @@ conference** as an **Astro site** (static output, no SSR, no backend).
 - "Sponsors" — a tiered logo wall (Platinum / Gold / Community) with a "Become a
   sponsor" link.
 - "FAQ" plus a short "Code of Conduct" panel.
-- A footer with social links and a newsletter signup that shows a friendly success
-  message on submit.
+- A footer with social links and a link to my newsletter signup page, if I provide one.
 
 **Design & content notes:**
 
@@ -33,8 +32,7 @@ conference** as an **Astro site** (static output, no SSR, no backend).
   gradient as the one signature accent, a geometric display face for headings
   (e.g. Space Grotesk), a clean sans for body (Inter), and a mono face
   (JetBrains Mono) for labels, times, and the countdown.
-- Use realistic content based on my answers — never "lorem ipsum". Invent believable
-  talk titles, abstracts, session times, hotel names, and sponsor names.
+- Use confirmed speakers, dates, ticket availability, venues, and sponsors. For a fictional conference, label the site and its schedule as demo content.
 - Use real images. Pull free photos that fit — e.g. `https://picsum.photos/seed/<unique-seed>/1200/800`
   (vary the seed per image) or Unsplash direct URLs fitting "conference keynote
   speaker on stage", "tech conference audience in auditorium", "networking coffee
@@ -52,28 +50,12 @@ conference** as an **Astro site** (static output, no SSR, no backend).
 <script src="https://spacefast.com/badge.js" data-example="conference"></script>
 ```
 
-**When the site is ready, publish it to Spacefast with the direct API — no account, install, or extra instructions needed:**
+**When the site is ready, publish it to Spacefast:**
 
 1. Use `./dist` as the publish folder. For no-build projects, put only the finished public files in that dedicated folder. Confirm it has `index.html` at its root and no secrets, source files, `.git`, or `.spacefast` state.
-2. First publish: send every file as multipart form data. This Bash/Zsh block preserves relative paths and works for one file or a whole folder:
-   ```bash
-   PUBLISH_ROOT=./dist
-   publish_files=()
-   while IFS= read -r -d "" file; do
-     relative=${file#"$PUBLISH_ROOT"/}
-     publish_files+=(-F "files=@$file;filename=$relative")
-   done < <(find "$PUBLISH_ROOT" -type f -print0)
-   curl -sS "${publish_files[@]}" "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-3. From the `{ "data": ... }` receipt, give me `data.space.liveUrl`, `data.version.immutableUrl`, `data.claim.url`, and `data.claim.expiresAt`. Remind me to claim within 6 hours. Keep `data.claim.token` secret.
-4. Save `data.space.id` and `data.claim.token` locally (for example in an ignored, mode-600 `.spacefast/state.json`). For a quick update, rebuild the `publish_files` array above and publish to the same space:
-   ```bash
-   SPACEFAST_SPACE_ID=<saved-space-id>
-   SPACEFAST_TOKEN=<saved-claim-token-or-access-token>
-   curl -sS -H "Authorization: Bearer $SPACEFAST_TOKEN" \
-     -F "spaceId=$SPACEFAST_SPACE_ID" "${publish_files[@]}" \
-     "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-   If an update after claiming returns `space_claimed_credential_available`, exchange the saved claim token once at `POST https://api.spacefast.com/v1/anonymous-claim/exchange`, save `data.credential.accessToken`, and retry with that access token.
+2. Fetch https://spacefast.com/setup.md and follow its current direct API publishing instructions. Check for an existing Space before creating one, and follow the returned upload and polling steps.
+3. Report success only when `data.next.action` is `done` and the intended version is serving. If more work is needed, report the returned next step.
+4. For an anonymous publish, give me `data.claim.message` unchanged. It contains the private preview (`data.claim.url`), the owner's claim link (`data.claim.claimUrl`), and the deadline (`data.claim.expiresAt`). Keep both links private. Never print the separate `data.claim.key`.
+5. Keep `data.space.id` and the returned credential securely for updates to the same Space. Follow the guide for credential recovery after claiming. Keep credentials and `.spacefast` state out of the published files, commits, and logs.
 
-**Optional shortcuts and reference only:** if the `sf` CLI is already installed, `sf publish ./dist --wait` does the same job. A zip of the publish folder is also supported, but neither the CLI nor a zip is required. Docs: [direct agent/API publishing](https://spacefast.com/setup) · [files and folders](https://spacefast.com/help/publishing) · [claiming](https://spacefast.com/help/anonymous-publish) · [updates and rollback](https://spacefast.com/help/versions)
+If the `sf` CLI is already installed, `sf publish ./dist --wait` follows the same publishing flow. See [publishing](https://spacefast.com/docs/publish/) and [claiming a Space](https://spacefast.com/docs/anonymous-and-claim/).
diff --git a/recipes/conference/site/src/components/Footer.astro b/recipes/conference/site/src/components/Footer.astro
index 9e98f99..b30598e 100644
--- a/recipes/conference/site/src/components/Footer.astro
+++ b/recipes/conference/site/src/components/Footer.astro
@@ -11,6 +11,8 @@ const year = new Date().getFullYear();
         <p>{conf.newsletterNote}</p>
       </div>
 
+      <p data-demo-note="true">Demo signup. No subscription is created and no email is sent.</p>
+
       <form class="signup" data-signup novalidate>
         <div class="signup__row">
           <label class="visually-hidden" for="signup-email">Email address</label>
@@ -24,13 +26,13 @@ const year = new Date().getFullYear();
             placeholder="you@studio.dev"
             required
           />
-          <button class="btn signup__btn" type="submit">Notify me</button>
+          <button class="btn signup__btn" type="submit">Preview</button>
         </div>
         <p class="signup__error" data-error role="alert" hidden>
           That doesn't look like an email — mind checking it?
         </p>
         <p class="signup__ok" data-ok role="status" hidden>
-          You're on the list. We'll email you the moment {Number(conf.year) + 1} dates are set. 🎟️
+          Preview complete. Nothing was sent.
         </p>
       </form>
     </div>
diff --git a/recipes/conference/site/src/layouts/Layout.astro b/recipes/conference/site/src/layouts/Layout.astro
index 9dc682e..64ccbeb 100644
--- a/recipes/conference/site/src/layouts/Layout.astro
+++ b/recipes/conference/site/src/layouts/Layout.astro
@@ -37,6 +37,12 @@ const { title, description } = Astro.props;
     />
   </head>
   <body>
+    <aside
+      aria-label="Example site"
+      style="margin:0;padding:0.75rem 1rem;background:#fff7d6;color:#29221a;font:14px/1.5 system-ui;text-align:center"
+    >
+      Example site with fictional content. Forms are previews.
+    </aside>
     <a class="skip-link" href="#about">Skip to content</a>
     <slot />
     <script src="https://spacefast.com/badge.js" data-example="conference"></script>
diff --git a/recipes/dashboard/meta.json b/recipes/dashboard/meta.json
index c2d9e68..5c4f988 100644
--- a/recipes/dashboard/meta.json
+++ b/recipes/dashboard/meta.json
@@ -5,7 +5,7 @@
   "publish_slug": "brightside-growth-dashboard",
   "vertical": "Data, internal & startup",
   "tech": "Vanilla JS",
-  "summary": "A single-screen, auto-refreshing growth dashboard for an online store — live KPI tiles with sparklines, a revenue trend, traffic sources, top products, and a channel leaderboard.",
+  "summary": "Explore an online store's revenue, traffic, and top products in a sample dashboard.",
   "order": 1,
   "live_url": "https://brightside-growth-dashboard.view.fast/",
   "setup_questions": [
diff --git a/recipes/dashboard/prompt.md b/recipes/dashboard/prompt.md
index 78cf89d..35fb2f6 100644
--- a/recipes/dashboard/prompt.md
+++ b/recipes/dashboard/prompt.md
@@ -50,28 +50,12 @@ team pins to the office TV and glances at all day — as a self-contained static
 <script src="https://spacefast.com/badge.js" data-example="dashboard"></script>
 ```
 
-**When the site is ready, publish it to Spacefast with the direct API — no account, install, or extra instructions needed:**
+**When the site is ready, publish it to Spacefast:**
 
 1. Use `./site` as the publish folder. For no-build projects, put only the finished public files in that dedicated folder. Confirm it has `index.html` at its root and no secrets, source files, `.git`, or `.spacefast` state.
-2. First publish: send every file as multipart form data. This Bash/Zsh block preserves relative paths and works for one file or a whole folder:
-   ```bash
-   PUBLISH_ROOT=./site
-   publish_files=()
-   while IFS= read -r -d "" file; do
-     relative=${file#"$PUBLISH_ROOT"/}
-     publish_files+=(-F "files=@$file;filename=$relative")
-   done < <(find "$PUBLISH_ROOT" -type f -print0)
-   curl -sS "${publish_files[@]}" "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-3. From the `{ "data": ... }` receipt, give me `data.space.liveUrl`, `data.version.immutableUrl`, `data.claim.url`, and `data.claim.expiresAt`. Remind me to claim within 6 hours. Keep `data.claim.token` secret.
-4. Save `data.space.id` and `data.claim.token` locally (for example in an ignored, mode-600 `.spacefast/state.json`). For a quick update, rebuild the `publish_files` array above and publish to the same space:
-   ```bash
-   SPACEFAST_SPACE_ID=<saved-space-id>
-   SPACEFAST_TOKEN=<saved-claim-token-or-access-token>
-   curl -sS -H "Authorization: Bearer $SPACEFAST_TOKEN" \
-     -F "spaceId=$SPACEFAST_SPACE_ID" "${publish_files[@]}" \
-     "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-   If an update after claiming returns `space_claimed_credential_available`, exchange the saved claim token once at `POST https://api.spacefast.com/v1/anonymous-claim/exchange`, save `data.credential.accessToken`, and retry with that access token.
+2. Fetch https://spacefast.com/setup.md and follow its current direct API publishing instructions. Check for an existing Space before creating one, and follow the returned upload and polling steps.
+3. Report success only when `data.next.action` is `done` and the intended version is serving. If more work is needed, report the returned next step.
+4. For an anonymous publish, give me `data.claim.message` unchanged. It contains the private preview (`data.claim.url`), the owner's claim link (`data.claim.claimUrl`), and the deadline (`data.claim.expiresAt`). Keep both links private. Never print the separate `data.claim.key`.
+5. Keep `data.space.id` and the returned credential securely for updates to the same Space. Follow the guide for credential recovery after claiming. Keep credentials and `.spacefast` state out of the published files, commits, and logs.
 
-**Optional shortcuts and reference only:** if the `sf` CLI is already installed, `sf publish ./site --wait` does the same job. A zip of the publish folder is also supported, but neither the CLI nor a zip is required. Docs: [direct agent/API publishing](https://spacefast.com/setup) · [files and folders](https://spacefast.com/help/publishing) · [claiming](https://spacefast.com/help/anonymous-publish) · [updates and rollback](https://spacefast.com/help/versions)
+If the `sf` CLI is already installed, `sf publish ./site --wait` follows the same publishing flow. See [publishing](https://spacefast.com/docs/publish/) and [claiming a Space](https://spacefast.com/docs/anonymous-and-claim/).
diff --git a/recipes/dashboard/site/index.html b/recipes/dashboard/site/index.html
index 89832d9..628e52e 100644
--- a/recipes/dashboard/site/index.html
+++ b/recipes/dashboard/site/index.html
@@ -13,6 +13,12 @@
   <link rel="stylesheet" href="styles.css" />
 </head>
 <body>
+    <aside
+      aria-label="Example site"
+      style="margin:0;padding:0.75rem 1rem;background:#fff7d6;color:#29221a;font:14px/1.5 system-ui;text-align:center"
+    >
+      Example site with fictional content. Numbers, quotes, and business details are sample content.
+    </aside>
   <a class="skip-link" href="#main">Skip to dashboard</a>
 
   <header class="topbar">
diff --git a/recipes/deck/meta.json b/recipes/deck/meta.json
index 6182854..b662f6c 100644
--- a/recipes/deck/meta.json
+++ b/recipes/deck/meta.json
@@ -4,7 +4,7 @@
   "slug": "deck",
   "vertical": "Data, internal & startup",
   "tech": "Vanilla JS",
-  "summary": "A presentable, browser-native reveal.js pitch deck with keyboard nav, speaker notes, PDF export, and bespoke data slides — TAM/SAM/SOM rings, an MRR chart, and use-of-funds bars.",
+  "summary": "Present a pitch deck in the browser, with speaker notes and PDF export.",
   "order": 300,
   "live_url": "https://deck.view.fast/",
   "setup_questions": [
diff --git a/recipes/deck/prompt.md b/recipes/deck/prompt.md
index e0107f7..f2bdb8d 100644
--- a/recipes/deck/prompt.md
+++ b/recipes/deck/prompt.md
@@ -24,7 +24,7 @@ vanilla-JS app — a single `index.html` plus a small CSS and JS file, with
 **Design & content notes:**
 
 - A confident, modern boardroom palette: a deep ink background (`#0A0E17`), an indigo→teal accent gradient (`#7C9BFF → #4FD8C4`), Space Grotesk for headings and Inter for body. Generous whitespace, rounded cards, no clip-art.
-- Use realistic content based on my answers — never "lorem ipsum". Invent believable, internally-consistent numbers (ARR, growth %, retention, market size) if I leave gaps, and label any estimates as estimates.
+- Use the business figures and sources I provide. Label forecasts and their assumptions. Omit missing historical metrics, customer proof, and market-size claims. Fictional sample figures must say "Sample data" on each affected slide.
 - Use real images. Pull a free photo that fits the title background, e.g.
   `https://picsum.photos/seed/northwind-board/1920/1080`, darken it behind the text, and add an empty `alt` (it's decorative).
 - Load reveal.js, its notes plugin, and its highlight plugin from a CDN (e.g. jsDelivr). reveal.js v5 handles PDF pagination itself when the URL carries `?print-pdf` — no extra print stylesheet needed.
@@ -36,28 +36,12 @@ vanilla-JS app — a single `index.html` plus a small CSS and JS file, with
 <script src="https://spacefast.com/badge.js" data-example="deck"></script>
 ```
 
-**When the site is ready, publish it to Spacefast with the direct API — no account, install, or extra instructions needed:**
+**When the site is ready, publish it to Spacefast:**
 
 1. Use `./site` as the publish folder. For no-build projects, put only the finished public files in that dedicated folder. Confirm it has `index.html` at its root and no secrets, source files, `.git`, or `.spacefast` state.
-2. First publish: send every file as multipart form data. This Bash/Zsh block preserves relative paths and works for one file or a whole folder:
-   ```bash
-   PUBLISH_ROOT=./site
-   publish_files=()
-   while IFS= read -r -d "" file; do
-     relative=${file#"$PUBLISH_ROOT"/}
-     publish_files+=(-F "files=@$file;filename=$relative")
-   done < <(find "$PUBLISH_ROOT" -type f -print0)
-   curl -sS "${publish_files[@]}" "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-3. From the `{ "data": ... }` receipt, give me `data.space.liveUrl`, `data.version.immutableUrl`, `data.claim.url`, and `data.claim.expiresAt`. Remind me to claim within 6 hours. Keep `data.claim.token` secret.
-4. Save `data.space.id` and `data.claim.token` locally (for example in an ignored, mode-600 `.spacefast/state.json`). For a quick update, rebuild the `publish_files` array above and publish to the same space:
-   ```bash
-   SPACEFAST_SPACE_ID=<saved-space-id>
-   SPACEFAST_TOKEN=<saved-claim-token-or-access-token>
-   curl -sS -H "Authorization: Bearer $SPACEFAST_TOKEN" \
-     -F "spaceId=$SPACEFAST_SPACE_ID" "${publish_files[@]}" \
-     "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-   If an update after claiming returns `space_claimed_credential_available`, exchange the saved claim token once at `POST https://api.spacefast.com/v1/anonymous-claim/exchange`, save `data.credential.accessToken`, and retry with that access token.
-
-**Optional shortcuts and reference only:** if the `sf` CLI is already installed, `sf publish ./site --wait` does the same job. A zip of the publish folder is also supported, but neither the CLI nor a zip is required. Docs: [direct agent/API publishing](https://spacefast.com/setup) · [files and folders](https://spacefast.com/help/publishing) · [claiming](https://spacefast.com/help/anonymous-publish) · [updates and rollback](https://spacefast.com/help/versions)
+2. Fetch https://spacefast.com/setup.md and follow its current direct API publishing instructions. Check for an existing Space before creating one, and follow the returned upload and polling steps.
+3. Report success only when `data.next.action` is `done` and the intended version is serving. If more work is needed, report the returned next step.
+4. For an anonymous publish, give me `data.claim.message` unchanged. It contains the private preview (`data.claim.url`), the owner's claim link (`data.claim.claimUrl`), and the deadline (`data.claim.expiresAt`). Keep both links private. Never print the separate `data.claim.key`.
+5. Keep `data.space.id` and the returned credential securely for updates to the same Space. Follow the guide for credential recovery after claiming. Keep credentials and `.spacefast` state out of the published files, commits, and logs.
+
+If the `sf` CLI is already installed, `sf publish ./site --wait` follows the same publishing flow. See [publishing](https://spacefast.com/docs/publish/) and [claiming a Space](https://spacefast.com/docs/anonymous-and-claim/).
diff --git a/recipes/deck/site/index.html b/recipes/deck/site/index.html
index 6e6afd1..8818f3c 100644
--- a/recipes/deck/site/index.html
+++ b/recipes/deck/site/index.html
@@ -18,6 +18,12 @@
   <link rel="stylesheet" href="assets/style.css" />
 </head>
 <body>
+    <aside
+      aria-label="Example site"
+      style="margin:0;padding:0.75rem 1rem;background:#fff7d6;color:#29221a;font:14px/1.5 system-ui;text-align:center"
+    >
+      Example site with fictional content. Numbers, quotes, and business details are sample content.
+    </aside>
   <div class="reveal">
     <div class="slides">
 
diff --git a/recipes/docs/meta.json b/recipes/docs/meta.json
index 1c559f3..0cec8c2 100644
--- a/recipes/docs/meta.json
+++ b/recipes/docs/meta.json
@@ -4,7 +4,7 @@
   "slug": "docs",
   "vertical": "Developers & integrations",
   "tech": "Astro",
-  "summary": "A multi-page documentation site for an open-source library — grouped sidebar nav, getting-started and guides, an API reference, build-time syntax-highlighted code, a working ⌘K search, and a version dropdown.",
+  "summary": "Build searchable documentation with guides, code examples, and an API reference.",
   "order": 300,
   "live_url": "https://docs.view.fast/",
   "setup_questions": [
diff --git a/recipes/docs/prompt.md b/recipes/docs/prompt.md
index a996b6d..6a4c6ca 100644
--- a/recipes/docs/prompt.md
+++ b/recipes/docs/prompt.md
@@ -39,9 +39,7 @@ Build me a **multi-page documentation site for an open-source software library**
   emerald→sky gradient brand accent, a geometric display face (e.g. Space Grotesk)
   for headings, Inter for body, and a monospace (e.g. JetBrains Mono) for code.
   Generous reading measure, calm spacing, crisp borders.
-- Write **realistic technical content** for the library based on my answers — real
-  API names, believable code, real release notes. Never "lorem ipsum"; invent
-  plausible details if I leave gaps.
+- Use the actual API names, signatures, working code examples, and release notes I provide or can verify in the project. Ask for missing technical details instead of inventing behavior.
 - Use real images where they help (e.g. a code-editor screenshot on the landing
   hero). Pull free photos that fit, e.g.
   `https://picsum.photos/seed/docs-1/1200/800` (vary the seed), and add descriptive `alt` text.
@@ -60,28 +58,12 @@ in the shared root layout so every page includes it):
 <script src="https://spacefast.com/badge.js" data-example="docs"></script>
 ```
 
-**When the site is ready, publish it to Spacefast with the direct API — no account, install, or extra instructions needed:**
+**When the site is ready, publish it to Spacefast:**
 
 1. Use `./dist` as the publish folder. For no-build projects, put only the finished public files in that dedicated folder. Confirm it has `index.html` at its root and no secrets, source files, `.git`, or `.spacefast` state.
-2. First publish: send every file as multipart form data. This Bash/Zsh block preserves relative paths and works for one file or a whole folder:
-   ```bash
-   PUBLISH_ROOT=./dist
-   publish_files=()
-   while IFS= read -r -d "" file; do
-     relative=${file#"$PUBLISH_ROOT"/}
-     publish_files+=(-F "files=@$file;filename=$relative")
-   done < <(find "$PUBLISH_ROOT" -type f -print0)
-   curl -sS "${publish_files[@]}" "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-3. From the `{ "data": ... }` receipt, give me `data.space.liveUrl`, `data.version.immutableUrl`, `data.claim.url`, and `data.claim.expiresAt`. Remind me to claim within 6 hours. Keep `data.claim.token` secret.
-4. Save `data.space.id` and `data.claim.token` locally (for example in an ignored, mode-600 `.spacefast/state.json`). For a quick update, rebuild the `publish_files` array above and publish to the same space:
-   ```bash
-   SPACEFAST_SPACE_ID=<saved-space-id>
-   SPACEFAST_TOKEN=<saved-claim-token-or-access-token>
-   curl -sS -H "Authorization: Bearer $SPACEFAST_TOKEN" \
-     -F "spaceId=$SPACEFAST_SPACE_ID" "${publish_files[@]}" \
-     "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-   If an update after claiming returns `space_claimed_credential_available`, exchange the saved claim token once at `POST https://api.spacefast.com/v1/anonymous-claim/exchange`, save `data.credential.accessToken`, and retry with that access token.
+2. Fetch https://spacefast.com/setup.md and follow its current direct API publishing instructions. Check for an existing Space before creating one, and follow the returned upload and polling steps.
+3. Report success only when `data.next.action` is `done` and the intended version is serving. If more work is needed, report the returned next step.
+4. For an anonymous publish, give me `data.claim.message` unchanged. It contains the private preview (`data.claim.url`), the owner's claim link (`data.claim.claimUrl`), and the deadline (`data.claim.expiresAt`). Keep both links private. Never print the separate `data.claim.key`.
+5. Keep `data.space.id` and the returned credential securely for updates to the same Space. Follow the guide for credential recovery after claiming. Keep credentials and `.spacefast` state out of the published files, commits, and logs.
 
-**Optional shortcuts and reference only:** if the `sf` CLI is already installed, `sf publish ./dist --wait` does the same job. A zip of the publish folder is also supported, but neither the CLI nor a zip is required. Docs: [direct agent/API publishing](https://spacefast.com/setup) · [files and folders](https://spacefast.com/help/publishing) · [claiming](https://spacefast.com/help/anonymous-publish) · [updates and rollback](https://spacefast.com/help/versions)
+If the `sf` CLI is already installed, `sf publish ./dist --wait` follows the same publishing flow. See [publishing](https://spacefast.com/docs/publish/) and [claiming a Space](https://spacefast.com/docs/anonymous-and-claim/).
diff --git a/recipes/docs/site/src/layouts/Base.astro b/recipes/docs/site/src/layouts/Base.astro
index 6efd988..103f9d8 100644
--- a/recipes/docs/site/src/layouts/Base.astro
+++ b/recipes/docs/site/src/layouts/Base.astro
@@ -36,6 +36,12 @@ const fullTitle = title === 'Overview' ? `${site.name} — ${site.tagline}` : `$
     />
   </head>
   <body>
+    <aside
+      aria-label="Example site"
+      style="margin:0;padding:0.75rem 1rem;background:#fff7d6;color:#29221a;font:14px/1.5 system-ui;text-align:center"
+    >
+      Example site with fictional content. Numbers, quotes, and business details are sample content.
+    </aside>
     <a class="skip-link" href="#main">Skip to content</a>
 
     <div class="verbanner" data-verbanner role="status">
diff --git a/recipes/foodtruck/meta.json b/recipes/foodtruck/meta.json
index 3da8f72..1e57250 100644
--- a/recipes/foodtruck/meta.json
+++ b/recipes/foodtruck/meta.json
@@ -4,7 +4,7 @@
   "slug": "foodtruck",
   "vertical": "Local & small business",
   "tech": "Vanilla JS",
-  "summary": "A mobile-first food-truck site whose centerpiece is a weekly schedule that auto-highlights where the truck is parked today, with one-tap map directions and a live \"we're here now\" banner.",
+  "summary": "Show today's food-truck stop, this week's schedule, and directions.",
   "order": 3,
   "live_url": "https://foodtruck.view.fast/",
   "setup_questions": [
diff --git a/recipes/foodtruck/prompt.md b/recipes/foodtruck/prompt.md
index 9f04554..365f601 100644
--- a/recipes/foodtruck/prompt.md
+++ b/recipes/foodtruck/prompt.md
@@ -12,14 +12,14 @@ Build me a **mobile-first website for my food truck whose centerpiece is a weekl
 - A full-bleed hero with a truck photo, the name big, a tagline, and a **live "We're at … today" banner** that JavaScript fills in from the schedule (and shows "Open now / Opens at … / next stop on …" depending on the current day and time).
 - A **"This week's route"** section: a list of day → location → hours, ordered so today comes first and today's row is visually highlighted. Each open day has a one-tap **Directions** link that opens Google Maps to that address. Day-off rows read as closed.
 - A **Menu** grouped into tacos, burritos/bowls, sides, and drinks, each item with a price and a one-line description; mark veg options.
-- A **Catering / private events** blurb with perks and a **quote-request form** that validates name + email and shows a friendly success state on submit (plus a `mailto:` and `tel:` fallback).
+- A catering section with a quote-request form for name, email, and event details, plus email and phone links. For any form that sends information, ask for my form endpoint or hosted signup URL. Use the supplied destination and show success only after it confirms receipt. A link to another service does not confirm completion. Without a destination, label the form "Demo only" beside its fields, label its button "Preview", and say "Preview complete. Nothing was sent." Never treat `localStorage` as delivery or store personal form data there.
 - A **gallery strip** of food/truck photos.
 - A footer with contact info and Instagram / TikTok links.
 
 **Design & content notes:**
 
 - Bright, appetizing food-truck mood: warm cream paper background, a bold chili-red primary with gochujang-orange and sesame-gold accents, near-black warm ink for text. Big condensed display type (e.g. Anton) for headings, clean Inter for body.
-- Use realistic content based on my answers — never "lorem ipsum". Invent believable LA-style stops, menu copy, and prices if I'm vague.
+- Use my actual stops, menu, prices, and opening hours. Ask for missing locations instead of inventing directions.
 - Use real images. Pull free photos that fit, e.g. `https://picsum.photos/seed/kimchi-taco-truck-1/1200/800` (vary the seed per image), with descriptive `alt` text.
 - Put the schedule as data in `app.js` (days indexed Sun=0…Sat=6, open/close as minutes from midnight) and compute "today" + "open now" client-side. Build the Google Maps links with `https://www.google.com/maps/dir/?api=1&destination=`.
 - Keep it accessible (semantic HTML, labelled form fields, keyboard support, good contrast) and mobile-first.
@@ -30,28 +30,12 @@ Build me a **mobile-first website for my food truck whose centerpiece is a weekl
 <script src="https://spacefast.com/badge.js" data-example="foodtruck"></script>
 ```
 
-**When the site is ready, publish it to Spacefast with the direct API — no account, install, or extra instructions needed:**
+**When the site is ready, publish it to Spacefast:**
 
 1. Use `./site` as the publish folder. For no-build projects, put only the finished public files in that dedicated folder. Confirm it has `index.html` at its root and no secrets, source files, `.git`, or `.spacefast` state.
-2. First publish: send every file as multipart form data. This Bash/Zsh block preserves relative paths and works for one file or a whole folder:
-   ```bash
-   PUBLISH_ROOT=./site
-   publish_files=()
-   while IFS= read -r -d "" file; do
-     relative=${file#"$PUBLISH_ROOT"/}
-     publish_files+=(-F "files=@$file;filename=$relative")
-   done < <(find "$PUBLISH_ROOT" -type f -print0)
-   curl -sS "${publish_files[@]}" "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-3. From the `{ "data": ... }` receipt, give me `data.space.liveUrl`, `data.version.immutableUrl`, `data.claim.url`, and `data.claim.expiresAt`. Remind me to claim within 6 hours. Keep `data.claim.token` secret.
-4. Save `data.space.id` and `data.claim.token` locally (for example in an ignored, mode-600 `.spacefast/state.json`). For a quick update, rebuild the `publish_files` array above and publish to the same space:
-   ```bash
-   SPACEFAST_SPACE_ID=<saved-space-id>
-   SPACEFAST_TOKEN=<saved-claim-token-or-access-token>
-   curl -sS -H "Authorization: Bearer $SPACEFAST_TOKEN" \
-     -F "spaceId=$SPACEFAST_SPACE_ID" "${publish_files[@]}" \
-     "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-   If an update after claiming returns `space_claimed_credential_available`, exchange the saved claim token once at `POST https://api.spacefast.com/v1/anonymous-claim/exchange`, save `data.credential.accessToken`, and retry with that access token.
-
-**Optional shortcuts and reference only:** if the `sf` CLI is already installed, `sf publish ./site --wait` does the same job. A zip of the publish folder is also supported, but neither the CLI nor a zip is required. Docs: [direct agent/API publishing](https://spacefast.com/setup) · [files and folders](https://spacefast.com/help/publishing) · [claiming](https://spacefast.com/help/anonymous-publish) · [updates and rollback](https://spacefast.com/help/versions)
+2. Fetch https://spacefast.com/setup.md and follow its current direct API publishing instructions. Check for an existing Space before creating one, and follow the returned upload and polling steps.
+3. Report success only when `data.next.action` is `done` and the intended version is serving. If more work is needed, report the returned next step.
+4. For an anonymous publish, give me `data.claim.message` unchanged. It contains the private preview (`data.claim.url`), the owner's claim link (`data.claim.claimUrl`), and the deadline (`data.claim.expiresAt`). Keep both links private. Never print the separate `data.claim.key`.
+5. Keep `data.space.id` and the returned credential securely for updates to the same Space. Follow the guide for credential recovery after claiming. Keep credentials and `.spacefast` state out of the published files, commits, and logs.
+
+If the `sf` CLI is already installed, `sf publish ./site --wait` follows the same publishing flow. See [publishing](https://spacefast.com/docs/publish/) and [claiming a Space](https://spacefast.com/docs/anonymous-and-claim/).
diff --git a/recipes/foodtruck/site/app.js b/recipes/foodtruck/site/app.js
index 53f0285..04a23b6 100644
--- a/recipes/foodtruck/site/app.js
+++ b/recipes/foodtruck/site/app.js
@@ -195,10 +195,8 @@
         return;
       }
 
-      var first = name.value.trim().split(" ")[0];
       form.querySelectorAll(".field, .field-row, button[type=submit]").forEach(function (n) { n.style.display = "none"; });
-      status.innerHTML = "🌮 Thanks, " + first + "! Your inquiry's in — we usually reply within a day. " +
-        "Truck-bound right now? Email <a href=\"mailto:catering@kimchitacoco.example\">catering@kimchitacoco.example</a>.";
+      status.innerHTML = 'Preview complete. Nothing was sent.';
       status.className = "form-status ok";
       status.style.fontSize = "1.05rem";
       status.focus && status.focus();
diff --git a/recipes/foodtruck/site/index.html b/recipes/foodtruck/site/index.html
index fe81296..d50fe85 100644
--- a/recipes/foodtruck/site/index.html
+++ b/recipes/foodtruck/site/index.html
@@ -20,6 +20,12 @@
   <link rel="stylesheet" href="styles.css" />
 </head>
 <body>
+    <aside
+      aria-label="Example site"
+      style="margin:0;padding:0.75rem 1rem;background:#fff7d6;color:#29221a;font:14px/1.5 system-ui;text-align:center"
+    >
+      Example site with fictional content. Forms are previews.
+    </aside>
   <a class="skip-link" href="#menu">Skip to menu</a>
 
   <!-- ===== Header ===== -->
@@ -168,6 +174,8 @@ <h2>Catering &amp; private events</h2>
         </p>
       </div>
 
+      <p data-demo-note="true">Demo form. Nothing is sent or booked.</p>
+
       <form class="catering-form" id="catering-form" novalidate>
         <h3>Request a quote</h3>
         <div class="field">
@@ -192,7 +200,7 @@ <h3>Request a quote</h3>
           <label for="cf-msg">Tell us about it</label>
           <textarea id="cf-msg" name="message" rows="3" placeholder="Backyard 40th, mostly veg eaters, sunset in Highland Park…"></textarea>
         </div>
-        <button class="btn btn-primary btn-block" type="submit">Send inquiry</button>
+        <button class="btn btn-primary btn-block" type="submit">Preview</button>
         <p class="form-status" id="form-status" role="status" aria-live="polite"></p>
       </form>
     </div>
diff --git a/recipes/fundraiser/meta.json b/recipes/fundraiser/meta.json
index 7a0b30e..2edbca6 100644
--- a/recipes/fundraiser/meta.json
+++ b/recipes/fundraiser/meta.json
@@ -4,7 +4,7 @@
   "slug": "fundraiser",
   "vertical": "Personal & creative",
   "tech": "Vanilla JS",
-  "summary": "A one-page community-fundraiser site with an animated goal thermometer, a working donate button and modal, and a live donor wall that grows as people give.",
+  "summary": "Explain your cause, show a funding goal, and link to your donation page.",
   "order": 300,
   "live_url": "https://fundraiser.view.fast/",
   "setup_questions": [
@@ -20,12 +20,12 @@
     "neighbors gathered together at a community center"
   ],
   "sections": [
-    "Hero with a community photo, the cause, an emotional lede, and the live fundraising widget",
+    "Hero with the cause, community photo, and confirmed campaign totals",
     "Animated progress bar with dollars raised, goal, percentage, donor count, and days left",
     "Cause story with an organizer pull-quote, a 'where the money goes' budget, and a photo gallery",
     "Ways-to-give tiers that open the donate form pre-filled",
-    "Donate button + modal (preset/custom amount, name, note, anonymous) with a thank-you state",
-    "Donor wall of cards that updates instantly and persists across refreshes",
+    "Donation link to your payment service, or a labelled demo with no payment made",
+    "Donor wall using confirmed donations, or clearly labelled local sample data",
     "Share section with a working copy-link button and X / Facebook / email links",
     "Footer with org name, contact, and nonprofit fine print"
   ],
diff --git a/recipes/fundraiser/prompt.md b/recipes/fundraiser/prompt.md
index 13d6ba7..fc06307 100644
--- a/recipes/fundraiser/prompt.md
+++ b/recipes/fundraiser/prompt.md
@@ -10,23 +10,23 @@ Build me a **one-page fundraising campaign site for a local cause** as a vanilla
 
 **Then build a complete, polished, responsive site with:**
 
-- A **hero** with a striking community photo, the cause name, a short emotional lede, and the live fundraising widget pinned right there.
+- A **hero** with a striking community photo, the cause name, a short emotional lede, and the fundraising summary pinned right there.
 - An **animated progress bar** that fills from 0% to the current total on load, with the dollars raised, the goal, the percentage, the donor count, and the days left — all computed, not hard-coded into the markup.
 - A **cause story** section in a warm, human voice, a pull-quote from an organizer, a "where the money goes" budget panel, and a small photo gallery.
 - A **"ways to give"** row of suggested amounts (each one opens the donate form pre-filled).
-- A **donate button + modal**: choose a preset or custom amount, enter a name and optional note, optionally give anonymously, then submit. On submit it validates, shows a thank-you state, bumps the running total and progress bar, and drops the new donor onto the wall instantly. Persist donations in `localStorage` so they survive a refresh.
-- A **donor wall**: a grid of donor cards (colored initials avatar, name, note, amount), seeded with the real donors and growing as people give.
+- A donation button using my payment link. If I provide none, show a button labelled "Demo donation" and a preview modal. Say "Demo complete. No payment was made." Do not increase real campaign totals or add a donor without verified payment confirmation. Keep any simulated totals in a separate, clearly labelled demo.
+- A **donor wall**: a grid of donor cards (colored initials avatar, name, note, amount), using confirmed donations only.
 - A **share** section: a "copy link" button that actually copies and confirms, plus pre-filled X / Facebook / email share links.
 - A footer with the org name, a contact email, and the nonprofit fine print.
 
 **Design & content notes:**
 
 - Warm, hand-made, community-grant mood: a cream paper base, a confident coral primary, a deep teal, and a harvest-gold accent. A characterful serif (e.g. Fraunces) for headings, a clean sans (e.g. Inter) for body. Soft rounded cards, a slightly tilted hero photo, gentle motion.
-- Use realistic content based on my answers — never "lorem ipsum". Invent believable donor names, notes, and budget lines if I leave gaps.
+- Use only confirmed campaign totals, donors who consented to be named, organizer quotes, and budget details. Omit missing claims. A fictional campaign must be labelled as a demo throughout.
 - Use real images. Pull free photos that fit, e.g.
   `https://picsum.photos/seed/community-mural-1/1200/800` (vary the seed) or Pexels, and add
   descriptive `alt` text. Good search terms: community mural painting, volunteers neighborhood project.
-- No build step — a single `index.html` with a linked CSS and JS file that opens straight in a browser. Make the progress bar and donor math real: derive everything from a small config object (goal, base raised, end date, seed donors) so the numbers stay honest. This is a demo, so no real payment is processed — wire the button to my payment link or leave a clearly-labeled demo state.
+- No build step — a single `index.html` with a linked CSS and JS file that opens straight in a browser. Make the progress bar and donor math real: derive everything from a small config object (goal, base raised, end date, seed donors) so the numbers stay honest. Use my payment link for donations, or keep simulated donations clearly labelled as a demo.
 - Keep it accessible (semantic HTML, labelled form fields, an `aria` live region on the donor wall, keyboard support, Escape closes the modal, and good contrast). Respect `prefers-reduced-motion`.
 
 **Add this exact line right before `</body>` so the site carries its badge:**
@@ -35,28 +35,12 @@ Build me a **one-page fundraising campaign site for a local cause** as a vanilla
 <script src="https://spacefast.com/badge.js" data-example="fundraiser"></script>
 ```
 
-**When the site is ready, publish it to Spacefast with the direct API — no account, install, or extra instructions needed:**
+**When the site is ready, publish it to Spacefast:**
 
 1. Use `./site` as the publish folder. For no-build projects, put only the finished public files in that dedicated folder. Confirm it has `index.html` at its root and no secrets, source files, `.git`, or `.spacefast` state.
-2. First publish: send every file as multipart form data. This Bash/Zsh block preserves relative paths and works for one file or a whole folder:
-   ```bash
-   PUBLISH_ROOT=./site
-   publish_files=()
-   while IFS= read -r -d "" file; do
-     relative=${file#"$PUBLISH_ROOT"/}
-     publish_files+=(-F "files=@$file;filename=$relative")
-   done < <(find "$PUBLISH_ROOT" -type f -print0)
-   curl -sS "${publish_files[@]}" "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-3. From the `{ "data": ... }` receipt, give me `data.space.liveUrl`, `data.version.immutableUrl`, `data.claim.url`, and `data.claim.expiresAt`. Remind me to claim within 6 hours. Keep `data.claim.token` secret.
-4. Save `data.space.id` and `data.claim.token` locally (for example in an ignored, mode-600 `.spacefast/state.json`). For a quick update, rebuild the `publish_files` array above and publish to the same space:
-   ```bash
-   SPACEFAST_SPACE_ID=<saved-space-id>
-   SPACEFAST_TOKEN=<saved-claim-token-or-access-token>
-   curl -sS -H "Authorization: Bearer $SPACEFAST_TOKEN" \
-     -F "spaceId=$SPACEFAST_SPACE_ID" "${publish_files[@]}" \
-     "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-   If an update after claiming returns `space_claimed_credential_available`, exchange the saved claim token once at `POST https://api.spacefast.com/v1/anonymous-claim/exchange`, save `data.credential.accessToken`, and retry with that access token.
-
-**Optional shortcuts and reference only:** if the `sf` CLI is already installed, `sf publish ./site --wait` does the same job. A zip of the publish folder is also supported, but neither the CLI nor a zip is required. Docs: [direct agent/API publishing](https://spacefast.com/setup) · [files and folders](https://spacefast.com/help/publishing) · [claiming](https://spacefast.com/help/anonymous-publish) · [updates and rollback](https://spacefast.com/help/versions)
+2. Fetch https://spacefast.com/setup.md and follow its current direct API publishing instructions. Check for an existing Space before creating one, and follow the returned upload and polling steps.
+3. Report success only when `data.next.action` is `done` and the intended version is serving. If more work is needed, report the returned next step.
+4. For an anonymous publish, give me `data.claim.message` unchanged. It contains the private preview (`data.claim.url`), the owner's claim link (`data.claim.claimUrl`), and the deadline (`data.claim.expiresAt`). Keep both links private. Never print the separate `data.claim.key`.
+5. Keep `data.space.id` and the returned credential securely for updates to the same Space. Follow the guide for credential recovery after claiming. Keep credentials and `.spacefast` state out of the published files, commits, and logs.
+
+If the `sf` CLI is already installed, `sf publish ./site --wait` follows the same publishing flow. See [publishing](https://spacefast.com/docs/publish/) and [claiming a Space](https://spacefast.com/docs/anonymous-and-claim/).
diff --git a/recipes/fundraiser/site/index.html b/recipes/fundraiser/site/index.html
index 394e271..d77b5a7 100644
--- a/recipes/fundraiser/site/index.html
+++ b/recipes/fundraiser/site/index.html
@@ -18,6 +18,12 @@
   <link rel="icon" href="data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 100 100'%3E%3Crect width='100' height='100' rx='22' fill='%23E2563E'/%3E%3Cpath d='M28 70 L46 30 L54 30 L72 70 L62 70 L50 44 L38 70 Z' fill='%23FCEFD8'/%3E%3C/svg%3E" />
 </head>
 <body>
+    <aside
+      aria-label="Example site"
+      style="margin:0;padding:0.75rem 1rem;background:#fff7d6;color:#29221a;font:14px/1.5 system-ui;text-align:center"
+    >
+      Example site with fictional content. Forms are previews.
+    </aside>
   <a class="skip-link" href="#story">Skip to content</a>
 
   <header class="topbar">
@@ -227,6 +233,8 @@ <h2 id="share-title">Can't give right now? Share it — that helps just as much.
         <h2 id="modal-title" class="modal-title">Help finish the mural</h2>
         <p class="modal-sub">Your name joins the wall the moment you give. (This is a demo — no real payment is taken.)</p>
 
+        <p data-demo-note="true">Demo donation. No payment is made. Totals and donor entries are sample data saved in this browser only.</p>
+
         <form data-form novalidate>
           <fieldset class="amounts">
             <legend>Choose an amount</legend>
@@ -259,16 +267,16 @@ <h2 id="modal-title" class="modal-title">Help finish the mural</h2>
           </label>
 
           <button class="btn btn-lg btn-full" type="submit" data-submit>
-            Give <span data-submit-amount>$50</span>
+            Preview <span data-submit-amount>$50</span> donation
           </button>
-          <p class="modal-fine">🔒 Demo only — no card is charged. Swap in your Stripe/PayPal link to go live.</p>
+          <p class="modal-fine">Demo only. No payment is made.</p>
         </form>
       </div>
 
       <div data-modal-success hidden>
         <div class="success-mark" aria-hidden="true">✓</div>
-        <h2 class="modal-title">Thank you, <span data-success-name>friend</span>!</h2>
-        <p class="modal-sub">Your <strong data-success-amount>$50</strong> just moved the bar. You're on the wall — scroll down to find your name.</p>
+        <h2 class="modal-title">Demo donation preview for <span data-success-name>friend</span></h2>
+        <p class="modal-sub">Your <strong data-success-amount>$50</strong> demo amount updated this browser's sample total. No payment was made. This is not a real donation.</p>
         <div class="success-stats">
           <div><span class="ss-num" data-raised-display>$0</span><span class="ss-lbl">raised so far</span></div>
           <div><span class="ss-num" data-pct-display>0</span><span class="ss-lbl">% of goal</span></div>
diff --git a/recipes/game/meta.json b/recipes/game/meta.json
index f7c6a05..86edfa8 100644
--- a/recipes/game/meta.json
+++ b/recipes/game/meta.json
@@ -4,7 +4,7 @@
   "slug": "game",
   "vertical": "Tools, apps & games",
   "tech": "HTML5 canvas game",
-  "summary": "A fully playable neon-synthwave brick-breaker — bounce a glowing ball to smash brick walls across five levels, catching falling power-ups.",
+  "summary": "Play a neon brick-breaker with five levels and falling power-ups.",
   "order": 5,
   "live_url": "https://game.view.fast/",
   "setup_questions": [
diff --git a/recipes/game/prompt.md b/recipes/game/prompt.md
index bfe53bd..1018514 100644
--- a/recipes/game/prompt.md
+++ b/recipes/game/prompt.md
@@ -30,28 +30,12 @@ Build me a **playable neon brick-breaker arcade game** (paddle, bouncing ball, d
 <script src="https://spacefast.com/badge.js" data-example="game"></script>
 ```
 
-**When the site is ready, publish it to Spacefast with the direct API — no account, install, or extra instructions needed:**
+**When the site is ready, publish it to Spacefast:**
 
 1. Use `./site` as the publish folder. For no-build projects, put only the finished public files in that dedicated folder. Confirm it has `index.html` at its root and no secrets, source files, `.git`, or `.spacefast` state.
-2. First publish: send every file as multipart form data. This Bash/Zsh block preserves relative paths and works for one file or a whole folder:
-   ```bash
-   PUBLISH_ROOT=./site
-   publish_files=()
-   while IFS= read -r -d "" file; do
-     relative=${file#"$PUBLISH_ROOT"/}
-     publish_files+=(-F "files=@$file;filename=$relative")
-   done < <(find "$PUBLISH_ROOT" -type f -print0)
-   curl -sS "${publish_files[@]}" "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-3. From the `{ "data": ... }` receipt, give me `data.space.liveUrl`, `data.version.immutableUrl`, `data.claim.url`, and `data.claim.expiresAt`. Remind me to claim within 6 hours. Keep `data.claim.token` secret.
-4. Save `data.space.id` and `data.claim.token` locally (for example in an ignored, mode-600 `.spacefast/state.json`). For a quick update, rebuild the `publish_files` array above and publish to the same space:
-   ```bash
-   SPACEFAST_SPACE_ID=<saved-space-id>
-   SPACEFAST_TOKEN=<saved-claim-token-or-access-token>
-   curl -sS -H "Authorization: Bearer $SPACEFAST_TOKEN" \
-     -F "spaceId=$SPACEFAST_SPACE_ID" "${publish_files[@]}" \
-     "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-   If an update after claiming returns `space_claimed_credential_available`, exchange the saved claim token once at `POST https://api.spacefast.com/v1/anonymous-claim/exchange`, save `data.credential.accessToken`, and retry with that access token.
-
-**Optional shortcuts and reference only:** if the `sf` CLI is already installed, `sf publish ./site --wait` does the same job. A zip of the publish folder is also supported, but neither the CLI nor a zip is required. Docs: [direct agent/API publishing](https://spacefast.com/setup) · [files and folders](https://spacefast.com/help/publishing) · [claiming](https://spacefast.com/help/anonymous-publish) · [updates and rollback](https://spacefast.com/help/versions)
+2. Fetch https://spacefast.com/setup.md and follow its current direct API publishing instructions. Check for an existing Space before creating one, and follow the returned upload and polling steps.
+3. Report success only when `data.next.action` is `done` and the intended version is serving. If more work is needed, report the returned next step.
+4. For an anonymous publish, give me `data.claim.message` unchanged. It contains the private preview (`data.claim.url`), the owner's claim link (`data.claim.claimUrl`), and the deadline (`data.claim.expiresAt`). Keep both links private. Never print the separate `data.claim.key`.
+5. Keep `data.space.id` and the returned credential securely for updates to the same Space. Follow the guide for credential recovery after claiming. Keep credentials and `.spacefast` state out of the published files, commits, and logs.
+
+If the `sf` CLI is already installed, `sf publish ./site --wait` follows the same publishing flow. See [publishing](https://spacefast.com/docs/publish/) and [claiming a Space](https://spacefast.com/docs/anonymous-and-claim/).
diff --git a/recipes/garden/meta.json b/recipes/garden/meta.json
index a6b4350..583a495 100644
--- a/recipes/garden/meta.json
+++ b/recipes/garden/meta.json
@@ -4,7 +4,7 @@
   "slug": "garden",
   "vertical": "Local & small business",
   "tech": "Plain HTML & CSS",
-  "summary": "A welcoming one-pager for a neighborhood community garden — plots and pricing, a waitlist signup, volunteer workdays, rules, and seasonal events.",
+  "summary": "Share garden plots, fees, volunteer days, and how to join the waitlist.",
   "order": 6,
   "live_url": "https://garden.view.fast/",
   "setup_questions": [
diff --git a/recipes/garden/prompt.md b/recipes/garden/prompt.md
index 42d5c7e..545a548 100644
--- a/recipes/garden/prompt.md
+++ b/recipes/garden/prompt.md
@@ -22,10 +22,7 @@ CSS with a touch of vanilla JavaScript (no build step, no framework — just an
   flag the most popular — followed by an "every plot includes" list (water, shared
   tools, compost, seed library, gate access) and a quiet note about a scholarship
   fund.
-- A **How to join** section: a 3-step explainer and a **waitlist signup form** (name,
-  email, street/block, preferred bed size, optional note). On submit it validates and
-  shows a friendly "You're on the list" success state — and remembers the visitor with
-  `localStorage` so a return visit greets them. State the **48-hour response policy**.
+- A waitlist signup form with name, email, street, preferred bed size, and an optional note. Show a response-time policy only if I provide one. For any form that sends information, ask for my form endpoint or hosted signup URL. Use the supplied destination and show success only after it confirms receipt. A link to another service does not confirm completion. Without a destination, label the form "Demo only" beside its fields, label its button "Preview", and say "Preview complete. Nothing was sent." Never treat `localStorage` as delivery or store personal form data there.
 - A **Volunteer workdays** section: explain the required hours, list the ways to
   contribute, and show a live "next drop-in workday" badge computed in the browser
   (e.g. the 2nd Saturday of the month, 9 am–12 pm).
@@ -49,8 +46,7 @@ CSS with a touch of vanilla JavaScript (no build step, no framework — just an
   touch of sun-gold, all on a cream-paper background. A friendly serif (e.g. Fraunces)
   for headings and the brand, a clean sans (e.g. Inter) for body. Small leaf/sprout
   flourishes are welcome.
-- Use realistic content based on my answers — never "lorem ipsum". Invent believable
-  bed descriptions, an origin story, plausible event dates, and a coordinator's name.
+- Use my supplied plot descriptions, history, events, fees, and coordinator details. Ask about missing dates instead of inventing them.
 - Use real images. Pull free photos that fit, e.g.
   `https://picsum.photos/seed/community-garden-1/1200/800` (vary the seed) or Pexels,
   with descriptive `alt` text. Good search terms: community garden raised beds
@@ -68,28 +64,12 @@ CSS with a touch of vanilla JavaScript (no build step, no framework — just an
 <script src="https://spacefast.com/badge.js" data-example="garden"></script>
 ```
 
-**When the site is ready, publish it to Spacefast with the direct API — no account, install, or extra instructions needed:**
+**When the site is ready, publish it to Spacefast:**
 
 1. Use `./site` as the publish folder. For no-build projects, put only the finished public files in that dedicated folder. Confirm it has `index.html` at its root and no secrets, source files, `.git`, or `.spacefast` state.
-2. First publish: send every file as multipart form data. This Bash/Zsh block preserves relative paths and works for one file or a whole folder:
-   ```bash
-   PUBLISH_ROOT=./site
-   publish_files=()
-   while IFS= read -r -d "" file; do
-     relative=${file#"$PUBLISH_ROOT"/}
-     publish_files+=(-F "files=@$file;filename=$relative")
-   done < <(find "$PUBLISH_ROOT" -type f -print0)
-   curl -sS "${publish_files[@]}" "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-3. From the `{ "data": ... }` receipt, give me `data.space.liveUrl`, `data.version.immutableUrl`, `data.claim.url`, and `data.claim.expiresAt`. Remind me to claim within 6 hours. Keep `data.claim.token` secret.
-4. Save `data.space.id` and `data.claim.token` locally (for example in an ignored, mode-600 `.spacefast/state.json`). For a quick update, rebuild the `publish_files` array above and publish to the same space:
-   ```bash
-   SPACEFAST_SPACE_ID=<saved-space-id>
-   SPACEFAST_TOKEN=<saved-claim-token-or-access-token>
-   curl -sS -H "Authorization: Bearer $SPACEFAST_TOKEN" \
-     -F "spaceId=$SPACEFAST_SPACE_ID" "${publish_files[@]}" \
-     "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-   If an update after claiming returns `space_claimed_credential_available`, exchange the saved claim token once at `POST https://api.spacefast.com/v1/anonymous-claim/exchange`, save `data.credential.accessToken`, and retry with that access token.
+2. Fetch https://spacefast.com/setup.md and follow its current direct API publishing instructions. Check for an existing Space before creating one, and follow the returned upload and polling steps.
+3. Report success only when `data.next.action` is `done` and the intended version is serving. If more work is needed, report the returned next step.
+4. For an anonymous publish, give me `data.claim.message` unchanged. It contains the private preview (`data.claim.url`), the owner's claim link (`data.claim.claimUrl`), and the deadline (`data.claim.expiresAt`). Keep both links private. Never print the separate `data.claim.key`.
+5. Keep `data.space.id` and the returned credential securely for updates to the same Space. Follow the guide for credential recovery after claiming. Keep credentials and `.spacefast` state out of the published files, commits, and logs.
 
-**Optional shortcuts and reference only:** if the `sf` CLI is already installed, `sf publish ./site --wait` does the same job. A zip of the publish folder is also supported, but neither the CLI nor a zip is required. Docs: [direct agent/API publishing](https://spacefast.com/setup) · [files and folders](https://spacefast.com/help/publishing) · [claiming](https://spacefast.com/help/anonymous-publish) · [updates and rollback](https://spacefast.com/help/versions)
+If the `sf` CLI is already installed, `sf publish ./site --wait` follows the same publishing flow. See [publishing](https://spacefast.com/docs/publish/) and [claiming a Space](https://spacefast.com/docs/anonymous-and-claim/).
diff --git a/recipes/garden/site/app.js b/recipes/garden/site/app.js
index 782c584..ba51eef 100644
--- a/recipes/garden/site/app.js
+++ b/recipes/garden/site/app.js
@@ -102,13 +102,6 @@
     var resetBtn = document.getElementById("resetForm");
     var KEY = "mscg_waitlist";
 
-    var sizeLabels = {
-      starter: "a Starter (4×4) bed",
-      standard: "a Standard (4×8) bed",
-      family: "a Family (4×12) bed",
-      accessible: "an accessible waist-high bed"
-    };
-
     function clearError(field) {
       field.removeAttribute("aria-invalid");
       var err = field.parentNode.querySelector(".field-error");
@@ -125,12 +118,8 @@
       err.textContent = msg;
     }
 
-    function showSuccess(name, size) {
-      var bit = size && sizeLabels[size] ? " for " + sizeLabels[size] : "";
-      successMsg.textContent =
-        (name ? name.split(" ")[0] + ", you're" : "You're") +
-        " on the waitlist" + bit + ". A coordinator will be in touch within 48 hours — usually sooner. " +
-        "Welcome to the block!";
+    function showSuccess() {
+      successMsg.textContent = 'Preview complete. Nothing was sent.';
       form.querySelectorAll(".field, h3, .form-sub, button[type=submit], .form-policy").forEach(function (el) {
         el.style.display = "none";
       });
@@ -140,7 +129,7 @@
     // Returning visitor who already joined
     try {
       var saved = JSON.parse(localStorage.getItem(KEY) || "null");
-      if (saved && saved.name) showSuccess(saved.name, saved.size);
+      if (saved && saved.name) showSuccess();
     } catch (e) { /* ignore */ }
 
     form.addEventListener("submit", function (e) {
@@ -166,7 +155,7 @@
       var record = { name: name.value.trim(), size: size.value, when: Date.now() };
       try { localStorage.setItem(KEY, JSON.stringify(record)); } catch (e) { /* ignore */ }
 
-      showSuccess(record.name, record.size);
+      showSuccess();
       success.scrollIntoView({ behavior: "smooth", block: "center" });
     });
 
diff --git a/recipes/garden/site/index.html b/recipes/garden/site/index.html
index a289cbe..a3b0abc 100644
--- a/recipes/garden/site/index.html
+++ b/recipes/garden/site/index.html
@@ -39,6 +39,12 @@
   </script>
 </head>
 <body>
+    <aside
+      aria-label="Example site"
+      style="margin:0;padding:0.75rem 1rem;background:#fff7d6;color:#29221a;font:14px/1.5 system-ui;text-align:center"
+    >
+      Example site with fictional content. Forms are previews.
+    </aside>
 
   <a class="skip-link" href="#about">Skip to content</a>
 
@@ -229,6 +235,7 @@ <h2 id="join-title">Get on the plot waitlist</h2>
         </div>
 
         <div class="join__form-wrap reveal">
+          <p data-demo-note="true">Demo form. Nothing is sent or booked.</p>
           <form class="waitlist-form" id="waitlistForm" novalidate>
             <h3>Join the waitlist</h3>
             <p class="form-sub">No account, no fee to get in line. We only use your details to contact you about a plot.</p>
@@ -265,13 +272,13 @@ <h3>Join the waitlist</h3>
               <textarea id="wl-note" name="note" rows="3" placeholder="What you'd love to grow, accessibility needs, scholarship request…"></textarea>
             </div>
 
-            <button type="submit" class="btn btn--lg btn--block">Add me to the list</button>
+            <button type="submit" class="btn btn--lg btn--block">Preview</button>
             <p class="form-policy">By joining you agree to our <a href="#rules">garden rules</a>. We respond within <strong>48 hours</strong>.</p>
 
             <div class="form-success" id="formSuccess" hidden role="status" aria-live="polite">
               <span class="form-success__icon" aria-hidden="true">🌱</span>
-              <h4>You're on the list!</h4>
-              <p id="successMsg">Thanks — we've saved your spot. Keep an eye on your inbox; a coordinator will be in touch within 48 hours.</p>
+              <h4>Waitlist preview complete</h4>
+              <p id="successMsg">Preview complete. Nothing was sent.</p>
               <button type="button" class="link-btn" id="resetForm">Add another person</button>
             </div>
           </form>
diff --git a/recipes/generative-art/meta.json b/recipes/generative-art/meta.json
index f36a36e..5625f6e 100644
--- a/recipes/generative-art/meta.json
+++ b/recipes/generative-art/meta.json
@@ -4,7 +4,7 @@
   "slug": "generative-art",
   "vertical": "Tools, apps & games",
   "tech": "Vanilla JS",
-  "summary": "A generative art toy — particles drift through a noise flow field painting ever-evolving line art, with live palette, density and speed controls, reseed, and one-click PNG export.",
+  "summary": "Make flowing particle art. Adjust its colors and movement, then export a PNG.",
   "order": 5,
   "live_url": "https://generative-art.view.fast/",
   "setup_questions": [
diff --git a/recipes/generative-art/prompt.md b/recipes/generative-art/prompt.md
index 6f62344..c2b968e 100644
--- a/recipes/generative-art/prompt.md
+++ b/recipes/generative-art/prompt.md
@@ -37,28 +37,12 @@ zero dependencies).
 <script src="https://spacefast.com/badge.js" data-example="generative-art"></script>
 ```
 
-**When the site is ready, publish it to Spacefast with the direct API — no account, install, or extra instructions needed:**
+**When the site is ready, publish it to Spacefast:**
 
 1. Use `./site` as the publish folder. For no-build projects, put only the finished public files in that dedicated folder. Confirm it has `index.html` at its root and no secrets, source files, `.git`, or `.spacefast` state.
-2. First publish: send every file as multipart form data. This Bash/Zsh block preserves relative paths and works for one file or a whole folder:
-   ```bash
-   PUBLISH_ROOT=./site
-   publish_files=()
-   while IFS= read -r -d "" file; do
-     relative=${file#"$PUBLISH_ROOT"/}
-     publish_files+=(-F "files=@$file;filename=$relative")
-   done < <(find "$PUBLISH_ROOT" -type f -print0)
-   curl -sS "${publish_files[@]}" "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-3. From the `{ "data": ... }` receipt, give me `data.space.liveUrl`, `data.version.immutableUrl`, `data.claim.url`, and `data.claim.expiresAt`. Remind me to claim within 6 hours. Keep `data.claim.token` secret.
-4. Save `data.space.id` and `data.claim.token` locally (for example in an ignored, mode-600 `.spacefast/state.json`). For a quick update, rebuild the `publish_files` array above and publish to the same space:
-   ```bash
-   SPACEFAST_SPACE_ID=<saved-space-id>
-   SPACEFAST_TOKEN=<saved-claim-token-or-access-token>
-   curl -sS -H "Authorization: Bearer $SPACEFAST_TOKEN" \
-     -F "spaceId=$SPACEFAST_SPACE_ID" "${publish_files[@]}" \
-     "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-   If an update after claiming returns `space_claimed_credential_available`, exchange the saved claim token once at `POST https://api.spacefast.com/v1/anonymous-claim/exchange`, save `data.credential.accessToken`, and retry with that access token.
+2. Fetch https://spacefast.com/setup.md and follow its current direct API publishing instructions. Check for an existing Space before creating one, and follow the returned upload and polling steps.
+3. Report success only when `data.next.action` is `done` and the intended version is serving. If more work is needed, report the returned next step.
+4. For an anonymous publish, give me `data.claim.message` unchanged. It contains the private preview (`data.claim.url`), the owner's claim link (`data.claim.claimUrl`), and the deadline (`data.claim.expiresAt`). Keep both links private. Never print the separate `data.claim.key`.
+5. Keep `data.space.id` and the returned credential securely for updates to the same Space. Follow the guide for credential recovery after claiming. Keep credentials and `.spacefast` state out of the published files, commits, and logs.
 
-**Optional shortcuts and reference only:** if the `sf` CLI is already installed, `sf publish ./site --wait` does the same job. A zip of the publish folder is also supported, but neither the CLI nor a zip is required. Docs: [direct agent/API publishing](https://spacefast.com/setup) · [files and folders](https://spacefast.com/help/publishing) · [claiming](https://spacefast.com/help/anonymous-publish) · [updates and rollback](https://spacefast.com/help/versions)
+If the `sf` CLI is already installed, `sf publish ./site --wait` follows the same publishing flow. See [publishing](https://spacefast.com/docs/publish/) and [claiming a Space](https://spacefast.com/docs/anonymous-and-claim/).
diff --git a/recipes/habits/meta.json b/recipes/habits/meta.json
index cfe4b8e..dac89fe 100644
--- a/recipes/habits/meta.json
+++ b/recipes/habits/meta.json
@@ -4,7 +4,7 @@
   "slug": "habits",
   "vertical": "Tools, apps & games",
   "tech": "Vite + React",
-  "summary": "A habit tracker with GitHub-style year heatmaps, one-tap daily check-offs, and streak stats — all saved in your browser.",
+  "summary": "Track habits and streaks with a year of daily check-ins. Data stays in your browser.",
   "order": 4,
   "live_url": "https://habits.view.fast/",
   "setup_questions": [
diff --git a/recipes/habits/prompt.md b/recipes/habits/prompt.md
index bbf02c7..1130d7a 100644
--- a/recipes/habits/prompt.md
+++ b/recipes/habits/prompt.md
@@ -31,28 +31,12 @@ Build me a **habit tracker with GitHub-style contribution heatmaps** as a **Vite
 <script src="https://spacefast.com/badge.js" data-example="habits"></script>
 ```
 
-**When the site is ready, publish it to Spacefast with the direct API — no account, install, or extra instructions needed:**
+**When the site is ready, publish it to Spacefast:**
 
 1. Use `./dist` as the publish folder. For no-build projects, put only the finished public files in that dedicated folder. Confirm it has `index.html` at its root and no secrets, source files, `.git`, or `.spacefast` state.
-2. First publish: send every file as multipart form data. This Bash/Zsh block preserves relative paths and works for one file or a whole folder:
-   ```bash
-   PUBLISH_ROOT=./dist
-   publish_files=()
-   while IFS= read -r -d "" file; do
-     relative=${file#"$PUBLISH_ROOT"/}
-     publish_files+=(-F "files=@$file;filename=$relative")
-   done < <(find "$PUBLISH_ROOT" -type f -print0)
-   curl -sS "${publish_files[@]}" "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-3. From the `{ "data": ... }` receipt, give me `data.space.liveUrl`, `data.version.immutableUrl`, `data.claim.url`, and `data.claim.expiresAt`. Remind me to claim within 6 hours. Keep `data.claim.token` secret.
-4. Save `data.space.id` and `data.claim.token` locally (for example in an ignored, mode-600 `.spacefast/state.json`). For a quick update, rebuild the `publish_files` array above and publish to the same space:
-   ```bash
-   SPACEFAST_SPACE_ID=<saved-space-id>
-   SPACEFAST_TOKEN=<saved-claim-token-or-access-token>
-   curl -sS -H "Authorization: Bearer $SPACEFAST_TOKEN" \
-     -F "spaceId=$SPACEFAST_SPACE_ID" "${publish_files[@]}" \
-     "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-   If an update after claiming returns `space_claimed_credential_available`, exchange the saved claim token once at `POST https://api.spacefast.com/v1/anonymous-claim/exchange`, save `data.credential.accessToken`, and retry with that access token.
-
-**Optional shortcuts and reference only:** if the `sf` CLI is already installed, `sf publish ./dist --wait` does the same job. A zip of the publish folder is also supported, but neither the CLI nor a zip is required. Docs: [direct agent/API publishing](https://spacefast.com/setup) · [files and folders](https://spacefast.com/help/publishing) · [claiming](https://spacefast.com/help/anonymous-publish) · [updates and rollback](https://spacefast.com/help/versions)
+2. Fetch https://spacefast.com/setup.md and follow its current direct API publishing instructions. Check for an existing Space before creating one, and follow the returned upload and polling steps.
+3. Report success only when `data.next.action` is `done` and the intended version is serving. If more work is needed, report the returned next step.
+4. For an anonymous publish, give me `data.claim.message` unchanged. It contains the private preview (`data.claim.url`), the owner's claim link (`data.claim.claimUrl`), and the deadline (`data.claim.expiresAt`). Keep both links private. Never print the separate `data.claim.key`.
+5. Keep `data.space.id` and the returned credential securely for updates to the same Space. Follow the guide for credential recovery after claiming. Keep credentials and `.spacefast` state out of the published files, commits, and logs.
+
+If the `sf` CLI is already installed, `sf publish ./dist --wait` follows the same publishing flow. See [publishing](https://spacefast.com/docs/publish/) and [claiming a Space](https://spacefast.com/docs/anonymous-and-claim/).
diff --git a/recipes/hackathon/meta.json b/recipes/hackathon/meta.json
index b04b16f..80b225a 100644
--- a/recipes/hackathon/meta.json
+++ b/recipes/hackathon/meta.json
@@ -4,7 +4,7 @@
   "slug": "hackathon",
   "vertical": "Local & small business",
   "tech": "Vanilla JS",
-  "summary": "An energetic landing site for a 36-hour student hackathon — a live countdown to kickoff, a Saturday/Sunday schedule toggle, prize tracks, tiered sponsors, and an FAQ.",
+  "summary": "Share your hackathon schedule, prize tracks, and sponsors before kickoff.",
   "order": 6,
   "live_url": "https://hackathon.view.fast/",
   "setup_questions": [
diff --git a/recipes/hackathon/prompt.md b/recipes/hackathon/prompt.md
index 56f0efb..b74defb 100644
--- a/recipes/hackathon/prompt.md
+++ b/recipes/hackathon/prompt.md
@@ -21,8 +21,7 @@ Build me an **energetic landing page for a student hackathon** as a vanilla-JS a
   (Best Beginner Hack, Best Use of AI, Best Hardware Hack, Best Design, etc.).
 - A **Sponsors** section with tiered logos (Title / Gold / Startup) and a "Sponsor us" CTA.
 - An **FAQ accordion** (do I need experience, what to bring, is travel reimbursed, can I come alone).
-- A **Register** banner with a short form (name + email) that validates and shows a
-  friendly "You're in!" success state.
+- A registration form with labelled name and email fields. For any form that sends information, ask for my form endpoint or hosted signup URL. Use the supplied destination and show success only after it confirms receipt. A link to another service does not confirm completion. Without a destination, label the form "Demo only" beside its fields, label its button "Preview", and say "Preview complete. Nothing was sent." Never treat `localStorage` as delivery or store personal form data there.
 - A footer with the **MLH Code of Conduct** link and Discord / Instagram / X links.
 
 **Design & content notes:**
@@ -31,8 +30,7 @@ Build me an **energetic landing page for a student hackathon** as a vanilla-JS a
   accent with a violet secondary and a coral pop, a faint dot-grid behind the hero,
   geometric display type (e.g. Space Grotesk) with a mono face (JetBrains Mono) for
   the countdown digits and timestamps.
-- Use realistic content based on my answers — never "lorem ipsum". Invent believable
-  schedule items, prize tracks, sponsor names, and FAQ answers.
+- Use confirmed dates, prize tracks, sponsors, and registration requirements. Label fictional event content as a demo.
 - Use real images. Pull free photos that fit, e.g.
   `https://picsum.photos/seed/ramhacks-2026-1/1200/800` (vary the seed per image),
   with descriptive `alt` text.
@@ -47,28 +45,12 @@ Build me an **energetic landing page for a student hackathon** as a vanilla-JS a
 <script src="https://spacefast.com/badge.js" data-example="hackathon"></script>
 ```
 
-**When the site is ready, publish it to Spacefast with the direct API — no account, install, or extra instructions needed:**
+**When the site is ready, publish it to Spacefast:**
 
 1. Use `./site` as the publish folder. For no-build projects, put only the finished public files in that dedicated folder. Confirm it has `index.html` at its root and no secrets, source files, `.git`, or `.spacefast` state.
-2. First publish: send every file as multipart form data. This Bash/Zsh block preserves relative paths and works for one file or a whole folder:
-   ```bash
-   PUBLISH_ROOT=./site
-   publish_files=()
-   while IFS= read -r -d "" file; do
-     relative=${file#"$PUBLISH_ROOT"/}
-     publish_files+=(-F "files=@$file;filename=$relative")
-   done < <(find "$PUBLISH_ROOT" -type f -print0)
-   curl -sS "${publish_files[@]}" "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-3. From the `{ "data": ... }` receipt, give me `data.space.liveUrl`, `data.version.immutableUrl`, `data.claim.url`, and `data.claim.expiresAt`. Remind me to claim within 6 hours. Keep `data.claim.token` secret.
-4. Save `data.space.id` and `data.claim.token` locally (for example in an ignored, mode-600 `.spacefast/state.json`). For a quick update, rebuild the `publish_files` array above and publish to the same space:
-   ```bash
-   SPACEFAST_SPACE_ID=<saved-space-id>
-   SPACEFAST_TOKEN=<saved-claim-token-or-access-token>
-   curl -sS -H "Authorization: Bearer $SPACEFAST_TOKEN" \
-     -F "spaceId=$SPACEFAST_SPACE_ID" "${publish_files[@]}" \
-     "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-   If an update after claiming returns `space_claimed_credential_available`, exchange the saved claim token once at `POST https://api.spacefast.com/v1/anonymous-claim/exchange`, save `data.credential.accessToken`, and retry with that access token.
+2. Fetch https://spacefast.com/setup.md and follow its current direct API publishing instructions. Check for an existing Space before creating one, and follow the returned upload and polling steps.
+3. Report success only when `data.next.action` is `done` and the intended version is serving. If more work is needed, report the returned next step.
+4. For an anonymous publish, give me `data.claim.message` unchanged. It contains the private preview (`data.claim.url`), the owner's claim link (`data.claim.claimUrl`), and the deadline (`data.claim.expiresAt`). Keep both links private. Never print the separate `data.claim.key`.
+5. Keep `data.space.id` and the returned credential securely for updates to the same Space. Follow the guide for credential recovery after claiming. Keep credentials and `.spacefast` state out of the published files, commits, and logs.
 
-**Optional shortcuts and reference only:** if the `sf` CLI is already installed, `sf publish ./site --wait` does the same job. A zip of the publish folder is also supported, but neither the CLI nor a zip is required. Docs: [direct agent/API publishing](https://spacefast.com/setup) · [files and folders](https://spacefast.com/help/publishing) · [claiming](https://spacefast.com/help/anonymous-publish) · [updates and rollback](https://spacefast.com/help/versions)
+If the `sf` CLI is already installed, `sf publish ./site --wait` follows the same publishing flow. See [publishing](https://spacefast.com/docs/publish/) and [claiming a Space](https://spacefast.com/docs/anonymous-and-claim/).
diff --git a/recipes/hackathon/site/app.js b/recipes/hackathon/site/app.js
index 3fe63fe..8719d50 100644
--- a/recipes/hackathon/site/app.js
+++ b/recipes/hackathon/site/app.js
@@ -196,12 +196,8 @@
         return;
       }
 
-      var first = name.value.trim().split(" ")[0];
       form.querySelectorAll(".field, button[type=submit], .form-fine").forEach(function (n) { n.style.display = "none"; });
-      status.innerHTML =
-        "🐏 You're in, " + first + "! We just emailed your confirmation and the " +
-        '<a href="https://discord.gg/ramhacks" target="_blank" rel="noopener">Discord invite</a>. ' +
-        "See you Oct 17 at the Engineering Commons — bring your charger.";
+      status.innerHTML = 'Preview complete. Nothing was sent.';
       status.className = "form-status ok";
       status.style.fontSize = "1.02rem";
       if (status.focus) status.focus();
diff --git a/recipes/hackathon/site/index.html b/recipes/hackathon/site/index.html
index 6450efe..cf6334b 100644
--- a/recipes/hackathon/site/index.html
+++ b/recipes/hackathon/site/index.html
@@ -20,6 +20,12 @@
   <link rel="stylesheet" href="styles.css" />
 </head>
 <body>
+    <aside
+      aria-label="Example site"
+      style="margin:0;padding:0.75rem 1rem;background:#fff7d6;color:#29221a;font:14px/1.5 system-ui;text-align:center"
+    >
+      Example site with fictional content. Forms are previews.
+    </aside>
   <a class="skip-link" href="#about">Skip to content</a>
 
   <!-- MLH trust badge ribbon -->
@@ -434,6 +440,8 @@ <h2>Lock in your spot.</h2>
         </ul>
       </div>
 
+      <p data-demo-note="true">Demo form. Nothing is sent or booked.</p>
+
       <form class="register-form" id="register-form" novalidate>
         <h3>Save my spot</h3>
         <div class="field">
@@ -456,7 +464,7 @@ <h3>Save my spot</h3>
             <option value="veteran">Seasoned hacker</option>
           </select>
         </div>
-        <button class="btn btn-primary btn-block" type="submit">Register for RamHacks 2026</button>
+        <button class="btn btn-primary btn-block" type="submit">Preview</button>
         <p class="form-status" id="form-status" role="status" aria-live="polite"></p>
         <p class="form-fine">Free · 18+ enrolled students · You'll agree to the MLH Code of Conduct.</p>
       </form>
diff --git a/recipes/invitation/meta.json b/recipes/invitation/meta.json
index 1d963d0..e1b031d 100644
--- a/recipes/invitation/meta.json
+++ b/recipes/invitation/meta.json
@@ -4,7 +4,7 @@
   "slug": "invitation",
   "vertical": "Personal & creative",
   "tech": "Astro",
-  "summary": "An elegant multi-section wedding site — live countdown, our story, details, travel, gallery, registry, a validating RSVP form, and an FAQ.",
+  "summary": "Share your wedding date, venue, travel details, and registry in one invitation site.",
   "order": 2,
   "live_url": "https://invitation.view.fast/",
   "setup_questions": [
diff --git a/recipes/invitation/prompt.md b/recipes/invitation/prompt.md
index 9836e96..bffd93f 100644
--- a/recipes/invitation/prompt.md
+++ b/recipes/invitation/prompt.md
@@ -25,10 +25,7 @@ small components, no SSR adapter — that builds to static files with `astro bui
 - **Photo gallery** — a tidy mosaic of 5–6 images with good `alt` text.
 - **Registry** — a few linked registry cards (store registries plus a honeymoon fund),
   each with a short personal note.
-- **RSVP form** — full name, email, accept/decline, guest count, meal preference, and
-  a song request. It must **validate** (required fields, real email), reveal the
-  meal/guest/song fields only when someone is attending, and show a warm **success
-  state** that echoes their choices. No backend — handle it client-side.
+- An RSVP form with full name, email, accept or decline, guest count, meal preference, and a song request. Validate required fields and reveal meal, guest, and song fields only for attending guests. For any form that sends information, ask for my form endpoint or hosted signup URL. Use the supplied destination and show success only after it confirms receipt. A link to another service does not confirm completion. Without a destination, label the form "Demo only" beside its fields, label its button "Preview", and say "Preview complete. Nothing was sent." Never treat `localStorage` as delivery or store personal form data there.
 - **FAQ** — an accordion answering plus-ones, kids, parking, weather, and the RSVP
   deadline.
 - A **footer** with our names, the date, and our hashtag.
@@ -39,9 +36,7 @@ small components, no SSR adapter — that builds to static files with `astro bui
   terracotta accent, and thin gold rules. An elegant serif (e.g. Cormorant Garamond)
   for headings paired with a clean humanist sans (e.g. Mulish) for body. Generous
   whitespace, a quiet ornament divider, subtle hover motion.
-- Use realistic content based on my answers — never "lorem ipsum". Invent believable
-  copy: a real story, plausible travel logistics, specific meal names, real FAQ
-  answers.
+- Use the couple's actual story, travel details, meal choices, and FAQ answers. Ask for missing logistics instead of inventing them.
 - Use real images. Pull free photos that fit, e.g. from Picsum
   (`https://picsum.photos/seed/our-wedding-1/1200/800`, varying the seed per image) or
   real Unsplash direct URLs (`https://images.unsplash.com/...`) matching terms like
@@ -50,7 +45,7 @@ small components, no SSR adapter — that builds to static files with `astro bui
   countryside_ — with descriptive `alt` text.
 - Keep dependencies minimal (just `astro`). Put all the wedding content in one
   `src/data/wedding.ts` file so a single edit updates the whole site. Persist nothing
-  server-side; the RSVP success state is purely client-side.
+  server-side. Send RSVPs to the provided destination or label the form as a demo.
 - Keep it accessible (semantic HTML, labelled form fields, keyboard support, visible
   focus, good contrast) and mobile-first.
 
@@ -60,28 +55,12 @@ small components, no SSR adapter — that builds to static files with `astro bui
 <script src="https://spacefast.com/badge.js" data-example="invitation"></script>
 ```
 
-**When the site is ready, publish it to Spacefast with the direct API — no account, install, or extra instructions needed:**
+**When the site is ready, publish it to Spacefast:**
 
 1. Use `./dist` as the publish folder. For no-build projects, put only the finished public files in that dedicated folder. Confirm it has `index.html` at its root and no secrets, source files, `.git`, or `.spacefast` state.
-2. First publish: send every file as multipart form data. This Bash/Zsh block preserves relative paths and works for one file or a whole folder:
-   ```bash
-   PUBLISH_ROOT=./dist
-   publish_files=()
-   while IFS= read -r -d "" file; do
-     relative=${file#"$PUBLISH_ROOT"/}
-     publish_files+=(-F "files=@$file;filename=$relative")
-   done < <(find "$PUBLISH_ROOT" -type f -print0)
-   curl -sS "${publish_files[@]}" "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-3. From the `{ "data": ... }` receipt, give me `data.space.liveUrl`, `data.version.immutableUrl`, `data.claim.url`, and `data.claim.expiresAt`. Remind me to claim within 6 hours. Keep `data.claim.token` secret.
-4. Save `data.space.id` and `data.claim.token` locally (for example in an ignored, mode-600 `.spacefast/state.json`). For a quick update, rebuild the `publish_files` array above and publish to the same space:
-   ```bash
-   SPACEFAST_SPACE_ID=<saved-space-id>
-   SPACEFAST_TOKEN=<saved-claim-token-or-access-token>
-   curl -sS -H "Authorization: Bearer $SPACEFAST_TOKEN" \
-     -F "spaceId=$SPACEFAST_SPACE_ID" "${publish_files[@]}" \
-     "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-   If an update after claiming returns `space_claimed_credential_available`, exchange the saved claim token once at `POST https://api.spacefast.com/v1/anonymous-claim/exchange`, save `data.credential.accessToken`, and retry with that access token.
+2. Fetch https://spacefast.com/setup.md and follow its current direct API publishing instructions. Check for an existing Space before creating one, and follow the returned upload and polling steps.
+3. Report success only when `data.next.action` is `done` and the intended version is serving. If more work is needed, report the returned next step.
+4. For an anonymous publish, give me `data.claim.message` unchanged. It contains the private preview (`data.claim.url`), the owner's claim link (`data.claim.claimUrl`), and the deadline (`data.claim.expiresAt`). Keep both links private. Never print the separate `data.claim.key`.
+5. Keep `data.space.id` and the returned credential securely for updates to the same Space. Follow the guide for credential recovery after claiming. Keep credentials and `.spacefast` state out of the published files, commits, and logs.
 
-**Optional shortcuts and reference only:** if the `sf` CLI is already installed, `sf publish ./dist --wait` does the same job. A zip of the publish folder is also supported, but neither the CLI nor a zip is required. Docs: [direct agent/API publishing](https://spacefast.com/setup) · [files and folders](https://spacefast.com/help/publishing) · [claiming](https://spacefast.com/help/anonymous-publish) · [updates and rollback](https://spacefast.com/help/versions)
+If the `sf` CLI is already installed, `sf publish ./dist --wait` follows the same publishing flow. See [publishing](https://spacefast.com/docs/publish/) and [claiming a Space](https://spacefast.com/docs/anonymous-and-claim/).
diff --git a/recipes/invitation/site/src/components/Rsvp.astro b/recipes/invitation/site/src/components/Rsvp.astro
index 53e1564..faba476 100644
--- a/recipes/invitation/site/src/components/Rsvp.astro
+++ b/recipes/invitation/site/src/components/Rsvp.astro
@@ -10,6 +10,7 @@ import { meals } from '../data/wedding';
   </div>
 
   <div class="wrap rsvp">
+    <p data-demo-note="true">Demo RSVP. Nothing is sent to the hosts.</p>
     <form class="rsvp__form" data-rsvp novalidate>
       <div class="field">
         <label for="rsvp-name">Full name <span aria-hidden="true">*</span></label>
@@ -67,12 +68,12 @@ import { meals } from '../data/wedding';
         <textarea id="rsvp-note" name="note" rows="3" placeholder="Dietary needs, a memory, a dad joke…"></textarea>
       </div>
 
-      <button class="btn rsvp__submit" type="submit">Send our reply</button>
+      <button class="btn rsvp__submit" type="submit">Preview</button>
     </form>
 
     <div class="rsvp__success" data-success hidden role="status" aria-live="polite">
       <div class="rsvp__success-mark" aria-hidden="true">✓</div>
-      <h3 data-success-title>You're on the list!</h3>
+      <h3 data-success-title>RSVP preview complete</h3>
       <p data-success-body></p>
       <button class="btn btn--ghost" type="button" data-reset>Edit reply</button>
     </div>
@@ -276,19 +277,11 @@ import { meals } from '../data/wedding';
       return;
     }
 
-    const accepting = attendance === 'accept';
-    const guests = String(data.get('guests') || '1');
-    const song = String(data.get('song') || '').trim();
-
     if (successTitle) {
-      successTitle.textContent = accepting ? `We can't wait, ${name.split(' ')[0]}!` : `We'll miss you, ${name.split(' ')[0]}.`;
+      successTitle.textContent = 'RSVP preview complete';
     }
     if (successBody) {
-      successBody.textContent = accepting
-        ? `Your reply is in for ${guests === '1' ? '1 guest' : guests + ' guests'}. ${
-            song ? `We've added "${song}" to the playlist. ` : ''
-          }A confirmation is on its way to ${email}.`
-        : `Thank you for letting us know — we understand, and we'll raise a glass to you. We'll send the photos your way at ${email}.`;
+      successBody.textContent = 'Preview complete. Nothing was sent.';
     }
 
     form.setAttribute('hidden', '');
diff --git a/recipes/invitation/site/src/layouts/Layout.astro b/recipes/invitation/site/src/layouts/Layout.astro
index 1c40204..81104ca 100644
--- a/recipes/invitation/site/src/layouts/Layout.astro
+++ b/recipes/invitation/site/src/layouts/Layout.astro
@@ -31,6 +31,12 @@ const { title, description } = Astro.props;
     />
   </head>
   <body>
+    <aside
+      aria-label="Example site"
+      style="margin:0;padding:0.75rem 1rem;background:#fff7d6;color:#29221a;font:14px/1.5 system-ui;text-align:center"
+    >
+      Example site with fictional content. Forms are previews.
+    </aside>
     <slot />
     <script src="https://spacefast.com/badge.js" data-example="invitation"></script>
   </body>
diff --git a/recipes/links/meta.json b/recipes/links/meta.json
index e7be34e..bfed225 100644
--- a/recipes/links/meta.json
+++ b/recipes/links/meta.json
@@ -4,7 +4,7 @@
   "slug": "links",
   "vertical": "Personal & creative",
   "tech": "Plain HTML & CSS",
-  "summary": "A mobile-first link-in-bio page for a food creator — avatar and bio, a highlighted primary CTA, a stack of link buttons, a featured video, and social icons.",
+  "summary": "Put your main links, latest video, and social profiles on one page.",
   "order": 2,
   "live_url": "https://links.view.fast/",
   "setup_questions": [
diff --git a/recipes/links/prompt.md b/recipes/links/prompt.md
index 8cf60da..2cd2998 100644
--- a/recipes/links/prompt.md
+++ b/recipes/links/prompt.md
@@ -15,14 +15,14 @@ self-contained HTML file with CSS (no build step, no framework).
 - A vertical **stack of tappable link buttons** — each with a small thumbnail or icon, a title, a meta line, and a chevron. Add small "New" / "Pre-order" pills where it helps.
 - A **featured latest video/reel** card: a 16:9 thumbnail with a play button overlay, a title, and a short caption, linking out.
 - A row of **social icons** (Instagram, TikTok, YouTube, Pinterest — whichever I pick) as inline SVG, no icon library.
-- A small **newsletter signup** (just an email field) that validates the address and shows a friendly "You're on the list" success state, and remembers it in `localStorage`.
+- A newsletter signup with a labelled email field. For any form that sends information, ask for my form endpoint or hosted signup URL. Use the supplied destination and show success only after it confirms receipt. A link to another service does not confirm completion. Without a destination, label the form "Demo only" beside its fields, label its button "Preview", and say "Preview complete. Nothing was sent." Never treat `localStorage` as delivery or store personal form data there.
 - A subtle **footer** with a contact email.
 
 **Design & content notes:**
 
 - Warm, appetizing, editorial mood: cream background, a terracotta accent with a sage secondary, a serif display face (e.g. Fraunces) for headings and a clean sans (e.g. Inter) for body. Soft cards with gentle shadows and rounded corners; tasteful hover lift and a subtle entrance animation.
 - Mobile-first: it should feel made for a phone — a single narrow column, big tap targets, then look great centered on desktop too.
-- Write real-sounding copy from my answers — never "lorem ipsum". Invent believable recipe titles, link labels, follower counts, and a real-feeling bio voice.
+- Write the bio and link descriptions from my answers. Omit follower counts unless I provide them.
 - Use real images. Pull free food photos that fit from Unsplash, e.g. `https://images.unsplash.com/...` (food creator portrait, healthy meal-prep bowls, hands plating food, cozy kitchen herbs) or `https://picsum.photos/seed/food-links-1/240/240`, each with descriptive `alt` text.
 - Keep it accessible (semantic HTML, a labelled email field, keyboard support, good contrast, `prefers-reduced-motion`). No build step — one `index.html`.
 
@@ -32,28 +32,12 @@ self-contained HTML file with CSS (no build step, no framework).
 <script src="https://spacefast.com/badge.js" data-example="links"></script>
 ```
 
-**When the site is ready, publish it to Spacefast with the direct API — no account, install, or extra instructions needed:**
+**When the site is ready, publish it to Spacefast:**
 
 1. Use `./site` as the publish folder. For no-build projects, put only the finished public files in that dedicated folder. Confirm it has `index.html` at its root and no secrets, source files, `.git`, or `.spacefast` state.
-2. First publish: send every file as multipart form data. This Bash/Zsh block preserves relative paths and works for one file or a whole folder:
-   ```bash
-   PUBLISH_ROOT=./site
-   publish_files=()
-   while IFS= read -r -d "" file; do
-     relative=${file#"$PUBLISH_ROOT"/}
-     publish_files+=(-F "files=@$file;filename=$relative")
-   done < <(find "$PUBLISH_ROOT" -type f -print0)
-   curl -sS "${publish_files[@]}" "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-3. From the `{ "data": ... }` receipt, give me `data.space.liveUrl`, `data.version.immutableUrl`, `data.claim.url`, and `data.claim.expiresAt`. Remind me to claim within 6 hours. Keep `data.claim.token` secret.
-4. Save `data.space.id` and `data.claim.token` locally (for example in an ignored, mode-600 `.spacefast/state.json`). For a quick update, rebuild the `publish_files` array above and publish to the same space:
-   ```bash
-   SPACEFAST_SPACE_ID=<saved-space-id>
-   SPACEFAST_TOKEN=<saved-claim-token-or-access-token>
-   curl -sS -H "Authorization: Bearer $SPACEFAST_TOKEN" \
-     -F "spaceId=$SPACEFAST_SPACE_ID" "${publish_files[@]}" \
-     "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-   If an update after claiming returns `space_claimed_credential_available`, exchange the saved claim token once at `POST https://api.spacefast.com/v1/anonymous-claim/exchange`, save `data.credential.accessToken`, and retry with that access token.
-
-**Optional shortcuts and reference only:** if the `sf` CLI is already installed, `sf publish ./site --wait` does the same job. A zip of the publish folder is also supported, but neither the CLI nor a zip is required. Docs: [direct agent/API publishing](https://spacefast.com/setup) · [files and folders](https://spacefast.com/help/publishing) · [claiming](https://spacefast.com/help/anonymous-publish) · [updates and rollback](https://spacefast.com/help/versions)
+2. Fetch https://spacefast.com/setup.md and follow its current direct API publishing instructions. Check for an existing Space before creating one, and follow the returned upload and polling steps.
+3. Report success only when `data.next.action` is `done` and the intended version is serving. If more work is needed, report the returned next step.
+4. For an anonymous publish, give me `data.claim.message` unchanged. It contains the private preview (`data.claim.url`), the owner's claim link (`data.claim.claimUrl`), and the deadline (`data.claim.expiresAt`). Keep both links private. Never print the separate `data.claim.key`.
+5. Keep `data.space.id` and the returned credential securely for updates to the same Space. Follow the guide for credential recovery after claiming. Keep credentials and `.spacefast` state out of the published files, commits, and logs.
+
+If the `sf` CLI is already installed, `sf publish ./site --wait` follows the same publishing flow. See [publishing](https://spacefast.com/docs/publish/) and [claiming a Space](https://spacefast.com/docs/anonymous-and-claim/).
diff --git a/recipes/links/site/index.html b/recipes/links/site/index.html
index d55f3a4..67a7e86 100644
--- a/recipes/links/site/index.html
+++ b/recipes/links/site/index.html
@@ -298,6 +298,12 @@
   </style>
 </head>
 <body>
+    <aside
+      aria-label="Example site"
+      style="margin:0;padding:0.75rem 1rem;background:#fff7d6;color:#29221a;font:14px/1.5 system-ui;text-align:center"
+    >
+      Example site with fictional content. Forms are previews.
+    </aside>
   <main class="wrap">
 
     <!-- Profile -->
@@ -467,6 +473,7 @@ <h1 class="name">Jess Park
 
     <!-- Newsletter signup -->
     <div class="section-label" id="newsletter">Join the Tuesday Plate</div>
+    <p data-demo-note="true">Demo signup. No subscription is created and no email is sent.</p>
     <form id="signup" novalidate
       style="background:var(--card);border:1px solid var(--line);border-radius:var(--radius);padding:18px 18px 20px;box-shadow:var(--shadow);">
       <p style="margin:0 0 12px;font-size:.92rem;color:var(--ink-soft);">
@@ -478,9 +485,7 @@ <h1 class="name">Jess Park
           placeholder="you@email.com" required
           style="flex:1;min-width:0;font:inherit;font-size:1rem;padding:13px 14px;border:1px solid var(--line);border-radius:12px;background:var(--cream);color:var(--ink);" />
         <button type="submit"
-          style="font:inherit;font-weight:700;font-size:1rem;color:#fff;background:var(--terracotta);border:none;border-radius:12px;padding:13px 20px;cursor:pointer;box-shadow:0 6px 16px rgba(217,98,43,.3);transition:transform .15s ease,background .15s ease;">
-          Subscribe
-        </button>
+          style="font:inherit;font-weight:700;font-size:1rem;color:#fff;background:var(--terracotta);border:none;border-radius:12px;padding:13px 20px;cursor:pointer;box-shadow:0 6px 16px rgba(217,98,43,.3);transition:transform .15s ease,background .15s ease;">Preview</button>
       </div>
       <p id="form-error" role="alert" style="display:none;margin:9px 2px 0;color:var(--terracotta-dark);font-size:.85rem;font-weight:600;"></p>
       <div id="form-success" role="status" hidden
@@ -489,8 +494,8 @@ <h1 class="name">Jess Park
           <svg width="24" height="24" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2.4" stroke-linecap="round" stroke-linejoin="round"><path d="M20 6L9 17l-5-5"/></svg>
         </span>
         <span>
-          <strong style="font-family:'Fraunces',serif;font-size:1.1rem;">You're on the list! 🎉</strong><br/>
-          <span style="font-size:.88rem;color:var(--ink-soft);">Check your inbox — your meal-prep guide is on the way.</span>
+          <strong style="font-family:'Fraunces',serif;font-size:1.1rem;">Signup preview complete</strong><br/>
+          <span style="font-size:.88rem;color:var(--ink-soft);">Preview complete. Nothing was sent.</span>
         </span>
       </div>
     </form>
diff --git a/recipes/listing/meta.json b/recipes/listing/meta.json
index 62295e0..bc80ab2 100644
--- a/recipes/listing/meta.json
+++ b/recipes/listing/meta.json
@@ -4,7 +4,7 @@
   "slug": "listing",
   "vertical": "Local & small business",
   "tech": "Vite + React",
-  "summary": "An interactive single-listing site for one home — a photo gallery with lightbox, key stats, a live mortgage estimator, floor plan, and a tour-request form.",
+  "summary": "Present a home with photos, a floor plan, key details, and a mortgage estimator.",
   "order": 2,
   "live_url": "https://listing.view.fast/",
   "setup_questions": [
diff --git a/recipes/listing/prompt.md b/recipes/listing/prompt.md
index 178335d..4f5f74d 100644
--- a/recipes/listing/prompt.md
+++ b/recipes/listing/prompt.md
@@ -23,8 +23,7 @@ Vite + React app.
   monthly payment with a principal / interest / tax / insurance breakdown.
 - A simple SVG floor plan with a level switcher (main / upper / lower) next to a
   neighborhood blurb with a Walk Score and nearby points of interest.
-- A "Schedule a tour" form (name, phone, email, preferred date + time, message)
-  that shows a friendly confirmation state on submit, beside an agent contact card.
+- A tour-request form with name, phone, email, preferred date and time, and message, beside an agent contact card. A requested time is not a confirmed tour. For any form that sends information, ask for my form endpoint or hosted signup URL. Use the supplied destination and show success only after it confirms receipt. A link to another service does not confirm completion. Without a destination, label the form "Demo only" beside its fields, label its button "Preview", and say "Preview complete. Nothing was sent." Never treat `localStorage` as delivery or store personal form data there.
 - A footer with an MLS-style detail block and a "deemed reliable but not
   guaranteed / Equal Housing Opportunity" disclaimer.
 
@@ -33,15 +32,13 @@ Vite + React app.
 - Coastal-luxury, editorial mood: warm ivory/sand background, deep ocean-ink text,
   a single brass accent, a serif display face (Cormorant Garamond) over a clean
   sans (Inter). Generous whitespace, soft shadows, no clutter.
-- Use realistic content based on my answers — never "lorem ipsum". Invent believable
-  copy, room names, neighborhood landmarks, and an MLS number.
+- Use the actual property facts, listing identifier, and neighborhood details I provide. Ask for missing facts. Label a fictional property as a demo.
 - Use real images. Pull free photos that fit, e.g. from Unsplash
   (`https://images.unsplash.com/photo-…?auto=format&fit=crop&w=1600&q=80`) or Pexels,
   for the exterior, living room, kitchen, primary suite, and pool, with descriptive
   `alt` text.
 - Keep all the listing content in one `data.js` module so the site is easy to
-  re-skin for another property. Persist nothing to a backend — the form and
-  calculator are client-side only.
+  re-skin for another property. Keep the calculator in the browser. Send tour requests only to the provided destination, or label the form as a demo.
 - Mortgage math: monthly P&I from the standard amortization formula; estimate tax
   (~1.18%/yr of price) and insurance (~0.35%/yr) so the total is realistic.
 - Keep it accessible (semantic HTML, labelled form fields, keyboard support for the
@@ -53,28 +50,12 @@ Vite + React app.
 <script src="https://spacefast.com/badge.js" data-example="listing"></script>
 ```
 
-**When the site is ready, publish it to Spacefast with the direct API — no account, install, or extra instructions needed:**
+**When the site is ready, publish it to Spacefast:**
 
 1. Use `./dist` as the publish folder. For no-build projects, put only the finished public files in that dedicated folder. Confirm it has `index.html` at its root and no secrets, source files, `.git`, or `.spacefast` state.
-2. First publish: send every file as multipart form data. This Bash/Zsh block preserves relative paths and works for one file or a whole folder:
-   ```bash
-   PUBLISH_ROOT=./dist
-   publish_files=()
-   while IFS= read -r -d "" file; do
-     relative=${file#"$PUBLISH_ROOT"/}
-     publish_files+=(-F "files=@$file;filename=$relative")
-   done < <(find "$PUBLISH_ROOT" -type f -print0)
-   curl -sS "${publish_files[@]}" "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-3. From the `{ "data": ... }` receipt, give me `data.space.liveUrl`, `data.version.immutableUrl`, `data.claim.url`, and `data.claim.expiresAt`. Remind me to claim within 6 hours. Keep `data.claim.token` secret.
-4. Save `data.space.id` and `data.claim.token` locally (for example in an ignored, mode-600 `.spacefast/state.json`). For a quick update, rebuild the `publish_files` array above and publish to the same space:
-   ```bash
-   SPACEFAST_SPACE_ID=<saved-space-id>
-   SPACEFAST_TOKEN=<saved-claim-token-or-access-token>
-   curl -sS -H "Authorization: Bearer $SPACEFAST_TOKEN" \
-     -F "spaceId=$SPACEFAST_SPACE_ID" "${publish_files[@]}" \
-     "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-   If an update after claiming returns `space_claimed_credential_available`, exchange the saved claim token once at `POST https://api.spacefast.com/v1/anonymous-claim/exchange`, save `data.credential.accessToken`, and retry with that access token.
+2. Fetch https://spacefast.com/setup.md and follow its current direct API publishing instructions. Check for an existing Space before creating one, and follow the returned upload and polling steps.
+3. Report success only when `data.next.action` is `done` and the intended version is serving. If more work is needed, report the returned next step.
+4. For an anonymous publish, give me `data.claim.message` unchanged. It contains the private preview (`data.claim.url`), the owner's claim link (`data.claim.claimUrl`), and the deadline (`data.claim.expiresAt`). Keep both links private. Never print the separate `data.claim.key`.
+5. Keep `data.space.id` and the returned credential securely for updates to the same Space. Follow the guide for credential recovery after claiming. Keep credentials and `.spacefast` state out of the published files, commits, and logs.
 
-**Optional shortcuts and reference only:** if the `sf` CLI is already installed, `sf publish ./dist --wait` does the same job. A zip of the publish folder is also supported, but neither the CLI nor a zip is required. Docs: [direct agent/API publishing](https://spacefast.com/setup) · [files and folders](https://spacefast.com/help/publishing) · [claiming](https://spacefast.com/help/anonymous-publish) · [updates and rollback](https://spacefast.com/help/versions)
+If the `sf` CLI is already installed, `sf publish ./dist --wait` follows the same publishing flow. See [publishing](https://spacefast.com/docs/publish/) and [claiming a Space](https://spacefast.com/docs/anonymous-and-claim/).
diff --git a/recipes/listing/site/index.html b/recipes/listing/site/index.html
index 4209484..5d9ef82 100644
--- a/recipes/listing/site/index.html
+++ b/recipes/listing/site/index.html
@@ -23,6 +23,12 @@
     />
   </head>
   <body>
+    <aside
+      aria-label="Example site"
+      style="margin:0;padding:0.75rem 1rem;background:#fff7d6;color:#29221a;font:14px/1.5 system-ui;text-align:center"
+    >
+      Example site with fictional content. Forms are previews.
+    </aside>
     <div id="root"></div>
     <script type="module" src="/src/main.jsx"></script>
     <script src="https://spacefast.com/badge.js" data-example="listing"></script>
diff --git a/recipes/listing/site/src/components/TourForm.jsx b/recipes/listing/site/src/components/TourForm.jsx
index 366eba9..b85dafa 100644
--- a/recipes/listing/site/src/components/TourForm.jsx
+++ b/recipes/listing/site/src/components/TourForm.jsx
@@ -44,22 +44,16 @@ export default function TourForm() {
   };
 
   if (sent) {
-    const chosen = dates.find((d) => d.value === form.date);
     return (
       <section id="tour" className="section" aria-labelledby="tour-h">
         <div className="tour-success" role="status">
           <div className="tour-success__check" aria-hidden="true">
             &#10003;
           </div>
-          <h2 id="tour-h">You're on the calendar, {form.name.split(" ")[0]}.</h2>
-          <p>
-            {agent.name} will confirm your private showing of {property.address}{" "}
-            for <strong>{chosen ? chosen.label : form.date}</strong>,{" "}
-            <strong>{form.time.toLowerCase()}</strong>. Expect a text at{" "}
-            {form.phone || "your number"} within the hour.
-          </p>
+          <h2 id="tour-h">Tour preview complete</h2>
+          <p>Nothing was sent or booked. The selected time is a preview only.</p>
           <button className="btn btn--ghost" onClick={() => setSent(false)}>
-            Request another time
+            Preview another time
           </button>
         </div>
       </section>
@@ -99,6 +93,8 @@ export default function TourForm() {
         </div>
 
         <form className="tour-form" onSubmit={submit} noValidate>
+
+          <p style={{ gridColumn: "1 / -1", flexBasis: "100%" }} data-demo-note="true">Demo form. Nothing is sent or booked.</p>
           <div className="grid-2">
             <label className="field">
               <span className="field__label">Full name</span>
@@ -169,12 +165,9 @@ export default function TourForm() {
             />
           </label>
 
-          <button type="submit" className="btn btn--primary btn--block">
-            Request this showing
-          </button>
+          <button type="submit" className="btn btn--primary btn--block">Preview</button>
           <p className="form-fine">
-            By requesting a tour you agree to be contacted about this property.
-            No spam, ever.
+            Demo only. No showing is requested and no message is sent.
           </p>
         </form>
       </div>
diff --git a/recipes/memorial/meta.json b/recipes/memorial/meta.json
index ae1f163..1d4a05b 100644
--- a/recipes/memorial/meta.json
+++ b/recipes/memorial/meta.json
@@ -4,7 +4,7 @@
   "slug": "memorial",
   "vertical": "Personal & creative",
   "tech": "Plain HTML & CSS",
-  "summary": "A quiet, dignified tribute page — a framed portrait with dates and epitaph, a life story and timeline, a black-and-white photo gallery with a lightbox, service details, and a working memory wall that saves visitors' messages.",
+  "summary": "Remember someone with their story, photographs, and service details.",
   "order": 300,
   "live_url": "https://memorial.view.fast/",
   "setup_questions": [
@@ -23,7 +23,7 @@
     "Photo gallery in a click-to-enlarge lightbox with captions and keyboard nav",
     "Service & celebration cards (service, reception, live stream) with directions",
     "In-lieu-of-flowers donation card",
-    "Memory wall — seeded memories plus a validating form that persists via localStorage",
+    "Family-provided memories and a form connected to a shared destination, or a clearly labelled browser-only preview",
     "Soft footer with a candle motif"
   ],
   "based_on": "A realistic, evergreen example modeled on a common real-world need — the kind of dignified tribute page families build to remember a loved one and share service details."
diff --git a/recipes/memorial/prompt.md b/recipes/memorial/prompt.md
index a41c266..3dbaf4d 100644
--- a/recipes/memorial/prompt.md
+++ b/recipes/memorial/prompt.md
@@ -15,14 +15,14 @@ plain HTML & CSS site (a single `index.html`, no framework and no build step).
 - A **life story** section: flowing prose with a drop cap and one pull-quote, followed by a simple vertical timeline of life milestones.
 - A **photo gallery**: a responsive grid of photographs that open in a click-to-enlarge lightbox with captions, keyboard navigation (arrow keys, Escape), and previous/next buttons.
 - A **service & celebration** block: cards for the memorial service, the reception, and a live-stream note (date, time, address, and a "directions" link each), plus an "in lieu of flowers" donation card.
-- A **memory wall**: a few heartfelt seeded memories, and a form (name + message) that validates, shows a gentle thank-you confirmation, and saves new memories so they appear on the wall and persist on return via `localStorage`.
+- A memory wall with memories supplied by the family. Let visitors save a name and memory on this device with a note beside the form: "Memories saved here stay in this browser. They are not shared with the family or other visitors." Confirm with "Saved in this browser only." Link to a shared guestbook if I provide one.
 - A soft footer with the name, the years, and a single candle motif.
 
 **Design & content notes:**
 
 - Tone is everything: warm and calm, never clinical. Use an ivory/cream base, soft sage green and a muted gold accent, and deep warm-charcoal text. Pair an elegant serif display face (e.g. Cormorant Garamond) for headings with a readable serif (e.g. EB Garamond) for body text.
 - Render the portrait and gallery photographs in soft black-and-white so any source images feel like timeless family archives.
-- Use realistic content based on my answers — never "lorem ipsum". Write the life story, timeline, and seeded memories in a tender, human voice; invent believable details only to fill small gaps.
+- Use only the life details, photographs, quotes, and memories supplied or approved by the family. Leave missing details out. Never invent a memory or life event.
 - Use real images. Pull free photos that fit, e.g. from picsum (`https://picsum.photos/seed/memorial-1/1200/800?grayscale`, varying the seed) or Unsplash (`soft floral arrangement`, `candle warm memorial light`), and add descriptive `alt` text.
 - No build step — a single `index.html` with embedded CSS and a small script. Make the lightbox and the memory-wall form genuinely work; persist memories in `localStorage`.
 - Keep it accessible (semantic HTML, labelled form fields, keyboard support, focus management in the lightbox, good contrast) and respect `prefers-reduced-motion`.
@@ -33,28 +33,12 @@ plain HTML & CSS site (a single `index.html`, no framework and no build step).
 <script src="https://spacefast.com/badge.js" data-example="memorial"></script>
 ```
 
-**When the site is ready, publish it to Spacefast with the direct API — no account, install, or extra instructions needed:**
+**When the site is ready, publish it to Spacefast:**
 
 1. Use `./site` as the publish folder. For no-build projects, put only the finished public files in that dedicated folder. Confirm it has `index.html` at its root and no secrets, source files, `.git`, or `.spacefast` state.
-2. First publish: send every file as multipart form data. This Bash/Zsh block preserves relative paths and works for one file or a whole folder:
-   ```bash
-   PUBLISH_ROOT=./site
-   publish_files=()
-   while IFS= read -r -d "" file; do
-     relative=${file#"$PUBLISH_ROOT"/}
-     publish_files+=(-F "files=@$file;filename=$relative")
-   done < <(find "$PUBLISH_ROOT" -type f -print0)
-   curl -sS "${publish_files[@]}" "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-3. From the `{ "data": ... }` receipt, give me `data.space.liveUrl`, `data.version.immutableUrl`, `data.claim.url`, and `data.claim.expiresAt`. Remind me to claim within 6 hours. Keep `data.claim.token` secret.
-4. Save `data.space.id` and `data.claim.token` locally (for example in an ignored, mode-600 `.spacefast/state.json`). For a quick update, rebuild the `publish_files` array above and publish to the same space:
-   ```bash
-   SPACEFAST_SPACE_ID=<saved-space-id>
-   SPACEFAST_TOKEN=<saved-claim-token-or-access-token>
-   curl -sS -H "Authorization: Bearer $SPACEFAST_TOKEN" \
-     -F "spaceId=$SPACEFAST_SPACE_ID" "${publish_files[@]}" \
-     "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-   If an update after claiming returns `space_claimed_credential_available`, exchange the saved claim token once at `POST https://api.spacefast.com/v1/anonymous-claim/exchange`, save `data.credential.accessToken`, and retry with that access token.
-
-**Optional shortcuts and reference only:** if the `sf` CLI is already installed, `sf publish ./site --wait` does the same job. A zip of the publish folder is also supported, but neither the CLI nor a zip is required. Docs: [direct agent/API publishing](https://spacefast.com/setup) · [files and folders](https://spacefast.com/help/publishing) · [claiming](https://spacefast.com/help/anonymous-publish) · [updates and rollback](https://spacefast.com/help/versions)
+2. Fetch https://spacefast.com/setup.md and follow its current direct API publishing instructions. Check for an existing Space before creating one, and follow the returned upload and polling steps.
+3. Report success only when `data.next.action` is `done` and the intended version is serving. If more work is needed, report the returned next step.
+4. For an anonymous publish, give me `data.claim.message` unchanged. It contains the private preview (`data.claim.url`), the owner's claim link (`data.claim.claimUrl`), and the deadline (`data.claim.expiresAt`). Keep both links private. Never print the separate `data.claim.key`.
+5. Keep `data.space.id` and the returned credential securely for updates to the same Space. Follow the guide for credential recovery after claiming. Keep credentials and `.spacefast` state out of the published files, commits, and logs.
+
+If the `sf` CLI is already installed, `sf publish ./site --wait` follows the same publishing flow. See [publishing](https://spacefast.com/docs/publish/) and [claiming a Space](https://spacefast.com/docs/anonymous-and-claim/).
diff --git a/recipes/memorial/site/index.html b/recipes/memorial/site/index.html
index 99408aa..fba4a27 100644
--- a/recipes/memorial/site/index.html
+++ b/recipes/memorial/site/index.html
@@ -426,6 +426,12 @@
 </style>
 </head>
 <body>
+    <aside
+      aria-label="Example site"
+      style="margin:0;padding:0.75rem 1rem;background:#fff7d6;color:#29221a;font:14px/1.5 system-ui;text-align:center"
+    >
+      Example site with fictional content. Forms are previews. Nothing is sent, booked, signed, or paid.
+    </aside>
 
 <header class="bar">
   <div class="wrap">
@@ -550,9 +556,11 @@ <h2>The Memory Wall</h2>
       </div>
 
       <div class="form-success" id="formSuccess" role="status">
-        Thank you. Your memory has been added to the wall.
+        Your memory is saved in this browser only. It has not been shared with the family or other visitors.
       </div>
 
+      <p data-demo-note="true">Memories saved here stay in this browser. They are not shared with the family or other visitors.</p>
+
       <form class="memory-form reveal" id="memoryForm" novalidate>
         <div class="field">
           <label for="mwName">Your name</label>
@@ -564,7 +572,7 @@ <h2>The Memory Wall</h2>
           <textarea id="mwMessage" name="message" placeholder="A story, a kindness, a moment you carry…"></textarea>
           <p class="err" id="errMessage">Please share a few words.</p>
         </div>
-        <button type="submit" class="btn">Add to the wall</button>
+        <button type="submit" class="btn">Preview</button>
       </form>
 
       <div class="memory-grid reveal" id="memoryGrid"></div>
diff --git a/recipes/menu/meta.json b/recipes/menu/meta.json
index 0da3c5f..41e67b3 100644
--- a/recipes/menu/meta.json
+++ b/recipes/menu/meta.json
@@ -4,7 +4,7 @@
   "slug": "menu",
   "vertical": "Local & small business",
   "tech": "Plain HTML & CSS",
-  "summary": "A single-page site for a neighborhood ramen shop — a photographed menu, the broth story, hours, and a map that makes you hungry on first scroll.",
+  "summary": "Show your restaurant menu, hours, and location on one page.",
   "order": 5,
   "live_url": "https://menu.view.fast/",
   "setup_questions": [
diff --git a/recipes/menu/prompt.md b/recipes/menu/prompt.md
index 02e0c32..91e86b5 100644
--- a/recipes/menu/prompt.md
+++ b/recipes/menu/prompt.md
@@ -34,8 +34,7 @@ with a touch of vanilla JavaScript (no build step, no framework — just an
   persimmon-red accent and a soft lantern-gold. An elegant serif (e.g. Shippori
   Mincho) for headings and the brand, a clean sans (e.g. Inter) for body. A small
   kanji/lantern flourish is welcome.
-- Use realistic content based on my answers — never "lorem ipsum". Invent believable
-  dish descriptions, a chef backstory, and plausible hours.
+- Use the dishes, prices, opening hours, and restaurant history I provide. Ask for missing business details.
 - Use real images. Pull free photos that fit, e.g.
   `https://picsum.photos/seed/ramen-1/1200/800` (vary the seed) or Pexels, with
   descriptive `alt` text. Good search terms: tonkotsu ramen bowl chashu soft egg
@@ -53,28 +52,12 @@ with a touch of vanilla JavaScript (no build step, no framework — just an
 <script src="https://spacefast.com/badge.js" data-example="menu"></script>
 ```
 
-**When the site is ready, publish it to Spacefast with the direct API — no account, install, or extra instructions needed:**
+**When the site is ready, publish it to Spacefast:**
 
 1. Use `./site` as the publish folder. For no-build projects, put only the finished public files in that dedicated folder. Confirm it has `index.html` at its root and no secrets, source files, `.git`, or `.spacefast` state.
-2. First publish: send every file as multipart form data. This Bash/Zsh block preserves relative paths and works for one file or a whole folder:
-   ```bash
-   PUBLISH_ROOT=./site
-   publish_files=()
-   while IFS= read -r -d "" file; do
-     relative=${file#"$PUBLISH_ROOT"/}
-     publish_files+=(-F "files=@$file;filename=$relative")
-   done < <(find "$PUBLISH_ROOT" -type f -print0)
-   curl -sS "${publish_files[@]}" "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-3. From the `{ "data": ... }` receipt, give me `data.space.liveUrl`, `data.version.immutableUrl`, `data.claim.url`, and `data.claim.expiresAt`. Remind me to claim within 6 hours. Keep `data.claim.token` secret.
-4. Save `data.space.id` and `data.claim.token` locally (for example in an ignored, mode-600 `.spacefast/state.json`). For a quick update, rebuild the `publish_files` array above and publish to the same space:
-   ```bash
-   SPACEFAST_SPACE_ID=<saved-space-id>
-   SPACEFAST_TOKEN=<saved-claim-token-or-access-token>
-   curl -sS -H "Authorization: Bearer $SPACEFAST_TOKEN" \
-     -F "spaceId=$SPACEFAST_SPACE_ID" "${publish_files[@]}" \
-     "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-   If an update after claiming returns `space_claimed_credential_available`, exchange the saved claim token once at `POST https://api.spacefast.com/v1/anonymous-claim/exchange`, save `data.credential.accessToken`, and retry with that access token.
+2. Fetch https://spacefast.com/setup.md and follow its current direct API publishing instructions. Check for an existing Space before creating one, and follow the returned upload and polling steps.
+3. Report success only when `data.next.action` is `done` and the intended version is serving. If more work is needed, report the returned next step.
+4. For an anonymous publish, give me `data.claim.message` unchanged. It contains the private preview (`data.claim.url`), the owner's claim link (`data.claim.claimUrl`), and the deadline (`data.claim.expiresAt`). Keep both links private. Never print the separate `data.claim.key`.
+5. Keep `data.space.id` and the returned credential securely for updates to the same Space. Follow the guide for credential recovery after claiming. Keep credentials and `.spacefast` state out of the published files, commits, and logs.
 
-**Optional shortcuts and reference only:** if the `sf` CLI is already installed, `sf publish ./site --wait` does the same job. A zip of the publish folder is also supported, but neither the CLI nor a zip is required. Docs: [direct agent/API publishing](https://spacefast.com/setup) · [files and folders](https://spacefast.com/help/publishing) · [claiming](https://spacefast.com/help/anonymous-publish) · [updates and rollback](https://spacefast.com/help/versions)
+If the `sf` CLI is already installed, `sf publish ./site --wait` follows the same publishing flow. See [publishing](https://spacefast.com/docs/publish/) and [claiming a Space](https://spacefast.com/docs/anonymous-and-claim/).
diff --git a/recipes/menu/site/index.html b/recipes/menu/site/index.html
index ced2216..a0539e3 100644
--- a/recipes/menu/site/index.html
+++ b/recipes/menu/site/index.html
@@ -40,6 +40,12 @@
   </script>
 </head>
 <body>
+    <aside
+      aria-label="Example site"
+      style="margin:0;padding:0.75rem 1rem;background:#fff7d6;color:#29221a;font:14px/1.5 system-ui;text-align:center"
+    >
+      Example site with fictional content. Numbers, quotes, and business details are sample content.
+    </aside>
 
   <header class="site-header" id="header">
     <div class="wrap">
diff --git a/recipes/newsletter/meta.json b/recipes/newsletter/meta.json
index e2b50b3..f282392 100644
--- a/recipes/newsletter/meta.json
+++ b/recipes/newsletter/meta.json
@@ -4,7 +4,7 @@
   "slug": "newsletter",
   "vertical": "Personal & creative",
   "tech": "Plain HTML & CSS",
-  "summary": "A typographic home and archive for a curated weekly newsletter — featured issue, a full back catalogue, readable issue pages, and a working subscribe form.",
+  "summary": "Give your newsletter a home with a featured issue and a readable archive.",
   "order": 7,
   "live_url": "https://newsletter.view.fast/",
   "setup_questions": [
diff --git a/recipes/newsletter/prompt.md b/recipes/newsletter/prompt.md
index 5c84c3c..a1a4586 100644
--- a/recipes/newsletter/prompt.md
+++ b/recipes/newsletter/prompt.md
@@ -39,9 +39,7 @@ web pages with a prominent subscribe form.
   sample issue, issue headers, and an author portrait — all with descriptive `alt`
   text matching: minimal desk workspace flatlay, stack of design books on a table,
   abstract textured paper background, author portrait at desk window light.
-- The subscribe form should work client-side: validate the email and show a friendly,
-  personalised "You're on the list" success state (no backend). Persist the
-  subscriber in `localStorage` so returning readers see the confirmed state.
+- A subscribe form with a labelled email field and inline validation. For any form that sends information, ask for my form endpoint or hosted signup URL. Use the supplied destination and show success only after it confirms receipt. A link to another service does not confirm completion. Without a destination, label the form "Demo only" beside its fields, label its button "Preview", and say "Preview complete. Nothing was sent." Never treat `localStorage` as delivery or store personal form data there.
 - Keep it accessible (semantic HTML, a skip link, labelled fields, keyboard support,
   good contrast).
 
@@ -51,28 +49,12 @@ web pages with a prominent subscribe form.
 <script src="https://spacefast.com/badge.js" data-example="newsletter"></script>
 ```
 
-**When the site is ready, publish it to Spacefast with the direct API — no account, install, or extra instructions needed:**
+**When the site is ready, publish it to Spacefast:**
 
 1. Use `./site` as the publish folder. For no-build projects, put only the finished public files in that dedicated folder. Confirm it has `index.html` at its root and no secrets, source files, `.git`, or `.spacefast` state.
-2. First publish: send every file as multipart form data. This Bash/Zsh block preserves relative paths and works for one file or a whole folder:
-   ```bash
-   PUBLISH_ROOT=./site
-   publish_files=()
-   while IFS= read -r -d "" file; do
-     relative=${file#"$PUBLISH_ROOT"/}
-     publish_files+=(-F "files=@$file;filename=$relative")
-   done < <(find "$PUBLISH_ROOT" -type f -print0)
-   curl -sS "${publish_files[@]}" "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-3. From the `{ "data": ... }` receipt, give me `data.space.liveUrl`, `data.version.immutableUrl`, `data.claim.url`, and `data.claim.expiresAt`. Remind me to claim within 6 hours. Keep `data.claim.token` secret.
-4. Save `data.space.id` and `data.claim.token` locally (for example in an ignored, mode-600 `.spacefast/state.json`). For a quick update, rebuild the `publish_files` array above and publish to the same space:
-   ```bash
-   SPACEFAST_SPACE_ID=<saved-space-id>
-   SPACEFAST_TOKEN=<saved-claim-token-or-access-token>
-   curl -sS -H "Authorization: Bearer $SPACEFAST_TOKEN" \
-     -F "spaceId=$SPACEFAST_SPACE_ID" "${publish_files[@]}" \
-     "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-   If an update after claiming returns `space_claimed_credential_available`, exchange the saved claim token once at `POST https://api.spacefast.com/v1/anonymous-claim/exchange`, save `data.credential.accessToken`, and retry with that access token.
+2. Fetch https://spacefast.com/setup.md and follow its current direct API publishing instructions. Check for an existing Space before creating one, and follow the returned upload and polling steps.
+3. Report success only when `data.next.action` is `done` and the intended version is serving. If more work is needed, report the returned next step.
+4. For an anonymous publish, give me `data.claim.message` unchanged. It contains the private preview (`data.claim.url`), the owner's claim link (`data.claim.claimUrl`), and the deadline (`data.claim.expiresAt`). Keep both links private. Never print the separate `data.claim.key`.
+5. Keep `data.space.id` and the returned credential securely for updates to the same Space. Follow the guide for credential recovery after claiming. Keep credentials and `.spacefast` state out of the published files, commits, and logs.
 
-**Optional shortcuts and reference only:** if the `sf` CLI is already installed, `sf publish ./site --wait` does the same job. A zip of the publish folder is also supported, but neither the CLI nor a zip is required. Docs: [direct agent/API publishing](https://spacefast.com/setup) · [files and folders](https://spacefast.com/help/publishing) · [claiming](https://spacefast.com/help/anonymous-publish) · [updates and rollback](https://spacefast.com/help/versions)
+If the `sf` CLI is already installed, `sf publish ./site --wait` follows the same publishing flow. See [publishing](https://spacefast.com/docs/publish/) and [claiming a Space](https://spacefast.com/docs/anonymous-and-claim/).
diff --git a/recipes/newsletter/site/about.html b/recipes/newsletter/site/about.html
index bf36ec1..5b31cd5 100644
--- a/recipes/newsletter/site/about.html
+++ b/recipes/newsletter/site/about.html
@@ -11,6 +11,12 @@
   <link rel="stylesheet" href="styles.css" />
 </head>
 <body>
+    <aside
+      aria-label="Example site"
+      style="margin:0;padding:0.75rem 1rem;background:#fff7d6;color:#29221a;font:14px/1.5 system-ui;text-align:center"
+    >
+      Example site with fictional content. Forms are previews.
+    </aside>
   <a class="skip-link" href="#main">Skip to content</a>
 
   <header class="masthead">
@@ -84,18 +90,19 @@ <h2>Why it’s free</h2>
         <div class="subscribe subscribe--lg">
           <h2>Read along with me</h2>
           <p>If any of that sounds like your kind of thing, the next issue is yours.</p>
+          <p data-demo-note="true">Demo signup. No subscription is created and no email is sent.</p>
           <form class="subscribe__form" novalidate>
             <div class="subscribe__field">
               <label for="email-about">Your email</label>
               <input id="email-about" type="email" name="email" required
                      autocomplete="email" placeholder="you@studio.com" />
             </div>
-            <button class="btn" type="submit">Subscribe</button>
+            <button class="btn" type="submit">Preview</button>
           </form>
           <p class="subscribe__meta">Free, weekly, one-click unsubscribe.</p>
           <p class="subscribe__ok">
             <span class="check" aria-hidden="true">✓</span>
-            <span>Lovely to have you, <strong class="subscribe__ok-name">friend</strong>. See you Thursday.</span>
+            <span>Preview complete. Nothing was sent.</span>
           </p>
         </div>
       </div>
diff --git a/recipes/newsletter/site/archive.html b/recipes/newsletter/site/archive.html
index 8156c05..1852783 100644
--- a/recipes/newsletter/site/archive.html
+++ b/recipes/newsletter/site/archive.html
@@ -11,6 +11,12 @@
   <link rel="stylesheet" href="styles.css" />
 </head>
 <body>
+    <aside
+      aria-label="Example site"
+      style="margin:0;padding:0.75rem 1rem;background:#fff7d6;color:#29221a;font:14px/1.5 system-ui;text-align:center"
+    >
+      Example site with fictional content. Forms are previews.
+    </aside>
   <a class="skip-link" href="#main">Skip to content</a>
 
   <header class="masthead">
@@ -183,13 +189,14 @@ <h1>Eighty-seven Thursdays.</h1>
         <div class="subscribe subscribe--lg">
           <h2>Don’t want to keep checking back?</h2>
           <p>Let the archive come to you. One issue, every Thursday.</p>
+          <p data-demo-note="true">Demo signup. No subscription is created and no email is sent.</p>
           <form class="subscribe__form" novalidate>
             <div class="subscribe__field">
               <label for="email-arch">Your email</label>
               <input id="email-arch" type="email" name="email" required
                      autocomplete="email" placeholder="you@studio.com" />
             </div>
-            <button class="btn" type="submit">Subscribe</button>
+            <button class="btn" type="submit">Preview</button>
           </form>
           <p class="subscribe__meta">Free. Weekly. One-click unsubscribe.</p>
           <p class="subscribe__ok">
diff --git a/recipes/newsletter/site/index.html b/recipes/newsletter/site/index.html
index e6b8ef1..ed2e411 100644
--- a/recipes/newsletter/site/index.html
+++ b/recipes/newsletter/site/index.html
@@ -14,6 +14,12 @@
   <link rel="stylesheet" href="styles.css" />
 </head>
 <body>
+    <aside
+      aria-label="Example site"
+      style="margin:0;padding:0.75rem 1rem;background:#fff7d6;color:#29221a;font:14px/1.5 system-ui;text-align:center"
+    >
+      Example site with fictional content. Forms are previews.
+    </aside>
   <a class="skip-link" href="#main">Skip to content</a>
 
   <header class="masthead">
@@ -45,18 +51,19 @@ <h1>A weekly <em>trim</em> of design, craft &amp; the slow web.</h1>
         <div class="subscribe" id="join">
           <h2>Get the next issue</h2>
           <p>Free, weekly, and easy to leave. Join 6,400 designers, writers, and tinkerers.</p>
+          <p data-demo-note="true">Demo signup. No subscription is created and no email is sent.</p>
           <form class="subscribe__form" novalidate data-greet>
             <div class="subscribe__field">
               <label for="email-hero">Your email</label>
               <input id="email-hero" type="email" name="email" required
                      autocomplete="email" placeholder="you@studio.com" />
             </div>
-            <button class="btn" type="submit">Subscribe</button>
+            <button class="btn" type="submit">Preview</button>
           </form>
           <p class="subscribe__meta">One email a week. Unsubscribe in one click — no hard feelings.</p>
           <p class="subscribe__ok">
             <span class="check" aria-hidden="true">✓</span>
-            <span>You're on the list, <strong class="subscribe__ok-name">friend</strong>. Issue 88 lands Thursday.</span>
+            <span>Preview complete. Nothing was sent.</span>
           </p>
         </div>
       </div>
@@ -132,18 +139,19 @@ <h2>Three things, then you’re done</h2>
         <div class="subscribe subscribe--lg">
           <h2>Start with Thursday’s issue</h2>
           <p>It takes four minutes to read and one click to leave. That’s the whole pitch.</p>
+          <p data-demo-note="true">Demo signup. No subscription is created and no email is sent.</p>
           <form class="subscribe__form" novalidate>
             <div class="subscribe__field">
               <label for="email-foot">Your email</label>
               <input id="email-foot" type="email" name="email" required
                      autocomplete="email" placeholder="you@studio.com" />
             </div>
-            <button class="btn" type="submit">Subscribe free</button>
+            <button class="btn" type="submit">Preview</button>
           </form>
           <p class="subscribe__meta">No spam, ever. Read the latest issue first if you’re unsure.</p>
           <p class="subscribe__ok">
             <span class="check" aria-hidden="true">✓</span>
-            <span>Welcome aboard, <strong class="subscribe__ok-name">friend</strong>. Check your inbox to confirm.</span>
+            <span>Preview complete. Nothing was sent.</span>
           </p>
         </div>
       </div>
diff --git a/recipes/newsletter/site/issues/issue-85.html b/recipes/newsletter/site/issues/issue-85.html
index 1de409c..5c71636 100644
--- a/recipes/newsletter/site/issues/issue-85.html
+++ b/recipes/newsletter/site/issues/issue-85.html
@@ -11,6 +11,12 @@
   <link rel="stylesheet" href="../styles.css" />
 </head>
 <body>
+    <aside
+      aria-label="Example site"
+      style="margin:0;padding:0.75rem 1rem;background:#fff7d6;color:#29221a;font:14px/1.5 system-ui;text-align:center"
+    >
+      Example site with fictional content. Forms are previews.
+    </aside>
   <a class="skip-link" href="#main">Skip to content</a>
 
   <header class="masthead">
@@ -139,18 +145,19 @@ <h3>Slipbox</h3>
         <div class="subscribe subscribe--lg">
           <h2>Get the next one in your inbox</h2>
           <p>One issue, every Thursday. Free, and easy to leave.</p>
+          <p data-demo-note="true">Demo signup. No subscription is created and no email is sent.</p>
           <form class="subscribe__form" novalidate>
             <div class="subscribe__field">
               <label for="email-i85">Your email</label>
               <input id="email-i85" type="email" name="email" required
                      autocomplete="email" placeholder="you@studio.com" />
             </div>
-            <button class="btn" type="submit">Subscribe</button>
+            <button class="btn" type="submit">Preview</button>
           </form>
           <p class="subscribe__meta">Free, weekly, one-click out.</p>
           <p class="subscribe__ok">
             <span class="check" aria-hidden="true">✓</span>
-            <span>You’re in, <strong class="subscribe__ok-name">friend</strong>. See you Thursday.</span>
+            <span>Preview complete. Nothing was sent.</span>
           </p>
         </div>
       </div>
diff --git a/recipes/newsletter/site/issues/issue-86.html b/recipes/newsletter/site/issues/issue-86.html
index 00eba8b..8ab8cf4 100644
--- a/recipes/newsletter/site/issues/issue-86.html
+++ b/recipes/newsletter/site/issues/issue-86.html
@@ -11,6 +11,12 @@
   <link rel="stylesheet" href="../styles.css" />
 </head>
 <body>
+    <aside
+      aria-label="Example site"
+      style="margin:0;padding:0.75rem 1rem;background:#fff7d6;color:#29221a;font:14px/1.5 system-ui;text-align:center"
+    >
+      Example site with fictional content. Forms are previews.
+    </aside>
   <a class="skip-link" href="#main">Skip to content</a>
 
   <header class="masthead">
@@ -136,18 +142,19 @@ <h3>Smoothie</h3>
         <div class="subscribe subscribe--lg">
           <h2>Get the next one in your inbox</h2>
           <p>One issue, every Thursday. Free, and easy to leave.</p>
+          <p data-demo-note="true">Demo signup. No subscription is created and no email is sent.</p>
           <form class="subscribe__form" novalidate>
             <div class="subscribe__field">
               <label for="email-i86">Your email</label>
               <input id="email-i86" type="email" name="email" required
                      autocomplete="email" placeholder="you@studio.com" />
             </div>
-            <button class="btn" type="submit">Subscribe</button>
+            <button class="btn" type="submit">Preview</button>
           </form>
           <p class="subscribe__meta">Free, weekly, one-click out.</p>
           <p class="subscribe__ok">
             <span class="check" aria-hidden="true">✓</span>
-            <span>You’re in, <strong class="subscribe__ok-name">friend</strong>. See you Thursday.</span>
+            <span>Preview complete. Nothing was sent.</span>
           </p>
         </div>
       </div>
diff --git a/recipes/newsletter/site/issues/issue-87.html b/recipes/newsletter/site/issues/issue-87.html
index bf8eab7..1ac8398 100644
--- a/recipes/newsletter/site/issues/issue-87.html
+++ b/recipes/newsletter/site/issues/issue-87.html
@@ -11,6 +11,12 @@
   <link rel="stylesheet" href="../styles.css" />
 </head>
 <body>
+    <aside
+      aria-label="Example site"
+      style="margin:0;padding:0.75rem 1rem;background:#fff7d6;color:#29221a;font:14px/1.5 system-ui;text-align:center"
+    >
+      Example site with fictional content. Forms are previews.
+    </aside>
   <a class="skip-link" href="#main">Skip to content</a>
 
   <header class="masthead">
@@ -139,18 +145,19 @@ <h3>Kept</h3>
         <div class="subscribe subscribe--lg">
           <h2>Get the next one in your inbox</h2>
           <p>You just read a full issue. The next lands Thursday — want it delivered?</p>
+          <p data-demo-note="true">Demo signup. No subscription is created and no email is sent.</p>
           <form class="subscribe__form" novalidate>
             <div class="subscribe__field">
               <label for="email-i87">Your email</label>
               <input id="email-i87" type="email" name="email" required
                      autocomplete="email" placeholder="you@studio.com" />
             </div>
-            <button class="btn" type="submit">Subscribe</button>
+            <button class="btn" type="submit">Preview</button>
           </form>
           <p class="subscribe__meta">Free, weekly, one-click out.</p>
           <p class="subscribe__ok">
             <span class="check" aria-hidden="true">✓</span>
-            <span>You’re in, <strong class="subscribe__ok-name">friend</strong>. See you Thursday.</span>
+            <span>Preview complete. Nothing was sent.</span>
           </p>
         </div>
       </div>
diff --git a/recipes/newsletter/site/subscribe.html b/recipes/newsletter/site/subscribe.html
index 69933d9..9072be1 100644
--- a/recipes/newsletter/site/subscribe.html
+++ b/recipes/newsletter/site/subscribe.html
@@ -11,6 +11,12 @@
   <link rel="stylesheet" href="styles.css" />
 </head>
 <body>
+    <aside
+      aria-label="Example site"
+      style="margin:0;padding:0.75rem 1rem;background:#fff7d6;color:#29221a;font:14px/1.5 system-ui;text-align:center"
+    >
+      Example site with fictional content. Forms are previews.
+    </aside>
   <a class="skip-link" href="#main">Skip to content</a>
 
   <header class="masthead">
@@ -41,18 +47,19 @@ <h1 style="font-size:clamp(2.4rem,6.5vw,3.8rem)">Join 6,400 people who read on T
         <div class="subscribe subscribe--lg" id="join">
           <h2>Subscribe to Offcuts</h2>
           <p>No welcome sequence, no upsell, no “premium tier.” Just the next issue.</p>
+          <p data-demo-note="true">Demo signup. No subscription is created and no email is sent.</p>
           <form class="subscribe__form" novalidate>
             <div class="subscribe__field">
               <label for="email-sub">Your email address</label>
               <input id="email-sub" type="email" name="email" required
                      autocomplete="email" placeholder="you@studio.com" />
             </div>
-            <button class="btn" type="submit">Subscribe free</button>
+            <button class="btn" type="submit">Preview</button>
           </form>
           <p class="subscribe__meta">By subscribing you agree to receive one email a week. Unsubscribe any time — it’s one click and I won’t email you again.</p>
           <p class="subscribe__ok">
             <span class="check" aria-hidden="true">✓</span>
-            <span>You’re on the list, <strong class="subscribe__ok-name">friend</strong>. Issue 88 lands this Thursday — check your inbox to confirm.</span>
+            <span>Preview complete. Nothing was sent.</span>
           </p>
         </div>
       </div>
diff --git a/recipes/notes/meta.json b/recipes/notes/meta.json
index 277fa1f..7f331cc 100644
--- a/recipes/notes/meta.json
+++ b/recipes/notes/meta.json
@@ -4,7 +4,7 @@
   "slug": "notes",
   "vertical": "Personal & creative",
   "tech": "Astro",
-  "summary": "A warm, greenhouse-themed digital garden built with Astro — Markdown notes that link with [[wiki links]], an automatic backlinks panel, a build-time link graph, instant search, and planted/growing/evergreen growth tags.",
+  "summary": "Publish linked notes with search, backlinks, and a graph of related ideas.",
   "order": 300,
   "live_url": "https://notes.view.fast/",
   "setup_questions": [
diff --git a/recipes/notes/prompt.md b/recipes/notes/prompt.md
index baf46d5..f3e1d21 100644
--- a/recipes/notes/prompt.md
+++ b/recipes/notes/prompt.md
@@ -57,28 +57,12 @@ content collections, `astro build` to static HTML — no server, no database).
 <script src="https://spacefast.com/badge.js" data-example="notes"></script>
 ```
 
-**When the site is ready, publish it to Spacefast with the direct API — no account, install, or extra instructions needed:**
+**When the site is ready, publish it to Spacefast:**
 
 1. Use `./dist` as the publish folder. For no-build projects, put only the finished public files in that dedicated folder. Confirm it has `index.html` at its root and no secrets, source files, `.git`, or `.spacefast` state.
-2. First publish: send every file as multipart form data. This Bash/Zsh block preserves relative paths and works for one file or a whole folder:
-   ```bash
-   PUBLISH_ROOT=./dist
-   publish_files=()
-   while IFS= read -r -d "" file; do
-     relative=${file#"$PUBLISH_ROOT"/}
-     publish_files+=(-F "files=@$file;filename=$relative")
-   done < <(find "$PUBLISH_ROOT" -type f -print0)
-   curl -sS "${publish_files[@]}" "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-3. From the `{ "data": ... }` receipt, give me `data.space.liveUrl`, `data.version.immutableUrl`, `data.claim.url`, and `data.claim.expiresAt`. Remind me to claim within 6 hours. Keep `data.claim.token` secret.
-4. Save `data.space.id` and `data.claim.token` locally (for example in an ignored, mode-600 `.spacefast/state.json`). For a quick update, rebuild the `publish_files` array above and publish to the same space:
-   ```bash
-   SPACEFAST_SPACE_ID=<saved-space-id>
-   SPACEFAST_TOKEN=<saved-claim-token-or-access-token>
-   curl -sS -H "Authorization: Bearer $SPACEFAST_TOKEN" \
-     -F "spaceId=$SPACEFAST_SPACE_ID" "${publish_files[@]}" \
-     "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-   If an update after claiming returns `space_claimed_credential_available`, exchange the saved claim token once at `POST https://api.spacefast.com/v1/anonymous-claim/exchange`, save `data.credential.accessToken`, and retry with that access token.
+2. Fetch https://spacefast.com/setup.md and follow its current direct API publishing instructions. Check for an existing Space before creating one, and follow the returned upload and polling steps.
+3. Report success only when `data.next.action` is `done` and the intended version is serving. If more work is needed, report the returned next step.
+4. For an anonymous publish, give me `data.claim.message` unchanged. It contains the private preview (`data.claim.url`), the owner's claim link (`data.claim.claimUrl`), and the deadline (`data.claim.expiresAt`). Keep both links private. Never print the separate `data.claim.key`.
+5. Keep `data.space.id` and the returned credential securely for updates to the same Space. Follow the guide for credential recovery after claiming. Keep credentials and `.spacefast` state out of the published files, commits, and logs.
 
-**Optional shortcuts and reference only:** if the `sf` CLI is already installed, `sf publish ./dist --wait` does the same job. A zip of the publish folder is also supported, but neither the CLI nor a zip is required. Docs: [direct agent/API publishing](https://spacefast.com/setup) · [files and folders](https://spacefast.com/help/publishing) · [claiming](https://spacefast.com/help/anonymous-publish) · [updates and rollback](https://spacefast.com/help/versions)
+If the `sf` CLI is already installed, `sf publish ./dist --wait` follows the same publishing flow. See [publishing](https://spacefast.com/docs/publish/) and [claiming a Space](https://spacefast.com/docs/anonymous-and-claim/).
diff --git a/recipes/party/meta.json b/recipes/party/meta.json
index 59ad46f..93675ea 100644
--- a/recipes/party/meta.json
+++ b/recipes/party/meta.json
@@ -4,7 +4,7 @@
   "slug": "party",
   "vertical": "Personal & creative",
   "tech": "Astro",
-  "summary": "A themed birthday-party invite with a live countdown, an embedded map and directions, a dress-code callout, and a validating RSVP form with guest count, a conditional +1, dietary needs, and a \"can't make it\" path.",
+  "summary": "Share party details, directions, and what guests need to know.",
   "order": 300,
   "live_url": "https://party.view.fast/",
   "setup_questions": [
diff --git a/recipes/party/prompt.md b/recipes/party/prompt.md
index 32cda5a..a3135f7 100644
--- a/recipes/party/prompt.md
+++ b/recipes/party/prompt.md
@@ -17,7 +17,7 @@ just `astro build` to a `dist/` folder).
 - A **details** section: the dress code shown front and centre, plus a tidy card grid for the practical stuff (food, drinks, gifts, weather plan) and a short personal note from the host.
 - A **run-of-show timeline**: what happens when — doors, toast, dinner, cake, dancing, last song.
 - A **map + directions** block: an embedded Google Map of the venue, an "open in Maps" button, and written directions (transit, parking/rideshare, how to find the door).
-- A working **RSVP form** with: name + email (validated), an accept/decline choice, and — when accepting — guest count, a +1 name field that appears only when bringing someone, a dietary preference, and a song request. When declining, show a **"can't make it" path** with a box to leave the host a birthday note. On submit, show a friendly, personalized confirmation and remember the reply on return via `localStorage`.
+- An RSVP form with name, email, accept or decline, guest count, an optional guest name, dietary needs, and a song request. Let declining guests leave the host a note. For any form that sends information, ask for my form endpoint or hosted signup URL. Use the supplied destination and show success only after it confirms receipt. A link to another service does not confirm completion. Without a destination, label the form "Demo only" beside its fields, label its button "Preview", and say "Preview complete. Nothing was sent." Never treat `localStorage` as delivery or store personal form data there.
 
 **Design & content notes:**
 
@@ -33,28 +33,12 @@ just `astro build` to a `dist/` folder).
 <script src="https://spacefast.com/badge.js" data-example="party"></script>
 ```
 
-**When the site is ready, publish it to Spacefast with the direct API — no account, install, or extra instructions needed:**
+**When the site is ready, publish it to Spacefast:**
 
 1. Use `./dist` as the publish folder. For no-build projects, put only the finished public files in that dedicated folder. Confirm it has `index.html` at its root and no secrets, source files, `.git`, or `.spacefast` state.
-2. First publish: send every file as multipart form data. This Bash/Zsh block preserves relative paths and works for one file or a whole folder:
-   ```bash
-   PUBLISH_ROOT=./dist
-   publish_files=()
-   while IFS= read -r -d "" file; do
-     relative=${file#"$PUBLISH_ROOT"/}
-     publish_files+=(-F "files=@$file;filename=$relative")
-   done < <(find "$PUBLISH_ROOT" -type f -print0)
-   curl -sS "${publish_files[@]}" "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-3. From the `{ "data": ... }` receipt, give me `data.space.liveUrl`, `data.version.immutableUrl`, `data.claim.url`, and `data.claim.expiresAt`. Remind me to claim within 6 hours. Keep `data.claim.token` secret.
-4. Save `data.space.id` and `data.claim.token` locally (for example in an ignored, mode-600 `.spacefast/state.json`). For a quick update, rebuild the `publish_files` array above and publish to the same space:
-   ```bash
-   SPACEFAST_SPACE_ID=<saved-space-id>
-   SPACEFAST_TOKEN=<saved-claim-token-or-access-token>
-   curl -sS -H "Authorization: Bearer $SPACEFAST_TOKEN" \
-     -F "spaceId=$SPACEFAST_SPACE_ID" "${publish_files[@]}" \
-     "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-   If an update after claiming returns `space_claimed_credential_available`, exchange the saved claim token once at `POST https://api.spacefast.com/v1/anonymous-claim/exchange`, save `data.credential.accessToken`, and retry with that access token.
-
-**Optional shortcuts and reference only:** if the `sf` CLI is already installed, `sf publish ./dist --wait` does the same job. A zip of the publish folder is also supported, but neither the CLI nor a zip is required. Docs: [direct agent/API publishing](https://spacefast.com/setup) · [files and folders](https://spacefast.com/help/publishing) · [claiming](https://spacefast.com/help/anonymous-publish) · [updates and rollback](https://spacefast.com/help/versions)
+2. Fetch https://spacefast.com/setup.md and follow its current direct API publishing instructions. Check for an existing Space before creating one, and follow the returned upload and polling steps.
+3. Report success only when `data.next.action` is `done` and the intended version is serving. If more work is needed, report the returned next step.
+4. For an anonymous publish, give me `data.claim.message` unchanged. It contains the private preview (`data.claim.url`), the owner's claim link (`data.claim.claimUrl`), and the deadline (`data.claim.expiresAt`). Keep both links private. Never print the separate `data.claim.key`.
+5. Keep `data.space.id` and the returned credential securely for updates to the same Space. Follow the guide for credential recovery after claiming. Keep credentials and `.spacefast` state out of the published files, commits, and logs.
+
+If the `sf` CLI is already installed, `sf publish ./dist --wait` follows the same publishing flow. See [publishing](https://spacefast.com/docs/publish/) and [claiming a Space](https://spacefast.com/docs/anonymous-and-claim/).
diff --git a/recipes/party/site/src/components/Rsvp.astro b/recipes/party/site/src/components/Rsvp.astro
index be2a60f..502b5f4 100644
--- a/recipes/party/site/src/components/Rsvp.astro
+++ b/recipes/party/site/src/components/Rsvp.astro
@@ -13,6 +13,7 @@ import { party, meals } from '../data/party';
   </div>
 
   <div class="wrap rsvp">
+    <p data-demo-note="true">Demo RSVP. Nothing is sent to the hosts.</p>
     <form class="rsvp__form" data-rsvp novalidate>
       <div class="field">
         <label for="rsvp-name">Your name <span aria-hidden="true">*</span></label>
@@ -86,12 +87,12 @@ import { party, meals } from '../data/party';
         </div>
       </div>
 
-      <button class="btn rsvp__submit" type="submit">Send my reply</button>
+      <button class="btn rsvp__submit" type="submit">Preview</button>
     </form>
 
     <div class="rsvp__success" data-success hidden role="status" aria-live="polite">
       <div class="rsvp__success-mark" aria-hidden="true">✓</div>
-      <h3 data-success-title>You're on the list!</h3>
+      <h3 data-success-title>RSVP preview complete</h3>
       <p data-success-body></p>
       <button class="btn btn--ghost" type="button" data-reset>Change my reply</button>
     </div>
@@ -305,27 +306,12 @@ import { party, meals } from '../data/party';
 
   const isEmail = (v: string) => /^[^\s@]+@[^\s@]+\.[^\s@]+$/.test(v);
 
-  const renderSuccess = (d: Record<string, string>) => {
-    const first = (d.name || '').split(' ')[0] || 'friend';
-    const accepting = d.attendance === 'accept';
+  const renderSuccess = () => {
     if (successTitle) {
-      successTitle.textContent = accepting
-        ? `See you there, ${first}! 🎉`
-        : `We'll miss you, ${first} 💔`;
+      successTitle.textContent = 'RSVP preview complete';
     }
     if (successBody) {
-      if (accepting) {
-        const count =
-          d.guests === '1' ? 'just you' : `${d.guests} of you${d.plusone ? ` (hi, ${d.plusone}!)` : ''}`;
-        successBody.textContent =
-          `You're down for ${count}. ` +
-          (d.song ? `"${d.song}" is going on the playlist. ` : '') +
-          `We've emailed the address and door details to ${d.email}.`;
-      } else {
-        successBody.textContent =
-          (d.message ? `Thank you for the note — it means a lot. ` : `Totally understood. `) +
-          `We'll raise a glass to you and send photos to ${d.email}.`;
-      }
+      successBody.textContent = 'Preview complete. Nothing was sent.';
     }
     form?.setAttribute('hidden', '');
     success?.removeAttribute('hidden');
@@ -368,7 +354,7 @@ import { party, meals } from '../data/party';
     } catch {
       /* private mode — no problem, the reply still shows */
     }
-    renderSuccess(reply);
+    renderSuccess();
     success?.scrollIntoView({ behavior: 'smooth', block: 'center' });
   });
 
@@ -381,7 +367,7 @@ import { party, meals } from '../data/party';
   // If they already replied on this device, greet them with their saved answer.
   try {
     const saved = localStorage.getItem(STORE_KEY);
-    if (saved) renderSuccess(JSON.parse(saved));
+    if (saved) renderSuccess();
   } catch {
     /* ignore */
   }
diff --git a/recipes/party/site/src/layouts/Layout.astro b/recipes/party/site/src/layouts/Layout.astro
index ad4c187..51a1d9b 100644
--- a/recipes/party/site/src/layouts/Layout.astro
+++ b/recipes/party/site/src/layouts/Layout.astro
@@ -35,6 +35,12 @@ const { title, description } = Astro.props;
     />
   </head>
   <body>
+    <aside
+      aria-label="Example site"
+      style="margin:0;padding:0.75rem 1rem;background:#fff7d6;color:#29221a;font:14px/1.5 system-ui;text-align:center"
+    >
+      Example site with fictional content. Forms are previews.
+    </aside>
     <slot />
     <script src="https://spacefast.com/badge.js" data-example="party"></script>
   </body>
diff --git a/recipes/photos/meta.json b/recipes/photos/meta.json
index 2118b71..b0cbd9c 100644
--- a/recipes/photos/meta.json
+++ b/recipes/photos/meta.json
@@ -4,7 +4,7 @@
   "slug": "photos",
   "vertical": "Personal & creative",
   "tech": "Astro",
-  "summary": "A calm, image-first portfolio for a landscape and travel photographer, with named photo series, a full-screen lightbox, an about page, and a contact form.",
+  "summary": "Organize your photography into galleries with a lightbox and contact details.",
   "order": 4,
   "live_url": "https://photos.view.fast/",
   "setup_questions": [
diff --git a/recipes/photos/prompt.md b/recipes/photos/prompt.md
index c7435ed..9746c18 100644
--- a/recipes/photos/prompt.md
+++ b/recipes/photos/prompt.md
@@ -21,8 +21,7 @@ small static **Astro site** (no SSR, no adapters — just `astro build`).
   and a short recognition/press list.
 - A **Prints / shop teaser**: a few open-edition sizes and prices, with a note that
   orders go through the contact form.
-- A **Contact** section: a validating form (name, email, topic, message) that shows a
-  warm, personalized success state on submit, plus direct email and Instagram links.
+- A contact form with name, email, topic, and message, plus direct email and Instagram links. For any form that sends information, ask for my form endpoint or hosted signup URL. Use the supplied destination and show success only after it confirms receipt. A link to another service does not confirm completion. Without a destination, label the form "Demo only" beside its fields, label its button "Preview", and say "Preview complete. Nothing was sent." Never treat `localStorage` as delivery or store personal form data there.
 
 **Design & content notes:**
 
@@ -30,8 +29,7 @@ small static **Astro site** (no SSR, no adapters — just `astro build`).
   one muted oxblood accent used sparingly, lots of whitespace. An elegant serif
   (e.g. Fraunces) for the name and headings over a clean sans (e.g. Inter) for body.
   Let the photographs carry the page.
-- Use realistic content based on my answers — never "lorem ipsum". Invent believable
-  series blurbs, photo captions, a bio, a client list, and print prices.
+- Write captions and a bio from my answers. Include clients and print prices only when I supply them.
 - Use real images. Pull free photos that fit, e.g.
   `https://picsum.photos/seed/<your-seed>/1200/800` (vary the seed per image), with
   descriptive `alt` text. Use the black-and-white treatment for any portrait series.
@@ -47,28 +45,12 @@ small static **Astro site** (no SSR, no adapters — just `astro build`).
 <script src="https://spacefast.com/badge.js" data-example="photos"></script>
 ```
 
-**When the site is ready, publish it to Spacefast with the direct API — no account, install, or extra instructions needed:**
+**When the site is ready, publish it to Spacefast:**
 
 1. Use `./dist` as the publish folder. For no-build projects, put only the finished public files in that dedicated folder. Confirm it has `index.html` at its root and no secrets, source files, `.git`, or `.spacefast` state.
-2. First publish: send every file as multipart form data. This Bash/Zsh block preserves relative paths and works for one file or a whole folder:
-   ```bash
-   PUBLISH_ROOT=./dist
-   publish_files=()
-   while IFS= read -r -d "" file; do
-     relative=${file#"$PUBLISH_ROOT"/}
-     publish_files+=(-F "files=@$file;filename=$relative")
-   done < <(find "$PUBLISH_ROOT" -type f -print0)
-   curl -sS "${publish_files[@]}" "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-3. From the `{ "data": ... }` receipt, give me `data.space.liveUrl`, `data.version.immutableUrl`, `data.claim.url`, and `data.claim.expiresAt`. Remind me to claim within 6 hours. Keep `data.claim.token` secret.
-4. Save `data.space.id` and `data.claim.token` locally (for example in an ignored, mode-600 `.spacefast/state.json`). For a quick update, rebuild the `publish_files` array above and publish to the same space:
-   ```bash
-   SPACEFAST_SPACE_ID=<saved-space-id>
-   SPACEFAST_TOKEN=<saved-claim-token-or-access-token>
-   curl -sS -H "Authorization: Bearer $SPACEFAST_TOKEN" \
-     -F "spaceId=$SPACEFAST_SPACE_ID" "${publish_files[@]}" \
-     "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-   If an update after claiming returns `space_claimed_credential_available`, exchange the saved claim token once at `POST https://api.spacefast.com/v1/anonymous-claim/exchange`, save `data.credential.accessToken`, and retry with that access token.
+2. Fetch https://spacefast.com/setup.md and follow its current direct API publishing instructions. Check for an existing Space before creating one, and follow the returned upload and polling steps.
+3. Report success only when `data.next.action` is `done` and the intended version is serving. If more work is needed, report the returned next step.
+4. For an anonymous publish, give me `data.claim.message` unchanged. It contains the private preview (`data.claim.url`), the owner's claim link (`data.claim.claimUrl`), and the deadline (`data.claim.expiresAt`). Keep both links private. Never print the separate `data.claim.key`.
+5. Keep `data.space.id` and the returned credential securely for updates to the same Space. Follow the guide for credential recovery after claiming. Keep credentials and `.spacefast` state out of the published files, commits, and logs.
 
-**Optional shortcuts and reference only:** if the `sf` CLI is already installed, `sf publish ./dist --wait` does the same job. A zip of the publish folder is also supported, but neither the CLI nor a zip is required. Docs: [direct agent/API publishing](https://spacefast.com/setup) · [files and folders](https://spacefast.com/help/publishing) · [claiming](https://spacefast.com/help/anonymous-publish) · [updates and rollback](https://spacefast.com/help/versions)
+If the `sf` CLI is already installed, `sf publish ./dist --wait` follows the same publishing flow. See [publishing](https://spacefast.com/docs/publish/) and [claiming a Space](https://spacefast.com/docs/anonymous-and-claim/).
diff --git a/recipes/photos/site/src/components/Contact.astro b/recipes/photos/site/src/components/Contact.astro
index b591279..b89e3d3 100644
--- a/recipes/photos/site/src/components/Contact.astro
+++ b/recipes/photos/site/src/components/Contact.astro
@@ -15,6 +15,7 @@ import { studio } from '../data/portfolio';
 
     <div class="contact-grid">
       <div>
+        <p data-demo-note="true">Demo form. Nothing is sent or booked.</p>
         <form id="contact-form" novalidate>
           <div class="field">
             <label for="cf-name">Your name</label>
@@ -49,12 +50,12 @@ import { studio } from '../data/portfolio';
               placeholder="Tell me a little about the project, the timeline, and where in the world it is."
             ></textarea>
           </div>
-          <button class="btn" type="submit">Send message →</button>
+          <button class="btn" type="submit">Preview</button>
           <p id="cf-error" role="alert" style="display:none;color:var(--accent);margin:0.9rem 0 0;font-size:0.9rem;"></p>
         </form>
 
         <div class="form-success" id="cf-success" role="status" aria-live="polite">
-          <h3>Thanks — that's on its way.</h3>
+          <h3>Contact preview complete</h3>
           <p id="cf-success-body"></p>
         </div>
       </div>
@@ -97,12 +98,8 @@ import { studio } from '../data/portfolio';
       }
       return;
     }
-    const data = new FormData(form);
-    const name = String(data.get('name') || '').trim().split(' ')[0] || 'there';
     if (successBody) {
-      successBody.textContent =
-        `Got it, ${name} — I'll get back to you at ${data.get('email')} within a couple of days. ` +
-        `In the meantime, the prints are all open editions, so there's no rush on anything.`;
+      successBody.textContent = 'Preview complete. Nothing was sent.';
     }
     form.style.display = 'none';
     success?.classList.add('is-visible');
diff --git a/recipes/photos/site/src/layouts/Layout.astro b/recipes/photos/site/src/layouts/Layout.astro
index fed7912..1956a7c 100644
--- a/recipes/photos/site/src/layouts/Layout.astro
+++ b/recipes/photos/site/src/layouts/Layout.astro
@@ -44,6 +44,12 @@ const {
     />
   </head>
   <body>
+    <aside
+      aria-label="Example site"
+      style="margin:0;padding:0.75rem 1rem;background:#fff7d6;color:#29221a;font:14px/1.5 system-ui;text-align:center"
+    >
+      Example site with fictional content. Forms are previews.
+    </aside>
     <slot />
     <script>
       // Sticky-nav hairline + scroll reveal, shared across every page.
diff --git a/recipes/portfolio/meta.json b/recipes/portfolio/meta.json
index faa67fe..9f073fd 100644
--- a/recipes/portfolio/meta.json
+++ b/recipes/portfolio/meta.json
@@ -4,7 +4,7 @@
   "slug": "portfolio",
   "vertical": "Personal & creative",
   "tech": "HTML5 canvas game",
-  "summary": "An explorable pixel-art portfolio — walk a little avatar around a cozy room and step up to the desk, bookshelf, poster, and mailbox to reveal projects, an about, a resume, and contact links.",
+  "summary": "Let visitors explore your projects by walking through a pixel-art room.",
   "order": 6,
   "live_url": "https://portfolio.view.fast/",
   "setup_questions": [
diff --git a/recipes/portfolio/prompt.md b/recipes/portfolio/prompt.md
index 4bc3765..f19a148 100644
--- a/recipes/portfolio/prompt.md
+++ b/recipes/portfolio/prompt.md
@@ -33,8 +33,7 @@ framework, no image files; draw every sprite procedurally on a `<canvas>`).
 - Cozy 16-bit game mood: warm woods and a calm sage wall, one orange accent and one
   teal accent, a rounded display font for headings and a clean sans for body, plus a
   monospace for little code/label details. Dark frame around the canvas.
-- Use realistic content based on my answers — never "lorem ipsum". Invent believable
-  project blurbs and a plausible work history if I'm light on detail.
+- Use my real projects, roles, and work history. Ask for missing facts instead of inventing credentials or achievements.
 - The panels are HTML overlays on top of the canvas, so the project links and contact
   rows are real, focusable, accessible links — not pixels.
 - Optional polish: a tiny WebAudio "blip" when a panel opens, and a gentle bob on the
@@ -49,28 +48,12 @@ framework, no image files; draw every sprite procedurally on a `<canvas>`).
 <script src="https://spacefast.com/badge.js" data-example="portfolio"></script>
 ```
 
-**When the site is ready, publish it to Spacefast with the direct API — no account, install, or extra instructions needed:**
+**When the site is ready, publish it to Spacefast:**
 
 1. Use `./site` as the publish folder. For no-build projects, put only the finished public files in that dedicated folder. Confirm it has `index.html` at its root and no secrets, source files, `.git`, or `.spacefast` state.
-2. First publish: send every file as multipart form data. This Bash/Zsh block preserves relative paths and works for one file or a whole folder:
-   ```bash
-   PUBLISH_ROOT=./site
-   publish_files=()
-   while IFS= read -r -d "" file; do
-     relative=${file#"$PUBLISH_ROOT"/}
-     publish_files+=(-F "files=@$file;filename=$relative")
-   done < <(find "$PUBLISH_ROOT" -type f -print0)
-   curl -sS "${publish_files[@]}" "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-3. From the `{ "data": ... }` receipt, give me `data.space.liveUrl`, `data.version.immutableUrl`, `data.claim.url`, and `data.claim.expiresAt`. Remind me to claim within 6 hours. Keep `data.claim.token` secret.
-4. Save `data.space.id` and `data.claim.token` locally (for example in an ignored, mode-600 `.spacefast/state.json`). For a quick update, rebuild the `publish_files` array above and publish to the same space:
-   ```bash
-   SPACEFAST_SPACE_ID=<saved-space-id>
-   SPACEFAST_TOKEN=<saved-claim-token-or-access-token>
-   curl -sS -H "Authorization: Bearer $SPACEFAST_TOKEN" \
-     -F "spaceId=$SPACEFAST_SPACE_ID" "${publish_files[@]}" \
-     "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-   If an update after claiming returns `space_claimed_credential_available`, exchange the saved claim token once at `POST https://api.spacefast.com/v1/anonymous-claim/exchange`, save `data.credential.accessToken`, and retry with that access token.
+2. Fetch https://spacefast.com/setup.md and follow its current direct API publishing instructions. Check for an existing Space before creating one, and follow the returned upload and polling steps.
+3. Report success only when `data.next.action` is `done` and the intended version is serving. If more work is needed, report the returned next step.
+4. For an anonymous publish, give me `data.claim.message` unchanged. It contains the private preview (`data.claim.url`), the owner's claim link (`data.claim.claimUrl`), and the deadline (`data.claim.expiresAt`). Keep both links private. Never print the separate `data.claim.key`.
+5. Keep `data.space.id` and the returned credential securely for updates to the same Space. Follow the guide for credential recovery after claiming. Keep credentials and `.spacefast` state out of the published files, commits, and logs.
 
-**Optional shortcuts and reference only:** if the `sf` CLI is already installed, `sf publish ./site --wait` does the same job. A zip of the publish folder is also supported, but neither the CLI nor a zip is required. Docs: [direct agent/API publishing](https://spacefast.com/setup) · [files and folders](https://spacefast.com/help/publishing) · [claiming](https://spacefast.com/help/anonymous-publish) · [updates and rollback](https://spacefast.com/help/versions)
+If the `sf` CLI is already installed, `sf publish ./site --wait` follows the same publishing flow. See [publishing](https://spacefast.com/docs/publish/) and [claiming a Space](https://spacefast.com/docs/anonymous-and-claim/).
diff --git a/recipes/portfolio/site/index.html b/recipes/portfolio/site/index.html
index 3bd2083..816ab8e 100644
--- a/recipes/portfolio/site/index.html
+++ b/recipes/portfolio/site/index.html
@@ -228,6 +228,12 @@
 </style>
 </head>
 <body>
+    <aside
+      aria-label="Example site"
+      style="margin:0;padding:0.75rem 1rem;background:#fff7d6;color:#29221a;font:14px/1.5 system-ui;text-align:center"
+    >
+      Example site with fictional content. Numbers, quotes, and business details are sample content.
+    </aside>
 <div class="stage">
   <div class="titlebar">
     <span class="dot" aria-hidden="true"></span>
diff --git a/recipes/proposal/meta.json b/recipes/proposal/meta.json
index 52b8909..89ff184 100644
--- a/recipes/proposal/meta.json
+++ b/recipes/proposal/meta.json
@@ -4,7 +4,7 @@
   "slug": "proposal",
   "vertical": "Data, internal & startup",
   "tech": "Astro",
-  "summary": "A personalized \"prepared for Acme Co.\" sales proposal — scope, a gated timeline, three selectable pricing tiers, and a working accept/sign CTA that recomputes the agreement and remembers the acceptance.",
+  "summary": "Present a client proposal with scope, milestones, and selectable pricing options.",
   "order": 300,
   "live_url": "https://proposal.view.fast/",
   "setup_questions": [
@@ -23,8 +23,8 @@
     "Scope of work as workstream cards with fixed-scope deliverable checklists",
     "Five-phase, gated project timeline with week ranges and milestones",
     "Three selectable pricing tiers (Essential / Signature / Partner) with a recommended badge",
-    "Accept & sign CTA: tier-aware agreement summary + typed e-signature, success state, and localStorage persistence",
+    "Tier-aware acceptance preview, or a link to your actual signing service",
     "FAQ and studio contact footer"
   ],
-  "based_on": "A realistic, evergreen example modeled on a common real-world need: the personalized client sales proposal a freelancer or studio sends to win a project — scope, timeline, tiered pricing, and an accept/sign button — the kind normally trapped in PandaDoc/Qwilr behind a login."
+  "based_on": "A realistic, evergreen example modeled on a common real-world need: the personalized client sales proposal a freelancer or studio sends to win a project — scope, timeline, tiered pricing, and an acceptance preview or signing-service link — the kind normally trapped in PandaDoc/Qwilr behind a login."
 }
diff --git a/recipes/proposal/prompt.md b/recipes/proposal/prompt.md
index 06db814..0e9a503 100644
--- a/recipes/proposal/prompt.md
+++ b/recipes/proposal/prompt.md
@@ -1,5 +1,5 @@
 Build me a **personalized, one-page sales proposal site** — a "prepared for {client}"
-page with scope, timeline, pricing tiers, and a working accept/sign button — as an
+page with scope, timeline, pricing tiers, and an acceptance preview or signing-service link — as an
 **Astro site** (a real, minimal Astro project I can build with `bun run build`).
 
 **Before you build, ask me these questions in one message and wait for my answers. If I skip anything, choose a sensible default and tell me what you chose:**
@@ -22,12 +22,7 @@ page with scope, timeline, pricing tiers, and a working accept/sign button — a
 - **Pricing tiers**: 2–3 selectable cards with price, cadence, feature checklist,
   and a "Recommended" badge on the middle one. Clicking a tier selects it and
   updates the accept form below.
-- An **accept & sign** section: an agreement summary that reflects the selected
-  tier (tier name, total, and a 40% deposit line that recomputes), and a sign form
-  with full name, work email, a typed e-signature that must match the name, and an
-  "I agree to the terms" checkbox. On submit it validates, shows a success state
-  ("Thank you, {first name} — accepted!") with a signed receipt and reference
-  number, and persists the acceptance in `localStorage` so it survives a refresh.
+- An acceptance section reflecting the selected tier, total, and deposit. Use the signing-service link I provide. Without one, build a form labelled "Acceptance preview" with name, email, typed name, and an agreement checkbox. Its button says "Preview acceptance" and its result says "Preview complete. Nothing was signed or sent." Do not generate a signed receipt or acceptance reference for browser-only data.
 - A short **FAQ** and a **footer** with studio contact details.
 
 **Design & content notes:**
@@ -38,8 +33,7 @@ page with scope, timeline, pricing tiers, and a working accept/sign button — a
   (**IBM Plex Mono**) for every figure and reference number.
 - A dark navy cover and a dark navy accept/sign section bookend the light reading
   sections, with a subtle reading-progress bar at the top.
-- Use realistic content based on my answers — never "lorem ipsum". Invent
-  believable scope bullets, milestones, and terms if I leave gaps.
+- Draft scope and milestones from my answers. Mark suggested terms and dates as drafts for my review. Do not imply agreement before a confirmed signing flow.
 - Use real images. Pull free photos that fit, e.g.
   `https://picsum.photos/seed/proposal-1/1200/800` (vary the seed) or Pexels,
   and add descriptive `alt` text. Use a calm, professional handshake/office photo
@@ -60,28 +54,12 @@ page with scope, timeline, pricing tiers, and a working accept/sign button — a
 <script src="https://spacefast.com/badge.js" data-example="proposal"></script>
 ```
 
-**When the site is ready, publish it to Spacefast with the direct API — no account, install, or extra instructions needed:**
+**When the site is ready, publish it to Spacefast:**
 
 1. Use `./dist` as the publish folder. For no-build projects, put only the finished public files in that dedicated folder. Confirm it has `index.html` at its root and no secrets, source files, `.git`, or `.spacefast` state.
-2. First publish: send every file as multipart form data. This Bash/Zsh block preserves relative paths and works for one file or a whole folder:
-   ```bash
-   PUBLISH_ROOT=./dist
-   publish_files=()
-   while IFS= read -r -d "" file; do
-     relative=${file#"$PUBLISH_ROOT"/}
-     publish_files+=(-F "files=@$file;filename=$relative")
-   done < <(find "$PUBLISH_ROOT" -type f -print0)
-   curl -sS "${publish_files[@]}" "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-3. From the `{ "data": ... }` receipt, give me `data.space.liveUrl`, `data.version.immutableUrl`, `data.claim.url`, and `data.claim.expiresAt`. Remind me to claim within 6 hours. Keep `data.claim.token` secret.
-4. Save `data.space.id` and `data.claim.token` locally (for example in an ignored, mode-600 `.spacefast/state.json`). For a quick update, rebuild the `publish_files` array above and publish to the same space:
-   ```bash
-   SPACEFAST_SPACE_ID=<saved-space-id>
-   SPACEFAST_TOKEN=<saved-claim-token-or-access-token>
-   curl -sS -H "Authorization: Bearer $SPACEFAST_TOKEN" \
-     -F "spaceId=$SPACEFAST_SPACE_ID" "${publish_files[@]}" \
-     "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-   If an update after claiming returns `space_claimed_credential_available`, exchange the saved claim token once at `POST https://api.spacefast.com/v1/anonymous-claim/exchange`, save `data.credential.accessToken`, and retry with that access token.
+2. Fetch https://spacefast.com/setup.md and follow its current direct API publishing instructions. Check for an existing Space before creating one, and follow the returned upload and polling steps.
+3. Report success only when `data.next.action` is `done` and the intended version is serving. If more work is needed, report the returned next step.
+4. For an anonymous publish, give me `data.claim.message` unchanged. It contains the private preview (`data.claim.url`), the owner's claim link (`data.claim.claimUrl`), and the deadline (`data.claim.expiresAt`). Keep both links private. Never print the separate `data.claim.key`.
+5. Keep `data.space.id` and the returned credential securely for updates to the same Space. Follow the guide for credential recovery after claiming. Keep credentials and `.spacefast` state out of the published files, commits, and logs.
 
-**Optional shortcuts and reference only:** if the `sf` CLI is already installed, `sf publish ./dist --wait` does the same job. A zip of the publish folder is also supported, but neither the CLI nor a zip is required. Docs: [direct agent/API publishing](https://spacefast.com/setup) · [files and folders](https://spacefast.com/help/publishing) · [claiming](https://spacefast.com/help/anonymous-publish) · [updates and rollback](https://spacefast.com/help/versions)
+If the `sf` CLI is already installed, `sf publish ./dist --wait` follows the same publishing flow. See [publishing](https://spacefast.com/docs/publish/) and [claiming a Space](https://spacefast.com/docs/anonymous-and-claim/).
diff --git a/recipes/proposal/site/src/layouts/Layout.astro b/recipes/proposal/site/src/layouts/Layout.astro
index 0653638..3d527cc 100644
--- a/recipes/proposal/site/src/layouts/Layout.astro
+++ b/recipes/proposal/site/src/layouts/Layout.astro
@@ -37,6 +37,12 @@ const {
     />
   </head>
   <body>
+    <aside
+      aria-label="Example site"
+      style="margin:0;padding:0.75rem 1rem;background:#fff7d6;color:#29221a;font:14px/1.5 system-ui;text-align:center"
+    >
+      Example site with fictional content. Forms are previews.
+    </aside>
     <slot />
 
     <script src="https://spacefast.com/badge.js" data-example="proposal"></script>
diff --git a/recipes/proposal/site/src/pages/index.astro b/recipes/proposal/site/src/pages/index.astro
index 7687285..08f5cac 100644
--- a/recipes/proposal/site/src/pages/index.astro
+++ b/recipes/proposal/site/src/pages/index.astro
@@ -31,7 +31,7 @@ const brand = `<svg viewBox="0 0 32 32" aria-hidden="true"><rect width="32" heig
         {meta.proposalNo} · Valid until {meta.validUntil}
       </div>
       <a class="topbar__cta" href="#accept">
-        Accept proposal
+        Preview acceptance
         <svg
           width="14"
           height="14"
@@ -249,7 +249,7 @@ const brand = `<svg viewBox="0 0 32 32" aria-hidden="true"><rect width="32" heig
     <section class="section accept" id="accept">
       <div class="wrap">
         <div class="section-head reveal" style="margin-bottom:0">
-          <p class="eyebrow">Accept &amp; sign</p>
+          <p class="eyebrow">Acceptance preview</p>
           <h2>Ready when you are, {meta.preparedFor}</h2>
           <p class="accept__lead">
             Review the summary, type your name to sign, and you're done. We'll
@@ -290,7 +290,8 @@ const brand = `<svg viewBox="0 0 32 32" aria-hidden="true"><rect width="32" heig
 
           <!-- signature -->
           <div class="sign-card reveal" id="sign-card">
-            <h3>Sign to accept</h3>
+            <h3>Preview acceptance</h3>
+            <p data-demo-note="true">Acceptance preview. Nothing is signed or sent.</p>
             <form id="sign-form" novalidate>
               <div class="field" id="f-name">
                 <label for="name-input">Full name</label>
@@ -319,7 +320,7 @@ const brand = `<svg viewBox="0 0 32 32" aria-hidden="true"><rect width="32" heig
               </div>
 
               <div class="field" id="f-sign">
-                <label for="sign-input">Type your name to sign</label>
+                <label for="sign-input">Type your name for the preview</label>
                 <input
                   type="text"
                   id="sign-input"
@@ -329,7 +330,7 @@ const brand = `<svg viewBox="0 0 32 32" aria-hidden="true"><rect width="32" heig
                   required
                 />
                 <p class="hint" id="sign-hint">
-                  Your typed name is a legally binding e-signature.
+                  This demo does not create a signature or agreement.
                 </p>
                 <p class="err">Your signature must match your full name.</p>
               </div>
@@ -337,13 +338,13 @@ const brand = `<svg viewBox="0 0 32 32" aria-hidden="true"><rect width="32" heig
               <label class="agree">
                 <input type="checkbox" id="agree-input" required />
                 <span>
-                  I have read and agree to the scope, timeline, and terms of
-                  this proposal on behalf of {meta.preparedFor}.
+                  I understand that this is a preview for {meta.preparedFor}.
+                  No agreement will be created.
                 </span>
               </label>
 
               <button type="submit" class="btn-accept" id="accept-btn">
-                Accept &amp; sign for <span id="btn-total" class="mono"
+                Preview acceptance for <span id="btn-total" class="mono"
                   >{fmt(recommended.price)}</span
                 >
               </button>
@@ -363,7 +364,7 @@ const brand = `<svg viewBox="0 0 32 32" aria-hidden="true"><rect width="32" heig
                   <polyline points="20 6 9 17 4 12"></polyline>
                 </svg>
               </div>
-              <h3 id="accepted-title">Proposal accepted</h3>
+              <h3 id="accepted-title">Acceptance preview complete</h3>
               <p id="accepted-body"></p>
               <div class="receipt mono" id="accepted-receipt"></div>
               <button type="button" class="btn-reset" id="reset-btn">
@@ -540,25 +541,14 @@ const brand = `<svg viewBox="0 0 32 32" aria-hidden="true"><rect width="32" heig
       }
 
       function showAccepted(rec) {
-        document.getElementById('accepted-title').textContent =
-          'Thank you, ' + rec.name.split(' ')[0] + ' — accepted!';
-        acceptedBody.textContent =
-          rec.name +
-          ' accepted the ' +
-          rec.tier +
-          ' engagement (' +
-          fmt(rec.price) +
-          ') on ' +
-          rec.date +
-          '. A copy is on its way to ' +
-          rec.email +
-          '.';
+        document.getElementById('accepted-title').textContent = 'Acceptance preview complete';
+        acceptedBody.textContent = 'Nothing was signed or sent. This preview is saved only in this browser.';
         acceptedReceipt.innerHTML =
-          '<b>Signed</b> ' +
+          '<b>Typed name, preview only</b> ' +
           rec.signature +
-          '<br><b>Reference</b> ' +
+          '<br><b>Preview reference</b> ' +
           rec.ref +
-          '<br><b>Accepted</b> ' +
+          '<br><b>Preview time</b> ' +
           rec.datetime;
         card.classList.add('is-accepted');
       }
diff --git a/recipes/qr/meta.json b/recipes/qr/meta.json
index 40781b2..85c7ce0 100644
--- a/recipes/qr/meta.json
+++ b/recipes/qr/meta.json
@@ -4,7 +4,7 @@
   "slug": "qr",
   "vertical": "Data, internal & startup",
   "tech": "Plain HTML & CSS",
-  "summary": "A mobile-first landing a printed QR code points to — a brand header, one featured product with a tap-to-copy promo code, a single primary call-to-action, secondary links, and a QR code the page renders itself.",
+  "summary": "Give a printed QR code a landing page with one clear next step.",
   "order": 300,
   "live_url": "https://qr.view.fast/",
   "setup_questions": [
diff --git a/recipes/qr/prompt.md b/recipes/qr/prompt.md
index bbf914a..7c835a3 100644
--- a/recipes/qr/prompt.md
+++ b/recipes/qr/prompt.md
@@ -44,8 +44,7 @@ JavaScript (a single `index.html` plus a CSS and JS file, no build step).
   accent color used sparingly for the primary button, the promo, and link icons. A
   characterful serif (e.g. Fraunces) for the brand name and headlines, a clean sans
   (e.g. Inter) for everything else.
-- Use realistic content based on my answers — never "lorem ipsum". Invent believable
-  product details, addresses, and hours if I leave gaps.
+- Use the product details, prices, addresses, hours, and offer terms I provide. Ask for missing business facts.
 - Use real images. Pull free photos that fit, e.g.
   `https://picsum.photos/seed/product-qr-1/1200/800` (vary the seed) or Pexels,
   and add descriptive `alt` text. Add an `onerror` fallback to
@@ -64,28 +63,12 @@ JavaScript (a single `index.html` plus a CSS and JS file, no build step).
 <script src="https://spacefast.com/badge.js" data-example="qr"></script>
 ```
 
-**When the site is ready, publish it to Spacefast with the direct API — no account, install, or extra instructions needed:**
+**When the site is ready, publish it to Spacefast:**
 
 1. Use `./site` as the publish folder. For no-build projects, put only the finished public files in that dedicated folder. Confirm it has `index.html` at its root and no secrets, source files, `.git`, or `.spacefast` state.
-2. First publish: send every file as multipart form data. This Bash/Zsh block preserves relative paths and works for one file or a whole folder:
-   ```bash
-   PUBLISH_ROOT=./site
-   publish_files=()
-   while IFS= read -r -d "" file; do
-     relative=${file#"$PUBLISH_ROOT"/}
-     publish_files+=(-F "files=@$file;filename=$relative")
-   done < <(find "$PUBLISH_ROOT" -type f -print0)
-   curl -sS "${publish_files[@]}" "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-3. From the `{ "data": ... }` receipt, give me `data.space.liveUrl`, `data.version.immutableUrl`, `data.claim.url`, and `data.claim.expiresAt`. Remind me to claim within 6 hours. Keep `data.claim.token` secret.
-4. Save `data.space.id` and `data.claim.token` locally (for example in an ignored, mode-600 `.spacefast/state.json`). For a quick update, rebuild the `publish_files` array above and publish to the same space:
-   ```bash
-   SPACEFAST_SPACE_ID=<saved-space-id>
-   SPACEFAST_TOKEN=<saved-claim-token-or-access-token>
-   curl -sS -H "Authorization: Bearer $SPACEFAST_TOKEN" \
-     -F "spaceId=$SPACEFAST_SPACE_ID" "${publish_files[@]}" \
-     "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-   If an update after claiming returns `space_claimed_credential_available`, exchange the saved claim token once at `POST https://api.spacefast.com/v1/anonymous-claim/exchange`, save `data.credential.accessToken`, and retry with that access token.
+2. Fetch https://spacefast.com/setup.md and follow its current direct API publishing instructions. Check for an existing Space before creating one, and follow the returned upload and polling steps.
+3. Report success only when `data.next.action` is `done` and the intended version is serving. If more work is needed, report the returned next step.
+4. For an anonymous publish, give me `data.claim.message` unchanged. It contains the private preview (`data.claim.url`), the owner's claim link (`data.claim.claimUrl`), and the deadline (`data.claim.expiresAt`). Keep both links private. Never print the separate `data.claim.key`.
+5. Keep `data.space.id` and the returned credential securely for updates to the same Space. Follow the guide for credential recovery after claiming. Keep credentials and `.spacefast` state out of the published files, commits, and logs.
 
-**Optional shortcuts and reference only:** if the `sf` CLI is already installed, `sf publish ./site --wait` does the same job. A zip of the publish folder is also supported, but neither the CLI nor a zip is required. Docs: [direct agent/API publishing](https://spacefast.com/setup) · [files and folders](https://spacefast.com/help/publishing) · [claiming](https://spacefast.com/help/anonymous-publish) · [updates and rollback](https://spacefast.com/help/versions)
+If the `sf` CLI is already installed, `sf publish ./site --wait` follows the same publishing flow. See [publishing](https://spacefast.com/docs/publish/) and [claiming a Space](https://spacefast.com/docs/anonymous-and-claim/).
diff --git a/recipes/qr/site/index.html b/recipes/qr/site/index.html
index b906b37..07a9d15 100644
--- a/recipes/qr/site/index.html
+++ b/recipes/qr/site/index.html
@@ -19,6 +19,12 @@
   <link rel="stylesheet" href="assets/styles.css" />
 </head>
 <body>
+    <aside
+      aria-label="Example site"
+      style="margin:0;padding:0.75rem 1rem;background:#fff7d6;color:#29221a;font:14px/1.5 system-ui;text-align:center"
+    >
+      Example site with fictional content. Numbers, quotes, and business details are sample content.
+    </aside>
   <a class="skip-link" href="#main">Skip to content</a>
 
   <div class="phone">
diff --git a/recipes/recipes/meta.json b/recipes/recipes/meta.json
index 81c7b29..a670cdc 100644
--- a/recipes/recipes/meta.json
+++ b/recipes/recipes/meta.json
@@ -4,7 +4,7 @@
   "slug": "recipes",
   "vertical": "Personal & creative",
   "tech": "Vite + React",
-  "summary": "A weeknight recipe blog with a searchable, filterable index and recipe pages that scale servings and print a clean card.",
+  "summary": "Publish recipes readers can search, filter, scale, and print.",
   "order": 5,
   "live_url": "https://recipes.view.fast/",
   "setup_questions": [
diff --git a/recipes/recipes/prompt.md b/recipes/recipes/prompt.md
index c5cd1e4..7a80bc3 100644
--- a/recipes/recipes/prompt.md
+++ b/recipes/recipes/prompt.md
@@ -14,7 +14,7 @@ Build me a **weeknight recipe blog with a filterable recipe index and printable,
 - **Recipe page** — hero photo, intro in the cook's voice, a prep / cook / total / serves stat bar, an **ingredients list with a serving-size scaler** (a slider plus +/− that recomputes every quantity into nice kitchen fractions like ¾ and 1½), checkable ingredients, a numbered step-by-step method, and a "Nora's tip" callout.
 - **Print card** — a "Print card" button that opens the browser print dialog showing a clean, single-page card (title, scaled ingredients, numbered method, tip) with all the site chrome hidden via a print stylesheet.
 - **About the cook** — a warm, personal bio with a photo and a few playful stats.
-- **Newsletter / save-this-recipe signup** — name + email that validates the email and shows a friendly "You're on the list!" success state on submit.
+- A newsletter signup with labelled name and email fields. For any form that sends information, ask for my form endpoint or hosted signup URL. Use the supplied destination and show success only after it confirms receipt. A link to another service does not confirm completion. Without a destination, label the form "Demo only" beside its fields, label its button "Preview", and say "Preview complete. Nothing was sent." Never treat `localStorage` as delivery or store personal form data there.
 
 **Design & content notes:**
 
@@ -31,28 +31,12 @@ Build me a **weeknight recipe blog with a filterable recipe index and printable,
 <script src="https://spacefast.com/badge.js" data-example="recipes"></script>
 ```
 
-**When the site is ready, publish it to Spacefast with the direct API — no account, install, or extra instructions needed:**
+**When the site is ready, publish it to Spacefast:**
 
 1. Use `./dist` as the publish folder. For no-build projects, put only the finished public files in that dedicated folder. Confirm it has `index.html` at its root and no secrets, source files, `.git`, or `.spacefast` state.
-2. First publish: send every file as multipart form data. This Bash/Zsh block preserves relative paths and works for one file or a whole folder:
-   ```bash
-   PUBLISH_ROOT=./dist
-   publish_files=()
-   while IFS= read -r -d "" file; do
-     relative=${file#"$PUBLISH_ROOT"/}
-     publish_files+=(-F "files=@$file;filename=$relative")
-   done < <(find "$PUBLISH_ROOT" -type f -print0)
-   curl -sS "${publish_files[@]}" "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-3. From the `{ "data": ... }` receipt, give me `data.space.liveUrl`, `data.version.immutableUrl`, `data.claim.url`, and `data.claim.expiresAt`. Remind me to claim within 6 hours. Keep `data.claim.token` secret.
-4. Save `data.space.id` and `data.claim.token` locally (for example in an ignored, mode-600 `.spacefast/state.json`). For a quick update, rebuild the `publish_files` array above and publish to the same space:
-   ```bash
-   SPACEFAST_SPACE_ID=<saved-space-id>
-   SPACEFAST_TOKEN=<saved-claim-token-or-access-token>
-   curl -sS -H "Authorization: Bearer $SPACEFAST_TOKEN" \
-     -F "spaceId=$SPACEFAST_SPACE_ID" "${publish_files[@]}" \
-     "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-   If an update after claiming returns `space_claimed_credential_available`, exchange the saved claim token once at `POST https://api.spacefast.com/v1/anonymous-claim/exchange`, save `data.credential.accessToken`, and retry with that access token.
-
-**Optional shortcuts and reference only:** if the `sf` CLI is already installed, `sf publish ./dist --wait` does the same job. A zip of the publish folder is also supported, but neither the CLI nor a zip is required. Docs: [direct agent/API publishing](https://spacefast.com/setup) · [files and folders](https://spacefast.com/help/publishing) · [claiming](https://spacefast.com/help/anonymous-publish) · [updates and rollback](https://spacefast.com/help/versions)
+2. Fetch https://spacefast.com/setup.md and follow its current direct API publishing instructions. Check for an existing Space before creating one, and follow the returned upload and polling steps.
+3. Report success only when `data.next.action` is `done` and the intended version is serving. If more work is needed, report the returned next step.
+4. For an anonymous publish, give me `data.claim.message` unchanged. It contains the private preview (`data.claim.url`), the owner's claim link (`data.claim.claimUrl`), and the deadline (`data.claim.expiresAt`). Keep both links private. Never print the separate `data.claim.key`.
+5. Keep `data.space.id` and the returned credential securely for updates to the same Space. Follow the guide for credential recovery after claiming. Keep credentials and `.spacefast` state out of the published files, commits, and logs.
+
+If the `sf` CLI is already installed, `sf publish ./dist --wait` follows the same publishing flow. See [publishing](https://spacefast.com/docs/publish/) and [claiming a Space](https://spacefast.com/docs/anonymous-and-claim/).
diff --git a/recipes/recipes/site/index.html b/recipes/recipes/site/index.html
index 738eea9..599f369 100644
--- a/recipes/recipes/site/index.html
+++ b/recipes/recipes/site/index.html
@@ -23,6 +23,12 @@
     />
   </head>
   <body>
+    <aside
+      aria-label="Example site"
+      style="margin:0;padding:0.75rem 1rem;background:#fff7d6;color:#29221a;font:14px/1.5 system-ui;text-align:center"
+    >
+      Example site with fictional content. Forms are previews.
+    </aside>
     <div id="root"></div>
     <script type="module" src="/src/main.jsx"></script>
     <script src="https://spacefast.com/badge.js" data-example="recipes"></script>
diff --git a/recipes/recipes/site/src/App.jsx b/recipes/recipes/site/src/App.jsx
index 223d177..01a7e4a 100644
--- a/recipes/recipes/site/src/App.jsx
+++ b/recipes/recipes/site/src/App.jsx
@@ -135,11 +135,12 @@ function Newsletter({ variant = "block" }) {
       </div>
       {done ? (
         <div className="newsletter-success" role="status">
-          <strong>You're on the list{name ? `, ${name.split(" ")[0]}` : ""}! 🎉</strong>
-          <p>Check your inbox Friday for the first one. Welcome to the kitchen.</p>
+          <strong>Signup preview complete{name ? `, ${name.split(" ")[0]}` : ""}! 🎉</strong>
+          <p>Preview complete. Nothing was sent.</p>
         </div>
       ) : (
         <form className="newsletter-form" onSubmit={submit} noValidate>
+          <p style={{ gridColumn: "1 / -1", flexBasis: "100%" }} data-demo-note="true">Demo signup. No subscription is created and no email is sent.</p>
           <div className="field">
             <label htmlFor="nl-name">First name</label>
             <input
@@ -165,9 +166,7 @@ function Newsletter({ variant = "block" }) {
               required
             />
           </div>
-          <button type="submit" className="btn btn-primary">
-            Send me Friday's recipe
-          </button>
+          <button type="submit" className="btn btn-primary">Preview</button>
           {error && (
             <p id="nl-error" className="form-error" role="alert">
               {error}
diff --git a/recipes/report/meta.json b/recipes/report/meta.json
index 6fb9eb1..6c3e0ac 100644
--- a/recipes/report/meta.json
+++ b/recipes/report/meta.json
@@ -4,7 +4,7 @@
   "slug": "report",
   "vertical": "Data, internal & startup",
   "tech": "Astro",
-  "summary": "A long-form annual community survey report — methodology, demographic charts, tool rankings, sentiment scales, and an editor's takeaways.",
+  "summary": "Present survey findings with methodology, charts, and takeaways.",
   "order": 3,
   "live_url": "https://report.view.fast/",
   "setup_questions": [
diff --git a/recipes/report/prompt.md b/recipes/report/prompt.md
index eb3aeb1..e1830a3 100644
--- a/recipes/report/prompt.md
+++ b/recipes/report/prompt.md
@@ -40,8 +40,7 @@ and the Stack Overflow Developer Survey — as an **Astro site** (static, no SSR
   charting library to download. Keep one source-of-truth data file so all the
   numbers stay internally consistent (the demographic breakdowns should sum to
   the total respondent count).
-- Use realistic content based on my answers — never “lorem ipsum.” Invent
-  believable figures, rankings, and quotable write-in comments.
+- Use the survey dataset and methodology I provide. Do not invent responses, rankings, or quotes. If no dataset is available, build a report labelled "Sample survey data" with fictional results identified beside each chart.
 - Use real images. Pull free photos that fit, e.g.
   `https://picsum.photos/seed/coworking-1/1200/800` (vary the seed) or
   Pexels, and add descriptive `alt` text.
@@ -54,28 +53,12 @@ and the Stack Overflow Developer Survey — as an **Astro site** (static, no SSR
 <script src="https://spacefast.com/badge.js" data-example="report"></script>
 ```
 
-**When the site is ready, publish it to Spacefast with the direct API — no account, install, or extra instructions needed:**
+**When the site is ready, publish it to Spacefast:**
 
 1. Use `./dist` as the publish folder. For no-build projects, put only the finished public files in that dedicated folder. Confirm it has `index.html` at its root and no secrets, source files, `.git`, or `.spacefast` state.
-2. First publish: send every file as multipart form data. This Bash/Zsh block preserves relative paths and works for one file or a whole folder:
-   ```bash
-   PUBLISH_ROOT=./dist
-   publish_files=()
-   while IFS= read -r -d "" file; do
-     relative=${file#"$PUBLISH_ROOT"/}
-     publish_files+=(-F "files=@$file;filename=$relative")
-   done < <(find "$PUBLISH_ROOT" -type f -print0)
-   curl -sS "${publish_files[@]}" "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-3. From the `{ "data": ... }` receipt, give me `data.space.liveUrl`, `data.version.immutableUrl`, `data.claim.url`, and `data.claim.expiresAt`. Remind me to claim within 6 hours. Keep `data.claim.token` secret.
-4. Save `data.space.id` and `data.claim.token` locally (for example in an ignored, mode-600 `.spacefast/state.json`). For a quick update, rebuild the `publish_files` array above and publish to the same space:
-   ```bash
-   SPACEFAST_SPACE_ID=<saved-space-id>
-   SPACEFAST_TOKEN=<saved-claim-token-or-access-token>
-   curl -sS -H "Authorization: Bearer $SPACEFAST_TOKEN" \
-     -F "spaceId=$SPACEFAST_SPACE_ID" "${publish_files[@]}" \
-     "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-   If an update after claiming returns `space_claimed_credential_available`, exchange the saved claim token once at `POST https://api.spacefast.com/v1/anonymous-claim/exchange`, save `data.credential.accessToken`, and retry with that access token.
+2. Fetch https://spacefast.com/setup.md and follow its current direct API publishing instructions. Check for an existing Space before creating one, and follow the returned upload and polling steps.
+3. Report success only when `data.next.action` is `done` and the intended version is serving. If more work is needed, report the returned next step.
+4. For an anonymous publish, give me `data.claim.message` unchanged. It contains the private preview (`data.claim.url`), the owner's claim link (`data.claim.claimUrl`), and the deadline (`data.claim.expiresAt`). Keep both links private. Never print the separate `data.claim.key`.
+5. Keep `data.space.id` and the returned credential securely for updates to the same Space. Follow the guide for credential recovery after claiming. Keep credentials and `.spacefast` state out of the published files, commits, and logs.
 
-**Optional shortcuts and reference only:** if the `sf` CLI is already installed, `sf publish ./dist --wait` does the same job. A zip of the publish folder is also supported, but neither the CLI nor a zip is required. Docs: [direct agent/API publishing](https://spacefast.com/setup) · [files and folders](https://spacefast.com/help/publishing) · [claiming](https://spacefast.com/help/anonymous-publish) · [updates and rollback](https://spacefast.com/help/versions)
+If the `sf` CLI is already installed, `sf publish ./dist --wait` follows the same publishing flow. See [publishing](https://spacefast.com/docs/publish/) and [claiming a Space](https://spacefast.com/docs/anonymous-and-claim/).
diff --git a/recipes/report/site/src/layouts/Layout.astro b/recipes/report/site/src/layouts/Layout.astro
index f63e134..740fc08 100644
--- a/recipes/report/site/src/layouts/Layout.astro
+++ b/recipes/report/site/src/layouts/Layout.astro
@@ -39,6 +39,12 @@ const {
     />
   </head>
   <body>
+    <aside
+      aria-label="Example site"
+      style="margin:0;padding:0.75rem 1rem;background:#fff7d6;color:#29221a;font:14px/1.5 system-ui;text-align:center"
+    >
+      Example site with fictional content. Numbers, quotes, and business details are sample content.
+    </aside>
     <slot />
 
     <script>
diff --git a/recipes/resume/meta.json b/recipes/resume/meta.json
index 3d9b3e1..59e520b 100644
--- a/recipes/resume/meta.json
+++ b/recipes/resume/meta.json
@@ -4,7 +4,7 @@
   "slug": "resume",
   "vertical": "Personal & creative",
   "tech": "Plain HTML & CSS",
-  "summary": "A clean single-page web resume with a contact header, an experience timeline, a skills sidebar with animated proficiency meters, and a print-to-PDF stylesheet behind a Download PDF button.",
+  "summary": "Publish your experience and skills as a web resume readers can save as a PDF.",
   "order": 300,
   "live_url": "https://resume.view.fast/",
   "setup_questions": [
diff --git a/recipes/resume/prompt.md b/recipes/resume/prompt.md
index a16e778..bb2aede 100644
--- a/recipes/resume/prompt.md
+++ b/recipes/resume/prompt.md
@@ -31,8 +31,7 @@ opens straight in a browser.
 - Include a dedicated **print-to-PDF stylesheet** (`@media print`) that hides the
   toolbar and badge, switches to high-contrast black ink, keeps the two columns,
   prevents roles from breaking across pages, and fits cleanly onto one page.
-- Use realistic content based on my answers — never "lorem ipsum". Invent
-  believable, specific bullet points (with numbers) if I leave gaps.
+- Use my actual roles, experience, and achievements. Include numerical results only when I provide them. Ask for missing details instead of inventing qualifications.
 - Use real images. Pull free photos that fit — a professional headshot and a
   minimal desk/notebook footer image — e.g.
   `https://picsum.photos/seed/headshot-1/480/480` (vary the seed), and add
@@ -49,28 +48,12 @@ opens straight in a browser.
 <script src="https://spacefast.com/badge.js" data-example="resume"></script>
 ```
 
-**When the site is ready, publish it to Spacefast with the direct API — no account, install, or extra instructions needed:**
+**When the site is ready, publish it to Spacefast:**
 
 1. Use `./site` as the publish folder. For no-build projects, put only the finished public files in that dedicated folder. Confirm it has `index.html` at its root and no secrets, source files, `.git`, or `.spacefast` state.
-2. First publish: send every file as multipart form data. This Bash/Zsh block preserves relative paths and works for one file or a whole folder:
-   ```bash
-   PUBLISH_ROOT=./site
-   publish_files=()
-   while IFS= read -r -d "" file; do
-     relative=${file#"$PUBLISH_ROOT"/}
-     publish_files+=(-F "files=@$file;filename=$relative")
-   done < <(find "$PUBLISH_ROOT" -type f -print0)
-   curl -sS "${publish_files[@]}" "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-3. From the `{ "data": ... }` receipt, give me `data.space.liveUrl`, `data.version.immutableUrl`, `data.claim.url`, and `data.claim.expiresAt`. Remind me to claim within 6 hours. Keep `data.claim.token` secret.
-4. Save `data.space.id` and `data.claim.token` locally (for example in an ignored, mode-600 `.spacefast/state.json`). For a quick update, rebuild the `publish_files` array above and publish to the same space:
-   ```bash
-   SPACEFAST_SPACE_ID=<saved-space-id>
-   SPACEFAST_TOKEN=<saved-claim-token-or-access-token>
-   curl -sS -H "Authorization: Bearer $SPACEFAST_TOKEN" \
-     -F "spaceId=$SPACEFAST_SPACE_ID" "${publish_files[@]}" \
-     "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-   If an update after claiming returns `space_claimed_credential_available`, exchange the saved claim token once at `POST https://api.spacefast.com/v1/anonymous-claim/exchange`, save `data.credential.accessToken`, and retry with that access token.
+2. Fetch https://spacefast.com/setup.md and follow its current direct API publishing instructions. Check for an existing Space before creating one, and follow the returned upload and polling steps.
+3. Report success only when `data.next.action` is `done` and the intended version is serving. If more work is needed, report the returned next step.
+4. For an anonymous publish, give me `data.claim.message` unchanged. It contains the private preview (`data.claim.url`), the owner's claim link (`data.claim.claimUrl`), and the deadline (`data.claim.expiresAt`). Keep both links private. Never print the separate `data.claim.key`.
+5. Keep `data.space.id` and the returned credential securely for updates to the same Space. Follow the guide for credential recovery after claiming. Keep credentials and `.spacefast` state out of the published files, commits, and logs.
 
-**Optional shortcuts and reference only:** if the `sf` CLI is already installed, `sf publish ./site --wait` does the same job. A zip of the publish folder is also supported, but neither the CLI nor a zip is required. Docs: [direct agent/API publishing](https://spacefast.com/setup) · [files and folders](https://spacefast.com/help/publishing) · [claiming](https://spacefast.com/help/anonymous-publish) · [updates and rollback](https://spacefast.com/help/versions)
+If the `sf` CLI is already installed, `sf publish ./site --wait` follows the same publishing flow. See [publishing](https://spacefast.com/docs/publish/) and [claiming a Space](https://spacefast.com/docs/anonymous-and-claim/).
diff --git a/recipes/resume/site/index.html b/recipes/resume/site/index.html
index a9730c9..3fdd1fe 100644
--- a/recipes/resume/site/index.html
+++ b/recipes/resume/site/index.html
@@ -18,6 +18,12 @@
   <link rel="stylesheet" href="assets/styles.css" />
 </head>
 <body>
+    <aside
+      aria-label="Example site"
+      style="margin:0;padding:0.75rem 1rem;background:#fff7d6;color:#29221a;font:14px/1.5 system-ui;text-align:center"
+    >
+      Example site with fictional content. Numbers, quotes, and business details are sample content.
+    </aside>
   <a class="skip-link" href="#main">Skip to content</a>
 
   <div class="toolbar" role="toolbar" aria-label="Page actions">
diff --git a/recipes/revenue-review/meta.json b/recipes/revenue-review/meta.json
index 7fcddab..21163eb 100644
--- a/recipes/revenue-review/meta.json
+++ b/recipes/revenue-review/meta.json
@@ -4,7 +4,7 @@
   "slug": "revenue-review",
   "vertical": "Data, internal & startup",
   "tech": "Vite + React",
-  "summary": "An interactive year-end SaaS revenue review — an executive KPI strip, an ARR bridge waterfall that sums, MRR movement, cohort retention, revenue mix, churn, and a base/bull/bear forecast.",
+  "summary": "Review sample SaaS revenue with growth, retention, churn, and forecast charts.",
   "order": 2,
   "live_url": "https://revenue-review.view.fast/",
   "setup_questions": [
diff --git a/recipes/revenue-review/prompt.md b/recipes/revenue-review/prompt.md
index ebe3bd1..b4a34c2 100644
--- a/recipes/revenue-review/prompt.md
+++ b/recipes/revenue-review/prompt.md
@@ -53,28 +53,12 @@ forecast — as a **Vite + React app**.
 <script src="https://spacefast.com/badge.js" data-example="revenue-review"></script>
 ```
 
-**When the site is ready, publish it to Spacefast with the direct API — no account, install, or extra instructions needed:**
+**When the site is ready, publish it to Spacefast:**
 
 1. Use `./dist` as the publish folder. For no-build projects, put only the finished public files in that dedicated folder. Confirm it has `index.html` at its root and no secrets, source files, `.git`, or `.spacefast` state.
-2. First publish: send every file as multipart form data. This Bash/Zsh block preserves relative paths and works for one file or a whole folder:
-   ```bash
-   PUBLISH_ROOT=./dist
-   publish_files=()
-   while IFS= read -r -d "" file; do
-     relative=${file#"$PUBLISH_ROOT"/}
-     publish_files+=(-F "files=@$file;filename=$relative")
-   done < <(find "$PUBLISH_ROOT" -type f -print0)
-   curl -sS "${publish_files[@]}" "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-3. From the `{ "data": ... }` receipt, give me `data.space.liveUrl`, `data.version.immutableUrl`, `data.claim.url`, and `data.claim.expiresAt`. Remind me to claim within 6 hours. Keep `data.claim.token` secret.
-4. Save `data.space.id` and `data.claim.token` locally (for example in an ignored, mode-600 `.spacefast/state.json`). For a quick update, rebuild the `publish_files` array above and publish to the same space:
-   ```bash
-   SPACEFAST_SPACE_ID=<saved-space-id>
-   SPACEFAST_TOKEN=<saved-claim-token-or-access-token>
-   curl -sS -H "Authorization: Bearer $SPACEFAST_TOKEN" \
-     -F "spaceId=$SPACEFAST_SPACE_ID" "${publish_files[@]}" \
-     "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-   If an update after claiming returns `space_claimed_credential_available`, exchange the saved claim token once at `POST https://api.spacefast.com/v1/anonymous-claim/exchange`, save `data.credential.accessToken`, and retry with that access token.
+2. Fetch https://spacefast.com/setup.md and follow its current direct API publishing instructions. Check for an existing Space before creating one, and follow the returned upload and polling steps.
+3. Report success only when `data.next.action` is `done` and the intended version is serving. If more work is needed, report the returned next step.
+4. For an anonymous publish, give me `data.claim.message` unchanged. It contains the private preview (`data.claim.url`), the owner's claim link (`data.claim.claimUrl`), and the deadline (`data.claim.expiresAt`). Keep both links private. Never print the separate `data.claim.key`.
+5. Keep `data.space.id` and the returned credential securely for updates to the same Space. Follow the guide for credential recovery after claiming. Keep credentials and `.spacefast` state out of the published files, commits, and logs.
 
-**Optional shortcuts and reference only:** if the `sf` CLI is already installed, `sf publish ./dist --wait` does the same job. A zip of the publish folder is also supported, but neither the CLI nor a zip is required. Docs: [direct agent/API publishing](https://spacefast.com/setup) · [files and folders](https://spacefast.com/help/publishing) · [claiming](https://spacefast.com/help/anonymous-publish) · [updates and rollback](https://spacefast.com/help/versions)
+If the `sf` CLI is already installed, `sf publish ./dist --wait` follows the same publishing flow. See [publishing](https://spacefast.com/docs/publish/) and [claiming a Space](https://spacefast.com/docs/anonymous-and-claim/).
diff --git a/recipes/revenue-review/site/index.html b/recipes/revenue-review/site/index.html
index e4578d4..bc12747 100644
--- a/recipes/revenue-review/site/index.html
+++ b/recipes/revenue-review/site/index.html
@@ -24,6 +24,12 @@
     />
   </head>
   <body>
+    <aside
+      aria-label="Example site"
+      style="margin:0;padding:0.75rem 1rem;background:#fff7d6;color:#29221a;font:14px/1.5 system-ui;text-align:center"
+    >
+      Example site with fictional content. Numbers, quotes, and business details are sample content.
+    </aside>
     <div id="root"></div>
     <script type="module" src="/src/main.jsx"></script>
     <script src="https://spacefast.com/badge.js" data-example="revenue-review"></script>
diff --git a/recipes/roi/meta.json b/recipes/roi/meta.json
index d78907a..f8fac92 100644
--- a/recipes/roi/meta.json
+++ b/recipes/roi/meta.json
@@ -4,7 +4,7 @@
   "slug": "roi",
   "vertical": "Data, internal & startup",
   "tech": "Vanilla JS",
-  "summary": "A B2B ROI / lead-gen calculator — enter your support spend, team size, and ticket volume and watch projected savings, payback, and reclaimed hours compute live with animated SVG charts, behind a gated \"email me the report\" CTA.",
+  "summary": "Estimate savings from your own inputs and formula. Show the assumptions beside the results.",
   "order": 300,
   "live_url": "https://roi.view.fast/",
   "setup_questions": [
@@ -26,7 +26,7 @@
     "Before/after bar chart (monthly cost today vs with the product) drawn in SVG",
     "Cumulative net-savings area chart over 12 months",
     "'Where the savings come from' three-step explanation of the model",
-    "Gated 'email me the report' lead-capture CTA with validation and success state",
+    "Report request connected to your chosen service, or a labelled preview with no email sent",
     "Social proof: customer logos and a testimonial"
   ],
   "based_on": "A B2B SaaS ROI / savings calculator landing page — the lead-gen pattern marketing teams build to turn a few inputs (spend, team size, volume) into a projected-savings number with a chart and a gated 'email me the report' CTA. Modeled on an AI customer-support tool that auto-resolves a share of tickets."
diff --git a/recipes/roi/prompt.md b/recipes/roi/prompt.md
index 2979ca7..b7d8c95 100644
--- a/recipes/roi/prompt.md
+++ b/recipes/roi/prompt.md
@@ -18,7 +18,7 @@ framework and no build step).
 - A **live results panel** that recomputes on every keystroke or slider drag: a big headline "net savings, year one" number, plus a stat grid (net savings / month, hours or units reclaimed, payback period, return multiple).
 - A **before/after bar chart** (cost today vs cost with the product) and a **cumulative-savings area chart** across 12 months — both drawn in inline SVG, no chart library, animated when values change.
 - A "where the savings come from" section: three numbered steps that explain the model honestly, so the number feels earned, not hand-wavy.
-- A **gated lead-capture CTA**: a name + work-email + company form that validates the email, and on submit hides the fields and shows a friendly success state ("report's on its way to …") that echoes the visitor's computed savings. A "run another scenario" link resets it.
+- A lead form with name, work email, and company, alongside the calculated savings. Offer a local report download when no email delivery service is configured. Say "Download your estimate" instead of claiming an email was sent. For any form that sends information, ask for my form endpoint or hosted signup URL. Use the supplied destination and show success only after it confirms receipt. A link to another service does not confirm completion. Without a destination, label the form "Demo only" beside its fields, label its button "Preview", and say "Preview complete. Nothing was sent." Never treat `localStorage` as delivery or store personal form data there.
 - A social-proof strip (customer logos + one testimonial with a headshot) and a footer.
 
 **Design & content notes:**
@@ -27,9 +27,7 @@ framework and no build step).
   confident indigo→violet brand gradient, and a single emerald accent reserved for
   savings/positive numbers. Use a geometric display face (e.g. Sora) for headings and
   Inter for body. Round the corners, keep generous whitespace.
-- Use realistic content based on my answers — never "lorem ipsum". Invent believable
-  customer names, a testimonial, and sensible default input values (a typical
-  mid-market team) so the page looks alive on first load.
+- Use my formula and sourced customer claims. Omit logos and testimonials without permission and exact quotes. Label default inputs as examples and show the assumptions behind every estimate.
 - Make the math real and defensible: clamp the inputs to sane ranges, format currency
   with `Intl.NumberFormat`, animate the result numbers, and keep the assumptions
   (deflection rate, per-seat price) visible near the inputs with a "reset to a typical
@@ -49,28 +47,12 @@ framework and no build step).
 <script src="https://spacefast.com/badge.js" data-example="roi"></script>
 ```
 
-**When the site is ready, publish it to Spacefast with the direct API — no account, install, or extra instructions needed:**
+**When the site is ready, publish it to Spacefast:**
 
 1. Use `./site` as the publish folder. For no-build projects, put only the finished public files in that dedicated folder. Confirm it has `index.html` at its root and no secrets, source files, `.git`, or `.spacefast` state.
-2. First publish: send every file as multipart form data. This Bash/Zsh block preserves relative paths and works for one file or a whole folder:
-   ```bash
-   PUBLISH_ROOT=./site
-   publish_files=()
-   while IFS= read -r -d "" file; do
-     relative=${file#"$PUBLISH_ROOT"/}
-     publish_files+=(-F "files=@$file;filename=$relative")
-   done < <(find "$PUBLISH_ROOT" -type f -print0)
-   curl -sS "${publish_files[@]}" "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-3. From the `{ "data": ... }` receipt, give me `data.space.liveUrl`, `data.version.immutableUrl`, `data.claim.url`, and `data.claim.expiresAt`. Remind me to claim within 6 hours. Keep `data.claim.token` secret.
-4. Save `data.space.id` and `data.claim.token` locally (for example in an ignored, mode-600 `.spacefast/state.json`). For a quick update, rebuild the `publish_files` array above and publish to the same space:
-   ```bash
-   SPACEFAST_SPACE_ID=<saved-space-id>
-   SPACEFAST_TOKEN=<saved-claim-token-or-access-token>
-   curl -sS -H "Authorization: Bearer $SPACEFAST_TOKEN" \
-     -F "spaceId=$SPACEFAST_SPACE_ID" "${publish_files[@]}" \
-     "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-   If an update after claiming returns `space_claimed_credential_available`, exchange the saved claim token once at `POST https://api.spacefast.com/v1/anonymous-claim/exchange`, save `data.credential.accessToken`, and retry with that access token.
+2. Fetch https://spacefast.com/setup.md and follow its current direct API publishing instructions. Check for an existing Space before creating one, and follow the returned upload and polling steps.
+3. Report success only when `data.next.action` is `done` and the intended version is serving. If more work is needed, report the returned next step.
+4. For an anonymous publish, give me `data.claim.message` unchanged. It contains the private preview (`data.claim.url`), the owner's claim link (`data.claim.claimUrl`), and the deadline (`data.claim.expiresAt`). Keep both links private. Never print the separate `data.claim.key`.
+5. Keep `data.space.id` and the returned credential securely for updates to the same Space. Follow the guide for credential recovery after claiming. Keep credentials and `.spacefast` state out of the published files, commits, and logs.
 
-**Optional shortcuts and reference only:** if the `sf` CLI is already installed, `sf publish ./site --wait` does the same job. A zip of the publish folder is also supported, but neither the CLI nor a zip is required. Docs: [direct agent/API publishing](https://spacefast.com/setup) · [files and folders](https://spacefast.com/help/publishing) · [claiming](https://spacefast.com/help/anonymous-publish) · [updates and rollback](https://spacefast.com/help/versions)
+If the `sf` CLI is already installed, `sf publish ./site --wait` follows the same publishing flow. See [publishing](https://spacefast.com/docs/publish/) and [claiming a Space](https://spacefast.com/docs/anonymous-and-claim/).
diff --git a/recipes/roi/site/assets/app.js b/recipes/roi/site/assets/app.js
index 9c5e30a..2b00abe 100644
--- a/recipes/roi/site/assets/app.js
+++ b/recipes/roi/site/assets/app.js
@@ -280,10 +280,7 @@
     }
 
     const r = compute(readInputs());
-    const name = $("lead-name").value.trim().split(/\s+/)[0];
-    $("success-line").textContent =
-      "Thanks " + name + " — your ROI report (" + usd0.format(Math.max(0, r.annual)) +
-      " / year) is on its way to " + emailInput.value.trim() + ".";
+    $("success-line").textContent = 'Preview complete. Nothing was sent.';
 
     // hide the fields, show success
     Array.from(leadForm.querySelectorAll(".field, .btn-block, .form-fine")).forEach((n) => (n.hidden = true));
diff --git a/recipes/roi/site/index.html b/recipes/roi/site/index.html
index 8eba270..c11311c 100644
--- a/recipes/roi/site/index.html
+++ b/recipes/roi/site/index.html
@@ -12,6 +12,12 @@
   <link rel="icon" href="data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 32 32'%3E%3Crect width='32' height='32' rx='8' fill='%234f46e5'/%3E%3Cpath d='M16 6l3 7 7 .6-5.3 4.6 1.7 7L16 27.5 9.6 31.2l1.7-7L6 19.6 13 19z' fill='%23ffffff' opacity='.0'/%3E%3Ccircle cx='16' cy='16' r='4.5' fill='%23fff'/%3E%3Ccircle cx='16' cy='16' r='9' fill='none' stroke='%23fff' stroke-width='1.6' opacity='.55'/%3E%3C/svg%3E" />
 </head>
 <body>
+    <aside
+      aria-label="Example site"
+      style="margin:0;padding:0.75rem 1rem;background:#fff7d6;color:#29221a;font:14px/1.5 system-ui;text-align:center"
+    >
+      Example site with fictional content. Forms are previews.
+    </aside>
   <header class="site-nav" aria-label="Primary">
     <div class="wrap nav-inner">
       <a class="brand" href="#top" aria-label="Beacon home">
@@ -212,6 +218,8 @@ <h2>Get the full ROI report as a PDF</h2>
           </ul>
         </div>
 
+        <p data-demo-note="true">Demo estimate. No email is sent.</p>
+
         <form class="card report-form" id="lead-form" novalidate>
           <div class="field">
             <label for="lead-name">Your name</label>
@@ -226,13 +234,13 @@ <h2>Get the full ROI report as a PDF</h2>
             <label for="lead-company">Company</label>
             <input type="text" id="lead-company" name="company" autocomplete="organization" placeholder="Acme Inc." />
           </div>
-          <button type="submit" class="btn btn-primary btn-block">Email me the report</button>
-          <p class="form-fine">Your snapshot: <strong id="lead-summary">$156,576 / year</strong>. No spam — one report, then we'll get out of your inbox.</p>
+          <button type="submit" class="btn btn-primary btn-block">Preview</button>
+          <p class="form-fine">Your snapshot: <strong id="lead-summary">$156,576 / year</strong>. Demo only. No report is emailed.</p>
 
           <div class="success" id="lead-success" hidden>
             <div class="success-check" aria-hidden="true">✓</div>
-            <h3>Report's on its way</h3>
-            <p id="success-line">We just emailed your ROI report. Check your inbox in a minute.</p>
+            <h3>Estimate preview complete</h3>
+            <p id="success-line">Preview complete. Nothing was sent.</p>
             <button type="button" class="link-btn" id="lead-reset">Run another scenario</button>
           </div>
         </form>
diff --git a/recipes/saas/meta.json b/recipes/saas/meta.json
index cdf7d68..d38f3a3 100644
--- a/recipes/saas/meta.json
+++ b/recipes/saas/meta.json
@@ -4,14 +4,14 @@
   "slug": "saas",
   "vertical": "Data, internal & startup",
   "tech": "Astro",
-  "summary": "A dark-mode B2B SaaS landing page for an issue tracker — hero screenshot, logo cloud, feature deep-dives, testimonials, pricing, and FAQ.",
+  "summary": "Introduce your SaaS product with a demo screenshot, features, and pricing.",
   "order": 8,
   "live_url": "https://saas.view.fast/",
   "setup_questions": [
     "What's the product name and the one-sentence outcome it delivers (e.g. \"plan, track, and ship product work in one place\")?",
     "Who is the target customer — what kind of team or role?",
     "What are your 3-4 core features to highlight?",
-    "Do you have customer or company names to use as social proof, or should I use realistic placeholders?"
+    "Which customer quotes or company names do I have permission to use? I will omit proof you do not supply."
   ],
   "photo_terms": [
     "saas dashboard ui screenshot dark mode",
diff --git a/recipes/saas/prompt.md b/recipes/saas/prompt.md
index 6e9a0a3..c3ac4d0 100644
--- a/recipes/saas/prompt.md
+++ b/recipes/saas/prompt.md
@@ -12,7 +12,7 @@ HTML/CSS).
 **Then build a complete, polished, responsive site with:**
 
 - A sticky nav with product / pricing / customers / docs links and a "Start free" CTA.
-- A hero: a one-line outcome headline, a sub-headline, an email-only signup, and a hero product screenshot.
+- A hero with a one-line outcome headline, a subhead, a signup link or form, and an HTML/CSS product mockup labelled as a demo. For any form that sends information, ask for my form endpoint or hosted signup URL. Use the supplied destination and show success only after it confirms receipt. A link to another service does not confirm completion. Without a destination, label the form "Demo only" beside its fields, label its button "Preview", and say "Preview complete. Nothing was sent." Never treat `localStorage` as delivery or store personal form data there.
 - A logo cloud / "trusted by" social-proof strip.
 - Three or four feature deep-dives, alternating image + copy (e.g. issues, sprints/cycles, roadmap, keyboard-driven workflow), each with a short bulleted list of specifics.
 - A metric / stat band ("Ship 30% faster") with three or four big numbers.
@@ -25,7 +25,7 @@ HTML/CSS).
 
 - Restrained, modern dark mode — near-black background, a single violet→cyan accent gradient, clean sans (Inter), tight letter-spacing on headings, generous whitespace. Think Linear / Vercel / Height.
 - For the product "screenshots", build a stylised app UI mock in HTML/CSS (a window with a sidebar, an issues board, a burndown chart, a roadmap, a command menu) rather than a stock photo — it looks far sharper and stays fast. Use real avatar photos for testimonials.
-- Use realistic content based on my answers — never "lorem ipsum". Invent believable issue titles, company names, testimonials, and pricing.
+- Use my actual features and prices. Include customer logos and testimonials only when I supply approved assets, quotes, and attribution. Label invented issue titles and product screens as demo content.
 - Use real images where photos make sense (testimonial avatars, any team shots). Pull free photos that fit, e.g. from Unsplash (`https://images.unsplash.com/...`) or `https://picsum.photos/seed/yourseed/96/96`, and add descriptive `alt` text.
 - Put copy in an Astro data module and loop over it in the page; split the product mock into its own component.
 - Keep it accessible (semantic HTML, a labelled email field, keyboard support, good contrast) and mobile-first (sidebar hides on small screens, plans stack, the featured plan floats to the top).
@@ -36,28 +36,12 @@ HTML/CSS).
 <script src="https://spacefast.com/badge.js" data-example="saas"></script>
 ```
 
-**When the site is ready, publish it to Spacefast with the direct API — no account, install, or extra instructions needed:**
+**When the site is ready, publish it to Spacefast:**
 
 1. Use `./dist` as the publish folder. For no-build projects, put only the finished public files in that dedicated folder. Confirm it has `index.html` at its root and no secrets, source files, `.git`, or `.spacefast` state.
-2. First publish: send every file as multipart form data. This Bash/Zsh block preserves relative paths and works for one file or a whole folder:
-   ```bash
-   PUBLISH_ROOT=./dist
-   publish_files=()
-   while IFS= read -r -d "" file; do
-     relative=${file#"$PUBLISH_ROOT"/}
-     publish_files+=(-F "files=@$file;filename=$relative")
-   done < <(find "$PUBLISH_ROOT" -type f -print0)
-   curl -sS "${publish_files[@]}" "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-3. From the `{ "data": ... }` receipt, give me `data.space.liveUrl`, `data.version.immutableUrl`, `data.claim.url`, and `data.claim.expiresAt`. Remind me to claim within 6 hours. Keep `data.claim.token` secret.
-4. Save `data.space.id` and `data.claim.token` locally (for example in an ignored, mode-600 `.spacefast/state.json`). For a quick update, rebuild the `publish_files` array above and publish to the same space:
-   ```bash
-   SPACEFAST_SPACE_ID=<saved-space-id>
-   SPACEFAST_TOKEN=<saved-claim-token-or-access-token>
-   curl -sS -H "Authorization: Bearer $SPACEFAST_TOKEN" \
-     -F "spaceId=$SPACEFAST_SPACE_ID" "${publish_files[@]}" \
-     "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-   If an update after claiming returns `space_claimed_credential_available`, exchange the saved claim token once at `POST https://api.spacefast.com/v1/anonymous-claim/exchange`, save `data.credential.accessToken`, and retry with that access token.
-
-**Optional shortcuts and reference only:** if the `sf` CLI is already installed, `sf publish ./dist --wait` does the same job. A zip of the publish folder is also supported, but neither the CLI nor a zip is required. Docs: [direct agent/API publishing](https://spacefast.com/setup) · [files and folders](https://spacefast.com/help/publishing) · [claiming](https://spacefast.com/help/anonymous-publish) · [updates and rollback](https://spacefast.com/help/versions)
+2. Fetch https://spacefast.com/setup.md and follow its current direct API publishing instructions. Check for an existing Space before creating one, and follow the returned upload and polling steps.
+3. Report success only when `data.next.action` is `done` and the intended version is serving. If more work is needed, report the returned next step.
+4. For an anonymous publish, give me `data.claim.message` unchanged. It contains the private preview (`data.claim.url`), the owner's claim link (`data.claim.claimUrl`), and the deadline (`data.claim.expiresAt`). Keep both links private. Never print the separate `data.claim.key`.
+5. Keep `data.space.id` and the returned credential securely for updates to the same Space. Follow the guide for credential recovery after claiming. Keep credentials and `.spacefast` state out of the published files, commits, and logs.
+
+If the `sf` CLI is already installed, `sf publish ./dist --wait` follows the same publishing flow. See [publishing](https://spacefast.com/docs/publish/) and [claiming a Space](https://spacefast.com/docs/anonymous-and-claim/).
diff --git a/recipes/saas/site/src/layouts/Base.astro b/recipes/saas/site/src/layouts/Base.astro
index 3c4c219..f453d1c 100644
--- a/recipes/saas/site/src/layouts/Base.astro
+++ b/recipes/saas/site/src/layouts/Base.astro
@@ -33,6 +33,12 @@ const { title, description } = Astro.props;
     />
   </head>
   <body>
+    <aside
+      aria-label="Example site"
+      style="margin:0;padding:0.75rem 1rem;background:#fff7d6;color:#29221a;font:14px/1.5 system-ui;text-align:center"
+    >
+      Example site with fictional content. Forms are previews.
+    </aside>
     <slot />
     <script src="https://spacefast.com/badge.js" data-example="saas"></script>
   </body>
diff --git a/recipes/saas/site/src/pages/index.astro b/recipes/saas/site/src/pages/index.astro
index 5db3d16..2931112 100644
--- a/recipes/saas/site/src/pages/index.astro
+++ b/recipes/saas/site/src/pages/index.astro
@@ -62,6 +62,8 @@ import {
       <h1>{site.tagline}</h1>
       <p class="lede">{site.sub}</p>
 
+      <p data-demo-note="true">Demo signup. No subscription is created and no email is sent.</p>
+
       <form class="signup" id="hero-form" novalidate>
         <label class="sr" for="hero-email">Work email</label>
         <input
@@ -73,9 +75,9 @@ import {
           placeholder="you@company.com"
           required
         />
-        <button class="btn btn-grad" type="submit">Start free</button>
+        <button class="btn btn-grad" type="submit">Preview</button>
         <p class="signup-ok" id="hero-ok" role="status" aria-live="polite" hidden>
-          You're in — check <b id="hero-ok-email">your inbox</b> for the magic link.
+          Preview for <b id="hero-ok-email">your email</b>. Nothing was sent.
         </p>
       </form>
       <p class="micro">Free for up to 10 members · No credit card · SOC 2 Type II</p>
@@ -260,6 +262,7 @@ import {
       <div class="cta-card">
         <h2>Plan your next cycle in Tideline</h2>
         <p>Set up your workspace in under two minutes. Free for up to 10 members.</p>
+        <p data-demo-note="true">Demo signup. No subscription is created and no email is sent.</p>
         <form class="signup signup-cta" id="cta-form" novalidate>
           <label class="sr" for="cta-email">Work email</label>
           <input
@@ -271,9 +274,9 @@ import {
             placeholder="you@company.com"
             required
           />
-          <button class="btn btn-primary" type="submit">Start free</button>
+          <button class="btn btn-primary" type="submit">Preview</button>
           <p class="signup-ok" id="cta-ok" role="status" aria-live="polite" hidden>
-            You're in — check <b id="cta-ok-email">your inbox</b> to finish setup.
+            Preview for <b id="cta-ok-email">your email</b>. Nothing was sent.
           </p>
         </form>
         <p class="micro">No credit card required · Cancel anytime</p>
@@ -337,7 +340,7 @@ import {
         ok.hidden = false;
         input.disabled = true;
         var btn = form.querySelector("button");
-        if (btn) { btn.disabled = true; btn.textContent = "Sent ✓"; }
+        if (btn) { btn.disabled = true; btn.textContent = "Preview complete"; }
       });
     }
     wire("hero-form", "hero-ok", "hero-ok-email");
diff --git a/recipes/savings/meta.json b/recipes/savings/meta.json
index 4a871ce..6813d99 100644
--- a/recipes/savings/meta.json
+++ b/recipes/savings/meta.json
@@ -4,7 +4,7 @@
   "slug": "savings",
   "vertical": "Tools, apps & games",
   "tech": "Vanilla JS",
-  "summary": "A savings-goal calculator — set a target and a deadline, and it solves your monthly contribution and charts the compound growth toward the goal.",
+  "summary": "Set a savings goal and deadline. Estimate monthly contributions and growth.",
   "order": 3,
   "live_url": "https://savings.view.fast/",
   "setup_questions": [
diff --git a/recipes/savings/prompt.md b/recipes/savings/prompt.md
index 4282a92..2d17a0e 100644
--- a/recipes/savings/prompt.md
+++ b/recipes/savings/prompt.md
@@ -55,28 +55,12 @@ Build me a **savings-goal calculator** as a vanilla-JS app (a single static site
 <script src="https://spacefast.com/badge.js" data-example="savings"></script>
 ```
 
-**When the site is ready, publish it to Spacefast with the direct API — no account, install, or extra instructions needed:**
+**When the site is ready, publish it to Spacefast:**
 
 1. Use `./site` as the publish folder. For no-build projects, put only the finished public files in that dedicated folder. Confirm it has `index.html` at its root and no secrets, source files, `.git`, or `.spacefast` state.
-2. First publish: send every file as multipart form data. This Bash/Zsh block preserves relative paths and works for one file or a whole folder:
-   ```bash
-   PUBLISH_ROOT=./site
-   publish_files=()
-   while IFS= read -r -d "" file; do
-     relative=${file#"$PUBLISH_ROOT"/}
-     publish_files+=(-F "files=@$file;filename=$relative")
-   done < <(find "$PUBLISH_ROOT" -type f -print0)
-   curl -sS "${publish_files[@]}" "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-3. From the `{ "data": ... }` receipt, give me `data.space.liveUrl`, `data.version.immutableUrl`, `data.claim.url`, and `data.claim.expiresAt`. Remind me to claim within 6 hours. Keep `data.claim.token` secret.
-4. Save `data.space.id` and `data.claim.token` locally (for example in an ignored, mode-600 `.spacefast/state.json`). For a quick update, rebuild the `publish_files` array above and publish to the same space:
-   ```bash
-   SPACEFAST_SPACE_ID=<saved-space-id>
-   SPACEFAST_TOKEN=<saved-claim-token-or-access-token>
-   curl -sS -H "Authorization: Bearer $SPACEFAST_TOKEN" \
-     -F "spaceId=$SPACEFAST_SPACE_ID" "${publish_files[@]}" \
-     "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-   If an update after claiming returns `space_claimed_credential_available`, exchange the saved claim token once at `POST https://api.spacefast.com/v1/anonymous-claim/exchange`, save `data.credential.accessToken`, and retry with that access token.
+2. Fetch https://spacefast.com/setup.md and follow its current direct API publishing instructions. Check for an existing Space before creating one, and follow the returned upload and polling steps.
+3. Report success only when `data.next.action` is `done` and the intended version is serving. If more work is needed, report the returned next step.
+4. For an anonymous publish, give me `data.claim.message` unchanged. It contains the private preview (`data.claim.url`), the owner's claim link (`data.claim.claimUrl`), and the deadline (`data.claim.expiresAt`). Keep both links private. Never print the separate `data.claim.key`.
+5. Keep `data.space.id` and the returned credential securely for updates to the same Space. Follow the guide for credential recovery after claiming. Keep credentials and `.spacefast` state out of the published files, commits, and logs.
 
-**Optional shortcuts and reference only:** if the `sf` CLI is already installed, `sf publish ./site --wait` does the same job. A zip of the publish folder is also supported, but neither the CLI nor a zip is required. Docs: [direct agent/API publishing](https://spacefast.com/setup) · [files and folders](https://spacefast.com/help/publishing) · [claiming](https://spacefast.com/help/anonymous-publish) · [updates and rollback](https://spacefast.com/help/versions)
+If the `sf` CLI is already installed, `sf publish ./site --wait` follows the same publishing flow. See [publishing](https://spacefast.com/docs/publish/) and [claiming a Space](https://spacefast.com/docs/anonymous-and-claim/).
diff --git a/recipes/soon/meta.json b/recipes/soon/meta.json
index 4792131..31dc915 100644
--- a/recipes/soon/meta.json
+++ b/recipes/soon/meta.json
@@ -4,7 +4,7 @@
   "slug": "soon",
   "vertical": "Data, internal & startup",
   "tech": "Vanilla JS",
-  "summary": "A single-screen coming-soon teaser with a live launch countdown, a validating email capture that confirms and remembers you, a waitlist counter, and social links.",
+  "summary": "Announce a launch with a countdown and a link to your signup form.",
   "order": 300,
   "live_url": "https://soon.view.fast/",
   "setup_questions": [
@@ -20,7 +20,7 @@
   "sections": [
     "Logo + serif headline + one-line promise",
     "Live launch countdown (days/hours/minutes/seconds) with a 'we're live' end state",
-    "Validating email capture with inline errors and a warm success state",
+    "Signup connected to your chosen service, or a labelled preview with no email sent",
     "Waitlist counter that ticks up once you've joined",
     "Social links + contact email"
   ],
diff --git a/recipes/soon/prompt.md b/recipes/soon/prompt.md
index e443424..6d99c7b 100644
--- a/recipes/soon/prompt.md
+++ b/recipes/soon/prompt.md
@@ -17,12 +17,8 @@ Build me a **single-screen "coming soon" teaser page** as a vanilla-JS app
 - A **live launch countdown** to the target date — days / hours / minutes /
   seconds, updating every second, with a tidy "Targeting <date>" line. When the
   date passes it should flip to a "We're live" state instead of going negative.
-- An **email capture** with real validation (friendly inline errors for empty
-  and malformed addresses) that swaps to a warm "You're on the list" success
-  state on submit, and remembers a returning visitor via localStorage so they
-  see the thank-you again instead of the form.
-- A subtle **waitlist counter** ("Join N builders already waiting") that ticks up
-  by one once you've joined.
+- An email capture with labelled fields and inline validation. Show a waitlist count only when I provide a verified count or a connected service returns it. Never increment it based only on local validation. For any form that sends information, ask for my form endpoint or hosted signup URL. Use the supplied destination and show success only after it confirms receipt. A link to another service does not confirm completion. Without a destination, label the form "Demo only" beside its fields, label its button "Preview", and say "Preview complete. Nothing was sent." Never treat `localStorage` as delivery or store personal form data there.
+- An optional waitlist counter from verified data. Omit it when no source is supplied.
 - A row of **social links** (X, GitHub, LinkedIn) plus a contact email.
 
 **Design & content notes:**
@@ -31,15 +27,14 @@ Build me a **single-screen "coming soon" teaser page** as a vanilla-JS app
   gradient "aurora" (amber → violet → rose) glowing up from the horizon, a
   frosted-glass card, and a fine film grain. A serif display face (e.g. Fraunces)
   for the headline and a clean sans (e.g. Inter) for everything else.
-- Use realistic content based on my answers — never "lorem ipsum". Invent a
-  believable promise and waitlist number if I leave gaps.
+- Write the product promise from my answers. Omit signup counts unless I provide verified data. Label a fictional product as a demo.
 - This page can stand entirely on its CSS gradient atmosphere — no hero photo
   needed. If you do add imagery (e.g. an Open Graph preview), use real free
   photos that fit, e.g. `https://picsum.photos/seed/soon-og/1200/630`, with
   descriptive `alt` text.
 - No build step — a single `index.html` with a linked CSS and JS file that opens
   straight in a browser. Drive the countdown from one editable `LAUNCH` date
-  constant; make the form actually validate; persist the signup in localStorage.
+  constant; make the form actually validate; use the signup destination rule above.
 - Keep it accessible (semantic HTML, a labelled email field, a skip link,
   keyboard support, `aria-live` on the countdown and form status, good contrast,
   and a `prefers-reduced-motion` fallback that stills the animation).
@@ -50,28 +45,12 @@ Build me a **single-screen "coming soon" teaser page** as a vanilla-JS app
 <script src="https://spacefast.com/badge.js" data-example="soon"></script>
 ```
 
-**When the site is ready, publish it to Spacefast with the direct API — no account, install, or extra instructions needed:**
+**When the site is ready, publish it to Spacefast:**
 
 1. Use `./site` as the publish folder. For no-build projects, put only the finished public files in that dedicated folder. Confirm it has `index.html` at its root and no secrets, source files, `.git`, or `.spacefast` state.
-2. First publish: send every file as multipart form data. This Bash/Zsh block preserves relative paths and works for one file or a whole folder:
-   ```bash
-   PUBLISH_ROOT=./site
-   publish_files=()
-   while IFS= read -r -d "" file; do
-     relative=${file#"$PUBLISH_ROOT"/}
-     publish_files+=(-F "files=@$file;filename=$relative")
-   done < <(find "$PUBLISH_ROOT" -type f -print0)
-   curl -sS "${publish_files[@]}" "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-3. From the `{ "data": ... }` receipt, give me `data.space.liveUrl`, `data.version.immutableUrl`, `data.claim.url`, and `data.claim.expiresAt`. Remind me to claim within 6 hours. Keep `data.claim.token` secret.
-4. Save `data.space.id` and `data.claim.token` locally (for example in an ignored, mode-600 `.spacefast/state.json`). For a quick update, rebuild the `publish_files` array above and publish to the same space:
-   ```bash
-   SPACEFAST_SPACE_ID=<saved-space-id>
-   SPACEFAST_TOKEN=<saved-claim-token-or-access-token>
-   curl -sS -H "Authorization: Bearer $SPACEFAST_TOKEN" \
-     -F "spaceId=$SPACEFAST_SPACE_ID" "${publish_files[@]}" \
-     "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-   If an update after claiming returns `space_claimed_credential_available`, exchange the saved claim token once at `POST https://api.spacefast.com/v1/anonymous-claim/exchange`, save `data.credential.accessToken`, and retry with that access token.
+2. Fetch https://spacefast.com/setup.md and follow its current direct API publishing instructions. Check for an existing Space before creating one, and follow the returned upload and polling steps.
+3. Report success only when `data.next.action` is `done` and the intended version is serving. If more work is needed, report the returned next step.
+4. For an anonymous publish, give me `data.claim.message` unchanged. It contains the private preview (`data.claim.url`), the owner's claim link (`data.claim.claimUrl`), and the deadline (`data.claim.expiresAt`). Keep both links private. Never print the separate `data.claim.key`.
+5. Keep `data.space.id` and the returned credential securely for updates to the same Space. Follow the guide for credential recovery after claiming. Keep credentials and `.spacefast` state out of the published files, commits, and logs.
 
-**Optional shortcuts and reference only:** if the `sf` CLI is already installed, `sf publish ./site --wait` does the same job. A zip of the publish folder is also supported, but neither the CLI nor a zip is required. Docs: [direct agent/API publishing](https://spacefast.com/setup) · [files and folders](https://spacefast.com/help/publishing) · [claiming](https://spacefast.com/help/anonymous-publish) · [updates and rollback](https://spacefast.com/help/versions)
+If the `sf` CLI is already installed, `sf publish ./site --wait` follows the same publishing flow. See [publishing](https://spacefast.com/docs/publish/) and [claiming a Space](https://spacefast.com/docs/anonymous-and-claim/).
diff --git a/recipes/soon/site/assets/app.js b/recipes/soon/site/assets/app.js
index 6382a14..a66de67 100644
--- a/recipes/soon/site/assets/app.js
+++ b/recipes/soon/site/assets/app.js
@@ -93,8 +93,7 @@
     form.hidden = true;
     success.hidden = false;
     if (successSub && email) {
-      successSub.textContent =
-        "We'll email " + email + " the moment Northpeak opens. No spam, just the invite.";
+      successSub.textContent = 'Preview complete. Nothing was sent.';
     }
     renderCount(true);
   }
diff --git a/recipes/soon/site/index.html b/recipes/soon/site/index.html
index 0f0111d..40cea37 100644
--- a/recipes/soon/site/index.html
+++ b/recipes/soon/site/index.html
@@ -20,6 +20,12 @@
   <link rel="stylesheet" href="assets/styles.css" />
 </head>
 <body>
+    <aside
+      aria-label="Example site"
+      style="margin:0;padding:0.75rem 1rem;background:#fff7d6;color:#29221a;font:14px/1.5 system-ui;text-align:center"
+    >
+      Example site with fictional content. Forms are previews.
+    </aside>
   <a class="skip-link" href="#signup">Skip to early-access signup</a>
 
   <!-- Animated atmosphere -->
@@ -77,6 +83,8 @@ <h2 id="cd-label" class="countdown__label">Launching in</h2>
       <section class="signup" id="signup" aria-labelledby="signup-label">
         <h2 id="signup-label" class="signup__label">Get early access</h2>
 
+        <p data-demo-note="true">Demo signup. No subscription is created and no email is sent.</p>
+
         <form class="form" id="signup-form" novalidate>
           <div class="form__row">
             <label class="visually-hidden" for="email">Email address</label>
@@ -105,8 +113,8 @@ <h2 id="signup-label" class="signup__label">Get early access</h2>
             <svg viewBox="0 0 24 24" width="22" height="22"><path d="M4 12.5l5 5L20 6.5" fill="none" stroke="currentColor" stroke-width="2.2" stroke-linecap="round" stroke-linejoin="round"/></svg>
           </span>
           <div class="success__body">
-            <p class="success__title">You're on the list.</p>
-            <p class="success__sub" id="success-sub">We'll email you the moment Northpeak opens. No spam, just the invite.</p>
+            <p class="success__title">Signup preview complete</p>
+            <p class="success__sub" id="success-sub">Preview complete. Nothing was sent.</p>
           </div>
         </div>
 
diff --git a/recipes/status/meta.json b/recipes/status/meta.json
index 846c66e..ced929c 100644
--- a/recipes/status/meta.json
+++ b/recipes/status/meta.json
@@ -4,7 +4,7 @@
   "slug": "status",
   "vertical": "Data, internal & startup",
   "tech": "Vanilla JS",
-  "summary": "A public status page for an API product — overall-status banner, per-component 90-day uptime bars, an incident timeline, scheduled maintenance, and a subscribe box.",
+  "summary": "Build a sample status page with service history, incidents, and maintenance notices.",
   "order": 14,
   "live_url": "https://status.view.fast/",
   "setup_questions": [
diff --git a/recipes/status/prompt.md b/recipes/status/prompt.md
index 27d77fa..f15a69d 100644
--- a/recipes/status/prompt.md
+++ b/recipes/status/prompt.md
@@ -14,13 +14,13 @@ Build me a **public status page for my API / hosting product** — the kind of p
 - An **active-incident block** with a posted-update **timeline** that reads newest-first through the standard lifecycle: Investigating → Identified → Monitoring → Resolved, each entry timestamped in UTC.
 - A **scheduled maintenance** section with one or two upcoming windows (date chip, what's happening, and the maintenance window in UTC + a local timezone).
 - A **past-incidents history** grouped by date, each incident with a severity pill, a duration, and its own compact resolution timeline.
-- A **subscribe-to-updates** box: an email field that validates, shows an inline error for bad input, and on success swaps to a friendly "You're subscribed" confirmation (persist it in `localStorage` so it stays confirmed on reload). Include alternate channels — a Twitter/X handle, an RSS feed, and a status-webhook link.
+- A subscribe-to-updates box with a labelled email field and inline validation. Include my actual alternate channels, such as RSS or a status feed. For any form that sends information, ask for my form endpoint or hosted signup URL. Use the supplied destination and show success only after it confirms receipt. A link to another service does not confirm completion. Without a destination, label the form "Demo only" beside its fields, label its button "Preview", and say "Preview complete. Nothing was sent." Never treat `localStorage` as delivery or store personal form data there.
 - A footer with the marketing site, docs, and support email.
 
 **Design & content notes:**
 
 - Calm, trustworthy NOC/dashboard aesthetic: dark navy background, generous whitespace, a single green "operational" accent plus amber/red/indigo for the other states, Inter for text and a monospace (e.g. JetBrains Mono) for timestamps and numbers. Status pages have a strict visual grammar — keep it clean and unambiguous.
-- Write real-sounding incident copy from my answers — never "lorem ipsum". Invent believable, specific incidents (e.g. "a bad config push removed a connection-pool limit and saturated the primary database"), realistic UTC timestamps, durations, and uptime numbers like 99.98%.
+- Use actual incident records and monitoring data when available. Otherwise label the banner, uptime charts, and incident history "Sample data, not live monitoring." Never present generated uptime as a measured reliability claim.
 - Generate the 90-day bars in JavaScript from per-component data so they're stable across reloads (a deterministic seed, with a few realistic blips), and compute each uptime percentage and the overall banner state from that data.
 - Use real images only where they help (this page is mostly UI). If you add any, pull free photos that fit, e.g. `https://picsum.photos/seed/server-room-1/1200/800`, with descriptive `alt` text.
 - Keep it accessible (semantic HTML, a labelled form, keyboard support, good contrast, `aria-label`s on the uptime bars and a polite live region on the banner) and mobile-first (the bars and timeline should reflow cleanly on a phone).
@@ -31,28 +31,12 @@ Build me a **public status page for my API / hosting product** — the kind of p
 <script src="https://spacefast.com/badge.js" data-example="status"></script>
 ```
 
-**When the site is ready, publish it to Spacefast with the direct API — no account, install, or extra instructions needed:**
+**When the site is ready, publish it to Spacefast:**
 
 1. Use `./site` as the publish folder. For no-build projects, put only the finished public files in that dedicated folder. Confirm it has `index.html` at its root and no secrets, source files, `.git`, or `.spacefast` state.
-2. First publish: send every file as multipart form data. This Bash/Zsh block preserves relative paths and works for one file or a whole folder:
-   ```bash
-   PUBLISH_ROOT=./site
-   publish_files=()
-   while IFS= read -r -d "" file; do
-     relative=${file#"$PUBLISH_ROOT"/}
-     publish_files+=(-F "files=@$file;filename=$relative")
-   done < <(find "$PUBLISH_ROOT" -type f -print0)
-   curl -sS "${publish_files[@]}" "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-3. From the `{ "data": ... }` receipt, give me `data.space.liveUrl`, `data.version.immutableUrl`, `data.claim.url`, and `data.claim.expiresAt`. Remind me to claim within 6 hours. Keep `data.claim.token` secret.
-4. Save `data.space.id` and `data.claim.token` locally (for example in an ignored, mode-600 `.spacefast/state.json`). For a quick update, rebuild the `publish_files` array above and publish to the same space:
-   ```bash
-   SPACEFAST_SPACE_ID=<saved-space-id>
-   SPACEFAST_TOKEN=<saved-claim-token-or-access-token>
-   curl -sS -H "Authorization: Bearer $SPACEFAST_TOKEN" \
-     -F "spaceId=$SPACEFAST_SPACE_ID" "${publish_files[@]}" \
-     "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-   If an update after claiming returns `space_claimed_credential_available`, exchange the saved claim token once at `POST https://api.spacefast.com/v1/anonymous-claim/exchange`, save `data.credential.accessToken`, and retry with that access token.
-
-**Optional shortcuts and reference only:** if the `sf` CLI is already installed, `sf publish ./site --wait` does the same job. A zip of the publish folder is also supported, but neither the CLI nor a zip is required. Docs: [direct agent/API publishing](https://spacefast.com/setup) · [files and folders](https://spacefast.com/help/publishing) · [claiming](https://spacefast.com/help/anonymous-publish) · [updates and rollback](https://spacefast.com/help/versions)
+2. Fetch https://spacefast.com/setup.md and follow its current direct API publishing instructions. Check for an existing Space before creating one, and follow the returned upload and polling steps.
+3. Report success only when `data.next.action` is `done` and the intended version is serving. If more work is needed, report the returned next step.
+4. For an anonymous publish, give me `data.claim.message` unchanged. It contains the private preview (`data.claim.url`), the owner's claim link (`data.claim.claimUrl`), and the deadline (`data.claim.expiresAt`). Keep both links private. Never print the separate `data.claim.key`.
+5. Keep `data.space.id` and the returned credential securely for updates to the same Space. Follow the guide for credential recovery after claiming. Keep credentials and `.spacefast` state out of the published files, commits, and logs.
+
+If the `sf` CLI is already installed, `sf publish ./site --wait` follows the same publishing flow. See [publishing](https://spacefast.com/docs/publish/) and [claiming a Space](https://spacefast.com/docs/anonymous-and-claim/).
diff --git a/recipes/status/site/index.html b/recipes/status/site/index.html
index 33e12d7..019f161 100644
--- a/recipes/status/site/index.html
+++ b/recipes/status/site/index.html
@@ -13,6 +13,12 @@
   <link rel="stylesheet" href="styles.css" />
 </head>
 <body>
+    <aside
+      aria-label="Example site"
+      style="margin:0;padding:0.75rem 1rem;background:#fff7d6;color:#29221a;font:14px/1.5 system-ui;text-align:center"
+    >
+      Example site with fictional content. Forms are previews.
+    </aside>
   <a class="skip-link" href="#main">Skip to status</a>
 
   <header class="site-header">
@@ -184,18 +190,19 @@ <h4>Planned Postgres upgrade to 16.3 — completed</h4>
           <h2 id="subscribe-h">Get notified</h2>
           <p>Subscribe to receive an email the moment we open or resolve an incident, plus a heads-up before scheduled maintenance.</p>
         </div>
+        <p data-demo-note="true">Demo signup. No subscription is created and no email is sent.</p>
         <form class="subscribe-form" id="subscribe-form" novalidate>
           <div class="field">
             <label for="email">Email address</label>
             <div class="field-row">
               <input type="email" id="email" name="email" inputmode="email" autocomplete="email" placeholder="you@company.com" required aria-describedby="subscribe-note" />
-              <button type="submit" class="btn-primary">Subscribe</button>
+              <button type="submit" class="btn-primary">Preview</button>
             </div>
             <p class="field-error" id="email-error" role="alert" hidden>Please enter a valid email address.</p>
             <p class="field-note" id="subscribe-note">No spam — incident notifications only. Unsubscribe anytime.</p>
           </div>
           <p class="subscribe-success" id="subscribe-success" role="status" hidden>
-            <span aria-hidden="true">✓</span> You're subscribed. We'll email <strong id="success-email"></strong> when status changes.
+            <span aria-hidden="true">✓</span> Preview complete for <strong id="success-email"></strong>. Nothing was sent or subscribed.
           </p>
         </form>
         <div class="subscribe-alt">
diff --git a/recipes/studio/meta.json b/recipes/studio/meta.json
index 7350a2d..48ef12c 100644
--- a/recipes/studio/meta.json
+++ b/recipes/studio/meta.json
@@ -4,7 +4,7 @@
   "slug": "studio",
   "vertical": "Data, internal & startup",
   "tech": "Vanilla JS",
-  "summary": "A work-first portfolio for a brand & web design studio — statement hero, a JS-filtered project grid, a before/after case study, and a contact form.",
+  "summary": "Show your design work, case studies, services, and contact details.",
   "order": 22,
   "live_url": "https://studio.view.fast/",
   "setup_questions": [
diff --git a/recipes/studio/prompt.md b/recipes/studio/prompt.md
index 19010f4..c74e7b5 100644
--- a/recipes/studio/prompt.md
+++ b/recipes/studio/prompt.md
@@ -24,8 +24,7 @@ Build me a **portfolio site for my brand &amp; web design studio** as a vanilla-
 - An **About / studio philosophy** section with a couple of paragraphs in the studio's
   voice and a small team grid (photo, name, role).
 - A **client logo strip** as a row of wordmarks.
-- A **contact form** (name, email, project type, message) that validates inline and
-  shows a friendly, personalized success state — no backend.
+- A contact form with name, email, project type, and message, with inline validation. For any form that sends information, ask for my form endpoint or hosted signup URL. Use the supplied destination and show success only after it confirms receipt. A link to another service does not confirm completion. Without a destination, label the form "Demo only" beside its fields, label its button "Preview", and say "Preview complete. Nothing was sent." Never treat `localStorage` as delivery or store personal form data there.
 - A footer with the studio email, social links, and location.
 
 **Design &amp; content notes:**
@@ -34,15 +33,13 @@ Build me a **portfolio site for my brand &amp; web design studio** as a vanilla-
   bold accent (a vermilion/coral). Pair a high-contrast serif display (Fraunces) for
   headlines with a clean grotesque (Space Grotesk) for body. Generous whitespace, a
   thin running marquee of disciplines, subtle hover lifts and image zooms — no slop.
-- Use realistic content based on my answers — never "lorem ipsum". Invent believable
-  project names, client quotes, result numbers, team members, and bios.
+- Use the projects, clients, results, team details, and quotes I provide. Omit client proof without approved facts and attribution. Label fictional case studies as sample work.
 - Use real images. Pull free photos that fit, e.g. from
   `https://picsum.photos/seed/northbound-studio-1/1200/800` (vary the seed per image)
   or fitting Unsplash photos of branding mockup flatlays, a design-studio workspace,
   bold typographic posters, and packaging — all with descriptive `alt` text.
 - Keep it accessible (semantic HTML, labelled form fields, good contrast, keyboard
-  support, a skip link) and mobile-first with a working hamburger menu. Persist nothing
-  to a server; do all interactivity (filter, before/after, form) in plain JS.
+  support, a skip link) and mobile-first with a working hamburger menu. Keep filters and before/after controls in plain JS. Use the contact destination rule above.
 
 **Add this exact line right before `</body>` so the site carries its badge:**
 
@@ -50,28 +47,12 @@ Build me a **portfolio site for my brand &amp; web design studio** as a vanilla-
 <script src="https://spacefast.com/badge.js" data-example="studio"></script>
 ```
 
-**When the site is ready, publish it to Spacefast with the direct API — no account, install, or extra instructions needed:**
+**When the site is ready, publish it to Spacefast:**
 
 1. Use `./site` as the publish folder. For no-build projects, put only the finished public files in that dedicated folder. Confirm it has `index.html` at its root and no secrets, source files, `.git`, or `.spacefast` state.
-2. First publish: send every file as multipart form data. This Bash/Zsh block preserves relative paths and works for one file or a whole folder:
-   ```bash
-   PUBLISH_ROOT=./site
-   publish_files=()
-   while IFS= read -r -d "" file; do
-     relative=${file#"$PUBLISH_ROOT"/}
-     publish_files+=(-F "files=@$file;filename=$relative")
-   done < <(find "$PUBLISH_ROOT" -type f -print0)
-   curl -sS "${publish_files[@]}" "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-3. From the `{ "data": ... }` receipt, give me `data.space.liveUrl`, `data.version.immutableUrl`, `data.claim.url`, and `data.claim.expiresAt`. Remind me to claim within 6 hours. Keep `data.claim.token` secret.
-4. Save `data.space.id` and `data.claim.token` locally (for example in an ignored, mode-600 `.spacefast/state.json`). For a quick update, rebuild the `publish_files` array above and publish to the same space:
-   ```bash
-   SPACEFAST_SPACE_ID=<saved-space-id>
-   SPACEFAST_TOKEN=<saved-claim-token-or-access-token>
-   curl -sS -H "Authorization: Bearer $SPACEFAST_TOKEN" \
-     -F "spaceId=$SPACEFAST_SPACE_ID" "${publish_files[@]}" \
-     "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-   If an update after claiming returns `space_claimed_credential_available`, exchange the saved claim token once at `POST https://api.spacefast.com/v1/anonymous-claim/exchange`, save `data.credential.accessToken`, and retry with that access token.
+2. Fetch https://spacefast.com/setup.md and follow its current direct API publishing instructions. Check for an existing Space before creating one, and follow the returned upload and polling steps.
+3. Report success only when `data.next.action` is `done` and the intended version is serving. If more work is needed, report the returned next step.
+4. For an anonymous publish, give me `data.claim.message` unchanged. It contains the private preview (`data.claim.url`), the owner's claim link (`data.claim.claimUrl`), and the deadline (`data.claim.expiresAt`). Keep both links private. Never print the separate `data.claim.key`.
+5. Keep `data.space.id` and the returned credential securely for updates to the same Space. Follow the guide for credential recovery after claiming. Keep credentials and `.spacefast` state out of the published files, commits, and logs.
 
-**Optional shortcuts and reference only:** if the `sf` CLI is already installed, `sf publish ./site --wait` does the same job. A zip of the publish folder is also supported, but neither the CLI nor a zip is required. Docs: [direct agent/API publishing](https://spacefast.com/setup) · [files and folders](https://spacefast.com/help/publishing) · [claiming](https://spacefast.com/help/anonymous-publish) · [updates and rollback](https://spacefast.com/help/versions)
+If the `sf` CLI is already installed, `sf publish ./site --wait` follows the same publishing flow. See [publishing](https://spacefast.com/docs/publish/) and [claiming a Space](https://spacefast.com/docs/anonymous-and-claim/).
diff --git a/recipes/studio/site/app.js b/recipes/studio/site/app.js
index 0df1e1b..47a24c8 100644
--- a/recipes/studio/site/app.js
+++ b/recipes/studio/site/app.js
@@ -127,11 +127,10 @@
       }
 
       // Personalize success copy
-      var firstName = data.name.split(" ")[0];
       var heading = document.getElementById("success-heading");
       var body = document.getElementById("success-body");
-      if (heading) heading.textContent = "Thanks, " + firstName + " — it's in our inbox.";
-      if (body) body.textContent = "We've noted you're after “" + data["project-type"] + "”. A real person will reply within two business days.";
+      if (heading) heading.textContent = 'Contact preview complete';
+      if (body) body.textContent = 'Preview complete. Nothing was sent.';
 
       form.hidden = true;
       if (success) {
diff --git a/recipes/studio/site/index.html b/recipes/studio/site/index.html
index 2e6d4e6..ac1a722 100644
--- a/recipes/studio/site/index.html
+++ b/recipes/studio/site/index.html
@@ -21,6 +21,12 @@
   <link rel="icon" href="data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 32 32'%3E%3Crect width='32' height='32' rx='7' fill='%2313110d'/%3E%3Cpath d='M9 23V9l14 14V9' fill='none' stroke='%23ec5b35' stroke-width='2.6' stroke-linecap='round' stroke-linejoin='round'/%3E%3C/svg%3E" />
 </head>
 <body>
+    <aside
+      aria-label="Example site"
+      style="margin:0;padding:0.75rem 1rem;background:#fff7d6;color:#29221a;font:14px/1.5 system-ui;text-align:center"
+    >
+      Example site with fictional content. Forms are previews.
+    </aside>
   <a class="skip-link" href="#main">Skip to content</a>
 
   <!-- ===== Header ===== -->
@@ -362,6 +368,8 @@ <h2 id="contact-title" class="section-title">Tell us what you're building.</h2>
           </ul>
         </div>
 
+        <p data-demo-note="true">Demo form. Nothing is sent or booked.</p>
+
         <form class="contact-form" id="contact-form" novalidate>
           <div class="field">
             <label for="name">Your name</label>
@@ -391,17 +399,17 @@ <h2 id="contact-title" class="section-title">Tell us what you're building.</h2>
             <textarea id="message" name="message" rows="4" required placeholder="We're a coffee roaster launching in spring and need a brand plus a shop site…"></textarea>
             <span class="error" data-for="message"></span>
           </div>
-          <button class="btn btn-solid btn-block" type="submit">Send it our way</button>
-          <p class="form-note">No newsletters, no spam — just a reply from a human.</p>
+          <button class="btn btn-solid btn-block" type="submit">Preview</button>
+          <p class="form-note">Demo only. No message is sent.</p>
         </form>
 
         <div class="contact-success" id="contact-success" hidden role="status">
           <div class="success-mark" aria-hidden="true">
             <svg width="44" height="44" viewBox="0 0 24 24" fill="none"><path d="M5 13l4 4L19 7" stroke="currentColor" stroke-width="2.4" stroke-linecap="round" stroke-linejoin="round"/></svg>
           </div>
-          <h3 id="success-heading">Thanks — it's in our inbox.</h3>
-          <p id="success-body">We'll be in touch soon.</p>
-          <button class="btn btn-text" type="button" id="reset-form">Send another →</button>
+          <h3 id="success-heading">Contact preview complete</h3>
+          <p id="success-body">Preview complete. Nothing was sent.</p>
+          <button class="btn btn-text" type="button" id="reset-form">Preview another →</button>
         </div>
       </div>
     </section>
diff --git a/recipes/technical-plan/meta.json b/recipes/technical-plan/meta.json
index 182d554..481261f 100644
--- a/recipes/technical-plan/meta.json
+++ b/recipes/technical-plan/meta.json
@@ -4,7 +4,7 @@
   "slug": "technical-plan",
   "vertical": "Data, internal & startup",
   "tech": "Plain HTML & CSS",
-  "summary": "A decision-ready technical plan for a cross-platform offline sync initiative — problem and scope, system architecture, milestones, risks, decisions, and open questions.",
+  "summary": "Share a technical plan with architecture, milestones, risks, and open decisions.",
   "order": 4,
   "live_url": "https://technical-plan.view.fast/",
   "setup_questions": [
diff --git a/recipes/technical-plan/prompt.md b/recipes/technical-plan/prompt.md
index 4866801..cf1a9ec 100644
--- a/recipes/technical-plan/prompt.md
+++ b/recipes/technical-plan/prompt.md
@@ -59,45 +59,13 @@ If I skip anything, choose a sensible default and tell me what you chose:**
 <script src="https://spacefast.com/badge.js" data-example="technical-plan"></script>
 ```
 
-**When the site is ready, publish it to Spacefast with the direct API — no account,
-install, or extra instructions needed:**
+**When the site is ready, publish it to Spacefast:**
 
 1. Use `./site` as the publish folder. Put only the finished public files there.
-   Confirm it has `index.html` at its root and no secrets, source-only files, `.git`,
-   or `.spacefast` state.
-2. First publish: send every file as multipart form data. This Bash/Zsh block
-   preserves relative paths and works for one file or a whole folder:
-   ```bash
-   PUBLISH_ROOT=./site
-   publish_files=()
-   while IFS= read -r -d "" file; do
-     relative=${file#"$PUBLISH_ROOT"/}
-     publish_files+=(-F "files=@$file;filename=$relative")
-   done < <(find "$PUBLISH_ROOT" -type f -print0)
-   curl -sS "${publish_files[@]}" "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-3. From the `{ "data": ... }` receipt, give me `data.space.liveUrl`,
-   `data.version.immutableUrl`, `data.claim.url`, and `data.claim.expiresAt`.
-   Remind me to claim within 6 hours. Keep `data.claim.token` secret.
-4. Save `data.space.id` and `data.claim.token` locally (for example in an ignored,
-   mode-600 `.spacefast/state.json`). For an update, rebuild the `publish_files`
-   array and publish to the same space:
-   ```bash
-   SPACEFAST_SPACE_ID=<saved-space-id>
-   SPACEFAST_TOKEN=<saved-claim-token-or-access-token>
-   curl -sS -H "Authorization: Bearer $SPACEFAST_TOKEN" \
-     -F "spaceId=$SPACEFAST_SPACE_ID" "${publish_files[@]}" \
-     "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-   If an update after claiming returns `space_claimed_credential_available`,
-   exchange the saved claim token once at
-   `POST https://api.spacefast.com/v1/anonymous-claim/exchange`, save
-   `data.credential.accessToken`, and retry with that access token.
+   Confirm it has `index.html` at its root and no secrets, source-only files, `.git`, or `.spacefast` state.
+2. Fetch https://spacefast.com/setup.md and follow its current direct API publishing instructions. Check for an existing Space before creating one, and follow the returned upload and polling steps.
+3. Report success only when `data.next.action` is `done` and the intended version is serving. If more work is needed, report the returned next step.
+4. For an anonymous publish, give me `data.claim.message` unchanged. It contains the private preview (`data.claim.url`), the owner's claim link (`data.claim.claimUrl`), and the deadline (`data.claim.expiresAt`). Keep both links private. Never print the separate `data.claim.key`.
+5. Keep `data.space.id` and the returned credential securely for updates to the same Space. Follow the guide for credential recovery after claiming. Keep credentials and `.spacefast` state out of the published files, commits, and logs.
 
-**Optional shortcuts and reference only:** if the `sf` CLI is already installed,
-`sf publish ./site --wait` does the same job. A zip of the publish folder is also
-supported, but neither the CLI nor a zip is required. Docs:
-[agent setup](https://spacefast.com/setup) ·
-[files and folders](https://spacefast.com/help/publishing) ·
-[claiming](https://spacefast.com/help/anonymous-publish) ·
-[updates and rollback](https://spacefast.com/help/versions)
+If the `sf` CLI is already installed, `sf publish ./site --wait` follows the same publishing flow. See [publishing](https://spacefast.com/docs/publish/) and [claiming a Space](https://spacefast.com/docs/anonymous-and-claim/).
diff --git a/recipes/tip/meta.json b/recipes/tip/meta.json
index 9ffc40d..f965f58 100644
--- a/recipes/tip/meta.json
+++ b/recipes/tip/meta.json
@@ -4,7 +4,7 @@
   "slug": "tip",
   "vertical": "Tools, apps & games",
   "tech": "Vanilla JS",
-  "summary": "A fast bill-and-tip splitter — enter the bill, tap a tip, set the people, and get a clean per-person amount with tip figured on the pre-tax total.",
+  "summary": "Split a bill and tip. Choose the party size and whether the tip includes tax.",
   "order": 1,
   "live_url": "https://tip.view.fast/",
   "setup_questions": [
diff --git a/recipes/tip/prompt.md b/recipes/tip/prompt.md
index 1fb7501..0636d93 100644
--- a/recipes/tip/prompt.md
+++ b/recipes/tip/prompt.md
@@ -42,28 +42,12 @@ CSS and a JS file, no build step, no framework).
 <script src="https://spacefast.com/badge.js" data-example="tip"></script>
 ```
 
-**When the site is ready, publish it to Spacefast with the direct API — no account, install, or extra instructions needed:**
+**When the site is ready, publish it to Spacefast:**
 
 1. Use `./site` as the publish folder. For no-build projects, put only the finished public files in that dedicated folder. Confirm it has `index.html` at its root and no secrets, source files, `.git`, or `.spacefast` state.
-2. First publish: send every file as multipart form data. This Bash/Zsh block preserves relative paths and works for one file or a whole folder:
-   ```bash
-   PUBLISH_ROOT=./site
-   publish_files=()
-   while IFS= read -r -d "" file; do
-     relative=${file#"$PUBLISH_ROOT"/}
-     publish_files+=(-F "files=@$file;filename=$relative")
-   done < <(find "$PUBLISH_ROOT" -type f -print0)
-   curl -sS "${publish_files[@]}" "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-3. From the `{ "data": ... }` receipt, give me `data.space.liveUrl`, `data.version.immutableUrl`, `data.claim.url`, and `data.claim.expiresAt`. Remind me to claim within 6 hours. Keep `data.claim.token` secret.
-4. Save `data.space.id` and `data.claim.token` locally (for example in an ignored, mode-600 `.spacefast/state.json`). For a quick update, rebuild the `publish_files` array above and publish to the same space:
-   ```bash
-   SPACEFAST_SPACE_ID=<saved-space-id>
-   SPACEFAST_TOKEN=<saved-claim-token-or-access-token>
-   curl -sS -H "Authorization: Bearer $SPACEFAST_TOKEN" \
-     -F "spaceId=$SPACEFAST_SPACE_ID" "${publish_files[@]}" \
-     "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-   If an update after claiming returns `space_claimed_credential_available`, exchange the saved claim token once at `POST https://api.spacefast.com/v1/anonymous-claim/exchange`, save `data.credential.accessToken`, and retry with that access token.
+2. Fetch https://spacefast.com/setup.md and follow its current direct API publishing instructions. Check for an existing Space before creating one, and follow the returned upload and polling steps.
+3. Report success only when `data.next.action` is `done` and the intended version is serving. If more work is needed, report the returned next step.
+4. For an anonymous publish, give me `data.claim.message` unchanged. It contains the private preview (`data.claim.url`), the owner's claim link (`data.claim.claimUrl`), and the deadline (`data.claim.expiresAt`). Keep both links private. Never print the separate `data.claim.key`.
+5. Keep `data.space.id` and the returned credential securely for updates to the same Space. Follow the guide for credential recovery after claiming. Keep credentials and `.spacefast` state out of the published files, commits, and logs.
 
-**Optional shortcuts and reference only:** if the `sf` CLI is already installed, `sf publish ./site --wait` does the same job. A zip of the publish folder is also supported, but neither the CLI nor a zip is required. Docs: [direct agent/API publishing](https://spacefast.com/setup) · [files and folders](https://spacefast.com/help/publishing) · [claiming](https://spacefast.com/help/anonymous-publish) · [updates and rollback](https://spacefast.com/help/versions)
+If the `sf` CLI is already installed, `sf publish ./site --wait` follows the same publishing flow. See [publishing](https://spacefast.com/docs/publish/) and [claiming a Space](https://spacefast.com/docs/anonymous-and-claim/).
diff --git a/recipes/trailhead/meta.json b/recipes/trailhead/meta.json
index 2800ca3..90918af 100644
--- a/recipes/trailhead/meta.json
+++ b/recipes/trailhead/meta.json
@@ -4,7 +4,7 @@
   "slug": "trailhead",
   "vertical": "Developers & integrations",
   "tech": "Next.js static export",
-  "summary": "A photo-led hiking guide built with the Next.js App Router, exported to flat HTML with `output: \"export\"` and served with accelerated images, redirects, and security headers.",
+  "summary": "Publish a hiking guide with trail details, photographs, and practical visitor information.",
   "order": 220,
   "live_url": "https://trailhead.view.fast/",
   "setup_questions": [
diff --git a/recipes/trailhead/prompt.md b/recipes/trailhead/prompt.md
index 0445e85..f23275e 100644
--- a/recipes/trailhead/prompt.md
+++ b/recipes/trailhead/prompt.md
@@ -63,29 +63,14 @@ Build me a **hiking trail guide** as a **Next.js static export** — an index of
 
 Put it in the root layout so every generated page gets it, and confirm it's in the built HTML — not injected by a client-side script tag helper, which would leave it out of the export.
 
-**When the site is ready, publish it to Spacefast with the direct API — no account, install, or extra instructions needed:**
+**When the site is ready, publish it to Spacefast:**
 
 1. Build first (`bun run build` / `npm run build`), then use `./out` as the publish folder. Confirm it has `index.html` at its root, plus `_redirects` and `_headers`, and no secrets, source files, `.git`, or `.spacefast` state.
-2. First publish: send every file as multipart form data. This Bash/Zsh block preserves relative paths and works for one file or a whole folder:
-   ```bash
-   PUBLISH_ROOT=./out
-   publish_files=()
-   while IFS= read -r -d "" file; do
-     relative=${file#"$PUBLISH_ROOT"/}
-     publish_files+=(-F "files=@$file;filename=$relative")
-   done < <(find "$PUBLISH_ROOT" -type f -print0)
-   curl -sS "${publish_files[@]}" "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-3. From the `{ "data": ... }` receipt, give me `data.space.liveUrl`, `data.version.immutableUrl`, `data.claim.url`, and `data.claim.expiresAt`. Remind me to claim within 6 hours. Keep `data.claim.token` secret.
-4. Save `data.space.id` and `data.claim.token` locally (for example in an ignored, mode-600 `.spacefast/state.json`). For a quick update, rebuild the `publish_files` array above and publish to the same space:
-   ```bash
-   SPACEFAST_SPACE_ID=<saved-space-id>
-   SPACEFAST_TOKEN=<saved-claim-token-or-access-token>
-   curl -sS -H "Authorization: Bearer $SPACEFAST_TOKEN" \
-     -F "spaceId=$SPACEFAST_SPACE_ID" "${publish_files[@]}" \
-     "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-   If an update after claiming returns `space_claimed_credential_available`, exchange the saved claim token once at `POST https://api.spacefast.com/v1/anonymous-claim/exchange`, save `data.credential.accessToken`, and retry with that access token.
-5. Then check the live site: `curl -sI <liveUrl>/trails/` should show your 301, and the trail pages' image URLs should point at `i0.wp.com`.
+2. Fetch https://spacefast.com/setup.md and follow its current direct API publishing instructions. Check for an existing Space before creating one, and follow the returned upload and polling steps.
+3. Report success only when `data.next.action` is `done` and the intended version is serving. If more work is needed, report the returned next step.
+4. For an anonymous publish, give me `data.claim.message` unchanged. It contains the private preview (`data.claim.url`), the owner's claim link (`data.claim.claimUrl`), and the deadline (`data.claim.expiresAt`). Keep both links private. Never print the separate `data.claim.key`.
+5. Keep `data.space.id` and the returned credential securely for updates to the same Space. Follow the guide for credential recovery after claiming. Keep credentials and `.spacefast` state out of the published files, commits, and logs.
+
+6. Using the returned access method, check that `/trails/` returns your 301 and the trail pages' built image URLs point at `i0.wp.com`.
 
-**Optional shortcuts and reference only:** if the `sf` CLI is already installed, `sf publish ./out --wait` does the same job. A zip of the publish folder is also supported, but neither the CLI nor a zip is required. Docs: [Next.js on Spacefast](https://spacefast.com/docs/frameworks) · [redirects](https://spacefast.com/docs/redirects) · [headers and settings](https://spacefast.com/docs/configuration) · [agent setup](https://spacefast.com/setup) · [claiming](https://spacefast.com/help/anonymous-publish)
+If the `sf` CLI is already installed, `sf publish ./out --wait` follows the same publishing flow. See [publishing](https://spacefast.com/docs/publish/) and [claiming a Space](https://spacefast.com/docs/anonymous-and-claim/).
diff --git a/recipes/unfurl/meta.json b/recipes/unfurl/meta.json
index b98e74d..b25926b 100644
--- a/recipes/unfurl/meta.json
+++ b/recipes/unfurl/meta.json
@@ -5,7 +5,7 @@
   "vertical": "Developers & integrations",
   "tech": "Next.js SSR (Functions)",
   "runtime": "functions",
-  "summary": "Paste any URL and the server fetches it, parses its OpenGraph and Twitter-card metadata, and renders the social preview card — a Next.js Route Handler plus an SSR page running on the Spacefast Functions runtime.",
+  "summary": "Inspect a public page's social preview. The server fetches its title, description, and image.",
   "order": 210,
   "live_url": "https://unfurl.view.fast/",
   "setup_questions": [
diff --git a/recipes/unfurl/prompt.md b/recipes/unfurl/prompt.md
index dc69b48..abc4add 100644
--- a/recipes/unfurl/prompt.md
+++ b/recipes/unfurl/prompt.md
@@ -55,13 +55,9 @@ Build me a **link preview inspector** as a **Next.js app that runs on a server**
    sf publish --wait --json
    ```
    Spacefast uploads the source, runs `next build`, bundles the output with the pinned OpenNext Cloudflare adapter, and ships the static half and the worker as one version.
-4. From the `{ "data": … }` receipt, give me `data.space.liveUrl`, `data.version.immutableUrl`, `data.claim.url`, and `data.claim.expiresAt`. Remind me to claim within 6 hours. Keep `data.claim.token` secret — the CLI already saved it under `.spacefast/`, which must stay out of git.
-5. Claim the space with `data.claim.url` (or publish while logged in). An unclaimed space may only call a short list of trusted APIs, so until it's claimed every unfurl comes back as a 403 from the target site.
-6. Prove it's really running server-side, and show me the output:
-   ```bash
-   curl -s "<liveUrl>api/unfurl?url=https://github.com/vercel/next.js" | head -c 600
-   curl -s "<liveUrl>u?url=https://github.com/vercel/next.js" | grep -o '<title>[^<]*</title>'
-   ```
+4. For an anonymous publish, give me `data.claim.message` unchanged. It contains the private preview, the owner's `data.claim.claimUrl`, and the returned deadline. Keep both links private and never print the separate `data.claim.key`. The CLI saves credentials under `.spacefast/`, which must stay out of git and published files.
+5. Ask me to open `data.claim.claimUrl` to claim the Space, or publish while logged in. Unclaimed Spaces have restricted outbound network access, so arbitrary unfurl targets may be refused until the Space is claimed.
+6. Use the returned access method to check `/api/unfurl?url=https://github.com/vercel/next.js` and `/u?url=https://github.com/vercel/next.js`. Show me the returned metadata and page title to prove the server-side route works. A private Space's bare URL does not grant access.
 7. To ship an update later, run `sf publish --wait` again from the same directory. The CLI remembers the space.
 
 **Optional and reference only:** `sf publish --dry-run --json` prints the resolved plan as JSON if you want to inspect the detected framework and output directory. Docs: [Functions runtime](https://spacefast.com/docs/functions) · [Next.js on Spacefast](https://spacefast.com/docs/frameworks) · [agent setup](https://spacefast.com/setup) · [claiming](https://spacefast.com/help/anonymous-publish) · [updates and rollback](https://spacefast.com/help/versions)
diff --git a/recipes/word-game/meta.json b/recipes/word-game/meta.json
index d567dcd..c24dc44 100644
--- a/recipes/word-game/meta.json
+++ b/recipes/word-game/meta.json
@@ -4,7 +4,7 @@
   "slug": "word-game",
   "vertical": "Tools, apps & games",
   "tech": "Vanilla JS",
-  "summary": "A daily five-letter word game — six guesses, green/yellow/gray tiles, streak stats, and a shareable emoji grid.",
+  "summary": "Play a daily five-letter word puzzle and share your result.",
   "order": 6,
   "live_url": "https://word-game.view.fast/",
   "setup_questions": [
diff --git a/recipes/word-game/prompt.md b/recipes/word-game/prompt.md
index df3831e..55df19a 100644
--- a/recipes/word-game/prompt.md
+++ b/recipes/word-game/prompt.md
@@ -51,28 +51,12 @@ no framework and no build step.
 <script src="https://spacefast.com/badge.js" data-example="word-game"></script>
 ```
 
-**When the site is ready, publish it to Spacefast with the direct API — no account, install, or extra instructions needed:**
+**When the site is ready, publish it to Spacefast:**
 
 1. Use `./site` as the publish folder. For no-build projects, put only the finished public files in that dedicated folder. Confirm it has `index.html` at its root and no secrets, source files, `.git`, or `.spacefast` state.
-2. First publish: send every file as multipart form data. This Bash/Zsh block preserves relative paths and works for one file or a whole folder:
-   ```bash
-   PUBLISH_ROOT=./site
-   publish_files=()
-   while IFS= read -r -d "" file; do
-     relative=${file#"$PUBLISH_ROOT"/}
-     publish_files+=(-F "files=@$file;filename=$relative")
-   done < <(find "$PUBLISH_ROOT" -type f -print0)
-   curl -sS "${publish_files[@]}" "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-3. From the `{ "data": ... }` receipt, give me `data.space.liveUrl`, `data.version.immutableUrl`, `data.claim.url`, and `data.claim.expiresAt`. Remind me to claim within 6 hours. Keep `data.claim.token` secret.
-4. Save `data.space.id` and `data.claim.token` locally (for example in an ignored, mode-600 `.spacefast/state.json`). For a quick update, rebuild the `publish_files` array above and publish to the same space:
-   ```bash
-   SPACEFAST_SPACE_ID=<saved-space-id>
-   SPACEFAST_TOKEN=<saved-claim-token-or-access-token>
-   curl -sS -H "Authorization: Bearer $SPACEFAST_TOKEN" \
-     -F "spaceId=$SPACEFAST_SPACE_ID" "${publish_files[@]}" \
-     "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-   If an update after claiming returns `space_claimed_credential_available`, exchange the saved claim token once at `POST https://api.spacefast.com/v1/anonymous-claim/exchange`, save `data.credential.accessToken`, and retry with that access token.
+2. Fetch https://spacefast.com/setup.md and follow its current direct API publishing instructions. Check for an existing Space before creating one, and follow the returned upload and polling steps.
+3. Report success only when `data.next.action` is `done` and the intended version is serving. If more work is needed, report the returned next step.
+4. For an anonymous publish, give me `data.claim.message` unchanged. It contains the private preview (`data.claim.url`), the owner's claim link (`data.claim.claimUrl`), and the deadline (`data.claim.expiresAt`). Keep both links private. Never print the separate `data.claim.key`.
+5. Keep `data.space.id` and the returned credential securely for updates to the same Space. Follow the guide for credential recovery after claiming. Keep credentials and `.spacefast` state out of the published files, commits, and logs.
 
-**Optional shortcuts and reference only:** if the `sf` CLI is already installed, `sf publish ./site --wait` does the same job. A zip of the publish folder is also supported, but neither the CLI nor a zip is required. Docs: [direct agent/API publishing](https://spacefast.com/setup) · [files and folders](https://spacefast.com/help/publishing) · [claiming](https://spacefast.com/help/anonymous-publish) · [updates and rollback](https://spacefast.com/help/versions)
+If the `sf` CLI is already installed, `sf publish ./site --wait` follows the same publishing flow. See [publishing](https://spacefast.com/docs/publish/) and [claiming a Space](https://spacefast.com/docs/anonymous-and-claim/).
diff --git a/recipes/wp-astro/meta.json b/recipes/wp-astro/meta.json
index d2b1179..754c10c 100644
--- a/recipes/wp-astro/meta.json
+++ b/recipes/wp-astro/meta.json
@@ -4,14 +4,14 @@
   "slug": "wp-astro",
   "vertical": "Developers & integrations",
   "tech": "Astro + WP REST API",
-  "summary": "A static editorial blog whose posts are pulled from a public WordPress REST API at build time and rendered to flat HTML with Astro — headless WordPress, no server at request time.",
+  "summary": "Build a static Astro blog from posts in a public WordPress site.",
   "order": 200,
   "live_url": "https://wp-astro.view.fast/",
   "setup_questions": [
     "What's the WordPress site to pull from (the REST API base, e.g. https://wordpress.org/news/wp-json/wp/v2)?",
     "What should the blog be called?",
     "Which categories, authors, or content types should be featured or excluded?",
-    "What's the accent color (a hex like"
+    "What accent color should the site use? For example, #0b6e4f."
   ],
   "photo_terms": [
     "wordpress dashboard on laptop screen",
diff --git a/recipes/wp-astro/prompt.md b/recipes/wp-astro/prompt.md
index 672e5db..f8afb37 100644
--- a/recipes/wp-astro/prompt.md
+++ b/recipes/wp-astro/prompt.md
@@ -31,28 +31,12 @@ Build me a **headless WordPress blog** as an **Astro site** that fetches posts f
 <script src="https://spacefast.com/badge.js" data-example="wp-astro"></script>
 ```
 
-**When the site is ready, publish it to Spacefast with the direct API — no account, install, or extra instructions needed:**
+**When the site is ready, publish it to Spacefast:**
 
 1. Use `./dist` as the publish folder. For no-build projects, put only the finished public files in that dedicated folder. Confirm it has `index.html` at its root and no secrets, source files, `.git`, or `.spacefast` state.
-2. First publish: send every file as multipart form data. This Bash/Zsh block preserves relative paths and works for one file or a whole folder:
-   ```bash
-   PUBLISH_ROOT=./dist
-   publish_files=()
-   while IFS= read -r -d "" file; do
-     relative=${file#"$PUBLISH_ROOT"/}
-     publish_files+=(-F "files=@$file;filename=$relative")
-   done < <(find "$PUBLISH_ROOT" -type f -print0)
-   curl -sS "${publish_files[@]}" "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-3. From the `{ "data": ... }` receipt, give me `data.space.liveUrl`, `data.version.immutableUrl`, `data.claim.url`, and `data.claim.expiresAt`. Remind me to claim within 6 hours. Keep `data.claim.token` secret.
-4. Save `data.space.id` and `data.claim.token` locally (for example in an ignored, mode-600 `.spacefast/state.json`). For a quick update, rebuild the `publish_files` array above and publish to the same space:
-   ```bash
-   SPACEFAST_SPACE_ID=<saved-space-id>
-   SPACEFAST_TOKEN=<saved-claim-token-or-access-token>
-   curl -sS -H "Authorization: Bearer $SPACEFAST_TOKEN" \
-     -F "spaceId=$SPACEFAST_SPACE_ID" "${publish_files[@]}" \
-     "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-   If an update after claiming returns `space_claimed_credential_available`, exchange the saved claim token once at `POST https://api.spacefast.com/v1/anonymous-claim/exchange`, save `data.credential.accessToken`, and retry with that access token.
-
-**Optional shortcuts and reference only:** if the `sf` CLI is already installed, `sf publish ./dist --wait` does the same job. A zip of the publish folder is also supported, but neither the CLI nor a zip is required. Docs: [direct agent/API publishing](https://spacefast.com/setup) · [files and folders](https://spacefast.com/help/publishing) · [claiming](https://spacefast.com/help/anonymous-publish) · [updates and rollback](https://spacefast.com/help/versions)
+2. Fetch https://spacefast.com/setup.md and follow its current direct API publishing instructions. Check for an existing Space before creating one, and follow the returned upload and polling steps.
+3. Report success only when `data.next.action` is `done` and the intended version is serving. If more work is needed, report the returned next step.
+4. For an anonymous publish, give me `data.claim.message` unchanged. It contains the private preview (`data.claim.url`), the owner's claim link (`data.claim.claimUrl`), and the deadline (`data.claim.expiresAt`). Keep both links private. Never print the separate `data.claim.key`.
+5. Keep `data.space.id` and the returned credential securely for updates to the same Space. Follow the guide for credential recovery after claiming. Keep credentials and `.spacefast` state out of the published files, commits, and logs.
+
+If the `sf` CLI is already installed, `sf publish ./dist --wait` follows the same publishing flow. See [publishing](https://spacefast.com/docs/publish/) and [claiming a Space](https://spacefast.com/docs/anonymous-and-claim/).
diff --git a/recipes/wp-react/meta.json b/recipes/wp-react/meta.json
index c5b0a7a..af13714 100644
--- a/recipes/wp-react/meta.json
+++ b/recipes/wp-react/meta.json
@@ -4,7 +4,7 @@
   "slug": "wp-react",
   "vertical": "Developers & integrations",
   "tech": "Vite + React + WP REST API",
-  "summary": "A polished reading app that fetches posts live from a WordPress REST API in the browser — card list, article view, client-side routing, search, and real loading/error states.",
+  "summary": "Browse and search WordPress posts in a React app that fetches them as you read.",
   "order": 201,
   "live_url": "https://wp-react.view.fast/",
   "setup_questions": [
diff --git a/recipes/wp-react/prompt.md b/recipes/wp-react/prompt.md
index 350940f..67ed5c6 100644
--- a/recipes/wp-react/prompt.md
+++ b/recipes/wp-react/prompt.md
@@ -58,28 +58,12 @@ fetches the content at runtime, no backend, no server-side rendering).
 <script src="https://spacefast.com/badge.js" data-example="wp-react"></script>
 ```
 
-**When the site is ready, publish it to Spacefast with the direct API — no account, install, or extra instructions needed:**
+**When the site is ready, publish it to Spacefast:**
 
 1. Use `./dist` as the publish folder. For no-build projects, put only the finished public files in that dedicated folder. Confirm it has `index.html` at its root and no secrets, source files, `.git`, or `.spacefast` state.
-2. First publish: send every file as multipart form data. This Bash/Zsh block preserves relative paths and works for one file or a whole folder:
-   ```bash
-   PUBLISH_ROOT=./dist
-   publish_files=()
-   while IFS= read -r -d "" file; do
-     relative=${file#"$PUBLISH_ROOT"/}
-     publish_files+=(-F "files=@$file;filename=$relative")
-   done < <(find "$PUBLISH_ROOT" -type f -print0)
-   curl -sS "${publish_files[@]}" "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-3. From the `{ "data": ... }` receipt, give me `data.space.liveUrl`, `data.version.immutableUrl`, `data.claim.url`, and `data.claim.expiresAt`. Remind me to claim within 6 hours. Keep `data.claim.token` secret.
-4. Save `data.space.id` and `data.claim.token` locally (for example in an ignored, mode-600 `.spacefast/state.json`). For a quick update, rebuild the `publish_files` array above and publish to the same space:
-   ```bash
-   SPACEFAST_SPACE_ID=<saved-space-id>
-   SPACEFAST_TOKEN=<saved-claim-token-or-access-token>
-   curl -sS -H "Authorization: Bearer $SPACEFAST_TOKEN" \
-     -F "spaceId=$SPACEFAST_SPACE_ID" "${publish_files[@]}" \
-     "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-   If an update after claiming returns `space_claimed_credential_available`, exchange the saved claim token once at `POST https://api.spacefast.com/v1/anonymous-claim/exchange`, save `data.credential.accessToken`, and retry with that access token.
+2. Fetch https://spacefast.com/setup.md and follow its current direct API publishing instructions. Check for an existing Space before creating one, and follow the returned upload and polling steps.
+3. Report success only when `data.next.action` is `done` and the intended version is serving. If more work is needed, report the returned next step.
+4. For an anonymous publish, give me `data.claim.message` unchanged. It contains the private preview (`data.claim.url`), the owner's claim link (`data.claim.claimUrl`), and the deadline (`data.claim.expiresAt`). Keep both links private. Never print the separate `data.claim.key`.
+5. Keep `data.space.id` and the returned credential securely for updates to the same Space. Follow the guide for credential recovery after claiming. Keep credentials and `.spacefast` state out of the published files, commits, and logs.
 
-**Optional shortcuts and reference only:** if the `sf` CLI is already installed, `sf publish ./dist --wait` does the same job. A zip of the publish folder is also supported, but neither the CLI nor a zip is required. Docs: [direct agent/API publishing](https://spacefast.com/setup) · [files and folders](https://spacefast.com/help/publishing) · [claiming](https://spacefast.com/help/anonymous-publish) · [updates and rollback](https://spacefast.com/help/versions)
+If the `sf` CLI is already installed, `sf publish ./dist --wait` follows the same publishing flow. See [publishing](https://spacefast.com/docs/publish/) and [claiming a Space](https://spacefast.com/docs/anonymous-and-claim/).
diff --git a/recipes/wp-zero/meta.json b/recipes/wp-zero/meta.json
index f2711cd..819045c 100644
--- a/recipes/wp-zero/meta.json
+++ b/recipes/wp-zero/meta.json
@@ -5,7 +5,7 @@
   "vertical": "Developers & integrations",
   "tech": "WordPress + Spacefast Zero",
   "runtime": "zero",
-  "summary": "A magazine whose articles come from a public WordPress REST API at build time and render to static pages, with a Spacefast Zero server behind them for realtime emoji reactions and server-side search over a build-time index.",
+  "summary": "Publish WordPress articles with live reactions and server-side search powered by Zero.",
   "order": 330,
   "live_url": "https://wp-zero.view.fast/",
   "setup_questions": [
diff --git a/recipes/zero-perfect/meta.json b/recipes/zero-perfect/meta.json
index 2e0f340..20f0573 100644
--- a/recipes/zero-perfect/meta.json
+++ b/recipes/zero-perfect/meta.json
@@ -5,7 +5,7 @@
   "vertical": "Tools, apps & games",
   "tech": "Spacefast Zero + Preact",
   "runtime": "zero",
-  "summary": "A minimal full-stack todo app with database-backed queries and mutations, guest and Gravatar auth, Cast realtime, routes, and an HTTP endpoint.",
+  "summary": "Build a shared task app with a database, sign-in, and realtime updates.",
   "order": 310,
   "live_url": "https://zero-perfect.view.fast/",
   "setup_questions": [
diff --git a/recipes/zine/meta.json b/recipes/zine/meta.json
index 99fb84b..c1a460d 100644
--- a/recipes/zine/meta.json
+++ b/recipes/zine/meta.json
@@ -4,14 +4,14 @@
   "slug": "zine",
   "vertical": "Personal & creative",
   "tech": "Plain HTML & CSS",
-  "summary": "A scrollable, art-directed riso web zine — seven full-viewport magazine spreads with custom display type, live film-grain and halftone texture, duotoned photos, and an \"issue-as-version\" colophon.",
+  "summary": "Publish a web zine with full-screen spreads, print textures, and contributor credits.",
   "order": 300,
   "live_url": "https://zine.view.fast/",
   "setup_questions": [
     "What's the theme/mood of the issue, and a title for it (e.g. \"Night Bloom\", \"Concrete & Moss\")?",
     "What are the 4–6 spreads of content (an editor's letter, a photo essay, a poem, an interview, field notes — tell me what each is about)?",
     "Aesthetic: retro-web, brutalist, or riso? And any colors to lean into?",
-    "Any real contributors, quotes, or images to feature — or should I invent believable ones?"
+    "Which contributors, quotes, and images may I use? I can label fictional material as sample content."
   ],
   "photo_terms": [
     "riso print texture colorful",
diff --git a/recipes/zine/prompt.md b/recipes/zine/prompt.md
index 8f0a4a4..081c168 100644
--- a/recipes/zine/prompt.md
+++ b/recipes/zine/prompt.md
@@ -7,16 +7,16 @@ unconventional, magazine-style spreads** as a **plain HTML & CSS** site (one
 1. What's the theme/mood of the issue, and a title for it (e.g. "Night Bloom", "Concrete & Moss")?
 2. What are the 4–6 spreads of content? (e.g. an editor's letter, a photo essay, a poem, an interview, field notes — tell me what each one is about.)
 3. Aesthetic: retro-web, brutalist, or riso? (And any colors you want me to lean into.)
-4. Optional: any real contributors, quotes, or images you want featured — otherwise I'll invent believable ones.
+4. Optional: any real contributors, quotes, or images you want featured — otherwise use original work and label fictional contributors and interviews as fiction.
 
 **Then build a complete, polished, responsive zine with:**
 
 - A **cover spread**: the zine's name set huge in a display face, an issue number, a tagline for the theme, and a "scroll to turn the page" cue. Treat it like a real magazine cover.
 - **4–6 art-directed spreads**, each filling the viewport and each visually distinct — for example: an editor's letter with a drop-cap, a photo essay in an asymmetric image mosaic, a full-bleed poem or pull-quote spread, an interview with Q&A and a pulled quote, and a "field notes" collage of cards.
 - **Custom type + texture**: pair a bold display font with a serif body and a monospace for captions (load from Google Fonts). Add a film-grain and halftone-dot overlay so it reads as printed, not flat. Allow deliberate "misregistration" — offset color shadows on the headlines.
-- A **colophon** spread: the fine print — who made it, what fonts and "inks" were used, contributors, and an **"issue-as-version"** note that frames each issue as a permanent, immutable version (it ties naturally to how Spacefast keeps every publish at its own URL).
+- A **colophon** spread: the fine print — who made it, what fonts and "inks" were used, contributors, and an **"issue-as-version"** note that frames each issue with a fixed version URL while that version is retained.
 - A running header that doubles as a **version tag** (e.g. "№01 · v1.0") and a spread counter that updates as you scroll.
-- A small newsletter signup in the colophon that validates the email, shows a friendly confirmation, and remembers returning readers via `localStorage`.
+- A newsletter signup in the colophon with a labelled email field. For any form that sends information, ask for my form endpoint or hosted signup URL. Use the supplied destination and show success only after it confirms receipt. A link to another service does not confirm completion. Without a destination, label the form "Demo only" beside its fields, label its button "Preview", and say "Preview complete. Nothing was sent." Never treat `localStorage` as delivery or store personal form data there.
 
 **Design & content notes:**
 
@@ -27,8 +27,7 @@ unconventional, magazine-style spreads** as a **plain HTML & CSS** site (one
 - Treat photos as **duotone riso prints**: desaturate them and tint each with a spot
   color via CSS blend modes, with a halftone dot pattern on top, so random photos still
   look like one cohesive printed issue.
-- Use realistic content based on my answers — never "lorem ipsum". Write a real editor's
-  letter, a real poem, a believable interview, real field notes.
+- Write original creative text from my theme. Attribute only real supplied quotes. Label fictional interviews and contributors as fiction instead of presenting them as real reporting.
 - Use real images. Pull free photos that fit — e.g. `https://picsum.photos/seed/zine-1/1200/800?grayscale`
   (vary the seed per image) or direct Unsplash URLs matching `riso print texture colorful`
   and `experimental editorial layout` — and add descriptive `alt` text.
@@ -43,28 +42,12 @@ unconventional, magazine-style spreads** as a **plain HTML & CSS** site (one
 <script src="https://spacefast.com/badge.js" data-example="zine"></script>
 ```
 
-**When the site is ready, publish it to Spacefast with the direct API — no account, install, or extra instructions needed:**
+**When the site is ready, publish it to Spacefast:**
 
 1. Use `./site` as the publish folder. For no-build projects, put only the finished public files in that dedicated folder. Confirm it has `index.html` at its root and no secrets, source files, `.git`, or `.spacefast` state.
-2. First publish: send every file as multipart form data. This Bash/Zsh block preserves relative paths and works for one file or a whole folder:
-   ```bash
-   PUBLISH_ROOT=./site
-   publish_files=()
-   while IFS= read -r -d "" file; do
-     relative=${file#"$PUBLISH_ROOT"/}
-     publish_files+=(-F "files=@$file;filename=$relative")
-   done < <(find "$PUBLISH_ROOT" -type f -print0)
-   curl -sS "${publish_files[@]}" "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-3. From the `{ "data": ... }` receipt, give me `data.space.liveUrl`, `data.version.immutableUrl`, `data.claim.url`, and `data.claim.expiresAt`. Remind me to claim within 6 hours. Keep `data.claim.token` secret.
-4. Save `data.space.id` and `data.claim.token` locally (for example in an ignored, mode-600 `.spacefast/state.json`). For a quick update, rebuild the `publish_files` array above and publish to the same space:
-   ```bash
-   SPACEFAST_SPACE_ID=<saved-space-id>
-   SPACEFAST_TOKEN=<saved-claim-token-or-access-token>
-   curl -sS -H "Authorization: Bearer $SPACEFAST_TOKEN" \
-     -F "spaceId=$SPACEFAST_SPACE_ID" "${publish_files[@]}" \
-     "https://api.spacefast.com/v1/publish?wait=1"
-   ```
-   If an update after claiming returns `space_claimed_credential_available`, exchange the saved claim token once at `POST https://api.spacefast.com/v1/anonymous-claim/exchange`, save `data.credential.accessToken`, and retry with that access token.
+2. Fetch https://spacefast.com/setup.md and follow its current direct API publishing instructions. Check for an existing Space before creating one, and follow the returned upload and polling steps.
+3. Report success only when `data.next.action` is `done` and the intended version is serving. If more work is needed, report the returned next step.
+4. For an anonymous publish, give me `data.claim.message` unchanged. It contains the private preview (`data.claim.url`), the owner's claim link (`data.claim.claimUrl`), and the deadline (`data.claim.expiresAt`). Keep both links private. Never print the separate `data.claim.key`.
+5. Keep `data.space.id` and the returned credential securely for updates to the same Space. Follow the guide for credential recovery after claiming. Keep credentials and `.spacefast` state out of the published files, commits, and logs.
 
-**Optional shortcuts and reference only:** if the `sf` CLI is already installed, `sf publish ./site --wait` does the same job. A zip of the publish folder is also supported, but neither the CLI nor a zip is required. Docs: [direct agent/API publishing](https://spacefast.com/setup) · [files and folders](https://spacefast.com/help/publishing) · [claiming](https://spacefast.com/help/anonymous-publish) · [updates and rollback](https://spacefast.com/help/versions)
+If the `sf` CLI is already installed, `sf publish ./site --wait` follows the same publishing flow. See [publishing](https://spacefast.com/docs/publish/) and [claiming a Space](https://spacefast.com/docs/anonymous-and-claim/).
diff --git a/recipes/zine/site/index.html b/recipes/zine/site/index.html
index a93e513..09b585d 100644
--- a/recipes/zine/site/index.html
+++ b/recipes/zine/site/index.html
@@ -240,6 +240,12 @@
 </style>
 </head>
 <body>
+    <aside
+      aria-label="Example site"
+      style="margin:0;padding:0.75rem 1rem;background:#fff7d6;color:#29221a;font:14px/1.5 system-ui;text-align:center"
+    >
+      Example site with fictional content. Forms are previews.
+    </aside>
   <div class="rail" id="rail"></div>
   <div class="runner">
     <span class="vtag"><span class="dot"></span> OFFCUTS&nbsp;<b>№01</b><span class="hide-sm">&nbsp;· Night Bloom</span></span>
@@ -416,11 +422,13 @@ <h2 class="rev">COLOPHON</h2>
           <b>Every issue is a version.</b> Night Bloom is <code>v1.0</code> of OFFCUTS. When we cut Issue 02 we won't overwrite this one — it keeps its own permanent URL, forever, the way a back-issue keeps its spine. That's just how publishing on <strong>Spacefast</strong> works: each publish is a version, and you can always reach the one you loved.
         </div>
 
+        <p data-demo-note="true">Demo signup. No subscription is created and no email is sent.</p>
+
         <form class="subscribe rev" id="sub" novalidate>
           <label for="email">Get Issue 02 in your inbox the night it drops</label>
           <div class="row">
             <input type="email" id="email" name="email" placeholder="you@aftermidnight.zine" autocomplete="email" required />
-            <button type="submit">Subscribe</button>
+            <button type="submit">Preview</button>
           </div>
           <p class="msg" id="submsg" role="status" aria-live="polite"></p>
         </form>
@@ -481,7 +489,7 @@ <h2 class="rev">COLOPHON</h2>
     var KEY = 'offcuts-subscribed';
 
     if(localStorage.getItem(KEY)){
-      msg.textContent = "You're already on the list — see you at Issue 02.";
+      msg.textContent = 'Preview complete. Nothing was sent.';
       msg.classList.remove('err');
       input.value = localStorage.getItem(KEY);
     }
@@ -491,14 +499,14 @@ <h2 class="rev">COLOPHON</h2>
       var val = input.value.trim();
       var ok = /^[^\s@]+@[^\s@]+\.[^\s@]+$/.test(val);
       if(!ok){
-        msg.textContent = 'That email looks a little out of register — try again.';
+        msg.textContent = 'Enter a valid email address to preview the signup.';
         msg.classList.add('err');
         input.focus();
         return;
       }
       localStorage.setItem(KEY, val);
       msg.classList.remove('err');
-      msg.textContent = "You're on the list. Issue 02 lands on the next full moon.";
+      msg.textContent = 'Preview complete. Nothing was sent.';
       form.querySelector('button').textContent = 'Done ✓';
     });
   </script>