Ops

Operational runbooks for the people keeping Guild running: schema changes, Clerk key rotation, transactional email, and Cloudflare Pages deploys.

Current platform state (2026-08-06):

Neon Postgres (live, schema applied) — see Schema changes
Clerk auth (live, dev instance, magic-link sign-in) — see Clerk keys
Resend transactional email (live, verified sender domain) — see Email
Cloudflare Pages project guild at guild.pages.dev (live, manual deploys only) — see Deploys
No custom domain yet (pass 13, human-gated, optional)

Runbooks

Topic	When you need it
Schema changes	Changing tables, policies, seed data
Clerk keys	Rotating or re-provisioning auth keys
Email	Understanding or debugging transactional email
Deploys	Shipping code to guild.pages.dev

Never commit .env.local (it's gitignored) and never paste credential values into chat, issues, or notes.
RLS is live in production — schema and policy changes ship through the same review path as code.
Apply order is binding: auth-shim.sql → schema.sql → rls-policies.sql → seed.sql. Never run the spec's §4.3/§7.5 ALTERs separately (columns are already consolidated in schema.sql — duplicate-column error).
Docs must match main. If a runbook would describe behavior that isn't in the code, mark it "coming in pass N" — don't invent it.

The build-out process that produced this platform is documented in Foundry orientation.