Knowledge > Runbooks > Technical Operations
Technical Operations Runbooks
Runbooks for database management, API debugging, infrastructure maintenance, and security operations across all ChurchWiseAI properties.
Runbooks
| Runbook | Description |
|---|---|
| supabase-migration.md | Run a database schema migration safely |
| db-performance.md | Investigate and resolve slow database queries |
| stripe-webhook-debug.md | Debug a Stripe webhook that failed or wasn't processed |
| embedding-regeneration.md | Regenerate vector embeddings in unified_rag_content |
| view-refresh.md | Refresh Supabase materialized views or cached aggregates |
| analytics-query.md | Query product analytics for reporting |
| error-log-triage.md | Triage and resolve error reports from ops_error_reports |
| security-incident.md | Respond to a security incident (exposed key, unauthorized access) |
| backup-verify.md | Verify Supabase data backups are intact |
| cost-audit.md | Audit monthly service costs across all vendors |
| running-tests.md | Where all test suites live and how to run them |
Safety Rules (Read First)
- ONE production Supabase — no staging. Every query hits live data.
- NEVER run DELETE/DROP/TRUNCATE without explicit founder approval.
unified_rag_contenthas 327K irreplaceable records — treat with extreme care.- Always filter
churcheswithdirectory_visible=true— 218K visible, 261K total. - Always paginate with
.range(offset, offset+999)— default 1000-row limit. - Stripe live mode requires
--api-key $STRIPE_LIVE_SECRET_KEY. Confirm with founder before writes.