QA & Launch Checks

What has been checked before launch.

This page shows what has been checked, what is still only a demo, and what needs your approval before a public launch.

Checks480 passed / 0 failedRoutes19 verified localMedia40 sets, posters + 540p tiers

Launch Checks

The site should be checked before it is trusted.

Page Check

Each page has a job and a basic response check.

Home, work, process, details, motion, package, proof, start.

Page and link check.
Visual Check

Screenshots show whether the design works on real screens.

Desktop, mobile, reduced motion, overflow, contrast.

Visual check packet.
Media Check

Media is tracked by source, size, and placement.

1080p masters, 540p versions, poster fallbacks, and no repeated card placements.

Media list.
Launch Check

Launch handoff should name the target, approval step, and rollback path.

Build notes, preview URL, page checks, and production approval.

Launch notes.

Launch Logic

Do not claim what has not been proved.

01

Capture

screenshots, video details, and page response

Claims with no inspection trail.
02

Compare

desktop, mobile, reduced motion, and overflow

Premium only in one viewport.
03

Correct

contrast, crop, text fit, and state repair

Known visual flaw left in place.
04

Close

build, visual checks, page checks, and deploy evidence

Launch without proof.

Proof Limits

The checks also say what they do not prove.

01

Screenshots get treated like business results.

Screenshots prove rendering only; they do not prove conversion, revenue, or award status.

Visual check notes with clear limits.
02

Older approval language gets mistaken for the current status.

Use the latest review status until a new review replaces it.

Current status remains not award-ready.
03

Outside reviewers cannot inspect your local machine.

Give reviewers screenshots, checks, and context in one review packet.

Self-contained review packet.

Launch Checks

What is checked, and what still needs proof.

P1preview checked

Visual Checks

The latest local review checked the rendered site.

What this shows
The latest local review passed desktop, mobile, reduced motion, accessibility, route, 404, and overflow checks.
What it does not prove
This proves local rendering and accessibility checks only; it does not prove production parity, conversion, client outcomes, award status, or final award readiness.
  • ViewportDesktop, mobile, and reduced-motion captures.
  • AccessibilityCritical and serious accessibility scan.
P2current status

Current Status

The current review status is not award-ready.

What this shows
The stricter review replaced the older local-green language.
What it does not prove
A new independent review is required before any final award-ready claim.
  • BrandBrand and logo evidence still need to be included in the next review packet.
  • ReviewIndependent review needs self-contained evidence.
P3preview checked

Media Plan

The current media set has optimized versions and poster fallbacks.

What this shows
Media checks verify that the generated files, posters, and smaller preview versions exist.
What it does not prove
This does not prove production performance until current production browser evidence is captured.
  • FallbackPoster-first video surfaces and reduced-motion behavior.
  • ScopeNo new paid media added in this polish pass.
P4current status

Claim Policy

Outcome, award, client-logo, and testimonial claims stay blocked unless they are real.

What this shows
Demo pages and homepage proof chips label limits instead of implying client results.
What it does not prove
Future client pages need their own receipts before public outcome language is allowed.
  • Claims0 client outcome claims in current public copy.
  • GateAward-ready language remains blocked until independent reviewers rerun.
P5current status

Page Map

The main pages cover examples, services, process, details, motion, package, proof, and intake.

What this shows
Home, work, services, process, systems, proof, motion, specimen, start, logo-board, merged cases, and 404 recovery are locally checkable.
What it does not prove
Preview deploy and production launch checks are separate from this local page map.
  • RecoveryOn-brand 404 and visible navigation paths.
  • Cases/cases intentionally redirects to /work to avoid a redundant thin route.
A white launch archive shelf holding glass trays, paper stacks, and inspection rolls.
Existing Higgsfield Study / Launch Archive

An unused archive frame assigned to the open cell in the launch-check ledger.

Premium work should leave a clear trail: pages checked, assets verified, states tested, and launch decisions recorded.