Launch gate status: RED
Latchwrit has strong app-level evidence in the checkout, but launch is not cleared while production access and domain verification remain unresolved.
Evidence qualifier: This report summarizes the latest known evidence in the repository. No live production capture or evidence timestamp is supplied in this checkout, so live production results are not independently verified here.
Why RED: unresolved HTTP 403 access and domain verification issues outweigh the repository-level passes below.
App-level evidence and repairs
What the checkout supports
These are repository checks, configuration facts, or documented browser journeys. They describe what is present in the app, not what has been observed on live production hosts.
PASS — repository evidence
Evidence source
`tests/e2e/launch-gate.spec.ts` and `tests/unit/supported-market-public-messaging.test.ts`
Interpretation
The checked-in journeys cover the homepage-to-readiness flow, supported Orlando and Tampa results, next actions, and browser error absence. Live production status is not independently verified here.
PASS — repository evidence
Evidence source
`tests/unit/pricing.test.ts`
Interpretation
The test covers the pricing API contract, approved monthly and annual offers, the client seed, and initial server-rendered markup. This is not a live checkout or payment claim.
PASS — repository evidence
Evidence source
`tests/unit/legal.test.ts`
Interpretation
The repository test covers complete pre-hydration content and route boundaries for Legal, Privacy, and Terms.
PASS — repository journey evidence
Evidence source
The maintained browser suite for `/contact`
Interpretation
A synthetic message reaches the success state without runtime or page errors. This does not claim real delivery or an owner response.
PASS — repository evidence
Evidence source
`tests/unit/supported-market-public-messaging.test.ts`
Interpretation
The regression limits public claims and city links to verified launch markets Orlando and Tampa and keeps unsupported-city metadata non-indexable.
COVERED IN TEST CONFIG
Evidence source
`playwright.config.ts` and `tests/README.md`
Interpretation
The configured browser projects cover desktop 1440×960 and iPhone 13 journeys. This is test coverage, not a recorded live production run.
PASS — source/config evidence
Evidence source
Launch-gate assertions and `next.user-config.ts`
Interpretation
Published source URLs are required to use `https://`, and non-canonical hosts are configured to redirect to `https://latchwrit.com`. A live certificate or host response was not checked here.
PASS — app configuration evidence
Evidence source
Public page metadata, metadata tests, sitemap, and robots configuration
Interpretation
Public routes define canonical metadata and supported-market titles and descriptions. Live crawler or indexing behavior is not verified in this checkout; robots indexing remains opt-in.
UNRESOLVED / RED IN PRODUCTION
Evidence source
`next.user-config.ts` and `tests/unit/canonical-domain-redirect.test.ts`
Interpretation
Rules exist for `latchwrit-2.polsia.app`, `latchwrit-2.polsia.io`, and `www.latchwrit.com` to redirect permanently to `https://latchwrit.com/:path*`. Live redirect behavior and domain ownership are not verified.
External dependency
Owner-blocked launch issues
These items require access to production and its domain infrastructure. They are separate from the app-level evidence above and remain unresolved in this checkout.
latchwrit.com and its configured source hosts before changing the launch status.What this means
The product surface has repository evidence for its key public journeys, but those checks cannot substitute for owner access to production. The launch gate stays RED until the 403 condition and domain verification are resolved and the live redirect chain is captured.