⚡ Johnson/Turner — Ops Hub

Single entry point to app environments, tools & docs. Internal & access-gated.

Access: D11 admin set (Chris, Dex, Mara, Tim, Jared) + onboarded collaborators · gated by Cloudflare Access

DIYvorce — Environments

DEV / Live app DEV
jt-diyvorce · current working data (April Wilson matter)
UAT / Staging UAT
jt-diyvorce-uat · acceptance testing before prod
Production BLOCKED
Blocked on SF Gate-1 (prod integration user + perm-set)

DIYvorce — Supabase (databases + edge functions + auth)

DEV project DEV
nljznilrhgwxtdyugftx
UAT project UAT
jeourmiqvxomdogsncex
PROD project PROD
pyrajicnlmekchtwgagt · schema ready, awaiting cutover

Platform & Tools

Cloudflare
Workers (hosting), Access (gating), analytics
GitHub — johnson-turner org
Code, CI/CD, ops repos
DIYvorce app repo
jt-diyvorce-app · branch ladder develop→staging→main
Ops repo (the shared brain)
diyvorce-ops · plans, decisions, runbooks, journals
Salesforce
System of record — matters, contacts, billing, team
Box
Client documents + creative/marketing assets

Key Docs & Runbooks (in the ops repo)

Go-Live Master Plan
The 6-workstream plan + decisions
Architecture Overview
How every system fits together
Prod Cutover Checklist
The gate between sandbox and real clients
Rollback Runbook
Break-glass: revert a bad deploy
Breach Response
Security incident procedure
Access & Revocation
Onboarding + credential isolation + revocation

Coming soon (v2 / v3)

v2 — Live status: per-environment up/down health, last-deploy info.
v3 — Usage & adoption: matters onboarded, active clients, questionnaire completion rate, payments, traffic — pulled from Supabase + Cloudflare analytics.
As Fairwell, the client portal, and other apps come online, they get their own sections here.