SOPs

SOPs here are living checklists. Like a pilot’s pre-flight or a surgeon’s safety protocol — simple, explicit, and they prevent costly mistakes.

The Rules

1. Every SOP is a numbered checklist. Steps are explicit, not prose. You should be able to tick them off one by one.
2. Checklists grow from experience. Start with ten steps. Do it. Realize you missed something. Add step eleven. The checklist evolves every time it is used.
3. Never skip a step because it seems obvious. The obvious steps are the ones that get forgotten under pressure. That is the whole point.
4. Post-task reflection catches what the checklist missed. When a step was obviously needed but was not there, add it.

Stubs

Each of these is a placeholder. Fill in when the next real run happens.

• New Repo Setup — build.txt, CLAUDE.md template, private GitHub, push, post-push-sync.
• New Domain on Cloudflare + GSC — DNS records, TXT verify, GSC add, sitemap.
• Deploy a New Cloudflare Pages Project — repo, build settings, env vars, custom domain, Zero Trust gate (this doc itself).
• VPS Service Deployment — systemd unit, env file, logs directory, webhook hookup.
• Supabase Schema Change — migration file, local test, remote apply, rollback plan.
• Episode Publishing — see /publish-episode skill.
• YouTube Upload Sweep — check the last 20 videos for anything still unlisted.

Where the Canonical SOPs Live

Some SOPs live in the cc super CLAUDE.md as rules, not as standalone docs. That file is the source of truth for behavioral rules across all repos. This wiki is for the operational SOPs — the step-by-step, do-this-then-that kind.