Events listed
0
Collect the proof that cannot come from source alone.
This worksheet converts the remaining launch gates into evidence lanes for the owner. It is not a seed script, payment authorization, media approval, credential request, or provider mutation plan.
Services listed
0
Public galleries
0
Tickets sold
0
Accounts signed up
9
Activation lane
Operator-owned event
Move event discovery, detail metadata, checkout quotes, ticket wallet, scanner, galleries, and analytics from honest-empty source proof to real-event proof.
Evidence to capture
- Published public event with confirmed schedule, venue, city, category, coordinates, cover image, and ticket tier.
- Public /events and event detail render the record with schema.org Event JSON-LD.
- Cart quote reads the live tier and shows server subtotal, fee, and estimated total without creating an order.
- Authorized host account can inspect sales, scans, reviews, and event analytics once activity exists.
Owner action
Approve or create the first real event and identify the host account allowed to verify it.
Stop condition
Do not seed fake public inventory or run a charge just to make event pages look complete.
Activation lane
Operator-owned service
Move the services marketplace from honest-empty readiness to real provider listing, detail, and booking-boundary proof.
Evidence to capture
- Listed provider service appears in public /services and public detail while draft services stay private.
- Service JSON-LD is visible only for listed records with safe title, description, category, and pricing.
- Provider workspace can read and manage its own listing under the approved account.
- Booking path reaches the expected Connect or payment boundary without exposing unavailable providers as payable.
Owner action
Approve or create the first real provider account and service listing, then decide whether payment proof stops at Connect readiness or continues into a booking.
Stop condition
Do not invent public marketplace rows or mark Connect live from source checks alone.
Activation lane
Authorized role accounts
Prove onboarding, account switching, role boundaries, admin preview, posting, collaboration, scanning, settings, and denials with actual authorized sessions.
Evidence to capture
- Buyer, host, provider, promoter, manager, scanner, and super-admin accounts are approved for QA.
- Each role can reach its intended workspace and is denied from routes it should not control.
- Email-password and Google sign-ins show expected verified/unverified behavior in production.
- No reusable credentials, tokens, or sensitive screenshots are stored in repo or notes.
Owner action
Provide approved test accounts or supervise the session while evidence is captured.
Stop condition
Do not reuse private owner credentials in automation, logs, screenshots, or durable notes.
Activation lane
Approved media set
Prove public, unlisted, private, protected grant, signed URL, manifest, ZIP, and native share/save behavior against real approved objects.
Evidence to capture
- Approved public, unlisted, and private gallery samples exist with known owners and non-owners.
- Signed upload and read URLs expire as expected and do not expose raw object keys to unauthorized users.
- Manifest and ZIP exports include integrity metadata and deny non-owner private access.
- Native share/copy/save behavior is checked with safe media on desktop and mobile.
Owner action
Approve the media sample, visibility mode, account context, and allowed browser/device checks.
Stop condition
Do not upload, expose, merge, delete, or transform real media without explicit approval.
Activation lane
Stripe and Connect proof
Prove the money path with the owner-approved Stripe account, mode, webhook, refund, Connect, Tax, Radar, KYC, and payout evidence.
Evidence to capture
- Stripe account mode, API keys, webhook endpoint, and signing secret are confirmed by the owner without exposing secret values.
- Checkout creates an approved test or live payment, webhook fulfillment issues tickets, and refund path records the expected result.
- Connect onboarding and provider booking prove payable provider state or fail closed with clear copy.
- Tax/Radar/KYC/payout balance or settlement evidence is captured from provider-side Stripe views.
Owner action
Authorize exact mode, transaction scope, refund scope, Connect account, and evidence source before any payment-side verification.
Stop condition
Do not run charges, refunds, transfers, or bank-affecting checks without explicit owner approval.
Activation lane
Operational monitoring
Move FE-11/FE-12 from source/read-only status to operational proof with alert channels, SLOs, trace/error review, and tested delivery.
Evidence to capture
- Uptime, 5xx/error rate, latency, failed deploy, checkout/webhook, and media-delivery alert policies are defined.
- Notification channels and recipients are owner-approved and tested without surprising people.
- SLOs, error budgets, Error Reporting review, and trace/latency review are recorded with timestamps.
- Rollback drills or traffic-shift runbooks capture revision, image, reason, and post-change behavior.
Owner action
Approve recipients, escalation rules, alert delivery test scope, and any provider mutations needed to install monitoring.
Stop condition
Do not create channels that page people or mutate provider monitoring without owner sign-off.