Preview delivery and review workflow

Corrected flow (2026-07-28): a background watcher generates each business's site via the ep044_group skill library as soon as it reaches Claimed — completed before the preview-ready email is sent, so the owner never sees a "generating" state. A new embedded-review skill lets the owner pick suggested changes per screen; submission is a structured, pre-filled mailto:, matching ep_044's existing no-backend pattern. Every step is grounded in the real pipeline_stages table already seeded in 0001_pipeline_seed.sql, ending with a post-delivery service date once the business reaches the terminal Subscriber stage.

Core stateAdmin review gateBusiness communicationReminder nudgeNot yet decided

Business-owner perspective

Prior stage

Claim already approved

Business status is Claimed.

business_claimed (10)
→
External

Preview-ready message

Benefits, link to the generated site, and the local business news link.

website_generated (11)
→
Core

Owner views the generated site

Resolved: a page_open_date_time is recorded per page in the review UI itself; no separate tracking beacon needed, it rides along in the eventual submission.

website_viewed (12)
→
Core

Owner submits changes / assets

Per screen: N questions × M options (starting 5×5, not fixed), point-and-click, plus one free-text "anything else," plus a default "no action required" option and a recorded page_open_date_time. Submits as a pre-filled mailto.

website_viewed (12)
→
Reminder

Nudge if delayed

Owner reminded if no submission arrives within an expected window.

→
Core

Awaiting review

No public change occurs; owner sees no status change yet.

website_viewed (12)
→
Reminder

Nudge if delayed

Owner reminded if admin's review needs a response and none arrives.

→
External

Estimated ready-for-activation date

Sent once admin review is complete.

website_ready (13)
→
External

Ready-for-activation message

Tells the owner the site is ready and includes the payment link — activation is a payment action, not a click.

publish_requested (14)
→
Reminder

Nudge if delayed

Owner reminded if the site sits ready without being activated.

→
Owner action

Owner activates the new site

Resolved: activation is a payment — the owner pays to go live, not just clicks a link.

website_published (15)
→
Terminal

Post-delivery service begins

Ongoing relationship stage; owner is told when the next service touchpoint is, stored on their business record.

subscriber (20)

Admin / operations perspective

Core

Claim-approval trigger

Preview stage begins.

business_claimed (10)
→
Core

Generate website (automated)

Background watcher checks for business_claimed status and runs the matching ep044_group category skill.

website_generated (11)
→
Core

Embed review skill (new)

New ep044_group skill weaves the point-and-click review UI into the generated site itself.

website_generated (11)
→
Core

Generate preview link

Links to the site just generated — generation is already complete by this point.

website_generated (11)
→
External

Send preview-ready message

Only sent once generation has actually succeeded — the owner never sees a "generating" wait state.

website_generated (11)
→
Core

Receive owner submission

One structured mailto per submission: selections, no-action-required pages, page_open_date_time per page, and free text. Absence of any submission (not partial view data) is what drives the intake reminder.

website_viewed (12)
→
Review gate

Review submitted material

Checks assets/changes against build requirements.

website_viewed (12)
→
Review gate

Set ready-for-activation date

Admin-entered date; explicit action, not automatic.

website_ready (13)
→
External

Send ETA message

Communicates the date without implying auto-activation.

website_ready (13)
→
Core

Update generated site

Same generation module as initial build, reused in "apply changes" mode -- not a separate mechanism.

website_ready (13)
→
External

Send ready-for-activation message

Distinct delivery record from the preview-ready and ETA messages; includes the payment link.

publish_requested (14)
→
Core

Observe owner activation (payment webhook)

A confirmed payment event, not a page-click, transitions the business automatically.

website_published (15)
→
Core

Set next post-delivery service date

Resolved: stored on the business record in the database as ongoing per-business info, not a separate table or scheduled task.

subscriber (20) — new column