Skip to content

Admin BWS DB Reference Validation

Date: 2026-08-29
Context: Confirm paused admin BWS refs are intentional hosted (Tier 6), not stale-wrong like RealOutcomes regression.

Summary

Check Result
Admin owns sovereign DB VM No — app-only BFF on VM 115
LAST1ADMIN_*_DATABASE_URL in BWS None (admin uses Supabase HTTP + service role, not direct app DATABASE_URL)
Hosted Supabase URLs in APP keys Intentional — points at live hosted projects admin proxies today
Stale deleted project refs None found

Admin BWS state is consistent with paused Tier 3 design. No corrective action before Tier 6.

Key inventory

Key URL / project Intentional?
LAST1ADMIN_APP_PROD_SUPABASE_URL https://tcthzakppndkykatoefx.supabase.co Yes — admin shared Supabase
LAST1ADMIN_APP_PROD_VITE_SUPABASE_URL same Yes — SPA build
LAST1ADMIN_APP_PROD_ONSET_SUPABASE_URL https://emxrmjysvxeboavhatry.supabase.co Yes — admin → Onset hosted (until Onset T-5)
LAST1ADMIN_APP_PROD_RADIOCHECK_SUPABASE_URL https://tcthzakppndkykatoefx.supabase.co Yes — RadioCheck hosted
Legacy unprefixed VITE_SUPABASE_URL tcthzakppndkykatoefx Legacy; render uses LAST1ADMIN_APP_PROD_*

Not expected until Tier 6: LAN URLs for RealOutcomes/Onset/RadioCheck/last1.app sovereign stacks.

Tier 6 reconnect (future)

When Ryan authorizes admin resume:

  1. Update LAST1ADMIN_APP_PROD_* upstream URLs to sovereign LAN or prod DNS per product.
  2. Run push-db-stack-bws.py is N/A (admin has no {product}-db).
  3. Re-render + recreate last1admin-app container after env change.

References