Started
Reviewer Evidence Index
Connect the live product, case study, pricing page, production gates, CI, release evidence, and commercial verifier into one public review path.
This page marks the next stage after the portfolio release: make the productization path visible, scoped, and verifiable while identity, billing, analytics, and support mature in explicit stages.
Commercial Readiness Tracks
Connect the live product, case study, pricing page, production gates, CI, release evidence, and commercial verifier into one public review path.
Define how the existing capability-account model graduates into conventional accounts, passkeys, tenant ownership, and supportable recovery.
Plan limits, subscription precedence, hosted Checkout, Portal, signed webhooks, event idempotency, fixed grace periods, and live AI usage metering now live in code.
Server-confirmed generation, cloud-save, and public-share milestones now measure anonymous journeys without logging founder briefs, evidence notes, sources, or provider payloads.
Expose decision-history quality, visual regression, cloud smoke, release evidence, and latency-risk decisions as operator-facing proof.
Update the threat model for checkout, account linking, support access, audit logs, public shares, retention, and deletion.
Entitlement Contract
The public deployment defaults to Team preview so tenant and RBAC smoke tests stay exercisable. Persisted subscription state takes precedence without rewriting workspace code.
/api/commercial/entitlementsFree demo
not-wired
Solo
stripe-ready
Team
stripe-ready
Reviewer Evidence Index
The readiness package is checked by scripts before release gates and production verification run.
npm run verify:commercial-readinessChecks this public stage, the detailed plan, README, case study, maturity note, roadmap, and task list stay linked.npx vitest run src/lib/launchlens/commercial-entitlements.test.ts src/app/api/commercial/entitlements/route.test.tsProves Free, Solo, and Team plan limits resolve to reviewer-safe API output and stable plan-limit codes.npx vitest run src/lib/launchlens/commercial-subscription.test.ts src/lib/launchlens/stripe-server.test.ts src/app/api/webhooks/stripe/route.test.tsProves billing-state precedence, fixed grace periods, signed event projection, and duplicate delivery handling.npx vitest run src/lib/launchlens/live-provider-usage.test.ts src/app/api/generate/route.live-usage.test.ts src/app/api/decision/route.live-usage.test.tsProves monthly live AI allowance is consumed before real provider calls and skipped for demo mode.npm run verify:portfolioKeeps the reviewer-facing story, public pages, demo script, and release handoff connected.npm run verify:production-demoRuns the public status check and Playwright e2e suite against the deployed production URL.npm run release:cloudVerifies migration, schema, cloud save/recovery/share privacy, tenant isolation, and RBAC smoke.npm run decision:history -- --window --size 5 --drift-threshold 5Keeps cited decision quality from drifting silently across recent eval runs.Current to next
Registration-free capability account with recovery key.
Decide how anonymous trials, passkeys, OAuth, tenant ownership, and account deletion coexist.
Operational Billing page with Stripe-ready Checkout, Portal, subscription state, idempotent webhooks, quota precedence, and live AI usage metering.
Run an account-owned Stripe sandbox acceptance flow, provision production prices, and archive activation evidence.
Quick-start guide, deterministic samples, and a privacy-minimized generation-to-handoff funnel.
Run 5–10 real-user sessions, then add only the evidence, decision, or re-entry events justified by observed friction.
CI, visual regression, CodeQL, cloud smoke, provider eval, and decision eval.
Expose release evidence, drift thresholds, latency risk, and owner response paths as a readable ops surface.
The stage is accepted only when the readiness verifier, portfolio verifier, release readiness verifier, production demo, and cloud gate all pass after deployment.
This phase does not pretend to ship merchant activation, OAuth, a support console, or an analytics warehouse. Stripe integration code and a minimal product funnel are present; external account activation remains a separate acceptance step.
Run the real-user activation study, complete the identity and tenant migration design, then add only the retention or flow changes supported by the resulting evidence.