Live is not complete
A route, revision, or HTTP 200 can prove reachability; it does not prove real inventory, authorized accounts, payments, media, or alerts.
Map every expansion wave to live evidence and owner gates.
This coverage matrix ties the platform overhaul and social promoter specs to deployed surfaces, source-backed proof, and the owner-gated evidence that still cannot be completed from code alone.
Source-backed is scoped
Tests and deployed source show the intended behavior and guards, but real operator records are still separate evidence.
Owner-gated proof stops
The remaining gates require explicit approval before credentials, provider state, payments, media, alerts, or real accounts are touched.
Platform overhaul workstreams
Trace source work to the remaining proof.
Rows from the platform overhaul spec grouped by the deployed surfaces and the still-missing owner proof.
Coverage lane
A1 Home redesign and buyer entry
Source-backed coverage
The public home, inventory counts, featured entry points, and readiness status are deployed without inventing public inventory.
Owner-gated proof
Launch-complete proof still needs an operator-owned event and service so the home surface can show real marketplace content.
Live routes to inspect
Coverage lane
A2 Feed and social posting
Source-backed coverage
Post/feed, collaboration, media, and malformed social route guards are source-backed with role and privacy boundaries recorded on status.
Owner-gated proof
Real promoter, host, client, and collaboration activity remains owner-gated before social analytics or posting can be called launch-proven.
Live routes to inspect
Coverage lane
A3 Nearby and geo discovery
Source-backed coverage
Nearby routing, public event/service discovery, and malformed location-adjacent route behavior are represented without requiring browser location permission.
Owner-gated proof
Physical browser permission checks, real mapped inventory, and city/area expectations remain waiting for owner-approved data and device QA.
Live routes to inspect
Coverage lane
A4 Auth modernization and onboarding
Source-backed coverage
Auth copy, account context, role workspace boundaries, settings, and fail-closed route guards are source-backed.
Owner-gated proof
Authorized buyer, host, provider, promoter, manager, scanner, and admin sessions are still required for production role QA.
Live routes to inspect
Coverage lane
A5/B1 Tickets and QR
Source-backed coverage
Ticket type, checkout quote, order, transfer, comp, refund, scan, and malformed payment/ticket/order ID guards have source and status coverage.
Owner-gated proof
Real checkout, webhook fulfillment, wallet display, QR scan, refund, and door-session proof remain Stripe and account gated.
Live routes to inspect
Coverage lane
A6 Orders and ticket wallet
Source-backed coverage
Orders, upcoming/past ticket surfaces, buyer fee quote behavior, and malformed order access boundaries are covered from source.
Owner-gated proof
A real account with real orders is required before the wallet and order history can be verified as launch-complete.
Live routes to inspect
Coverage lane
A7/A8 Mobile and quality sweep
Source-backed coverage
Responsive readiness, mobile modernization evidence, and public route checks are recorded for the deployed surfaces.
Owner-gated proof
Signed-in physical-device checks for auth, checkout, scanning, media save/share, and role workspaces remain owner-gated.
Live routes to inspect
Coverage lane
B4/B6 Accounts, admin, plans, and flags
Source-backed coverage
Plan catalog, entitlement cleanup, admin editor, active account context, preview boundaries, and malformed account/admin route guards are source-backed.
Owner-gated proof
Owner-approved admin and role-account sessions are still needed before admin controls or feature flags are treated as fully proven.
Live routes to inspect
Coverage lane
B2/B5/B7 Promoters and analytics
Source-backed coverage
Promoter readiness, collaboration consent, post/event analytics surfaces, and analytics matrix evidence are represented on deployed status pages.
Owner-gated proof
Real promoter invite, collaboration, post activity, views, interactions, ticket attribution, and payout proof remain owner-gated.
Live routes to inspect
Events social promoter waves
Trace source work to the remaining proof.
Rows from the events social promoter expansion spec and adjacent FE/TG lanes.
Coverage lane
W-A Events discovery
Source-backed coverage
Event cards, search/category/nearby readiness, featured entry points, public stats, and honest-empty behavior are deployed.
Owner-gated proof
A real operator event with venue, schedule, location, cover image, and public ticket tier is required for complete proof.
Live routes to inspect
Coverage lane
W-B Event detail and reviews
Source-backed coverage
Event detail metadata, crawlable Event JSON-LD, share targets, attendee review gate evidence, and malformed event IDs are source-backed.
Owner-gated proof
A real past event, buyer account, ticket-holder review, and authorized host review visibility remain owner-gated.
Live routes to inspect
Coverage lane
W-C Orders and settings
Source-backed coverage
Upcoming/past order surfaces, settings workspace evidence, avatar-adjacent copy, and account intent boundaries are tracked.
Owner-gated proof
A real signed-in account with real orders and approved profile media is needed before launch-complete proof.
Live routes to inspect
Coverage lane
W-D Content and positioning
Source-backed coverage
Public policies, use cases, nav/footer positioning, content readiness, and no-placeholder language are deployed.
Owner-gated proof
Owner-reviewed legal, privacy, refund, and marketplace policy approval remains required before treating copy as final.
Live routes to inspect
Coverage lane
W-E Promoters
Source-backed coverage
Promoter readiness records collab consent, promoter feed, attribution, analytics, and account boundary expectations.
Owner-gated proof
Real host-created promoter account, invite, accepted collaboration, post, transaction attribution, and payout evidence remain owner-gated.
Live routes to inspect
Coverage lane
FE-04 Payments and payouts
Source-backed coverage
Non-mutating checkout quotes, ticket checkout/webhook/refund source paths, Connect booking boundaries, malformed payment IDs, and fee evidence are recorded.
Owner-gated proof
Stripe mode, webhook, charge, refund, Connect, Tax, Radar, KYC, settlement, and bank payout checks require explicit owner authorization.
Live routes to inspect
Coverage lane
TG-PRIV/TG-ZIP Media privacy and exports
Source-backed coverage
Public/unlisted/private gallery access, signed manifests, ZIP export, quota, CORS-readable integrity metadata, and client SHA-256 verification are source-backed.
Owner-gated proof
Approved real media, protected grants, live bucket/IAM checks, durable revocation, ZIP integrity against real objects, and native save/share proof remain gated.
Live routes to inspect
Coverage lane
FE-11/FE-12 Observability and rollback
Source-backed coverage
Public health probes, Cloud Run revision visibility, recent log/Error Reporting/Trace read-only samples, and rollback checklist evidence are deployed.
Owner-gated proof
Alert policies, notification channels, SLOs, error budgets, trace instrumentation, alert delivery tests, and incident drills require owner approval.
Live routes to inspect
Coverage lane
FE-13 Release readiness and owner activation
Source-backed coverage
Activation worksheet, evidence packet, packet JSON, local builder, public preflight, owner intake, and this expansion coverage matrix are live.
Owner-gated proof
This matrix is a traceability surface only. It does not approve credentials, seed inventory, charge money, mutate media, page people, or close owner-gated proof.