sprocket-oauth
Connect ChatGPT to pre-approved company identities.
One MakeGood console for Hostinger, Supabase, Sprocket OAuth, Reclaim, and PoC release validation.
The front end stays lightweight. Authorization and company intelligence stay behind the backend boundary.
Host the operator experience on Hostinger. Keep data authority in Supabase.
Only browser-safe connection values live here.
No sb_secret_…, no service-role JWT, no database password, no OAuth client secret.
The console tracks execution. Supabase SQL Editor remains the migration surface.
supabase/01_base_schema.sqlCompany, knowledge, settings, history.
supabase/02_single_gpt_identity_oauth_rbac.sqlUsers, roles, permissions, clients, codes, tokens.
supabase/03_bootstrap_company_oauth_and_roles.sqlCreate company and save the raw OAuth secret outside this console.
supabase/04_add_or_update_user.sqlProvision Owner and Developing Estimator identities.
supabase/11_reclaim_legacy_history.sqlImports, conversations, messages, evidence, review state.
Edge Functions enforce identity, capabilities, financial visibility, and Reclaim publishing.
Connect ChatGPT to pre-approved company identities.
Load current user role and filter company intelligence.
Operator-only legacy history intake and publish boundary.
Avoid wildcard CORS for privileged Reclaim endpoints.
Configure Hostinger URL firstGenerate the Action settings and register the callback.
MakeGood imports the contractor’s prior AI estimating history before PoC release.
The critical PoC test is simple: same Sprocket, separate authenticated people, correct backend visibility.
Complete the required configuration and acceptance checks.