PUREArchitecture & Health
Admin › Architecture & Health

Site health score

One number rolling up backups, brain, findings & deploy. Recomputed live.

DB tables
Live surfaces
Rows (est)
Open findings

Technology architecture

How PURE is layered, top to bottom. Headless front end one Supabase brain edge workers automated crons git deploy.

Browser / Mobileheadless HTML+JS Netlify (CDN)acquisto.biz, no build Supabase brainPostgres + ~280 RPCs Edge workerschat·comms·cron·mcp ~70 pg_cron jobssweeps·brain·backup GitHub NetlifyTestin.MikeSupabase Backup + PITRdaily·point-in-time
1
Headless front end · static HTML/JS on Netlify (acquisto.biz), no build step
live
2
Shared standards layer · pure-boot.js gate · flags · theme · table · close · topbar
live
3
Data + logic brain · Supabase Postgres · ~280 mcp_* RPCs · RLS
live
4
Edge workers · chat (Poppy LLM) · pure-comms (email/SMS) · pure-cron · pure-mcp
live
5
Automation · ~70 pg_cron jobs · nightly sweep group · brain rescan · backups
live
6
Deploy + backup · GitHub (Testin.MikeSupabase) Netlify auto-build · Supabase PITR
live

Backup posture

Layered, and now checkpointed nightly. Documented here so recovery is never a mystery.

Loading checkpoint…
Order of recovery: Supabase PITR (point-in-time) last daily backup GitHub repo (code + deploy source) protocol batches. Checkpoint cron: backup-checkpoint, 5 AM UTC nightly.

Weaknesses & improvement roadmap

From the weekly architecture audit (arch-audit-weekly) + standing scope. Findings are live from pure_arch_findings.

Loading findings…

Uptime & performance

Live speed + availability. Full detail on the Observability surface.

Loading…
Deep metrics + history: Observability · GTmetrix perf-audit wrapper is live.

2nd brain & guardrails

Dynamic links across surfaces, modules, orgs, and permissions — rescanned nightly.

Loading…