The egg fills while you watch.

Most tools make you wait behind a spinner that says "Generating…". Yoshi does the opposite: it shows you the work. As the conversation lands facts, you see them flow into your egg — a live canvas of everything your site is being built from.

This is the moment the product earns belief. You're not trusting a black box; you're watching your business become a website, asset by asset.

What you see hauling in

Each task ("crate") reports as it completes, and the egg visibly gains substance:

   ┌──────────────── your egg ────────────────┐
   │  🏷  brand        Ottawa Towing Co.        │
   │  🎨  palette      derived from your logo   │
   │  🔧  services     Flatbed · Roadside · +2  │
   │  📍  areas        Barrhaven · Kanata · +9  │
   │  ⭐  reviews      12 pulled (4.8★)          │
   │  🖼  photos       7 matched to sections    │
   │  ✍️  copy         writing your pages…       │
   │  🌐  pages        ▓▓▓▓▓▓░░░  1,140 / ~1,800 │
   └───────────────────────────────────────────┘

That page counter is the differentiator made visible: you're not getting a 5-page site, you're getting the whole searchable footprint of your trade in your region.

The four things happening under the hood

You don't need to know these to use Yoshi — but seeing them builds trust, so we name them plainly:

1. Gather — pulling your real assets (services, reviews, photos, hours) from what you gave it.
2. Plan — deciding the page map: which services, which areas, which combinations are worth a page, what each page should say and how long it should be.
3. Make it yours — this is the magic. Yoshi individuates the site from who you are: a layout it picks for you, a logo it synthesises if you don't have one, your photos matched to the right slots, a palette from your brand, and a writing voice tuned to your trade. Two towing companies will not get the same site. status: live (uniqueness axes shipped; copy-voice in flight).
4. Generate — assembling every page, in every language you serve, into a complete, fast, static site.

The "make it yours" promise, concretely. Sameness is the failure mode of every site builder. Yoshi treats individuation as non-negotiable: layout, logo, imagery, copy voice, and even a "style-DNA" corner-radius personality are all derived deterministically from your business, so your site has a fingerprint. Hand the same trade to Yoshi twice and you get two genuinely different sites.

How long does it take?

The deterministic build is fast — the heavy lifting is gathering and writing, not rendering. You'll watch the egg fill in the time it takes to read a couple of reviews, not the six weeks an agency quotes. status: live for the generate step; gather/copy timings firm up as the conversational pipeline lands.

🌳 Open questions (the inquisitive seam)

• Is "watching it build" delight or anxiety? A live feed of 1,800 pages assembling could feel magical or overwhelming. Do we show the firehose, or a calm, curated highlight reel ("Found your reviews ✓ · Picked a layout ✓ · Writing your pages…")? Leaning: curated beats with an optional "show me everything" expander for the curious. Cycle 28 (collection canvas) + 30 (events).
• What if a step finds something wrong? Yoshi pulls a stale phone number, or a competitor's photo by mistake. Does the egg let you correct in place mid-build, or only at preview? Leaning: tap any egg item to fix it now — the canvas is editable, not just a status display. Cross-ref 03 Preview.
• Showing the "uniqueness" so it's believed, not just claimed. Could we show a tiny "here's another towing site Yoshi made — see how different yours is" comparison at build time? Powerful proof, but it risks confusing the user about their site. Cross-ref cycle 41 (example gallery), 40 (uniqueness).
• The honesty of AI-written copy. When Yoshi writes "20 years serving Ottawa," it must be true — it can only claim what the owner confirmed. How do we make the copy step visibly grounded (every claim traceable to an intake answer), never fabricated? Leaning: non-negotiable — no invented facts, and the preview flags any claim the user should verify. Decision; cross-ref the integrity rules in cycle 30.
• Can the user leave and come back? A 1,800-page build shouldn't chain them to the tab. Email/SMS "your site's ready to preview"? Leaning: yes — the egg is durable; notify on hatch. Cycle 30 persistence + 49 claim.