Skip to main content

Go-Live Readiness — ShareWiseAI — 2026-04-22T22:53Z

Summary​

Status: COMING SOON Product Health: N/A (not launched) Ops Instrumentation: N/A (not launched) Run date: 2026-04-22 Property config: C:/dev/knowledge/readiness/sharewise.yaml Codebase: churchwiseai-web/ at /social/* routes Production URL: https://sharewiseai.com (hostname rewrite to /social)

Presence check​

GET https://sharewiseai.com/
HTTP/1.1 200 OK  (X-Matched-Path: /social)
Server: Vercel / Next.js

Coming Soon landing page renders correctly. No 5xx. Response includes correct hostname rewrite to /social. Content-Security-Policy present and includes all social platform API domains (Facebook, Instagram, LinkedIn, Twitter, TikTok, Pinterest, YouTube).

Go-live blockers​

  • P0 oauth-integrations — Facebook, Instagram, X, TikTok, LinkedIn OAuth flows are code-complete in src/lib/social-oauth.ts (762 lines) and src/lib/social-publisher.ts (968 lines), but have never been tested end-to-end against real platform credentials. Real OAuth app registrations with Meta, Google, LinkedIn, X, and TikTok must be submitted, approved, and tested before launch.

  • P0 stripe-live-products — ShareWise has three test-mode Stripe products (prod_UBib20mCeszV1t Agency, prod_UBibA3AH4yuxvM Business, prod_UBibLjgRwdnbf7 Pro) but zero live-mode products. Live-mode products + prices must be created and wired to the checkout flow before any real subscriptions can be taken.

  • P0 publisher-service — Post scheduling and publishing queue (social-publisher.ts) is code-written but entirely untested against live platform APIs. Cannot verify publishing works until OAuth is functional.

  • P1 pilot-customers — No alpha/pilot customers onboarded. At minimum one real church account needs to run a full compose → schedule → publish cycle before the product is considered launch-ready.

  • P1 acceptance-specs-absent — sharewise.yaml declares acceptance_specs: []. No tier specs exist in knowledge/acceptance/ for any ShareWiseAI touchpoint (compose, schedule, publish, analytics). Per CLAUDE.md Rule 17, no customer-facing feature may be enabled without an approved spec.

  • P2 FA-021 — social-smoke.spec.ts exists in e2e/ (along with social-api.spec.ts, social-advanced.spec.ts, crud-social-*.spec.ts) but is excluded from CI as of 2026-04-03 because the product is not fully deployed. Must be re-added to test.yml before launch.

Current instrumentation state​

Code completeness (pre-launch):

  • Landing page (/social): complete, Coming Soon badge, waitlist CTA to email
  • Pricing page (/social/pricing): complete, Free/Pro/Business/Agency tiers shown
  • Login/signup pages: complete with form inputs
  • App shell (/social/app/*): 9 routes scaffolded (dashboard, compose, calendar, analytics, campaigns, library, platforms, settings, ai-advisor)
  • OAuth library: social-oauth.ts 762 lines — token exchange + meta fetch written
  • Publisher: social-publisher.ts 968 lines — queue logic written
  • AI content: social-ai.ts 213 lines — content generation written
  • Crypto: social-crypto.ts — token encryption written

Test files present (not in CI):

  • e2e/social-smoke.spec.ts — marketing page smoke tests
  • e2e/social-api.spec.ts — API contract tests
  • e2e/social-advanced.spec.ts — advanced flow tests
  • e2e/crud-social-campaigns.spec.ts
  • e2e/crud-social-platforms.spec.ts
  • e2e/crud-social-posts.spec.ts
  • e2e/crud-social-settings.spec.ts
  • src/test/unit/social-ai.test.ts — in CI (unit, no API calls)
  • src/test/unit/social-crypto.test.ts — in CI (unit)
  • src/test/unit/social-pricing.test.ts — in CI (unit)
  • src/test/unit/social-oauth.test.ts — excluded from CI (requires real OAuth tokens)
  • src/test/unit/social-platforms.test.ts — excluded from CI (requires real platform connections)

Stripe (test mode only):

  • prod_UBib20mCeszV1t — ShareWise AI Agency (test)
  • prod_UBibA3AH4yuxvM — ShareWise AI Business (test)
  • prod_UBibLjgRwdnbf7 — ShareWise AI Pro (test)
  • Live-mode products: 0

Monitoring: No cron health checks configured for ShareWiseAI. No analytics configured. No MailerLite automation wired beyond sharewise-waitlist group stub.

EvidenceValue
Landing page HTTP status200 OK
X-Matched-Path/social
Config fileC:/dev/knowledge/readiness/sharewise.yaml
Social lib filessrc/lib/social-oauth.ts (762L), src/lib/social-publisher.ts (968L), src/lib/social-ai.ts (213L)
Playwright specs7 spec files in churchwiseai-web/e2e/
Stripe test products3 (Agency, Business, Pro) — test mode only
CI statussocial-smoke.spec.ts excluded (FA-021, P2)
FOUNDER_ACTIONS entryFA-021 (P2 backlog)
Acceptance specs0 in knowledge/acceptance/
Pilot customers0

Delta from v1​

No v1 report existed in knowledge/readiness/reports/. This is the first structured scorecard for ShareWiseAI. All blockers match those declared in sharewise.yaml plus FA-021 surfaced from FOUNDER_ACTIONS.md and the acceptance-specs gap from direct inspection. No new blockers discovered beyond the declared list.