Skip to content
Browse documentation
Direction/Live

Public alpha launch checklist

Twenty evidence-led gates from repository hygiene through the recoverable Railway cutover.

Reviewed 2026-08-17 3 min read launch-checklist.md

This is CAPYN's 20-gate release register for the public alpha. A verified code gate means the repository contains the control and its automated evidence passed on 17 August 2026. It does not redefine the separate production gate for real funds.

#GateEvidenceStatus
1Repository hygieneSecret, placeholder, Java, Docker and debug-output sweepVerified
2Environment boundaryStrict environment parsing, log redaction and explicit proxy trustVerified
3Commercial contractOne plan catalogue drives limits, pricing and entitlementsVerified
4Payment readinessStripe Checkout, portal and signed webhook adaptersVerified
5Tenant securityOrganisation-scoped queries, role checks and IDOR testsVerified
6Quota concurrencyOrganisation and agent locks guard usage and spend reservationsVerified
7Authority lifecycleApproval races, replay, revocation and execution-time revalidation testedVerified
8Persistent billingPrisma subscription, usage and webhook schema plus migration invariantsVerified
9Product narrativeFour seeded decisions match the public demonstrationVerified
10API journeyAuthorization, approval and mock execution smoke pathVerified
11Website journeyPublic, docs and dashboard route smoke coverageVerified
12Search metadataTitles, descriptions, canonicals, Open Graph and JSON-LDVerified
13Crawl and headersRobots, sitemap, manifest, noindex and security headersVerified
14Interaction qualityResponsive, reduced-motion, keyboard and console reviewVerified
15DocumentationCanonical Markdown catalog rendered directly by the websiteVerified
16Release recordChangelog, explicit deferrals and this evidence registerVerified
17Full verificationLint, typecheck, unit/API/security tests and production buildsVerified
18Production smokeBuilt web and API exercised on isolated non-default portsVerified
19Public revisionAudited commits pushed and remote CI confirmedVerified
20Hosting cutoverRecoverable JudgeCat compute stop, CAPYN deploy and hosted verificationVerified

Commands

Run the complete repository gate:

corepack pnpm check
corepack pnpm audit --prod --audit-level high
corepack pnpm smoke:production
git diff --check

smoke:production starts the built API and web services temporarily on ports 4110 and 3110, verifies the four policy outcomes and public surfaces, then releases both ports. smoke:combined verifies the constrained one-service Railway adapter on three additional non-default ports. Neither requires Docker.

Hosted evidence

The synthetic public alpha is live at judgecat-production.up.railway.app. The 17 August 2026 cutover was verified against the deployed GitHub revision and a green remote CI run.

Hosted checks covered the four logical decisions, same-payload idempotency, conflicting-payload rejection, invalid credentials, agent-identity injection, denied execution, exact-request approval, approval replay, idempotent execution, least-privilege demo identity, Developer-plan metering and append-oriented audit output. They also covered all 22 public routes, all nine noindex dashboard routes, canonical and social metadata, JSON-LD, CSP, HSTS, robots, sitemap and the web manifest.

Railway's free-plan resource ceiling prevented a new project or second service. The authorized fallback stopped only JudgeCat's compute and reconnected that service to CAPYN. Its existing volume and domain records were preserved; no project, service, domain or volume was deleted.

Hosting safety boundary

The Railway cutover may stop JudgeCat's running compute only after CAPYN's public revision is green. Its persistent volume and custom domain remain intact so the stop is recoverable. Resource deletion is outside this checklist.

The hosted alpha remains a mock-execution developer demonstration. Stripe collection is available only when real provider credentials and price identifiers are supplied. Real settlement, production human identity, distributed rate limiting, provider reconciliation and the remaining controls in Security stay outside the public-alpha claim.