Launch rehearsal

Decide if the first real proof session can move.

This rehearsal reads the live public inventory snapshot and turns it into a go/no-go packet for the owner. It does not submit, persist, seed, mutate, authorize, charge, upload, page, request secrets, call private APIs, or create public inventory.

Decision

owner_records_required

Public reads

ready

Event rows

0

Service rows

0

Next decision

Hold production proof until owner-approved event and service records exist.

This is rehearsal readiness only. Owner approval, production record creation, checkout, booking, Stripe, protected media, monitoring, role-account QA, provider mutation, rollback execution, and launch-complete status remain separate gates; owner-approved event and service records are required before live data proof can move.

Rehearsal check

Public inventory baseline

ready

Public home, events, services, and plans routes responded with expected top-level keys.

Required proof

  • Attach the `/activation/inventory/packet` response to the proof session.
  • Record public route status, response bytes, counts, missing keys, and checked timestamps.
  • Confirm the snapshot is fresh immediately before any owner-approved record work.

Stop condition

Stop if public inventory reads are stale, missing expected keys, or contradict the planned proof lane.

Rehearsal check

Real event proof target

hold

Public inventory is honest-empty for events. A real operator-owned event record is still required before FE-02, FE-03, FE-04, or FE-06 can be proven with live data.

Required proof

  • Bring an owner-approved event alias, host account alias, schedule, public-safe location, ticket tier, and checkout or analytics scope.
  • Verify event list, event detail, JSON-LD, quote boundary, ticket wallet, and analytics evidence against the approved record only.
  • Separate discovery/detail proof from checkout, charge, refund, scan, and analytics proof.

Stop condition

Do not seed fake events, publish private drafts, create orders, expose private venue details, or run charges to make event proof pass.

Rehearsal check

Real service proof target

hold

Public inventory is honest-empty for services. A real operator-owned provider service is still required before service list, detail, booking, or Connect proof can be live-verified.

Required proof

  • Bring an owner-approved provider alias, service alias, category, city or coverage area, listing state, and booking or Connect boundary.
  • Verify `/services`, service detail, service JSON-LD, provider ownership, draft isolation, and booking or Connect behavior against the approved service only.
  • Separate listed public evidence from provider-private draft and payout evidence.

Stop condition

Do not invent provider rows, expose drafts, activate Connect, create bookings, or imply payout readiness from source coverage.

Rehearsal check

Role, payment, media, and monitoring approvals

owner approval required

Role-account QA, Stripe, protected media, monitoring channels, and rollback proof remain separate owner-controlled gates.

Required proof

  • Use approved buyer, host, provider, promoter, manager, scanner, and admin aliases without storing reusable credentials.
  • Keep Stripe mode, webhook, refund, Connect, Tax, Radar, KYC, payout, and balance proof inside the approved session scope.
  • Use safe media aliases and approved monitoring recipients; record rollback target revision before mutating providers.

Stop condition

Do not store passwords, tokens, cookies, raw emails, bank details, private media keys, private screenshots, or alert recipients in committed evidence.

Rehearsal check

Session closeout

owner approval required

The proof session can close only after passed, failed, contradicted, and still-gated checks are recorded separately.

Required proof

  • Attach source commit, Cloud Build, Cloud Run, health, packet, route, role, provider, and artifact evidence to the matching lane.
  • Record every failed or contradicted check without converting it into launch-complete status.
  • Update the ledger and archive with remaining gates before any public launch claim.

Stop condition

Do not mark launch complete from public GET checks, source tests, deployed HTML, screenshots, or adjacent completed lanes alone.

Rehearsal packet

Attach this packet after the live inventory snapshot and handoff review. Do not treat it as approval to mutate production data.