ClientsFlow Notes — one domain for every review note

🟢 root: clientsflow-notes.pages.dev 🔵 path: /<repo>/<doc>/ 🟣 Notion: master "Reports" DB

What changed

Before

1 file→1 CF project→cap hit 💥

~100 projects, hit the Pages project limit; deploys started failing.

After

all notes→1 project→/repo/doc/ paths

A persistent local root accumulates notes; one deploy re-uploads the whole tree.

Auto-Notion

note deploys→Reports DB page→live embed

Every reviewable note now also creates/updates a row in the master "Reports" DB (child of "Databases").

Client staging rule

client site→clientname-yy-mm-dd

New normative slug for client website staging (separate from notes).

How addressing works /<repo>/<doc>/

Piece Rule Example

Root one Pages project clientsflow-notes.pages.dev

Top folder git repo basename of the file /ghl-funnel/

Leaf folder doc slug — note folder name (climbs past site/dist/build); filename stem otherwise /journey-visualizer/

Index auto-generated root page lists every note grouped by repo clientsflow-notes.pages.dev/

Piece	Rule	Example
Root	one Pages project	`clientsflow-notes.pages.dev`
Top folder	git repo basename of the file	`/ghl-funnel/`
Leaf folder	doc slug — note folder name (climbs past `site/dist/build`); filename stem otherwise	`/journey-visualizer/`
Index	auto-generated root page lists every note grouped by repo	`clientsflow-notes.pages.dev/`

The pieces

File Role

~/.claude/hooks/notes_lib.py shared lib: slug/hierarchy, house-style root index, single-project deploy, Notion create-or-update

~/.claude/hooks/cf-staging-deploy.py Stop hook: place reviewable notes → one deploy → mirror to Notion (fail-open)

~/.claude/clientsflow-notes/ persistent local root that accumulates every note (the deploy source)

Reports DB 74f54118… master Notion DB under "Databases" — every note gets a row + live embed

File	Role
`~/.claude/hooks/notes_lib.py`	shared lib: slug/hierarchy, house-style root index, single-project deploy, Notion create-or-update
`~/.claude/hooks/cf-staging-deploy.py`	Stop hook: place reviewable notes → one deploy → mirror to Notion (fail-open)
`~/.claude/clientsflow-notes/`	persistent local root that accumulates every note (the deploy source)
Reports DB `74f54118…`	master Notion DB under "Databases" — every note gets a row + live embed

New global rule — client staging naming. Client website/landing-page staging deploys use a dated, normative slug: clientcompanyname-yy-mm-dd → clientcompanyname-yy-mm-dd.pages.dev. This is separate from the notes system (review docs go to clientsflow-notes; client sites stay one project per client, now consistently named).