knowledge-base.md881 lines · main

1	# Doltgres - knowledge base
2
3
4
5
6	# Briven Auth rebuild — SuperTokens knowledge base
7
8	Purpose: Library cabinet for LLM agents building new Briven Auth.
9	These are reference docs from SuperTokens — borrow good product/architecture ideas.
10	Briven Auth stays Briven-branded, multi-tenant on Briven Doltgres, not a raw SuperTokens install.
11
12	Date filed: 2026-07-22
13	URL count: 492 unique
14
15	## How agents should use this
16
17	### HARD RULE (flndrn, 2026-07-26 — never break)
18
19	Before any Auth change (magic link, OTP, OAuth/Konnos, sessions, MFA, passkeys, FDI, IdP, SSO, providers, secrets, allowed domains, enable/disable Auth, or any code under Auth surfaces):
20
21	1. You must open this file first.
22	2. You must open the matching SuperTokens section/URL below for that feature.
23	3. You must not guess login behavior. SuperTokens is the product map; Briven implements Briven-branded on Doltgres.
24	4. State in one plain sentence what the SuperTokens/KB behavior is, then code.
25
26	Also written into project root `CLAUDE.md`. Skipping this step is a rule violation, not a style preference.
27
28	### Always
29
30	1. Prefer Briven product rules (Doltgres-first, project isolation, `pk_briven_auth_`, no inventing Clerk).
31	2. For any database / Doltgres / Postgres-wire problem, open the Doltgres / Dolt official knowledge base section at the bottom of this file first (URLs from `AI_DOCS/dolt-reference/`). Also read `AI_DOCS/dolt-reference/00-doltgres-truth.md`.
32	3. When stuck on a login feature (sessions, passwordless, MFA, etc.), open the matching SuperTokens section below and keep Doltgres constraints from the Doltgres section.
33	4. Translate Supabase/MySQL examples to Briven Doltgres using official Doltgres docs — do not invent.
34	5. Do not paste SuperTokens branding into Briven UI — yellow Auth sub-dashboard, Briven styling.
35	6. Never abandon SuperTokens Core or change Auth architecture after one SQL error without reading Doltgres docs and notifying flndrn.
36
37	## Quickstart
38
39	- https://supertokens.com/docs/quickstart/introduction
40	- https://supertokens.com/docs/quickstart/frontend-setup
41	- https://supertokens.com/docs/quickstart/backend-setup
42	- https://supertokens.com/docs/quickstart/next-steps
43	- https://supertokens.com/docs/quickstart/example-applications
44	- https://supertokens.com/docs/quickstart/build-with-ai-tools
45
46	## Quickstart integrations
47
48	- https://supertokens.com/docs/quickstart/integrations/overview
49	- https://supertokens.com/docs/quickstart/integrations/aws-lambda/quickstart-guide
50	- https://supertokens.com/docs/quickstart/integrations/aws-lambda/session-verification
51	- https://supertokens.com/docs/quickstart/integrations/aws-lambda/appsync-integration
52	- https://supertokens.com/docs/quickstart/integrations/graphql
53	- https://supertokens.com/docs/quickstart/integrations/hasura
54	- https://supertokens.com/docs/quickstart/integrations/nestjs
55	- https://supertokens.com/docs/quickstart/integrations/netlify
56	- https://supertokens.com/docs/quickstart/integrations/nextjs/app-directory/about
57	- https://supertokens.com/docs/quickstart/integrations/nextjs/app-directory/init
58	- https://supertokens.com/docs/quickstart/integrations/nextjs/app-directory/setting-up-frontend
59	- https://supertokens.com/docs/quickstart/integrations/nextjs/app-directory/setting-up-backend
60	- https://supertokens.com/docs/quickstart/integrations/nextjs/app-directory/protecting-route
61	- https://supertokens.com/docs/quickstart/integrations/nextjs/app-directory/protecting-backend/session-verification-session-guard
62	- https://supertokens.com/docs/quickstart/integrations/nextjs/app-directory/protecting-backend/session-verification-middleware
63	- https://supertokens.com/docs/quickstart/integrations/nextjs/app-directory/server-components-requests
64	- https://supertokens.com/docs/quickstart/integrations/nextjs/app-directory/next-steps
65	- https://supertokens.com/docs/quickstart/integrations/nextjs/pages-directory/about
66	- https://supertokens.com/docs/quickstart/integrations/nextjs/pages-directory/init
67	- https://supertokens.com/docs/quickstart/integrations/nextjs/pages-directory/setting-up-frontend
68	- https://supertokens.com/docs/quickstart/integrations/nextjs/pages-directory/setting-up-backend
69	- https://supertokens.com/docs/quickstart/integrations/nextjs/pages-directory/protecting-route
70	- https://supertokens.com/docs/quickstart/integrations/nextjs/pages-directory/protecting-backend/in-api
71	- https://supertokens.com/docs/quickstart/integrations/nextjs/pages-directory/protecting-backend/in-ssr
72	- https://supertokens.com/docs/quickstart/integrations/nextjs/pages-directory/next-steps
73	- https://supertokens.com/docs/quickstart/integrations/supabase(Needs — Map to Briven Doltgres (not Supabase) when implementing.
74	- https://supertokens.com/docs/quickstart/integrations/vercel
75
76	## Authentication recipes
77
78	- https://supertokens.com/docs/authentication/overview
79	- https://supertokens.com/docs/authentication/email-password/introduction
80	- https://supertokens.com/docs/authentication/email-password/customize-the-sign-in-form
81	- https://supertokens.com/docs/authentication/email-password/customize-the-sign-up-form
82	- https://supertokens.com/docs/authentication/email-password/hooks-and-overrides
83	- https://supertokens.com/docs/authentication/email-password/password-hashing
84	- https://supertokens.com/docs/authentication/email-password/implement-username-login
85	- https://supertokens.com/docs/authentication/email-password/password-reset
86	- https://supertokens.com/docs/authentication/email-password/disable-signup
87	- https://supertokens.com/docs/authentication/email-password/password-managers
88	- https://supertokens.com/docs/authentication/passwordless/introduction
89	- https://supertokens.com/docs/authentication/passwordless/initial-setup
90	- https://supertokens.com/docs/authentication/passwordless/customize-the-magic-link
91	- https://supertokens.com/docs/authentication/passwordless/customize-the-otp
92	- https://supertokens.com/docs/authentication/passwordless/hooks-and-overrides
93	- https://supertokens.com/docs/authentication/passwordless/configure-email-and-sms-behavior
94	- https://supertokens.com/docs/authentication/passwordless/invite-link-flow
95	- https://supertokens.com/docs/authentication/passwordless/allow-list-flow
96	- https://supertokens.com/docs/authentication/social/introduction
97	- https://supertokens.com/docs/authentication/social/initial-setup
98	- https://supertokens.com/docs/authentication/social/built-in-providers-config
99	- https://supertokens.com/docs/authentication/social/custom-providers
100	- https://supertokens.com/docs/authentication/social/hooks-and-overrides
101	- https://supertokens.com/docs/authentication/social/add-multiple-clients-for-the-same-provider
102	- https://supertokens.com/docs/authentication/social/custom-invite-flow
103	- https://supertokens.com/docs/authentication/enterprise/introduction
104	- https://supertokens.com/docs/authentication/enterprise/important-concepts
105	- https://supertokens.com/docs/authentication/enterprise/initial-setup
106	- https://supertokens.com/docs/authentication/enterprise/common-domain-login
107	- https://supertokens.com/docs/authentication/enterprise/subdomain-login
108	- https://supertokens.com/docs/authentication/enterprise/tenant-discovery
109	- https://supertokens.com/docs/authentication/enterprise/manage-tenants
110	- https://supertokens.com/docs/authentication/enterprise/tenant-management-plugin
111	- https://supertokens.com/docs/authentication/enterprise/manage-apps
112	- https://supertokens.com/docs/authentication/enterprise/saml
113	- https://supertokens.com/docs/authentication/enterprise/legacy-saml
114	- https://supertokens.com/docs/authentication/unified-login/introduction
115	- https://supertokens.com/docs/authentication/unified-login/oauth2-basics
116	- https://supertokens.com/docs/authentication/unified-login/quickstart-guides/multiple-frontends-with-a-single-backend
117	- https://supertokens.com/docs/authentication/unified-login/quickstart-guides/multiple-frontends-with-separate-backends
118	- https://supertokens.com/docs/authentication/unified-login/quickstart-guides/reuse-website-login
119	- https://supertokens.com/docs/authentication/unified-login/work-with-scopes
120	- https://supertokens.com/docs/authentication/unified-login/verify-tokens
121	- https://supertokens.com/docs/authentication/unified-login/add-custom-claims-in-tokens
122	- https://supertokens.com/docs/authentication/m2m/introduction
123	- https://supertokens.com/docs/authentication/m2m/client-credentials
124	- https://supertokens.com/docs/authentication/m2m/legacy-flow
125	- https://supertokens.com/docs/authentication/passkeys/introduction
126	- https://supertokens.com/docs/authentication/passkeys/important-concepts
127	- https://supertokens.com/docs/authentication/passkeys/initial-setup
128	- https://supertokens.com/docs/authentication/passkeys/customization
129	- https://supertokens.com/docs/authentication/ai-authentication
130
131	## Additional verification (sessions, MFA, roles, captcha)
132
133	- https://supertokens.com/docs/additional-verification/session-verification/protect-api-routes
134	- https://supertokens.com/docs/additional-verification/session-verification/protect-frontend-routes
135	- https://supertokens.com/docs/additional-verification/session-verification/ssr
136	- https://supertokens.com/docs/additional-verification/session-verification/with-websocket
137	- https://supertokens.com/docs/additional-verification/session-verification/claim-validation
138	- https://supertokens.com/docs/additional-verification/mfa/introduction
139	- https://supertokens.com/docs/additional-verification/mfa/important-concepts
140	- https://supertokens.com/docs/additional-verification/mfa/initial-setup
141	- https://supertokens.com/docs/additional-verification/mfa/totp/totp-for-all-users
142	- https://supertokens.com/docs/additional-verification/mfa/totp/totp-for-opt-in-users
143	- https://supertokens.com/docs/additional-verification/mfa/email-sms-otp/otp-for-all-users
144	- https://supertokens.com/docs/additional-verification/mfa/email-sms-otp/otp-for-opt-in-users
145	- https://supertokens.com/docs/additional-verification/mfa/webauthn-setup
146	- https://supertokens.com/docs/additional-verification/mfa/backup-codes
147	- https://supertokens.com/docs/additional-verification/mfa/step-up-auth
148	- https://supertokens.com/docs/additional-verification/mfa/embed-the-prebuilt-ui
149	- https://supertokens.com/docs/additional-verification/mfa/protect-routes
150	- https://supertokens.com/docs/additional-verification/mfa/hooks-and-overrides
151	- https://supertokens.com/docs/additional-verification/mfa/migration/legacy-to-new
152	- https://supertokens.com/docs/additional-verification/mfa/migration/old-sdk-to-new
153	- https://supertokens.com/docs/additional-verification/mfa/legacy-mfa/legacy-vs-new
154	- https://supertokens.com/docs/additional-verification/mfa/legacy-mfa/how-it-works
155	- https://supertokens.com/docs/additional-verification/mfa/legacy-mfa/backend-setup/first-factor
156	- https://supertokens.com/docs/additional-verification/mfa/legacy-mfa/backend-setup/second-factor
157	- https://supertokens.com/docs/additional-verification/mfa/legacy-mfa/backend-setup/protecting-api
158	- https://supertokens.com/docs/additional-verification/mfa/legacy-mfa/frontend-custom
159	- https://supertokens.com/docs/additional-verification/mfa/legacy-mfa/prebuilt-ui/init
160	- https://supertokens.com/docs/additional-verification/mfa/legacy-mfa/prebuilt-ui/showing-login-ui
161	- https://supertokens.com/docs/additional-verification/mfa/legacy-mfa/prebuilt-ui/protecting-routes
162	- https://supertokens.com/docs/additional-verification/email-verification/introduction
163	- https://supertokens.com/docs/additional-verification/email-verification/initial-setup
164	- https://supertokens.com/docs/additional-verification/email-verification/protecting-routes
165	- https://supertokens.com/docs/additional-verification/email-verification/manual-actions
166	- https://supertokens.com/docs/additional-verification/email-verification/embed-in-page
167	- https://supertokens.com/docs/additional-verification/email-verification/changing-style
168	- https://supertokens.com/docs/additional-verification/email-verification/hooks-and-overrides
169	- https://supertokens.com/docs/additional-verification/attack-protection-suite/introduction
170	- https://supertokens.com/docs/additional-verification/attack-protection-suite/initial-setup
171	- https://supertokens.com/docs/additional-verification/user-roles/introduction
172	- https://supertokens.com/docs/additional-verification/user-roles/initial-setup
173	- https://supertokens.com/docs/additional-verification/user-roles/role-management-actions
174	- https://supertokens.com/docs/additional-verification/user-roles/protecting-routes
175	- https://supertokens.com/docs/additional-verification/captcha
176
177	## Post-authentication (sessions, users, dashboard)
178
179	- https://supertokens.com/docs/post-authentication/post-login-redirect
180	- https://supertokens.com/docs/post-authentication/session-management/introduction
181	- https://supertokens.com/docs/post-authentication/session-management/access-session-data
182	- https://supertokens.com/docs/post-authentication/session-management/session-invalidation
183	- https://supertokens.com/docs/post-authentication/session-management/share-session-across-sub-domains
184	- https://supertokens.com/docs/post-authentication/session-management/switch-between-cookies-and-header-authentication
185	- https://supertokens.com/docs/post-authentication/session-management/advanced-workflows/anonymous-session
186	- https://supertokens.com/docs/post-authentication/session-management/advanced-workflows/user-impersonation
187	- https://supertokens.com/docs/post-authentication/session-management/advanced-workflows/customize-error-handling
188	- https://supertokens.com/docs/post-authentication/session-management/advanced-workflows/multiple-api-endpoints
189	- https://supertokens.com/docs/post-authentication/session-management/advanced-workflows/disable-frontend-interceptors
190	- https://supertokens.com/docs/post-authentication/session-management/advanced-workflows/in-iframe
191	- https://supertokens.com/docs/post-authentication/session-management/advanced-workflows/access-token-blacklisting
192	- https://supertokens.com/docs/post-authentication/session-management/security
193	- https://supertokens.com/docs/post-authentication/user-management/introduction
194	- https://supertokens.com/docs/post-authentication/user-management/common-actions
195	- https://supertokens.com/docs/post-authentication/user-management/allow-users-to-update-their-data
196	- https://supertokens.com/docs/post-authentication/user-management/user-metadata
197	- https://supertokens.com/docs/post-authentication/user-management/user-profile
198	- https://supertokens.com/docs/post-authentication/user-management/account-deduplication
199	- https://supertokens.com/docs/post-authentication/user-management/user-banning
200	- https://supertokens.com/docs/post-authentication/user-management/progressive-profiling
201	- https://supertokens.com/docs/post-authentication/account-linking/introduction
202	- https://supertokens.com/docs/post-authentication/account-linking/important-concepts
203	- https://supertokens.com/docs/post-authentication/account-linking/automatic-account-linking
204	- https://supertokens.com/docs/post-authentication/account-linking/manual-account-linking
205	- https://supertokens.com/docs/post-authentication/account-linking/link-social-accounts
206	- https://supertokens.com/docs/post-authentication/account-linking/add-passwords-to-an-existing-account
207	- https://supertokens.com/docs/post-authentication/dashboard/introduction
208	- https://supertokens.com/docs/post-authentication/dashboard/initial-setup
209	- https://supertokens.com/docs/post-authentication/dashboard/user-management
210	- https://supertokens.com/docs/post-authentication/dashboard/tenant-management
211
212	## Migration
213
214	- https://supertokens.com/docs/migration/overview
215	- https://supertokens.com/docs/migration/account-migration
216	- https://supertokens.com/docs/migration/session-migration
217	- https://supertokens.com/docs/migration/legacy/about
218	- https://supertokens.com/docs/migration/legacy/account-creation/user-creation
219	- https://supertokens.com/docs/migration/legacy/account-creation/user-id-mapping
220	- https://supertokens.com/docs/migration/legacy/account-creation/email-verification
221	- https://supertokens.com/docs/migration/legacy/account-creation/ep-migration-without-password-hash
222	- https://supertokens.com/docs/migration/legacy/data-migration
223	- https://supertokens.com/docs/migration/legacy/session-migration
224	- https://supertokens.com/docs/migration/legacy/mfa-migration
225	- https://supertokens.com/docs/migration/rownd/migration-steps
226	- https://supertokens.com/docs/migration/rownd/sdk-integration-guide
227
228	## Platform configuration
229
230	- https://supertokens.com/docs/platform-configuration/supertokens-core/api-keys
231	- https://supertokens.com/docs/platform-configuration/supertokens-core/ip-allow-deny
232	- https://supertokens.com/docs/platform-configuration/supertokens-core/add-ssl-via-nginx
233	- https://supertokens.com/docs/platform-configuration/supertokens-core/base-path
234	- https://supertokens.com/docs/platform-configuration/supertokens-core/cli
235	- https://supertokens.com/docs/platform-configuration/email-delivery
236	- https://supertokens.com/docs/platform-configuration/sms-delivery
237
238	## Deployment
239
240	- https://supertokens.com/docs/deployment/self-host-supertokens
241	- https://supertokens.com/docs/deployment/rate-limits
242	- https://supertokens.com/docs/deployment/scalability
243	- https://supertokens.com/docs/deployment/telemetry
244	- https://supertokens.com/docs/deployment/migrate-from-mysql(Needs — Map to Migrate from MySQL → Doltgres for Briven.
245
246	## References (SDKs, FDI, CDI, plugins, testing)
247
248	- https://supertokens.com/docs/references/plugins/introduction
249	- https://supertokens.com/docs/references/plugins/captcha-nodejs
250	- https://supertokens.com/docs/references/plugins/captcha-react
251	- https://supertokens.com/docs/references/plugins/opentelemetry-nodejs
252	- https://supertokens.com/docs/references/plugins/profile-base-react
253	- https://supertokens.com/docs/references/plugins/profile-details-nodejs
254	- https://supertokens.com/docs/references/plugins/profile-details-react
255	- https://supertokens.com/docs/references/plugins/profile-details-shared
256	- https://supertokens.com/docs/references/plugins/progressive-profiling-nodejs
257	- https://supertokens.com/docs/references/plugins/progressive-profiling-react
258	- https://supertokens.com/docs/references/plugins/progressive-profiling-shared
259	- https://supertokens.com/docs/references/plugins/tenant-discovery-nodejs
260	- https://supertokens.com/docs/references/plugins/tenant-discovery-react
261	- https://supertokens.com/docs/references/plugins/tenants-nodejs
262	- https://supertokens.com/docs/references/plugins/tenants-react
263	- https://supertokens.com/docs/references/plugins/user-banning-nodejs
264	- https://supertokens.com/docs/references/plugins/user-banning-react
265	- https://supertokens.com/docs/references/frontend-sdks/reference
266	- https://supertokens.com/docs/references/frontend-sdks/function-overrides
267	- https://supertokens.com/docs/references/frontend-sdks/hooks
268	- https://supertokens.com/docs/references/frontend-sdks/prebuilt-ui/changing-colours
269	- https://supertokens.com/docs/references/frontend-sdks/prebuilt-ui/changing-style
270	- https://supertokens.com/docs/references/frontend-sdks/prebuilt-ui/override-react-components
271	- https://supertokens.com/docs/references/frontend-sdks/prebuilt-ui/embed-sign-in-up-form
272	- https://supertokens.com/docs/references/frontend-sdks/prebuilt-ui/shadow-dom
273	- https://supertokens.com/docs/references/frontend-sdks/prebuilt-ui/toc-privacypolicy
274	- https://supertokens.com/docs/references/frontend-sdks/prebuilt-ui/translations
275	- https://supertokens.com/docs/references/frontend-sdks/prebuilt-ui/ui-showcase
276	- https://supertokens.com/docs/references/frontend-sdks/supertokens-auth-react/package
277	- https://supertokens.com/docs/references/frontend-sdks/supertokens-auth-react/types
278	- https://supertokens.com/docs/references/frontend-sdks/supertokens-auth-react/recipe-emailpassword-types
279	- https://supertokens.com/docs/references/frontend-sdks/supertokens-auth-react/recipe-emailpassword
280	- https://supertokens.com/docs/references/frontend-sdks/supertokens-auth-react/recipe-emailverification-types
281	- https://supertokens.com/docs/references/frontend-sdks/supertokens-auth-react/recipe-emailverification
282	- https://supertokens.com/docs/references/frontend-sdks/supertokens-auth-react/recipe-multifactorauth-types
283	- https://supertokens.com/docs/references/frontend-sdks/supertokens-auth-react/recipe-multifactorauth
284	- https://supertokens.com/docs/references/frontend-sdks/supertokens-auth-react/recipe-multitenancy-types
285	- https://supertokens.com/docs/references/frontend-sdks/supertokens-auth-react/recipe-multitenancy
286	- https://supertokens.com/docs/references/frontend-sdks/supertokens-auth-react/recipe-oauth2provider-types
287	- https://supertokens.com/docs/references/frontend-sdks/supertokens-auth-react/recipe-oauth2provider
288	- https://supertokens.com/docs/references/frontend-sdks/supertokens-auth-react/recipe-passwordless-types
289	- https://supertokens.com/docs/references/frontend-sdks/supertokens-auth-react/recipe-passwordless
290	- https://supertokens.com/docs/references/frontend-sdks/supertokens-auth-react/recipe-session-types
291	- https://supertokens.com/docs/references/frontend-sdks/supertokens-auth-react/recipe-session
292	- https://supertokens.com/docs/references/frontend-sdks/supertokens-auth-react/recipe-thirdparty-types
293	- https://supertokens.com/docs/references/frontend-sdks/supertokens-auth-react/recipe-thirdparty
294	- https://supertokens.com/docs/references/frontend-sdks/supertokens-auth-react/recipe-totp-types
295	- https://supertokens.com/docs/references/frontend-sdks/supertokens-auth-react/recipe-totp
296	- https://supertokens.com/docs/references/frontend-sdks/supertokens-auth-react/recipe-userroles
297	- https://supertokens.com/docs/references/frontend-sdks/supertokens-auth-react/recipe-webauthn-types
298	- https://supertokens.com/docs/references/frontend-sdks/supertokens-auth-react/recipe-webauthn
299	- https://supertokens.com/docs/references/frontend-sdks/supertokens-web-js/package
300	- https://supertokens.com/docs/references/frontend-sdks/supertokens-web-js/types
301	- https://supertokens.com/docs/references/frontend-sdks/supertokens-web-js/recipe-emailpassword-types
302	- https://supertokens.com/docs/references/frontend-sdks/supertokens-web-js/recipe-emailpassword
303	- https://supertokens.com/docs/references/frontend-sdks/supertokens-web-js/recipe-emailverification-types
304	- https://supertokens.com/docs/references/frontend-sdks/supertokens-web-js/recipe-emailverification
305	- https://supertokens.com/docs/references/frontend-sdks/supertokens-web-js/recipe-multifactorauth-types
306	- https://supertokens.com/docs/references/frontend-sdks/supertokens-web-js/recipe-multifactorauth
307	- https://supertokens.com/docs/references/frontend-sdks/supertokens-web-js/recipe-multitenancy-types
308	- https://supertokens.com/docs/references/frontend-sdks/supertokens-web-js/recipe-multitenancy
309	- https://supertokens.com/docs/references/frontend-sdks/supertokens-web-js/recipe-oauth2provider-types
310	- https://supertokens.com/docs/references/frontend-sdks/supertokens-web-js/recipe-oauth2provider
311	- https://supertokens.com/docs/references/frontend-sdks/supertokens-web-js/recipe-passwordless-types
312	- https://supertokens.com/docs/references/frontend-sdks/supertokens-web-js/recipe-passwordless
313	- https://supertokens.com/docs/references/frontend-sdks/supertokens-web-js/recipe-session-types
314	- https://supertokens.com/docs/references/frontend-sdks/supertokens-web-js/recipe-session
315	- https://supertokens.com/docs/references/frontend-sdks/supertokens-web-js/recipe-thirdparty-types
316	- https://supertokens.com/docs/references/frontend-sdks/supertokens-web-js/recipe-thirdparty
317	- https://supertokens.com/docs/references/frontend-sdks/supertokens-web-js/recipe-totp-types
318	- https://supertokens.com/docs/references/frontend-sdks/supertokens-web-js/recipe-totp
319	- https://supertokens.com/docs/references/frontend-sdks/supertokens-web-js/recipe-userroles
320	- https://supertokens.com/docs/references/frontend-sdks/supertokens-web-js/recipe-webauthn-types
321	- https://supertokens.com/docs/references/frontend-sdks/supertokens-web-js/recipe-webauthn
322	- https://supertokens.com/docs/references/backend-sdks/reference
323	- https://supertokens.com/docs/references/backend-sdks/function-overrides
324	- https://supertokens.com/docs/references/backend-sdks/api-overrides
325	- https://supertokens.com/docs/references/backend-sdks/user-context
326	- https://supertokens.com/docs/references/backend-sdks/user-object
327	- https://supertokens.com/docs/references/backend-sdks/backend-sdk-core-interceptor
328	- https://supertokens.com/docs/references/backend-sdks/supertokens-nodejs/package
329	- https://supertokens.com/docs/references/backend-sdks/supertokens-nodejs/types
330	- https://supertokens.com/docs/references/backend-sdks/supertokens-nodejs/recipe-emailpassword-types
331	- https://supertokens.com/docs/references/backend-sdks/supertokens-nodejs/recipe-emailpassword
332	- https://supertokens.com/docs/references/backend-sdks/supertokens-nodejs/recipe-passwordless-types
333	- https://supertokens.com/docs/references/backend-sdks/supertokens-nodejs/recipe-passwordless
334	- https://supertokens.com/docs/references/backend-sdks/supertokens-nodejs/recipe-thirdparty-types
335	- https://supertokens.com/docs/references/backend-sdks/supertokens-nodejs/recipe-thirdparty
336	- https://supertokens.com/docs/references/backend-sdks/supertokens-nodejs/recipe-webauthn-types
337	- https://supertokens.com/docs/references/backend-sdks/supertokens-nodejs/recipe-webauthn
338	- https://supertokens.com/docs/references/backend-sdks/supertokens-nodejs/recipe-emailverification-types
339	- https://supertokens.com/docs/references/backend-sdks/supertokens-nodejs/recipe-emailverification
340	- https://supertokens.com/docs/references/backend-sdks/supertokens-nodejs/recipe-multifactorauth-types
341	- https://supertokens.com/docs/references/backend-sdks/supertokens-nodejs/recipe-multifactorauth
342	- https://supertokens.com/docs/references/backend-sdks/supertokens-nodejs/recipe-accountlinking-types
343	- https://supertokens.com/docs/references/backend-sdks/supertokens-nodejs/recipe-accountlinking
344	- https://supertokens.com/docs/references/backend-sdks/supertokens-nodejs/recipe-jwt-types
345	- https://supertokens.com/docs/references/backend-sdks/supertokens-nodejs/recipe-jwt
346	- https://supertokens.com/docs/references/backend-sdks/supertokens-nodejs/recipe-multitenancy-types
347	- https://supertokens.com/docs/references/backend-sdks/supertokens-nodejs/recipe-multitenancy
348	- https://supertokens.com/docs/references/backend-sdks/supertokens-nodejs/recipe-dashboard-types
349	- https://supertokens.com/docs/references/backend-sdks/supertokens-nodejs/recipe-dashboard
350	- https://supertokens.com/docs/references/backend-sdks/supertokens-nodejs/recipe-oauth2provider-types
351	- https://supertokens.com/docs/references/backend-sdks/supertokens-nodejs/recipe-oauth2provider
352	- https://supertokens.com/docs/references/backend-sdks/supertokens-nodejs/recipe-openid-types
353	- https://supertokens.com/docs/references/backend-sdks/supertokens-nodejs/recipe-openid
354	- https://supertokens.com/docs/references/backend-sdks/supertokens-nodejs/recipe-userroles-types
355	- https://supertokens.com/docs/references/backend-sdks/supertokens-nodejs/recipe-userroles
356	- https://supertokens.com/docs/references/backend-sdks/supertokens-nodejs/recipe-usermetadata-types
357	- https://supertokens.com/docs/references/backend-sdks/supertokens-nodejs/recipe-usermetadata
358	- https://supertokens.com/docs/references/backend-sdks/supertokens-nodejs/recipe-totp-types
359	- https://supertokens.com/docs/references/backend-sdks/supertokens-nodejs/recipe-totp
360	- https://supertokens.com/docs/references/backend-sdks/other-frameworks
361	- https://supertokens.com/docs/references/fdi/introduction
362	- https://supertokens.com/docs/references/fdi/email-verification/get-user-email-verify
363	- https://supertokens.com/docs/references/fdi/email-verification/post-user-email-verify
364	- https://supertokens.com/docs/references/fdi/email-verification/post-user-email-verify-token
365	- https://supertokens.com/docs/references/fdi/email-password/get-emailpassword-email-exists
366	- https://supertokens.com/docs/references/fdi/email-password/post-signin
367	- https://supertokens.com/docs/references/fdi/email-password/post-signup
368	- https://supertokens.com/docs/references/fdi/email-password/post-user-password-reset
369	- https://supertokens.com/docs/references/fdi/email-password/post-user-password-reset-token
370	- https://supertokens.com/docs/references/fdi/mfa/get-totp-device-list
371	- https://supertokens.com/docs/references/fdi/mfa/post-totp-device
372	- https://supertokens.com/docs/references/fdi/mfa/post-totp-device-remove
373	- https://supertokens.com/docs/references/fdi/mfa/post-totp-device-verify
374	- https://supertokens.com/docs/references/fdi/mfa/post-totp-verify
375	- https://supertokens.com/docs/references/fdi/mfa/put-mfa-info
376	- https://supertokens.com/docs/references/fdi/oauth/get-oauth-auth
377	- https://supertokens.com/docs/references/fdi/oauth/get-oauth-end_session
378	- https://supertokens.com/docs/references/fdi/oauth/get-oauth-login
379	- https://supertokens.com/docs/references/fdi/oauth/get-oauth-logininfo
380	- https://supertokens.com/docs/references/fdi/oauth/get-oauth-userinfo
381	- https://supertokens.com/docs/references/fdi/oauth/post-oauth-end_session
382	- https://supertokens.com/docs/references/fdi/oauth/post-oauth-introspect
383	- https://supertokens.com/docs/references/fdi/oauth/post-oauth-logout
384	- https://supertokens.com/docs/references/fdi/oauth/post-oauth-revoke
385	- https://supertokens.com/docs/references/fdi/oauth/post-oauth-token
386	- https://supertokens.com/docs/references/fdi/passwordless/get-passwordless-email-exists
387	- https://supertokens.com/docs/references/fdi/passwordless/get-passwordless-phoneNumber-exists
388	- https://supertokens.com/docs/references/fdi/passwordless/post-signinup-code
389	- https://supertokens.com/docs/references/fdi/passwordless/post-signinup-code-consume
390	- https://supertokens.com/docs/references/fdi/passwordless/post-signinup-code-resend
391	- https://supertokens.com/docs/references/fdi/session/post-session-refresh
392	- https://supertokens.com/docs/references/fdi/session/post-signout
393	- https://supertokens.com/docs/references/fdi/thirdparty/get-authorisationurl
394	- https://supertokens.com/docs/references/fdi/thirdparty/post-signinup
395	- https://supertokens.com/docs/references/fdi/thirdparty/post-callback-apple
396	- https://supertokens.com/docs/references/fdi/webauthn/get-webauthn-email-exists
397	- https://supertokens.com/docs/references/fdi/webauthn/post-webauthn-credential
398	- https://supertokens.com/docs/references/fdi/webauthn/post-webauthn-recover-account
399	- https://supertokens.com/docs/references/fdi/webauthn/post-webauthn-recover-account-token
400	- https://supertokens.com/docs/references/fdi/webauthn/post-webauthn-register-options
401	- https://supertokens.com/docs/references/fdi/webauthn/post-webauthn-signin
402	- https://supertokens.com/docs/references/fdi/webauthn/post-webauthn-signin-options
403	- https://supertokens.com/docs/references/fdi/webauthn/post-webauthn-signup
404	- https://supertokens.com/docs/references/fdi/get-loginmethods
405	- https://supertokens.com/docs/references/fdi/get-jwt-jwks-json
406	- https://supertokens.com/docs/references/fdi/get-well-known-openid-configuration
407	- https://supertokens.com/docs/references/fdi/get-example
408	- https://supertokens.com/docs/references/cdi/introduction
409	- https://supertokens.com/docs/references/cdi/account-linking/get-accountlinking-user-link-check
410	- https://supertokens.com/docs/references/cdi/account-linking/get-accountlinking-user-primary-check
411	- https://supertokens.com/docs/references/cdi/account-linking/post-accountlinking-user-link
412	- https://supertokens.com/docs/references/cdi/account-linking/post-accountlinking-user-primary
413	- https://supertokens.com/docs/references/cdi/account-linking/post-accountlinking-user-unlink
414	- https://supertokens.com/docs/references/cdi/import/get-bulk-import-users
415	- https://supertokens.com/docs/references/cdi/import/post-bulk-import-import
416	- https://supertokens.com/docs/references/cdi/import/post-bulk-import-users
417	- https://supertokens.com/docs/references/cdi/import/delete-bulk-import-users
418	- https://supertokens.com/docs/references/cdi/import/get-bulk-import-users-count
419	- https://supertokens.com/docs/references/cdi/core/get-root
420	- https://supertokens.com/docs/references/cdi/core/get-hello
421	- https://supertokens.com/docs/references/cdi/core/get-users
422	- https://supertokens.com/docs/references/cdi/core/get-users-by-accountinfo
423	- https://supertokens.com/docs/references/cdi/core/get-users-count
424	- https://supertokens.com/docs/references/cdi/core/get-apiversion
425	- https://supertokens.com/docs/references/cdi/core/get-ee-featureflag
426	- https://supertokens.com/docs/references/cdi/core/get-ee-license
427	- https://supertokens.com/docs/references/cdi/core/get-userid-map
428	- https://supertokens.com/docs/references/cdi/core/get-requests-stats
429	- https://supertokens.com/docs/references/cdi/core/get-telemetry
430	- https://supertokens.com/docs/references/cdi/core/get-user-id
431	- https://supertokens.com/docs/references/cdi/core/get-user-search-tags
432	- https://supertokens.com/docs/references/cdi/core/get-users-count-active
433	- https://supertokens.com/docs/references/cdi/core/get-config
434	- https://supertokens.com/docs/references/cdi/core/post-hello
435	- https://supertokens.com/docs/references/cdi/core/post-userid-map
436	- https://supertokens.com/docs/references/cdi/core/post-userid-map-remove
437	- https://supertokens.com/docs/references/cdi/core/post-user-remove
438	- https://supertokens.com/docs/references/cdi/core/put-hello
439	- https://supertokens.com/docs/references/cdi/core/put-ee-license
440	- https://supertokens.com/docs/references/cdi/core/put-userid-external-user-id-info
441	- https://supertokens.com/docs/references/cdi/core/delete-hello
442	- https://supertokens.com/docs/references/cdi/core/delete-ee-license
443	- https://supertokens.com/docs/references/cdi/dashboard/get-dashboard-tenant-core-config
444	- https://supertokens.com/docs/references/cdi/dashboard/get-dashboard-user-sessions
445	- https://supertokens.com/docs/references/cdi/dashboard/get-dashboard-users
446	- https://supertokens.com/docs/references/cdi/dashboard/post-dashboard-session-verify
447	- https://supertokens.com/docs/references/cdi/dashboard/post-dashboard-signin
448	- https://supertokens.com/docs/references/cdi/dashboard/post-dashboard-user
449	- https://supertokens.com/docs/references/cdi/dashboard/put-dashboard-user
450	- https://supertokens.com/docs/references/cdi/dashboard/delete-dashboard-session
451	- https://supertokens.com/docs/references/cdi/dashboard/delete-dashboard-user
452	- https://supertokens.com/docs/references/cdi/email-verification/get-user-email-verify
453	- https://supertokens.com/docs/references/cdi/email-verification/post-user-email-verify
454	- https://supertokens.com/docs/references/cdi/email-verification/post-user-email-verify-token
455	- https://supertokens.com/docs/references/cdi/email-verification/post-user-email-verify-token-remove
456	- https://supertokens.com/docs/references/cdi/email-verification/post-user-email-verify-remove
457	- https://supertokens.com/docs/references/cdi/email-password/post-signin
458	- https://supertokens.com/docs/references/cdi/email-password/post-signup
459	- https://supertokens.com/docs/references/cdi/email-password/post-user-password-reset-token
460	- https://supertokens.com/docs/references/cdi/email-password/post-user-password-reset-token-consume
461	- https://supertokens.com/docs/references/cdi/email-password/post-user-passwordhash-import
462	- https://supertokens.com/docs/references/cdi/email-password/put-user
463	- https://supertokens.com/docs/references/cdi/mfa/get-totp-device-list
464	- https://supertokens.com/docs/references/cdi/mfa/post-totp-device-verify
465	- https://supertokens.com/docs/references/cdi/mfa/post-totp-verify
466	- https://supertokens.com/docs/references/cdi/mfa/post-totp-device
467	- https://supertokens.com/docs/references/cdi/mfa/post-totp-device-remove
468	- https://supertokens.com/docs/references/cdi/mfa/post-totp-device-import
469	- https://supertokens.com/docs/references/cdi/mfa/put-totp-device
470	- https://supertokens.com/docs/references/cdi/multitenancy/get-multitenancy-tenant-v2
471	- https://supertokens.com/docs/references/cdi/multitenancy/get-multitenancy-tenant-list-v2
472	- https://supertokens.com/docs/references/cdi/multitenancy/get-multitenancy-app-list-v2
473	- https://supertokens.com/docs/references/cdi/multitenancy/get-multitenancy-connectionuridomain-list-v2
474	- https://supertokens.com/docs/references/cdi/multitenancy/post-multitenancy-config-thirdparty-remove
475	- https://supertokens.com/docs/references/cdi/multitenancy/post-multitenancy-tenant-user
476	- https://supertokens.com/docs/references/cdi/multitenancy/post-multitenancy-tenant-user-remove
477	- https://supertokens.com/docs/references/cdi/multitenancy/post-multitenancy-tenant-remove
478	- https://supertokens.com/docs/references/cdi/multitenancy/post-multitenancy-app-remove
479	- https://supertokens.com/docs/references/cdi/multitenancy/post-multitenancy-connectionuridomain-remove
480	- https://supertokens.com/docs/references/cdi/multitenancy/put-multitenancy-config-thirdparty
481	- https://supertokens.com/docs/references/cdi/multitenancy/put-multitenancy-tenant-v2
482	- https://supertokens.com/docs/references/cdi/multitenancy/put-multitenancy-app-v2
483	- https://supertokens.com/docs/references/cdi/multitenancy/put-multitenancy-connectionuridomain-v2
484	- https://supertokens.com/docs/references/cdi/oauth/get-well-known-jwks
485	- https://supertokens.com/docs/references/cdi/oauth/get-oauth2-auth
486	- https://supertokens.com/docs/references/cdi/oauth/get-oauth2-consent-request
487	- https://supertokens.com/docs/references/cdi/oauth/get-oauth2-login-request
488	- https://supertokens.com/docs/references/cdi/oauth/get-oauth2-client
489	- https://supertokens.com/docs/references/cdi/oauth/get-oauth2-clients
490	- https://supertokens.com/docs/references/cdi/oauth/get-oauth2-sessions-logout
491	- https://supertokens.com/docs/references/cdi/oauth/post-oauth2-client
492	- https://supertokens.com/docs/references/cdi/oauth/post-oauth2-client-remove
493	- https://supertokens.com/docs/references/cdi/oauth/post-oauth2-token-introspect
494	- https://supertokens.com/docs/references/cdi/oauth/post-oauth2-session-revoke
495	- https://supertokens.com/docs/references/cdi/oauth/get-oauth2-token
496	- https://supertokens.com/docs/references/cdi/oauth/post-oauth2-token-revoke
497	- https://supertokens.com/docs/references/cdi/oauth/post-oauth2-tokens-revoke
498	- https://supertokens.com/docs/references/cdi/oauth/post-oauth2-consent-request-accept
499	- https://supertokens.com/docs/references/cdi/oauth/post-oauth2-consent-request-reject
500	- https://supertokens.com/docs/references/cdi/oauth/post-oauth2-login-request-accept
501	- https://supertokens.com/docs/references/cdi/oauth/post-oauth2-login-request-reject
502	- https://supertokens.com/docs/references/cdi/oauth/post-oauth2-logout-request-accept
503	- https://supertokens.com/docs/references/cdi/oauth/post-oauth2-logout-request-reject
504	- https://supertokens.com/docs/references/cdi/oauth/put-oauth2-client
505	- https://supertokens.com/docs/references/cdi/passwordless/get-signinup-codes
506	- https://supertokens.com/docs/references/cdi/passwordless/post-signinup-code
507	- https://supertokens.com/docs/references/cdi/passwordless/post-signinup-code-check
508	- https://supertokens.com/docs/references/cdi/passwordless/post-signinup-code-consume
509	- https://supertokens.com/docs/references/cdi/passwordless/post-signinup-code-remove
510	- https://supertokens.com/docs/references/cdi/passwordless/post-signinup-codes-remove
511	- https://supertokens.com/docs/references/cdi/passwordless/put-user
512	- https://supertokens.com/docs/references/cdi/session/get-session-user
513	- https://supertokens.com/docs/references/cdi/session/get-session
514	- https://supertokens.com/docs/references/cdi/session/post-session
515	- https://supertokens.com/docs/references/cdi/session/post-session-remove
516	- https://supertokens.com/docs/references/cdi/session/post-jwt
517	- https://supertokens.com/docs/references/cdi/session/post-session-refresh
518	- https://supertokens.com/docs/references/cdi/session/post-session-regenerate
519	- https://supertokens.com/docs/references/cdi/session/post-session-verify
520	- https://supertokens.com/docs/references/cdi/session/put-jwt-data
521	- https://supertokens.com/docs/references/cdi/session/put-session-data
522	- https://supertokens.com/docs/references/cdi/thirdparty/post-signinup
523	- https://supertokens.com/docs/references/cdi/user-metadata/get-user-metadata
524	- https://supertokens.com/docs/references/cdi/user-metadata/post-user-metadata-remove
525	- https://supertokens.com/docs/references/cdi/user-metadata/put-user-metadata
526	- https://supertokens.com/docs/references/cdi/user-roles/get-role-users
527	- https://supertokens.com/docs/references/cdi/user-roles/get-user-roles
528	- https://supertokens.com/docs/references/cdi/user-roles/get-permission-roles
529	- https://supertokens.com/docs/references/cdi/user-roles/get-role-permissions
530	- https://supertokens.com/docs/references/cdi/user-roles/get-roles
531	- https://supertokens.com/docs/references/cdi/user-roles/post-user-role-remove
532	- https://supertokens.com/docs/references/cdi/user-roles/post-role-permissions-remove
533	- https://supertokens.com/docs/references/cdi/user-roles/post-role-remove
534	- https://supertokens.com/docs/references/cdi/user-roles/put-user-role
535	- https://supertokens.com/docs/references/cdi/user-roles/put-role
536	- https://supertokens.com/docs/references/testing-and-debugging/api-testing
537	- https://supertokens.com/docs/references/testing-and-debugging/how-to-troubleshoot
538	- https://supertokens.com/docs/references/testing-and-debugging/common-issues
539	- https://supertokens.com/docs/references/updating-supertokens
540	- https://supertokens.com/docs/references/compatibility-table
541	- https://supertokens.com/docs/references/cdi/webauthn/get-webauthn-options
542	- https://supertokens.com/docs/references/cdi/webauthn/get-webauthn-credential
543	- https://supertokens.com/docs/references/cdi/webauthn/get-webauthn-credentials
544	- https://supertokens.com/docs/references/cdi/webauthn/post-webauthn-recover
545	- https://supertokens.com/docs/references/cdi/webauthn/post-webauthn-registration-options
546	- https://supertokens.com/docs/references/cdi/webauthn/post-webauthn-signin-options
547	- https://supertokens.com/docs/references/cdi/webauthn/post-webauthn-signin
548	- https://supertokens.com/docs/references/cdi/webauthn/post-webauthn-signup
549	- https://supertokens.com/docs/references/cdi/webauthn/post-webauthn-register
550	- https://supertokens.com/docs/references/cdi/webauthn/post-webauthn-token-recovery
551	- https://supertokens.com/docs/references/cdi/webauthn/post-webauthn-token-consume
552	- https://supertokens.com/docs/references/cdi/webauthn/put-webauthn-email
553	- https://supertokens.com/docs/references/cdi/webauthn/delete-webauthn-options
554	- https://supertokens.com/docs/references/cdi/webauthn/delete-webauthn-credential
555
556	## Briven-specific mapping notes
557
558	\| SuperTokens docs say \| Briven Auth must do \|
559	\|----------------------\|---------------------\|
560	\| Supabase \| Briven Doltgres per project \|
561	\| MySQL migrate \| Migrate / store on Doltgres \|
562	\| Self-host Core \| Hosted by Briven platform (users do not run Core) \|
563	\| App domain backend SDK \| First-party auth on app + Briven Auth control plane \|
564	\| Dashboard \| Yellow Briven Auth sidebar section (sub-dashboard) \|
565
566
567
568	# Briven Pay build
569
570	# Briven database — Doltgres / Dolt official knowledge base
571
572	Purpose: Library cabinet for EVERY Briven build that touches SQL, Auth, backups, or Postgres-family compatibility.
573	Source: (1) flndrn official www.doltgres.com list (PRIMARY, complete set below) + (2) URLs from `AI_DOCS/dolt-reference/*` (local notes + often dolthub.com MySQL-Dolt siblings) (already in this repo). Agents must open these — do not guess.
574	HARD RULE: On any Doltgres / Postgres-wire error (including SuperTokens Core or any tool built for Postgres), search this section + `AI_DOCS/dolt-reference/00-doltgres-truth.md` before changing architecture. Never quit after one SQL error without reading these and notifying flndrn with options.
575
576	## Local distilled files (always read first)
577
578	- `AI_DOCS/dolt-reference/00-doltgres-truth.md` — authoritative DoltGres facts (Postgres-flavored)
579	- `AI_DOCS/dolt-reference/01-intro-install.md`
580	- `AI_DOCS/dolt-reference/02-use-cases.md`
581	- `AI_DOCS/dolt-reference/03-concepts-git.md`
582	- `AI_DOCS/dolt-reference/04-concepts-sql.md`
583	- `AI_DOCS/dolt-reference/05-rdbms-dolthub.md`
584	- `AI_DOCS/dolt-reference/06-sqlref-server.md`
585	- `AI_DOCS/dolt-reference/07-sqlref-version-control.md`
586	- `DOLTGRES-FIRST.md` — Briven hard product rule
587
588	## Official DoltGres docs (www.doltgres.com) — PRIMARY for Briven
589
590	Filed from flndrn full URL list (2026-07-22). These are the real DoltGres product docs (Postgres-flavored). Prefer these over dolthub.com MySQL-Dolt pages when they overlap.
591	Count: 51 URLs
592
593	### Introduction
594
595	- https://www.doltgres.com/docs/introduction/
596	- https://www.doltgres.com/docs/introduction/getting-started/
597	- https://www.doltgres.com/docs/introduction/installation/
598
599	### Concepts — git / version control
600
601	- https://www.doltgres.com/docs/concepts/git/branch/
602	- https://www.doltgres.com/docs/concepts/git/commits/
603	- https://www.doltgres.com/docs/concepts/git/conflicts/
604	- https://www.doltgres.com/docs/concepts/git/diff/
605	- https://www.doltgres.com/docs/concepts/git/log/
606	- https://www.doltgres.com/docs/concepts/git/merge/
607	- https://www.doltgres.com/docs/concepts/git/remotes/
608	- https://www.doltgres.com/docs/concepts/git/working-set/
609
610	### Concepts — SQL
611
612	- https://www.doltgres.com/docs/concepts/sql/constraints/
613	- https://www.doltgres.com/docs/concepts/sql/databases/
614	- https://www.doltgres.com/docs/concepts/sql/functions/
615	- https://www.doltgres.com/docs/concepts/sql/indexes/
616	- https://www.doltgres.com/docs/concepts/sql/primary-key/
617	- https://www.doltgres.com/docs/concepts/sql/procedures/
618	- https://www.doltgres.com/docs/concepts/sql/schema/
619	- https://www.doltgres.com/docs/concepts/sql/system-variables/
620	- https://www.doltgres.com/docs/concepts/sql/table/
621	- https://www.doltgres.com/docs/concepts/sql/transaction/
622	- https://www.doltgres.com/docs/concepts/sql/triggers/
623	- https://www.doltgres.com/docs/concepts/sql/types/
624	- https://www.doltgres.com/docs/concepts/sql/users-grants/
625	- https://www.doltgres.com/docs/concepts/sql/views/
626
627	### Concepts — RDBMS
628
629	- https://www.doltgres.com/docs/concepts/rdbms/backups/
630	- https://www.doltgres.com/docs/concepts/rdbms/replication/
631	- https://www.doltgres.com/docs/concepts/rdbms/server/
632
633	### Guides
634
635	- https://www.doltgres.com/docs/guides/cheat-sheet/
636	- https://www.doltgres.com/docs/guides/replication-from-postgres/
637
638	### Reference — server
639
640	- https://www.doltgres.com/docs/reference/server/access-management/
641	- https://www.doltgres.com/docs/reference/server/backups/
642	- https://www.doltgres.com/docs/reference/server/branch-permissions/
643	- https://www.doltgres.com/docs/reference/server/configuration/
644	- https://www.doltgres.com/docs/reference/server/garbage-collection/
645	- https://www.doltgres.com/docs/reference/server/troubleshooting/
646
647	### Reference — version control
648
649	- https://www.doltgres.com/docs/reference/version-control/branches/
650	- https://www.doltgres.com/docs/reference/version-control/dolt-sql-functions/
651	- https://www.doltgres.com/docs/reference/version-control/dolt-system-tables/
652	- https://www.doltgres.com/docs/reference/version-control/dolt-sysvars/
653	- https://www.doltgres.com/docs/reference/version-control/merges/
654	- https://www.doltgres.com/docs/reference/version-control/querying-history/
655	- https://www.doltgres.com/docs/reference/version-control/remotes/
656	- https://www.doltgres.com/docs/reference/version-control/sql-extensions/
657
658	### Reference — SQL support (Postgres-family gaps live here)
659
660	- https://www.doltgres.com/docs/reference/sql-support/supported-commands/
661	- https://www.doltgres.com/docs/reference/sql-support/supported-functions/
662	- https://www.doltgres.com/docs/reference/sql-support/supported-types/
663	- https://www.doltgres.com/docs/reference/sql-support/system-catalog-schema/
664
665	### Reference — clients
666
667	- https://www.doltgres.com/docs/reference/supported-clients/clients/
668
669	### Reference — benchmarks
670
671	- https://www.doltgres.com/docs/reference/benchmarks/correctness/
672	- https://www.doltgres.com/docs/reference/benchmarks/latency/
673	## Official DoltHub docs (Dolt often MySQL-flavored; translate to DoltGres Postgres)
674
675	### Introduction / install
676
677	- https://www.dolthub.com/docs/introduction/getting-started/
678	- https://www.dolthub.com/docs/introduction/getting-started/database/
679	- https://www.dolthub.com/docs/introduction/getting-started/git-for-data/
680	- https://www.dolthub.com/docs/introduction/getting-started/versioned-mysql-replica/
681	- https://www.dolthub.com/docs/introduction/installation/
682	- https://www.dolthub.com/docs/introduction/installation/application-server/
683	- https://www.dolthub.com/docs/introduction/installation/docker/
684	- https://www.dolthub.com/docs/introduction/installation/linux/
685	- https://www.dolthub.com/docs/introduction/installation/mac/
686	- https://www.dolthub.com/docs/introduction/installation/source/
687	- https://www.dolthub.com/docs/introduction/installation/upgrading/
688	- https://www.dolthub.com/docs/introduction/installation/windows/
689	- https://www.dolthub.com/docs/introduction/what-is-dolt/
690
691	### Use cases
692
693	- https://www.dolthub.com/docs/introduction/use-cases/
694	- https://www.dolthub.com/docs/introduction/use-cases/audit/
695	- https://www.dolthub.com/docs/introduction/use-cases/configuration-management/
696	- https://www.dolthub.com/docs/introduction/use-cases/data-and-model-quality/
697	- https://www.dolthub.com/docs/introduction/use-cases/data-sharing/
698	- https://www.dolthub.com/docs/introduction/use-cases/manual-data-curation/
699	- https://www.dolthub.com/docs/introduction/use-cases/offline-first/
700	- https://www.dolthub.com/docs/introduction/use-cases/vc-your-app/
701	- https://www.dolthub.com/docs/introduction/use-cases/versioned-replica/
702
703	### Concepts — overview + git / version control
704
705	- https://www.dolthub.com/docs/concepts/dolt/
706	- https://www.dolthub.com/docs/concepts/dolt/git/
707	- https://www.dolthub.com/docs/concepts/dolt/git/branch/
708	- https://www.dolthub.com/docs/concepts/dolt/git/commits/
709	- https://www.dolthub.com/docs/concepts/dolt/git/conflicts/
710	- https://www.dolthub.com/docs/concepts/dolt/git/diff/
711	- https://www.dolthub.com/docs/concepts/dolt/git/log/
712	- https://www.dolthub.com/docs/concepts/dolt/git/merge/
713	- https://www.dolthub.com/docs/concepts/dolt/git/remotes/
714	- https://www.dolthub.com/docs/concepts/dolt/git/working-set/
715
716	### Concepts — SQL
717
718	- https://www.dolthub.com/docs/concepts/dolt/sql/
719	- https://www.dolthub.com/docs/concepts/dolt/sql/constraints/
720	- https://www.dolthub.com/docs/concepts/dolt/sql/databases/
721	- https://www.dolthub.com/docs/concepts/dolt/sql/indexes/
722	- https://www.dolthub.com/docs/concepts/dolt/sql/primary-key/
723	- https://www.dolthub.com/docs/concepts/dolt/sql/procedures/
724	- https://www.dolthub.com/docs/concepts/dolt/sql/schema/
725	- https://www.dolthub.com/docs/concepts/dolt/sql/system-variables/
726	- https://www.dolthub.com/docs/concepts/dolt/sql/table/
727	- https://www.dolthub.com/docs/concepts/dolt/sql/transaction/
728	- https://www.dolthub.com/docs/concepts/dolt/sql/triggers/
729	- https://www.dolthub.com/docs/concepts/dolt/sql/types/
730	- https://www.dolthub.com/docs/concepts/dolt/sql/users-grants/
731	- https://www.dolthub.com/docs/concepts/dolt/sql/views/
732
733	### Concepts — RDBMS + DoltHub product
734
735	- https://www.dolthub.com/docs/concepts/dolt/rdbms/
736	- https://www.dolthub.com/docs/concepts/dolt/rdbms/backups/
737	- https://www.dolthub.com/docs/concepts/dolt/rdbms/replication/
738	- https://www.dolthub.com/docs/concepts/dolt/rdbms/server/
739	- https://www.dolthub.com/docs/concepts/dolthub/
740	- https://www.dolthub.com/docs/concepts/dolthub/forks/
741	- https://www.dolthub.com/docs/concepts/dolthub/issues/
742	- https://www.dolthub.com/docs/concepts/dolthub/permissions/
743	- https://www.dolthub.com/docs/concepts/dolthub/prs/
744
745	### SQL reference — server ops
746
747	- https://www.dolthub.com/docs/sql-reference/server/
748	- https://www.dolthub.com/docs/sql-reference/server/access-management/
749	- https://www.dolthub.com/docs/sql-reference/server/backups/
750	- https://www.dolthub.com/docs/sql-reference/server/branch-permissions/
751	- https://www.dolthub.com/docs/sql-reference/server/configuration/
752	- https://www.dolthub.com/docs/sql-reference/server/garbage-collection/
753	- https://www.dolthub.com/docs/sql-reference/server/hardware-requirements/
754	- https://www.dolthub.com/docs/sql-reference/server/metrics/
755	- https://www.dolthub.com/docs/sql-reference/server/replication/
756	- https://www.dolthub.com/docs/sql-reference/server/troubleshooting/
757
758	### SQL reference — version control API
759
760	- https://www.dolthub.com/docs/sql-reference/version-control/branches/
761	- https://www.dolthub.com/docs/sql-reference/version-control/dolt-sql-functions/
762	- https://www.dolthub.com/docs/sql-reference/version-control/dolt-sql-procedures/
763	- https://www.dolthub.com/docs/sql-reference/version-control/dolt-system-tables/
764	- https://www.dolthub.com/docs/sql-reference/version-control/dolt-sysvars/
765	- https://www.dolthub.com/docs/sql-reference/version-control/merges/
766	- https://www.dolthub.com/docs/sql-reference/version-control/querying-history/
767	- https://www.dolthub.com/docs/sql-reference/version-control/remote-authentication/
768	- https://www.dolthub.com/docs/sql-reference/version-control/remotes/
769	- https://www.dolthub.com/docs/sql-reference/version-control/saved-queries/
770	- https://www.dolthub.com/docs/sql-reference/version-control/sql-extensions/
771
772	## Blogs (product state / calling conventions)
773
774	- https://www.dolthub.com/blog/2024-07-30-re-introducing-dolt-functions/
775	- https://www.dolthub.com/blog/2025-04-16-doltgres-goes-beta/
776	- https://www.dolthub.com/blog/2025-10-16-state-of-doltgres/
777
778	## GitHub install (Dolt sibling — only if needed for concept)
779
780	- https://github.com/dolthub/dolt/releases/latest/download/install.sh
781
782	## Agent workflow when something fails on Doltgres
783
784	1. Read `AI_DOCS/dolt-reference/00-doltgres-truth.md` and the matching URL group above.
785	2. Doltgres = Postgres family (port 5432, `pg` driver). Missing feature ≠ abandon the product.
786	3. Prefer workarounds (SQL rewrite, session settings, driver, version, config) over stock Postgres.
787	4. Notify flndrn with: error text, which doc URL you used, options A/B/C — before switching architecture.
788
789	## Doltgres version pinning + upgrade process (flndrn, 2026-08-01)
790
791	Rule: Keep our Doltgres version in step with upstream. When DoltHub ships a new
792	`dolthub/doltgresql` release, we evaluate and (after testing) move our pinned version
793	along — because their releases carry the lock/concurrency/panic fixes we depend on.
794	Do this as a manual, tested process — NOT an auto-updater/Watchtower/host-side poller
795	(forbidden by `infra/CLAUDE.md`).
796
797	- Where the version is pinned: `infra/dokploy/compose.dokploy.yml` — the `doltgres`,
798	`dolt-backup`, and init services all use `image: dolthub/doltgresql:<version>` (a readable
799	version tag, not an opaque `@sha256` digest, so the version is visible + bumpable).
800	Current pin: `0.57.2` (upgraded from `0.56.6` on 2026-08-01).
801	- Watch for new releases: https://github.com/dolthub/doltgresql/releases and
802	https://github.com/dolthub/doltgresql/issues (customer-tagged issues show active fixes).
803	- Upgrade procedure (tested, no-guess):
804	1. Read the new release notes for lock / GC / panic / connection-stability fixes.
805	2. Validate data-read on a throwaway first: `docker run` the new image on a fresh
806	volume (fresh-init), `cp -a` a copy of the live db dirs in, start, and confirm it reads
807	them (`select count(*) from information_schema.tables …` on `briven_control`). Doltgres
808	upgrades are forward-compatible in practice (0.56.6 → 0.57.2 read cleanly, no migration).
809	3. Set `behavior.auto_gc_behavior.enable: false` in `config.yaml` (see incident below).
810	4. Bump the tag in BOTH the repo compose and France `/code` compose, swap the prepared data
811	into the live volume, and recreate via `scripts/safe-redeploy-service.sh doltgres`.
812	5. Verify version (`select dolt_version()`), all DBs serve, API boots, then **watch it hold
813	under load** past the previous failure window before calling it done.
814
815	## INCIDENT 2026-08-01 — Doltgres locked-under-load → whole platform 404 (ROOT-CAUSE FIXED)
816
817	Symptom: `api.briven.tech` returns Traefik `404 page not found` on every route (incl.
818	`/health`); `api` container crash-loops stuck at `applying migrations…`; Doltgres is "healthy"
819	but serves zero databases — every `psql` connect (even `postgres`/`template1`) returns
820	`FATAL: "database X does not exist"`, and trace logs show `database "briven_control" is locked
821	by another dolt process … holds an exclusive write lock` **even with the server stopped and no
822	other process alive. Recurs within 4–50 minutes** of normal API write load. All 22 DB dirs
823	on disk are intact (`.dolt/noms` valid) — not data loss.
824
825	Root cause: Doltgres `0.56.6` (our pin) has a database-lock defect under concurrent
826	write load. Upstream `0.57.1` shipped a lock-subsystem rewrite (`LockSubsystem.TryLock`)
827	and `0.56.9` fixed an INSERT panic (a regression since `0.56.5` — our `0.56.6` was affected).
828	`0.56.6` also predates the `auto_gc_behavior` config, and `0.57.1` enabled auto-GC by default
829	(auto-GC "breaks all open connections"). NOT related to issue #2600 (that's app-level advisory
830	locks). Verified against release notes, not guessed.
831
832	The SOLID fix (on Doltgres, per DOLTGRES-FIRST — no Postgres):
833	1. Upgrade `0.56.6` → `0.57.2` (validated: 0.57.2 reads 0.56.6 data unchanged; `briven_control`
834	51 tables, `briven_engine` 23 — no migration).
835	2. Disable auto-GC in `config.yaml`: under `behavior:` add
836	`auto_gc_behavior:\n enable: false` (only valid on 0.57.x — 0.56.6 rejects the key with
837	`field auto_gc_behavior not found`, which is how you know you must upgrade first).
838	3. Recreate doltgres on 0.57.2 with the prepared data; restart API; watch it hold under load.
839
840	Emergency triage (temporary, if you must restore before upgrading): a `cp -a` of each DB
841	dir to fresh inodes clears the stale lock and the server serves again — but on `0.56.6` it
842	re-jams under load within minutes-to-an-hour. It is NOT a fix; only the version upgrade is.
843	Recipe that reliably serves: **fresh-init an EMPTY volume (entrypoint), then copy the DB dirs
844	in** — a populated-but-uninitialized data-dir will NOT serve; and never leave `*.dirty`/rollback
845	DB copies inside the data-dir (Doltgres enumerates every subdir and one bad copy aborts the
846	whole multi-DB load).
847
848	Gotchas hit during the fix: (a) the `dolt-backup` job's `dolt_backup(sync-url)` writes to
849	every live DB and accelerates the lock/GC failure — keep it disabled until its method is
850	reworked to cold snapshots; (b) a stray `docker run --rm` doltgres can linger and hold the
851	volume lock — always `docker rm -f`; (c) load secrets into a shell var from `docker inspect …
852	DOLTGRES_PASSWORD` / `.env.prod` — never literal in a command.
853
854	### 2026-08-02 — REBOOT-SAFETY PROVEN LIVE (corrects the "restart doesn't recover" belief)
855
856	A controlled live test on France settled the open question of whether 0.57.2 survives a
857	restart/host-reboot:
858
859	1. `docker restart` the healthy live doltgres → all 24 databases re-served within 8s,
860	`briven_control` reachable, held steady across 64s of polling.
861	2. `docker restart` the api → healthy + public `/health`+`/ready` = 200 within 8s, routing
862	intact (`/v1/` → 404, not 5xx).
863
864	Conclusion: Doltgres 0.57.2 is reboot-safe. The earlier "a plain `docker restart` does
865	NOT recover it" note was wrong-cause — those restarts were of a container **already poisoned
866	by a full-deploy recreate under load**; restarting an already-broken container can't help, but
867	restarting a healthy one is clean (which is all a host reboot does).
868
869	The ONE remaining outage trigger is a full Dokploy deploy (`compose up --build
870	--remove-orphans`) that recreates doltgres while it's under write load (re-runs the entrypoint
871	on a live-but-busy data dir). So "100% production solid" = two locks, not a code change:
872	- autoDeploy OFF (verified via Dokploy API 2026-08-02: `briven-france` compose
873	`autoDeploy: false`) — a git push can no longer auto-rebuild.
874	- Service-scoped redeploys only (`scripts/safe-redeploy-service.sh <svc>`, never recreates
875	doltgres). Full `compose.deploy` only for the "red-panel → one green" rule (gotcha #13).
876
877	Proven-good under every normal op: load (373k-req + 10-writer stress, 0 errors), **restart/
878	reboot (above), `dolt_backup`+restart** (throwaway). Data is never lost — a not-serving state
879	keeps every DB dir intact on the `_doltgres_data` volume; recovery recipe is the fresh-init+copy
880	above. (Note: the Dokploy panel may show `composeStatus: error` from the 08-01 failed run — that
881	is a stale badge, not live health; the running stack is healthy.)

Preview

Doltgres - knowledge base

Briven Auth rebuild — SuperTokens knowledge base

Purpose: Library cabinet for LLM agents building new Briven Auth. These are reference docs from SuperTokens — borrow good product/architecture ideas. Briven Auth stays Briven-branded, multi-tenant on Briven Doltgres, not a raw SuperTokens install.

Date filed: 2026-07-22 URL count: 492 unique

How agents should use this

HARD RULE (flndrn, 2026-07-26 — never break)

Before any Auth change (magic link, OTP, OAuth/Konnos, sessions, MFA, passkeys, FDI, IdP, SSO, providers, secrets, allowed domains, enable/disable Auth, or any code under Auth surfaces):

You must open this file first.
You must open the matching SuperTokens section/URL below for that feature.
You must not guess login behavior. SuperTokens is the product map; Briven implements Briven-branded on Doltgres.
State in one plain sentence what the SuperTokens/KB behavior is, then code.

Also written into project root CLAUDE.md. Skipping this step is a rule violation, not a style preference.

Always

Prefer Briven product rules (Doltgres-first, project isolation, pk_briven_auth_, no inventing Clerk).
For any database / Doltgres / Postgres-wire problem, open the Doltgres / Dolt official knowledge base section at the bottom of this file first (URLs from AI_DOCS/dolt-reference/). Also read AI_DOCS/dolt-reference/00-doltgres-truth.md.
When stuck on a login feature (sessions, passwordless, MFA, etc.), open the matching SuperTokens section below and keep Doltgres constraints from the Doltgres section.
Translate Supabase/MySQL examples to Briven Doltgres using official Doltgres docs — do not invent.
Do not paste SuperTokens branding into Briven UI — yellow Auth sub-dashboard, Briven styling.
Never abandon SuperTokens Core or change Auth architecture after one SQL error without reading Doltgres docs and notifying flndrn.

Quickstart

Quickstart integrations

Authentication recipes

Additional verification (sessions, MFA, roles, captcha)

Post-authentication (sessions, users, dashboard)

Migration

Platform configuration

Deployment

https://supertokens.com/docs/deployment/self-host-supertokens
https://supertokens.com/docs/deployment/rate-limits
https://supertokens.com/docs/deployment/scalability
https://supertokens.com/docs/deployment/telemetry
https://supertokens.com/docs/deployment/migrate-from-mysql(Needs — Map to Migrate from MySQL → Doltgres for Briven.

References (SDKs, FDI, CDI, plugins, testing)

Briven-specific mapping notes

SuperTokens docs say	Briven Auth must do
Supabase	Briven Doltgres per project
MySQL migrate	Migrate / store on Doltgres
Self-host Core	Hosted by Briven platform (users do not run Core)
App domain backend SDK	First-party auth on app + Briven Auth control plane
Dashboard	Yellow Briven Auth sidebar section (sub-dashboard)

Briven Pay build

Briven database — Doltgres / Dolt official knowledge base

Purpose: Library cabinet for EVERY Briven build that touches SQL, Auth, backups, or Postgres-family compatibility. Source: (1) flndrn official www.doltgres.com list (PRIMARY, complete set below) + (2) URLs from AI_DOCS/dolt-reference/* (local notes + often dolthub.com MySQL-Dolt siblings) (already in this repo). Agents must open these — do not guess. HARD RULE: On any Doltgres / Postgres-wire error (including SuperTokens Core or any tool built for Postgres), search this section + AI_DOCS/dolt-reference/00-doltgres-truth.md before changing architecture. Never quit after one SQL error without reading these and notifying flndrn with options.

Local distilled files (always read first)

AI_DOCS/dolt-reference/00-doltgres-truth.md — authoritative DoltGres facts (Postgres-flavored)
AI_DOCS/dolt-reference/01-intro-install.md
AI_DOCS/dolt-reference/02-use-cases.md
AI_DOCS/dolt-reference/03-concepts-git.md
AI_DOCS/dolt-reference/04-concepts-sql.md
AI_DOCS/dolt-reference/05-rdbms-dolthub.md
AI_DOCS/dolt-reference/06-sqlref-server.md
AI_DOCS/dolt-reference/07-sqlref-version-control.md
DOLTGRES-FIRST.md — Briven hard product rule

Official DoltGres docs (www.doltgres.com) — PRIMARY for Briven

Filed from flndrn full URL list (2026-07-22). These are the real DoltGres product docs (Postgres-flavored). Prefer these over dolthub.com MySQL-Dolt pages when they overlap. Count: 51 URLs

Introduction

Concepts — git / version control

Concepts — SQL

Concepts — RDBMS

Guides

Reference — server

Reference — version control

Reference — SQL support (Postgres-family gaps live here)

Reference — clients

https://www.doltgres.com/docs/reference/supported-clients/clients/

Reference — benchmarks

Official DoltHub docs (Dolt often MySQL-flavored; translate to DoltGres Postgres)

Introduction / install

Use cases

Concepts — overview + git / version control

Concepts — SQL

Concepts — RDBMS + DoltHub product

SQL reference — server ops

SQL reference — version control API

Blogs (product state / calling conventions)

GitHub install (Dolt sibling — only if needed for concept)

https://github.com/dolthub/dolt/releases/latest/download/install.sh

Agent workflow when something fails on Doltgres

Read AI_DOCS/dolt-reference/00-doltgres-truth.md and the matching URL group above.
Doltgres = Postgres family (port 5432, pg driver). Missing feature ≠ abandon the product.
Prefer workarounds (SQL rewrite, session settings, driver, version, config) over stock Postgres.
Notify flndrn with: error text, which doc URL you used, options A/B/C — before switching architecture.

Doltgres version pinning + upgrade process (flndrn, 2026-08-01)

Rule: Keep our Doltgres version in step with upstream. When DoltHub ships a new dolthub/doltgresql release, we evaluate and (after testing) move our pinned version along — because their releases carry the lock/concurrency/panic fixes we depend on. Do this as a manual, tested process — NOT an auto-updater/Watchtower/host-side poller (forbidden by infra/CLAUDE.md).

Where the version is pinned: infra/dokploy/compose.dokploy.yml — the doltgres, dolt-backup, and init services all use image: dolthub/doltgresql:<version> (a readable version tag, not an opaque @sha256 digest, so the version is visible + bumpable). Current pin: 0.57.2 (upgraded from 0.56.6 on 2026-08-01).
Watch for new releases: https://github.com/dolthub/doltgresql/releases and https://github.com/dolthub/doltgresql/issues (customer-tagged issues show active fixes).
Upgrade procedure (tested, no-guess):
1. Read the new release notes for lock / GC / panic / connection-stability fixes.
2. Validate data-read on a throwaway first: docker run the new image on a fresh volume (fresh-init), cp -a a copy of the live db dirs in, start, and confirm it reads them (select count(*) from information_schema.tables … on briven_control). Doltgres upgrades are forward-compatible in practice (0.56.6 → 0.57.2 read cleanly, no migration).
3. Set behavior.auto_gc_behavior.enable: false in config.yaml (see incident below).
4. Bump the tag in BOTH the repo compose and France /code compose, swap the prepared data into the live volume, and recreate via scripts/safe-redeploy-service.sh doltgres.
5. Verify version (select dolt_version()), all DBs serve, API boots, then watch it hold under load past the previous failure window before calling it done.

INCIDENT 2026-08-01 — Doltgres locked-under-load → whole platform 404 (ROOT-CAUSE FIXED)

Symptom: api.briven.tech returns Traefik 404 page not found on every route (incl. /health); api container crash-loops stuck at applying migrations…; Doltgres is "healthy" but serves zero databases — every psql connect (even postgres/template1) returns FATAL: "database X does not exist", and trace logs show database "briven_control" is locked by another dolt process … holds an exclusive write lock even with the server stopped and no other process alive. Recurs within 4–50 minutes of normal API write load. All 22 DB dirs on disk are intact (.dolt/noms valid) — not data loss.

Root cause: Doltgres 0.56.6 (our pin) has a database-lock defect under concurrent write load. Upstream 0.57.1 shipped a lock-subsystem rewrite (LockSubsystem.TryLock) and 0.56.9 fixed an INSERT panic (a regression since 0.56.5 — our 0.56.6 was affected). 0.56.6 also predates the auto_gc_behavior config, and 0.57.1 enabled auto-GC by default (auto-GC "breaks all open connections"). NOT related to issue #2600 (that's app-level advisory locks). Verified against release notes, not guessed.

The SOLID fix (on Doltgres, per DOLTGRES-FIRST — no Postgres):

Upgrade 0.56.6 → 0.57.2 (validated: 0.57.2 reads 0.56.6 data unchanged; briven_control 51 tables, briven_engine 23 — no migration).
Disable auto-GC in config.yaml: under behavior: add auto_gc_behavior:\n enable: false (only valid on 0.57.x — 0.56.6 rejects the key with field auto_gc_behavior not found, which is how you know you must upgrade first).
Recreate doltgres on 0.57.2 with the prepared data; restart API; watch it hold under load.

Emergency triage (temporary, if you must restore before upgrading): a cp -a of each DB dir to fresh inodes clears the stale lock and the server serves again — but on 0.56.6 it re-jams under load within minutes-to-an-hour. It is NOT a fix; only the version upgrade is. Recipe that reliably serves: fresh-init an EMPTY volume (entrypoint), then copy the DB dirs in — a populated-but-uninitialized data-dir will NOT serve; and never leave *.dirty/rollback DB copies inside the data-dir (Doltgres enumerates every subdir and one bad copy aborts the whole multi-DB load).

Gotchas hit during the fix: (a) the dolt-backup job's dolt_backup(sync-url) writes to every live DB and accelerates the lock/GC failure — keep it disabled until its method is reworked to cold snapshots; (b) a stray docker run --rm doltgres can linger and hold the volume lock — always docker rm -f; (c) load secrets into a shell var from docker inspect … DOLTGRES_PASSWORD / .env.prod — never literal in a command.

2026-08-02 — REBOOT-SAFETY PROVEN LIVE (corrects the "restart doesn't recover" belief)

A controlled live test on France settled the open question of whether 0.57.2 survives a restart/host-reboot:

docker restart the healthy live doltgres → all 24 databases re-served within 8s, briven_control reachable, held steady across 64s of polling.
docker restart the api → healthy + public /health+/ready = 200 within 8s, routing intact (/v1/ → 404, not 5xx).

Conclusion: Doltgres 0.57.2 is reboot-safe. The earlier "a plain docker restart does NOT recover it" note was wrong-cause — those restarts were of a container already poisoned by a full-deploy recreate under load; restarting an already-broken container can't help, but restarting a healthy one is clean (which is all a host reboot does).

The ONE remaining outage trigger is a full Dokploy deploy (compose up --build --remove-orphans) that recreates doltgres while it's under write load (re-runs the entrypoint on a live-but-busy data dir). So "100% production solid" = two locks, not a code change:

autoDeploy OFF (verified via Dokploy API 2026-08-02: briven-france compose autoDeploy: false) — a git push can no longer auto-rebuild.
Service-scoped redeploys only (scripts/safe-redeploy-service.sh <svc>, never recreates doltgres). Full compose.deploy only for the "red-panel → one green" rule (gotcha #13).

Proven-good under every normal op: load (373k-req + 10-writer stress, 0 errors), restart/ reboot (above), dolt_backup+restart (throwaway). Data is never lost — a not-serving state keeps every DB dir intact on the _doltgres_data volume; recovery recipe is the fresh-init+copy above. (Note: the Dokploy panel may show composeStatus: error from the 08-01 failed run — that is a stale badge, not live health; the running stack is healthy.)