Slowburn Supabase Owner Evidence Template

Use this after running supabase/owner-run-all.sql or the separate schema, RLS, and verification SQL files in your own Supabase SQL Editor.

Paste back only non-secret proof values. Do not paste service-role keys, database passwords, JWT secrets, payment secrets, private user exports, or screenshots that show secrets.

schema_sql_success: yes/no
rls_sql_success: yes/no
rls_contract_passed: yes/no
verification_queries_reviewed: yes/no
table_inventory_count: number
rls_enabled_table_count: number
authenticated_table_grant_missing_rows: number
catalog_write_policy_rows: number
subscription_write_policy_rows: number
owner_policy_summary_reviewed: yes/no
notes: optional non-secret notes only

Expected clean values after a correct first run:

schema_sql_success: yes
rls_sql_success: yes
rls_contract_passed: yes
verification_queries_reviewed: yes
table_inventory_count: 42
rls_enabled_table_count: 42
authenticated_table_grant_missing_rows: 0
catalog_write_policy_rows: 0
subscription_write_policy_rows: 0
owner_policy_summary_reviewed: yes

This template does not prove the database is live by itself. Codex must still review the non-secret evidence, run the local gates, and keep auth, writes, uploads, billing, real sync, and local data clear blocked until the full proof chain passes.