Schema match
Use the records schema and sample packet so every lane has the expected field labels before review starts.
Review filled launch records before production proof.
Use this checklist after a packet passes validation and before any real event, service, account, media, payment, provider, or monitoring proof starts. It does not submit, persist, seed, mutate, authorize, charge, upload, page, request secrets, or create public inventory.
Owner approval window
Record who approved the proof window, what exact route or provider surface may be checked, and when the approval expires.
Alias redaction
Aliases only: no passwords, cookies, session text, API keys, webhook secrets, raw emails, bank details, private addresses, or media object keys.
Lane completeness
Each event, service, account, and media lane needs a filled value or an explicit not approved reason before it can be used for live proof.
Approved proof scope
Name the allowed checks, such as list/detail reachability, denied-role behavior, quote-only payment review, or manifest integrity, without broadening scope mid-run.
Stop condition
Stop when work needs real credentials, provider mutations, live payments, protected media grants, monitoring changes, or role-account QA beyond the approved scope.
Launch review required
Operator-owned event
Move FE-02, FE-03, FE-04, and FE-06 from honest-empty source proof to real event discovery, detail, quote, ticket, and analytics proof.
Filled values to review
- Event alias or planned slug: Alias only until approved
- Host account alias: Approved host QA account alias
- Schedule and timezone: Date, start/end, timezone, publish window
- Venue, city, and approximate area: Public-safe location details
- Ticket tier and checkout boundary: Tier alias, price, quantity, quote/checkout limit
- Allowed event proof: Discovery/detail/schema/quote/ticket/analytics scope
Approval questions
- Has the owner approved this lane for the current proof window?
- Are all sensitive identifiers redacted to aliases?
- Does the allowed proof scope avoid production mutation outside this lane?
- Did the validator pass before this checklist was used?
Stop condition
Do not seed fake public inventory, publish an event, create orders, run charges, or expose private venue details without owner approval.
Launch review required
Operator-owned service
Move the services marketplace from empty public readiness to real provider listing, detail, Connect boundary, and booking proof.
Filled values to review
- Provider account alias: Approved provider QA account alias
- Service alias or title: Public-safe listing title or alias
- Category, city, and coverage area: DJ, photo, security, city, radius
- Pricing and booking boundary: Starting price, deposit, quote-only, or Connect proof limit
- Listing state: Draft, listed, scheduled listing window
- Allowed service proof: List/detail/JSON-LD/booking/Connect error scope
Approval questions
- Has the owner approved this lane for the current proof window?
- Are all sensitive identifiers redacted to aliases?
- Does the allowed proof scope avoid production mutation outside this lane?
- Did the validator pass before this checklist was used?
Stop condition
Do not invent provider rows, expose drafts, activate Connect, create bookings, or imply payout readiness from source checks alone.
Launch review required
Authorized role accounts
Prepare FE-05 and FE-09 manual QA for workspace creation, active account context, role boundaries, scanner access, and admin denials.
Filled values to review
- Buyer alias: Approved buyer account alias
- Host or manager alias: Approved host/manager account alias
- Provider alias: Approved service provider account alias
- Promoter alias: Approved promoter account alias
- Scanner and admin aliases: Approved scanner/admin aliases or not approved
- Denied-route proof: Routes each role must not control
Approval questions
- Has the owner approved this lane for the current proof window?
- Are all sensitive identifiers redacted to aliases?
- Does the allowed proof scope avoid production mutation outside this lane?
- Did the validator pass before this checklist was used?
Stop condition
Do not store reusable credentials, cookies, tokens, private screenshots, raw emails, or owner account secrets in the packet.
Launch review required
Approved media sample
Prepare TG-PRIV and TG-ZIP live proof for public, unlisted, private, protected, manifest, ZIP, and native save/share behavior.
Filled values to review
- Gallery or object aliases: Aliases, not raw bucket keys
- Owner and non-owner aliases: Approved owner/non-owner account aliases
- Visibility modes: Public, unlisted, private, protected grant
- Manifest and ZIP proof: Expiry, photo count, SHA-256, quota/revocation scope
- Native device proof: Desktop/mobile share, copy, save scope
- Media limits: No edits, no deletion, no redistribution, preserve originals
Approval questions
- Has the owner approved this lane for the current proof window?
- Are all sensitive identifiers redacted to aliases?
- Does the allowed proof scope avoid production mutation outside this lane?
- Did the validator pass before this checklist was used?
Stop condition
Do not upload, expose, transform, merge, delete, redistribute, or grant access to real media without explicit approval.