Language quality
Keep the marketplace clear, customer-facing, and credible by reviewing wording, claims, route labels, demo boundaries, policy notes, and owner approval before launch.
Customer Copy
- Homepage, listings, categories, hubs, seller tools, and account pages should read like a marketplace people can browse and use.
- Action labels should stay direct: search, bid, watch, offer, buy now, checkout review, pickup, report, review, and sell.
- Long explanations should move into help, policy, setup, or operator routes instead of crowding the storefront.
Claim Safety
- Static pages should not imply real payments, real payout release, live shipment labels, active support staffing, or live account operations.
- Numbers should describe visible activity, seller stats, bids, watchers, prices, or clearly bounded readiness evidence.
- Customer-facing routes should avoid investor-deck phrasing, named-company pitch framing, and vague technology claims.
Demo Boundary
- Public routes keep the shopping experience first, then place current demo state and future platform state near the page end.
- Checkout, reports, reviews, messages, bids, offers, and listings can be tried as guided interactions without collecting sensitive details.
- Legal and privacy notes should be short, accurate, and separate from the first buying screen.
Route Labels
- Route names should sound like product surfaces: auction detail, order status, seller dashboard, hub pickup, condition guide, and setup center.
- Demo-map cards should group buyer, seller, hub, trust, and operator journeys so the route depth feels curated instead of dumped.
- Internal operating terms should not leak into customer navigation, marketplace cards, item pages, or policy headings.
Policy Clarity
- Buyer protection, seller standards, restricted items, returns, privacy, fees, and support pages should explain expected customer choices.
- Policy copy should tell users what happens, what evidence is needed, and where the next step lives.
- Any launch policy that still needs live service ownership should clearly say what is available now and what requires approval before launch.
Guard Coverage
- Site checks should reject broken route targets, missing state boundaries, fragile demo-map links, missing listing images, and route-package drift.
- Language checks should block pitch framing, prototype-first phrases, vague hype, and named-company language from the storefront bundle.
- Secret checks and scoped package validation should run before deployment.
Owner Review
- Owners should approve homepage claims, route coverage, policy wording, privacy wording, setup language, and launch notes before public release.
- Review should include desktop, mobile, route map, checkout review, report flow, seller tools, hub pages, and operator surfaces.
- Approval should stay linked to launch decision, owner handoff, service activation, and search indexing controls.
Release Checklist
- Run site checks, language checks, secret checks, package validation, live verification, and demo-map crawl after copy changes.
- Confirm placeholder domains remain neutral and noindex until owners intentionally choose a public launch.
- Keep the demo deployed only through the explicit static package.
Demo Map
Buyer, seller, hub, trust, and operator journeys grouped for a clean walkthrough.
Owner Handoff
Evidence bundle, activation gaps, ownership controls, deployment safety, and acceptance checks.
Launch Decision
Approval scope, deferred items, blockers, rollback controls, and evidence checklist.
Search Indexing
Noindex safety, public page planning, private route rules, structured data, and sitemap scope.
Localization Preferences
Language choices, translated listings, regional formats, customer notices, and support review.
Privacy & Data
Data boundary, technical request data, retention, staff access, and processor review.
Service Activation
Checkout, identity, notifications, media evidence, carrier handoff, and support readiness.
Current demo state
Language quality is represented as an owner review route.
The demo shows customer copy standards, claim safety, route labels, policy clarity, guard coverage, release checks, and owner approval without connecting live services.
Future platform state
Launch needs formal copy ownership.
Launch needs named owners for marketplace copy, policy changes, legal review, support templates, launch claims, SEO copy, localization, and ongoing route audits.