Routes, workflows, evidence, issues, release gates, and readiness
Quality
Quality command centre
Review QA, accessibility, performance, security, browser, mobile, routes, workflows, permissions, evidence, issues, and release gates in one place.
Audit, evidence, coverage, checks, issues, gates, and readiness events
Evidence validity, route, security, mobile, API, and launch policies
Quality command centre
Admins can inspect launch blockers, evidence validity, route and workflow coverage, security, mobile, accessibility, performance, API contracts, and release gates.
Readiness
Launch blockers and quality readiness states
Audits
Scoped automated and review-required audit records
Evidence
Evidence validity, expiry, and review status
Routes
Public, seller, buyer, admin, API, legal, and checkout routes
Workflows
Seller, buyer, admin, migration, growth, and reliability QA
Accessibility
WCAG, keyboard, screen reader, contrast, and focus references
Performance
Budgets without fabricated Core Web Vitals proof
Security
Auth, RBAC, secrets, tokens, headers, and unsafe mutation checks
Browsers
Chromium, Firefox, Safari, Edge, and mobile browser evidence
Mobile
Breakpoints, overflow, tap targets, tables, nav, and forms
Forms
Validation, error, success, privacy, and destructive-action states
States
Empty, loading, failure, blocked, offline, and degraded states
Permissions
Admin-only, owner-only, draft-only, approval-required access
Payloads
Private-field exposure checks for admin and public views
API contracts
Auth, RBAC, validation, mapper, error, and mutation checks
Issues
Triage, remediation, evidence, fixed, verified, and accepted risk
Release gates
Final launch approval stays separate from routine QA
Quality safety rules
Quality review records evidence and blockers. It does not replace final launch approval or expose private data.