Skip to main content

Go-Live Readiness — Pro Website — 2026-04-17T15:00Z

Overall: 39% (NOT READY) — 1 P0, 10 P1, 1 P2 open

NOT READY driven by: (a) 1 P0 orphan Stripe subscription surfaced from ops_errors (portfolio-wide, not pro-website-specific), (b) 3 dimensions failing outright (journeys, knowledge, docs).

9 Dimensions​

#DimensionScoreStatusEvidence
1User journeys1/5❌ FAIL2 registry entries absent, 1 null, 1 of 2 acceptance specs missing
2Desktop/tablet/mobile—⚠ WARN4 specs exist, 0 recent runs recorded in registry
3Knowledge accuracy0/18❌ FAILderive --check drift + 17 validate_product_knowledge WARNINGs
4Onboarding/billing1/2⚠ WARNcritical-path-gate green on main, monthly Stripe validator never run
5User docs0/2❌ FAIL/help/pro-website → 404, canonical_source: null in YAML
6Drift & issues3/4⚠ WARN0 open P0/P1 founder actions, 0 high-severity mod, API drift clean — BUT 1 P0 orphan Stripe sub in ops_errors (since 2026-04-14)
7Analytics1/1✅ PASS/api/founder/readiness returns 200 in prod, Readiness tab wired
8Marketing funnel2/4⚠ WARNLanding + pricing 200, demo subdomain 404, synthetic funnel test null
9Agent monitoring1/2⚠ WARNNo resource overlaps; voice-agent-testing-backlog stale (started 2026-04-15)

Scoring: pass=1.0, warn=0.5, fail=0.0 → (1 + 2.5 + 0) / 9 = 39%

Punch list​

P0 — fix before go-live​

  • [Portfolio-wide] Orphan Stripe subscription since 2026-04-14 — a paying customer exists without a premium_churches row. ops_errors shows this P0 occurred 2× and is unresolved. This is the same incident that drove the webhook-inbox refactor. Surface to founder — do not auto-fix.

P1 — fix before marketing push​

  1. Missing acceptance spec: knowledge/acceptance/cwa-pro-website.md (declared in YAML, file absent)
  2. Missing registry entry: cwa-onboarding-wizard referenced by critical_journeys[0] but not found in knowledge/tests/registry.yaml
  3. Missing registry entry: cwa-pro-website-ssr referenced by critical_journeys[2] but not found in registry
  4. Null registry entry: critical_journeys[1].edit-hero-customize.registry_entry is explicitly null — no automated test for the hero/staff/colors editor flow
  5. Knowledge drift: pnpm derive --check failed — derived files out of sync with knowledge/data/*.yaml. Self-heal skipped because repo has uncommitted WIP from another agent (FRESHNESS_REPORT.md, pricing.yaml, products.yaml, chatbot/overview.md, premium-page/overview.md). Founder decision required.
  6. 17× product_knowledge WARNINGs: rows with empty/short answers across multiple questions (cancel, transfer admin, login fix, team members, save illustrations, LensLines, page info, previous admin left, etc.). Likely caused by the drift above.
  7. Help page 404: https://churchwiseai.com/help/pro-website returns 404 — Pro Website has no customer-facing documentation at all.
  8. Help canonical source null: Even if the page existed, there is no accountable source in the YAML (help_surface.canonical_source: null) — no one owns help content for this product.
  9. No synthetic funnel test: marketing_funnel.synthetic_funnel_test: null — the landing→pricing→checkout flow has no automated smoke test.
  10. Demo subdomain 404: Configured sample_public_url: https://grace-community.john316.church returns 404. Either the demo church doesn't exist yet on the new domain, DNS/routing isn't complete, or YAML config points at a fictional slug.

P2​

  • voice-agent-testing-backlog workstream in ACTIVE_WORK.md is stale (started 2026-04-15, no activity marker refreshed within 24h).

Self-healed this run​

None. Knowledge drift self-heal (pnpm derive) was skipped because the knowledge/ repo has uncommitted WIP from another agent session. Mixing a derive regeneration with unrelated WIP risks a dirty commit. Founder should either (a) direct me to stash the WIP and rerun derive, or (b) ask the other agent to finish their work first.

  • SOT check output: C:/Users/johnm/AppData/Local/Temp/sot.json (18 findings, exit 1)
  • API drift check: cd C:/dev/churchwiseai-web && bash scripts/check-api-drift.sh → ALL CHECKS PASSED
  • Latest Critical Path Protection GitHub Actions run on main: SUCCESS (commit 17f05bad)
  • Tests workflow on main: FAILURE (pre-existing; also failed on prior commit 7af32980 — not a regression from the readiness PR)
  • Supabase queries: founder_action_items, moderation_violations, ops_errors — see run SQL in scorecard JSON
  • Playwright specs referencing pro-website: e2e/pro-website-standalone.spec.ts, e2e/journeys/pro-suite-chat.spec.ts, e2e/delivers/acceptance/pewsearch-pro-website.spec.ts, e2e/delivers/acceptance/pewsearch-premium.spec.ts
  1. Before doing anything else: resolve the P0 orphan Stripe subscription (who paid, which customer, create the premium_churches row manually via onboard flow).
  2. Create knowledge/acceptance/cwa-pro-website.md by running through the founder-interview methodology (it's the standalone Pro Website sales path — distinct from the PewSearch legacy path).
  3. Add 3 registry entries: cwa-onboarding-wizard, cwa-pro-website-ssr, and a new cwa-pro-website-edit entry to cover the hero/staff/colors editor journey.
  4. Coordinate with the other agent holding the knowledge/ repo WIP, then run pnpm derive to clear drift + the 17 PK warnings.
  5. Create /help/pro-website page with real content, and populate help_surface.canonical_source in YAML.
  6. Add a synthetic funnel test (e2e/synthetic/pro-website-funnel.spec.ts) that drives landing → pricing → /onboard → Stripe test-mode checkout.
  7. Verify grace-community.john316.church — either provision it or update YAML to point at a real demo subdomain.

Generated by /ensure-solid pro-website.