California Forever — Hub-Level Rules

This is the parent disambiguation hub for four related California Forever properties. Always start by figuring out WHICH property a request is about, then drop into that sub-folder's CLAUDE.md.

The Four Sub-Folders

Sub-folder Property URL
main-site/ Main marketing site californiaforever.com
solano-site/ Solano County site solano.californiaforever.com
solano-archive/ Read-only Plumb-era archive solanostaging.flywheelsites.com
brand-guide/ Brand guide (Next.js / Vercel) california-forever-brand-guide.vercel.app

See README.md for the full property table and routing rules.

Hard Rules (apply across all sub-folders)

  1. Identify the property first. Never save notes, run code, or take action without knowing which of the four properties you're working on. When in doubt, ask.
  2. Never touch the Solano archive. It exists as a frozen snapshot for the client. Read-only. If anyone asks for edits there, surface it as "are you sure? — that's the archive" before acting.
  3. Each sub-folder owns its own docs. Don't mix main-site notes into solano-site/ or vice versa. Cross-property work (e.g., a hub-level decision) lives at this parent level only.
  4. WAITING-ON-CLIENT.md stays at the parent root. Single-glance view of everything blocked across all four properties. Sections inside are tagged with which property each item belongs to.
  5. Production touches require per-action approval. Standard CLAUDE.md hard rule applies for all four properties — no SSH/SCP/wp-cli/DB writes/file pushes against any prod URL without an explicit, in-the-same-turn "yes, push it" referencing the specific action.

How to Use This Structure

If working on... Save docs to...
Main site (Phase II, Retainer, Slide Presentation, blog, pledge, etc.) main-site/
Solano site (current production, Spanish toggle, content updates, FAQs) solano-site/
The /solano/ sub-section planning (was parked Apr 2026) solano-site/ (planning lives with the Solano property)
Solano archive usually nothing — it's read-only. If someone genuinely needs a note, drop it in solano-archive/
Brand guide content / Slack /brand bot integration brand-guide/
Cross-property decisions (e.g., the May 2026 reorg) This parent folder root

Ecosystem Snapshot (May 2026)