Master reference

Indaba — Site Registry & Backup Protocol

One place that maps every site: where it publishes, where its source lives, where it's backed up, and who gets in. Aligns with Indaba_Resilience_and_Publishing_Playbook.md. Updated 12 Aug 2026.

Backup protocol (the rule)

Backup = timestamped zip + SHA-256 manifest, written to BOTH homes. Always named & confirmed.

Two triggers: (1) on command "create a backup"; (2) automatically before every publish / go-live — backup first, then publish.

Backup home 1

/Users/admin/claude code build/Backups/

Backup home 2 (iCloud)

…/Claude Indaba Build/Backups/

Naming

<SITE>_YYYYMMDD-HHMMSS.zip + .sha256

Three folders per site

① Publish (deploy)

The Netlify drag-deploy folder. Live file updates go here.

/Users/admin/Downloads/<SITE>

② Repo (version control)

Source of truth for Git/Vercel. NOT the publish folder.

…/Claude Indaba Build/indaba-platform

③ Backups (archive)

The two homes above. Separate from working folders.

both homes

Writing to the publish folder does not deploy — the folder still has to be dragged onto Netlify (and hard-refreshed). Site-build standard: externalize images to /assets/img (no inline base64 in production), deploy the folder, keep only light HTML/text in the project.

The site registry

Site	Edition	Domain	Publish folder (Downloads/)	Host	Status	Access
Six Isobel	Indaba Cases	cases.indaba.one	`ISOBEL-SITE`	Netlify → Vercel	Live	Danny (owner) · counsel
Federation (FSC)	Cases / Works	fsc.indaba.one	`FSC-SITE-LIVE`	Netlify	Live	Danny · Cornelius / Federation
getindaba.com	Platform / brand	getindaba.com	`GETINDABA-SITE`	Netlify	Ready to launch	Public (marketing)
the EnS Case File	Indaba Works	ens.indaba.one	`ENS-SITE` ✓ Works build	Netlify (`ens-indaba.netlify.app`)	Preview — redeploy pending	Danny (owner) · Savi · Esther
Indaba App	Multi-tenant platform	app.indaba.one · `*.indaba.one`	— (app, not static)	Vercel (planned)	Phase 2	All tenants (Supabase auth)
[ 6th — confirm ]	—	—	—	—	TBD	You mentioned six — tell me the sixth

DNS — where to point each domain

indaba.one DNS is managed at Vercel; getindaba.com uses its own registrar. For a Netlify subdomain, add a CNAME to that site's *.netlify.app (find it in the site's Netlify dashboard). Only ens-indaba.netlify.app is confirmed so far.

Domain	DNS managed at	Type	Name / Host	Value / Target	Notes
ens.indaba.one	Vercel	CNAME	`ens`	`ens-indaba.netlify.app`	✓ confirmed
cases.indaba.one	Vercel	CNAME	`cases`	`<isobel-site>.netlify.app`	confirm Netlify name
fsc.indaba.one	Vercel	CNAME	`fsc`	`<fsc-site>.netlify.app`	confirm Netlify name
getindaba.com (apex)	its registrar	A	`@`	`75.2.60.5`	Netlify load-balancer IP — verify in Netlify Domain settings; or switch to Netlify DNS nameservers
www.getindaba.com	its registrar	CNAME	`www`	`<getindaba-site>.netlify.app`	confirm Netlify name
*.indaba.one (app)	Vercel	CNAME / A	`*`	the Vercel app host	Phase 2 wildcard for all tenants

Access & logins

Model: magic-link sign-in (email → one-tap link, no passwords to manage). "Credentials" = the person's email + their private link. This needs Supabase auth (Phase 2) before real logins exist — today's sites are previews.

Owner / Admin: Danny "Shumba" (all sites).

EnS Case File: Esther → provision via magic-link sign-up · Savi Horne → via her own email · both as Principals.

Six Isobel: Danny + counsel.

INDABA · Site Registry & Backup Protocol · Convergence AI — internal working reference