Quality

Quality status

Review QA, accessibility, performance, security, browser, mobile, routes, workflows, permissions, evidence, issues, and release gates in one place.

Public quality status

High-level launch readiness without private issue details

AreaStateNext check
Quality runtimeready_for_auditQA evidence can pass audit when validation is clean
DigiShelf pre-launch gateblockedFinal human QA and launch approval remain pending
Accessibility certificationnot_providedAutomated/reference checks are not certification
Security penetration testnot_providedSecurity readiness is not a penetration test
Production performance proofnot_providedLocal budgets are not Core Web Vitals proof

Public-safe quality checks

Private issue details, credentials, and connector diagnostics are excluded

AreaStateNext check
Raw tokens/secretsblocked_if_seenCritical launch blocker if exposed
Private file keys/storage pathsblocked_if_seenCritical launch blocker if exposed
Payment and order private datablocked_if_seenCritical launch blocker if exposed
Buyer/seller private datablocked_if_seenCritical launch blocker if exposed
Provider/webhook payloadsblocked_if_seenCritical launch blocker if exposed

Quality safety rules

Quality review records evidence and blockers. It does not replace final launch approval or expose private data.

public-safe

Automated tests are not human QA approval.

Accessibility checks are not accessibility certification.

Security readiness is not a penetration test.

Local performance budgets are not production Core Web Vitals proof.

Route render checks are not payment, delivery, publishing, sending, or workflow success.

Checkout, delivery, publishing, sending, payout, and billing workflows require their own live QA evidence.

Emails, social posts, paid campaigns, public content, consent controls, and public claims require human approval.

Seller-facing and public views keep sensitive credentials, private file keys, payment details, buyer private data, and support notes out of display payloads.