Operator proof handoffUse this handoff before the next owner-approved proof session to name the event, service, role-account, payment, media, monitoring, and rollback inputs that must come from the owner. It does not submit, persist, seed, mutate, authorize, charge, upload, page, request secrets, call APIs, or create public inventory.
Handoff lane
Real event proof package
owner suppliedBring an owner-approved event alias, host account alias, schedule, venue-safe location, ticket tier, and allowed checkout/analytics scope into the next proof session.
Proof targets
- FE-02 public discovery and filtering against a real published event
- FE-03 event detail metadata and share targets against a real event
- FE-04 quote/checkout boundary against a real ticket tier
- FE-06 host analytics once real activity exists
Stop condition
Do not seed fake events, expose private venue details, create orders, or run charges without explicit owner approval.
Handoff lane
Real service proof package
owner suppliedBring an owner-approved provider alias, service alias, category/city coverage, listing state, and booking or Connect boundary into the next proof session.
Proof targets
- FE-SVC public services list and detail against a real listed service
- Provider-private draft isolation before public listing
- Service JSON-LD on listed records only
- Booking flow behavior at the owner-approved Connect or payment boundary
Stop condition
Do not invent provider rows, activate Connect, create bookings, or imply payout readiness from source checks alone.
Handoff lane
Authorized role-account proof package
owner suppliedBring approved buyer, host, provider, promoter, manager, scanner, and admin account aliases with route-allow and route-deny expectations.
Proof targets
- FE-05 onboarding and workspace creation with real accounts
- FE-09 active account context, capability routing, and denial states
- Scanner/admin access boundaries with authorized sessions
- Signed-in mobile checks without storing credentials or tokens
Stop condition
Do not store passwords, cookies, tokens, raw emails, private screenshots, or reusable owner credentials in the packet.
Handoff lane
Payment, media, and monitoring proof package
owner suppliedBring owner-approved Stripe mode, transaction/refund/Connect scope, safe media aliases, alert recipients, and rollback evidence scope.
Proof targets
- FE-04 Stripe checkout, webhook, refund, Connect, Tax, Radar, KYC, or payout evidence only within the approved scope
- TG-PRIV public, unlisted, private, protected grant, signed-read, and non-owner denial behavior
- TG-ZIP manifest, ZIP, quota, integrity, and native save/share behavior against approved media
- FE-11/FE-12 alert delivery, trace/error review, and rollback readiness after owner-approved provider changes
Stop condition
Do not run charges, refunds, transfers, media mutations, protected grants, alert-channel creation, or paging tests without explicit owner approval.