Owner Review & Change Intake

Detailed workflow for the EP047 Owner review & change intake node. Based on ep044_group/ep044_owner_review_skill/000_owner_review_skill.md. Double-click the node in the main gap register to return here.

Phase 1 — Review UI Embedded in owner-preview.html

Static site

owner-preview.html generated

Part of the standard EP044 site build. Contains a "Your review" section with #owner-review-root div.

site_generated (1.1)
→
Config

owner-review-config.js

Per-site config: reviewable screens, N questions per screen, M point-and-click options per question. Default: 5 questions × 5 options.

config_loaded (1.2)
→
Engine

owner-review-embed.js

Self-contained, flag-toggled engine (OWNER_REVIEW_ENABLED). Renders one <details> card per screen into the review root.

engine_loaded (1.3)

Phase 2 — Owner Interaction (fully static, no backend)

Owner opens

Owner opens owner-preview.html

Sees N review cards — one per site page. Each card has a "No action required" default option.

page_opened (2.1)
→
Per page

Owner reviews each page

Per card: M questions × N point-and-click radio options (option 1 = "keep as-is"), free-text "anything else" field, and page_open_date_time recorded client-side on first expand.

page_reviewed (2.2)
→
Submit

Owner clicks "Submit review"

Composes a single mailto: to the operator's inbox (e.g. edward.bell@thetechprinciple.com — never the business's own email).

submitted (2.3)

Phase 3 — Submission Format & Operator Processing

Structured

mailto: body format

Each screen line: screen_name, 1:option, 2:option, ..., anything_else: "text" or no_action_required: true for unopened / fine pages.

email_composed (3.1)
→
Operator

Operator reviews submission

Receives structured email. Can distinguish genuinely-reviewed pages (numbered answers) from pages nobody opened (no_action_required: true).

operator_reviewed (3.2)
→
Action

Operator decides next step

Based on feedback: queue content changes, trigger full regeneration, or approve site for activation.

action_taken (3.3)

Phase 4 — Change Execution

Content edits

Content-level changes applied

Text, images, contact details — updated directly by the operator in the generated site files.

content_applied (4.1)
→
Re-generation

Full regeneration (if needed)

Design-level or structural changes trigger a fresh site build using ep044_group skill with original business data + owner feedback.

regenerated (4.2)
→
Verify

Change verified & re-deployed

HTTPS URL verification, hash check, deployment. Owner can be notified of updated preview.

verified (4.3)

Key Rules from the Skill

Integration with EP047