Go-live rehearsal
Practice the launch day runbook before any live service turns on: timed checks, owner roles, route tests, support coverage, rollback drills, and approval evidence in one review path.
Timed Runbook
- Rehearsal starts with storefront smoke tests, route map checks, service health review, support coverage, and owner attendance.
- Each step needs owner, expected signal, evidence link, pass criteria, hold criteria, and next action.
- Timed checkpoints should cover launch minus one day, launch morning, first hour, first auction close, and end-of-day review.
Owner Roles
- Marketplace owner approves scope, launch timing, rollback authority, customer notices, and deferred items.
- Finance owner approves payment posture, seller releases, credits, fee lines, tax records, and settlement review.
- Support, trust, hub, and category owners confirm staffing, issue routing, restricted items, pickup readiness, and seller communication.
Route Smoke Tests
- Buyer flow checks search, listing detail, offer, bid, watch, cart review, order status, report flow, and account activity.
- Seller flow checks listing studio, seller dashboard, offer review, bulk import, storefront, analytics, and compliance status.
- Hub flow checks item checks, pickup scheduler, assurance passport, intake, fees, event calendar, and support handoff.
Service Watch
- Service health should show storefront availability, search, listing pages, checkout review, auction closeout, hub pickup, messages, and support coverage.
- Provider checks should stay visible for hosting, domain, media, identity, notifications, carriers, payment posture, and support tooling.
- Alerts should identify owner, severity, customer impact, rollback trigger, and next review time.
Support Drill
- Practice a missing item case, damaged shipment case, pickup release issue, seller appeal, restricted item rejection, and suspicious account review.
- Each drill needs required documents, customer notice, seller response window, support owner, and escalation path.
- Support readiness should confirm staff coverage, response targets, refund authority, appeal timing, and quality review.
Rollback Drill
- Practice restoring the previous static package, keeping custom domains isolated, preserving noindex rules, and confirming placeholders remain safe.
- Rollback criteria should include checkout provider failure, seller payout blocker, support coverage gap, privacy incident, domain problem, or severe search failure.
- Every rollback step needs owner, command evidence, verification route, customer notice, and after-action note.
Evidence Packet
- Evidence should include route crawl, package manifest, noindex headers, placeholder domain check, Supabase readbacks, service health, policy approval, and support staffing.
- Owner handoff should keep screenshots, route list, acceptance checks, activation gaps, rollback notes, and unresolved blockers together.
- Evidence should be reviewable without exposing secrets, payment data, private identity, addresses, or sensitive support notes.
Launch Decision
- Final decision records approved scope, blocked items, deferred items, owner sign-off, rollback authority, support coverage, and next review.
- Any failed rehearsal step should remain attached to the launch decision until fixed, accepted, or explicitly deferred.
- Approval should stay separate from customer-facing pages so the storefront remains commerce-first.
Migration Readiness
Seller, inventory, policy, record, redirect, support, and cutover checks before traffic moves.
Commerce Integration
Route contracts, event checks, access scopes, support handoff, and launch controls.
Event Delivery
Event names, retry review, replay controls, owner alerts, privacy limits, and recovery paths.
Retail Hub Activation
Location readiness, staff permissions, custody checks, pickup release, packing, and event drills.
Network Rollout
Market scoring, hub tiers, seller seeding, staffing, service gates, and rollback rules.
Launch Decision
Approved scope, blockers, deferred items, rollback controls, and owner sign-off.
Service Health
Storefront, checkout review, search, auction closeout, hub pickup, messages, and support.
Domain Launch
Placeholder domains, DNS cutover, SSL, noindex release, monitoring, and rollback.
Traffic Protection
Crawler controls, rate limits, request protection, secure headers, alerts, and owner approval.
Support Operations
Queue staffing, evidence handoff, response targets, refund authority, appeals, and quality review.
Owner Handoff
Evidence bundle, activation gaps, ownership controls, deployment safety, and acceptance checks.
Service Activation
Checkout, identity, notifications, media evidence, carriers, support, and launch guardrails.
Current demo state
Go-live rehearsal is represented as an owner review runbook.
The demo shows timed checks, role ownership, route smoke tests, service watch, support drills, rollback practice, and evidence packets without enabling launch-ready commerce services.
Future platform state
Live rehearsal needs connected service telemetry.
Launch needs launch monitoring, provider alerts, private staff permissions, accepted policies, customer notices, service credentials, support staffing, rollback authority, and final owner sign-off.