Evidence page

Integration evidence

This page summarizes the artifacts a company evaluator can inspect: customer routes, operator console, prepared data views, package boundary, noindex controls, and audit checks.

Frontend Evidence

Customer home, listing, category, seller, hub, order, support, policy, guide, and evidence routes.
Interactive search, auctions, cart review, watchlist, offers, messages, reports, and reviews.
Operator console with trust, supply, hubs, growth, launch, finance, routes, workflows, and playbook.

Data Layer Evidence

Supabase schema, seed data, buyer/seller/employee records, listings, auctions, orders, reports, hubs, and reviews.
Readiness views for scorecard, launch, integrations, routes, economics, policies, service levels, walkthroughs, and acceptance checks.
Action functions prepared for offers, messages, saved searches, checkout review, and purchase reviews.

Deployment Evidence

Netlify deploy uses an explicit package manifest.
Demo and placeholder domains use noindex headers and robots disallow.
Secret scanning blocks credentials from package and repository surfaces.

Audit Evidence

`scripts/check-site.mjs` validates route, operator, data layer, and asset coverage.
The language-quality check blocks pitch language on public customer surfaces.
`scripts/audit-demo-readiness.mjs` ties the current worktree to objective-level evidence.

Operator Console

Open the owner-facing console for launch readiness, unit economics, route coverage, workflows, and playbook.

Commerce Integration

Review route contracts, identity scopes, listing actions, events, support handoff, and launch controls.

Owner Handoff

Review the evidence bundle, service activation gaps, ownership controls, deployment safety, and acceptance checks.

Domain Launch

Review placeholder domains, DNS cutover, SSL, noindex release, monitoring, and rollback evidence.

Store-Assisted Resale Guide

Review the strategic operating model behind local intake, pickup, and high-value resale.

Current demo state

Help and evidence pages are written for the demo stage.

The demo explains policies, fees, condition proof, store-assisted resale, route coverage, and setup evidence without asking for private data.

Future platform state

Launch-ready help content needs clear ownership.

Launch needs final policies, support contact paths, fee approval, knowledge-base ownership, legal review, update history, and service-level tracking.