Notion Redesign Proposal, 2026-04-29¶

Creative refactor proposal grounded in notion-audit-2026-04-29 and notion-research-2026-04-29. Read this top-to-bottom and mark each section yes / no / modify; once you sign off, I move to apply.

Scope: Life OS (priority #1), JustinWieb-VR, Nova Design, Wiebelhaus Fishing, Gus The Bass. Skipped: Wiebelhaus Enterprises, Sip-N-Serve, Gus Outdoor Co (Gus Outdoor Co per spawn handoff).

Framework not data: every shape below is structural; you fill rows when you actually use the surface.

0. The TL;DR (revised 2026-04-29 after Justin's pushback)¶

Big call	Recommendation	Why
Workspace shape	Personal HQ as homepage; existing sidebar (Life + JustinWieb-VR + Nova Design + Wiebelhaus Fishing + Gus The Bass + Gus Outdoor Co.) stays as top-level brand pages below it	Justin's existing structure is mostly right; HQ adds the missing dashboard layer; Free plan stays simple
Tasks DB count	Five: Life Tasks, JWVR Tasks, Nova Tasks, Fishing Tasks, Bass Tasks. All identical schema.	Per Justin's call: separate DBs per brand for mental model and per-brand views. HQ rolls them up via Linked Database blocks.
Projects DB count	Five: same per-brand split, identical schema	Mirrors Tasks; same reasoning
Title field naming	Rename all titles to `Name`	Industry default; brain code stops needing per-DB title-field map; mobile shows the value, not the field name, so semantics aren't lost
Inbox sort flow	Telegram brain `sort_inbox` tool (capture or coordinator)	No Notion AI on Free plan; capture brain already has Claude; this fits the Forge-vs-Notion split (sort logic = grep-from-script = Forge side)
Creator pipeline	Keep Pillars; add Series + Deliverables + Derivatives; collapse Production status into 6-stage pipeline	Three-DB sponsor pattern is dominant in field; Production status as 3-state was the worst-fit enum in the audit
Marie Poulin integration	Lift her HQ daily dashboard + weekly review + monthly review templates	Highest-leverage primitives; ignore her formula-heavy rollups (mobile-hostile)
Thomas Frank integration	Lift his My Day dashboard structure + status lifecycle naming	Don't import full Ultimate Brain, it locks you in; cherry-pick
Daily Log	Add relations to Tasks (per-brand), Habits, Wellness Daily; brain-drafted post-mortem field	Rescues from graveyard status; one-page review surface
Sponsors	Split into Sponsors + Deals + Deliverables (three-DB pattern)	Current single Sponsors DB can't express a real pipeline

If you sign off on these 10 calls and nothing else, that's enough to ship.

1. Workspace shape (revised)¶

Personal HQ  (NEW page; your homepage, mobile-pinned via Favorites)
│
├── 📥 Inbox                 (single, top-level)
├── 🧠 Knowledge             (single, top-level, life-level)
├── 📚 Reading & Watch       (single, top-level)
├── 🎯 Areas                 (single, top-level, all brand + life areas)
├── 🎯 Goals                 (single, top-level)
├── 🔁 Habits                (single, top-level)
├── 📝 Daily Log             (single, top-level)
├── 💪 Wellness Daily        (single, top-level; quiet, Forge-fed)
│
└── Top-level brand pages (your existing sidebar, kept as-is):
    ├── 📦 Life              (personal hub, holds Life Tasks + Life Projects)
    ├── ⚡ JustinWieb-VR     (full creator pipeline: JWVR Tasks, JWVR Projects, Pillars, Series, Production, Published, Sponsors, Deals, Deliverables, Derivatives, Brand Reference)
    ├── 🌀 Nova Design       (client-work shape: Nova Tasks, Nova Projects, Clients, Brand Reference)
    ├── 🐟 Wiebelhaus Fishing (light: Fishing Tasks, Fishing Projects, Brand Reference)
    ├── 🎵 Gus The Bass       (light: Bass Tasks, Bass Projects, Brand Reference)
    └── 🌲 Gus Outdoor Co.   (PRESERVED, untouched)

Why this shape¶

Personal-layer DBs (Inbox, Knowledge, Reading, Areas, Goals, Habits, Daily Log, Wellness) are top-level singletons; you have one of each, brand is just a multi-select property where it matters
Per-brand Tasks and Projects live INSIDE each brand's top-level page (per Justin's "all separate DB" call)
Personal HQ sits above all of this, surfacing today's state via Linked Database blocks
No teamspaces; Free plan keeps the simple sidebar

Personal HQ contents (the dashboard)¶

Personal HQ
├── ⚡ Quick Capture button -> @forge_inbox_capture_bot in Telegram
│
├── 📥 Inbox today
│    └── Linked view of Inbox, filter: Sorted? = false, sorted by Created desc, capped at 10
│
├── ✅ Today across all brands (5 stacked Linked Database blocks)
│    ├── Life Tasks      filter: Today = true
│    ├── JWVR Tasks      filter: Today = true
│    ├── Nova Tasks      filter: Today = true
│    ├── Fishing Tasks   filter: Today = true
│    └── Bass Tasks      filter: Today = true
│
├── 🔁 Habits today      Linked view of Habits, filter: Date = today
├── 📝 Daily Log today   Linked view of Daily Log, filter: Date = today (one row, opens to full entry)
└── 🎯 Active Projects   Linked views per brand, status = Active, capped at 5 each

Mobile-friendly: Linked Database blocks load each section independently, no formula chains, no rollups across DBs.

Want a true unified "today" list?¶

The Telegram coordinator brain queries all 5 Tasks DBs in parallel and replies with a merged list in 2 seconds. Use this when you want one flat list instead of 5 stacked sections. HQ stays structured (per-brand sections); chat handles the merged view on demand.

2. Per-brand Tasks DBs (5 of them, identical schema)¶

Per Justin: separate Tasks DB per brand, NOT one unified DB. Five DBs with the SAME schema below. Brain has one tool tool_create_task(task, brand, ...) that routes to the right DB based on brand.

Shared schema (applied identically to Life Tasks, JWVR Tasks, Nova Tasks, Fishing Tasks, Bass Tasks)¶

Property	Type	Notes
Name	title	renamed from `Task` (same name across all 5 DBs so brain code is uniform)
Status	status	`Inbox / Next / Doing / Waiting / Done` (Inbox = un-triaged, Next = approved for soon, Doing = in flight, Waiting = blocked, Done = closed)
Priority	select	`Urgent / High / Medium / Low` (drop the lone 🔥 emoji; consistent or none)
Area	relation -> Areas (top-level Areas DB)
Project	relation -> the brand's own Projects DB (Life Tasks -> Life Projects, JWVR Tasks -> JWVR Projects, etc.)
Due	date
Scheduled	date	"do on this day" separate from due-date deadline
Today	formula	`Scheduled <= today AND Status != Done` (drives the Today view on HQ)
Source	select	`Telegram / iOS Shortcut / Brain / Email / Manual`
Notes	rich_text
Created	created_time
Done At	date	set by status -> Done; replaces the broken `Completed` last_edited_time

Per-DB views (pinned in each brand's page; HQ shows the cross-brand stack)¶

Today (filter: Today = true, sorted by Priority)
Doing (filter: Status = Doing)
Triage Inbox (filter: Status = Inbox, sorted by Created desc)
Waiting (filter: Status = Waiting)

Brain tool changes (handed to bot-refiner)¶

tool_create_task(task, brand, priority, due): brand selects which Tasks DB to write to. Allowed: life / jwvr / nova / fishing / bass. Today's signature already has a brand arg; just expand the routing.
tool_update_task(task_query, status, priority, due, brand): brain searches in the brand-specific DB, not just tasks. Brand becomes required.
tool_query_notion(database, filter_text): works correctly once title fields are renamed to Name and the filter shape is fixed.

What this kills¶

The current tasks DB (Life OS Tasks) and jwvr_tasks DB get archived. New 5-DB set replaces them.
Old per-DB title naming chaos: every Tasks DB now has Name as title.
Brain's broken tool_query_notion filter shape gets fixed in the same pass.

3. Per-brand Projects DBs (5 of them, identical schema)¶

Same pattern as Tasks. Five Projects DBs (Life Projects, JWVR Projects, Nova Projects, Fishing Projects, Bass Projects), all sharing the schema below.

Shared schema¶

Property	Type	Notes
Name	title	renamed from `Project`
Status	status	`Active / Paused / Archived / Done` (replaces 3-state enum)
Area	relation -> Areas (top-level)
Outcome	rich_text	keep, this is the PPV influence and it's the highest-value field
Start	date
Due	date
Goal	relation -> Goals (top-level)	optional
Tasks rollup	rollup count of related Tasks where Status != Done	per-brand: each Projects DB rolls up from its OWN Tasks DB
Notes	rich_text
Created	created_time

What this kills¶

Current projects (Life OS Projects) and jwvr_projects DBs archived; new 5-DB set replaces them
Schema-wise, each new Projects DB is a clone of the others; brain has one tool that routes by brand

4. Areas (mostly fine, one fix)¶

Keep DB. Changes:

Drop or repurpose the Color property (currently holds duplicate of title). If keeping, repurpose to actual color tags (red / orange / yellow / green / blue / purple) as a visual hierarchy hint
Add Brand multi_select (same options as Tasks/Projects). Areas can be life-only (Health, Family, Mind), brand-only (JWVR Audience Growth, Nova Client Pipeline), or both

The seeded Areas (Health, Wealth, Family, Career, Mind, Hobbies, Home, JWVR, Nova Design) already imply this shape; just normalize.

5. Inbox + Telegram-brain sort flow (no Notion AI)¶

Justin is on Notion Free plan. Sort logic moves to the Telegram coordinator brain, which already runs Claude.

Schema additions to Inbox¶

Property	Type	Notes
Name	title	renamed from `Title`
Destination	select	`Task / Knowledge / Reading / Project / Calendar / Archive / ?` (the ? means "brain wasn't sure, you decide")
Suggested Brand	select	`Life / JWVR / Nova / Fishing / Bass` (when destination is Task or Project)
Brain Notes	rich_text	brain writes its proposed title + priority + area here, ready for one-tap approval
(existing) Notes, Source, Tags, Created, Sorted?

Flow¶

Capture brain writes to Inbox (already works, no change). Sorted? = false, Destination = ?.
Justin types /sort 5 to @forge_lifeos_coordinator_bot (or @forge_inbox_capture_bot if we add it there).
Coordinator brain runs new tool tool_sort_inbox(count=5):
Queries Inbox where Sorted? = false, ordered by Created asc, capped at count
For each row, calls Claude with the row content and asks for {"destination": "...", "brand": "...", "title": "...", "priority": "...", "area": "..."}
Writes Brain's proposal back to the Inbox row's Destination, Suggested Brand, Brain Notes
Replies in Telegram with a numbered list: [1] xyz -> JWVR Task (priority Medium, area JWVR) etc.
Justin replies with one of:
approve all -> brain creates target rows, marks Inbox rows Sorted? = true, archives Inbox originals
approve 1 3 5 -> only those rows get executed
override 2 -> Knowledge -> brain corrects destination, then re-presents with all rows for final approve
Inbox rows that got executed disappear from the active Inbox view; archived Inbox rows are still queryable for audit.

Manual sort (without brain)¶

The Destination select on each Inbox row is also editable manually. Tap a row, set Destination to Task / Knowledge / etc., then a button "Execute sort" (a Notion automation OR a Telegram command /execute-inbox-sorts) processes everything with manual destinations set.

Why this is better than Notion AI¶

No paid plan needed
Brain already has full Forge context (Areas, Projects, Brands), Notion AI starts cold each invocation
Sort logic is grep-from-script (Forge side per the doctrine), not tap-to-think (Notion side); this routing matches the principle
Auditable: every brain decision lands in the Inbox row's Brain Notes field, so you can see what it thought before approving

6. Knowledge (Forge-grade source, Notion-grade index)¶

Schema changes:

Name title (already named Title, normalize to Name)
Add Type select: Note / MOC / Quote / Reference / Lesson (LYT-flavored)
Add Brand multi_select
Drop Topics (duplicate of Tags)
Add Forge URL url field: when a Knowledge item is canonically a Forge memory file (e.g., a reference_*.md), Notion entry is the human-facing index pointing at https://mkdocs.justinsforge.com/memory/general/...

Pattern in practice:

Light, narrative, journal-shaped knowledge: born in Notion, lives in Notion
Stable, factual, system-relevant: lives in Forge memory/general/, has a thin Notion entry pointing at it (so search-from-mobile finds it)
This collapses the duplicate-knowledge antipattern

7. Reading & Watch (status fix + creator angle)¶

Changes:

Name title (already Title, normalize)
Status enum: Want to read / Reading / Finished / Abandoned / Reference (replaces 3-state)
Add Brand multi_select (so research for JWVR videos and personal reading are separable)
Add Pillar relation -> Pillars (optional, JWVR teamspace surfaces filtered)
Drop emoji rating, use 1-5 numeric scale
Add Quote rich_text for the one line worth saving

8. Goals¶

Changes:

Name title (already Goal, normalize)
Replace Year + Quarter selects with Period Start + Period End dates (continuous timeframes; Timeframe select stays as the human label)
Add Target rich_text for measurable success criteria (PPV influence: "what does success look like, in numbers")
Add Brand multi_select
Linked Projects stays
Add Linked Habits relation -> Habits (so a habit can be tied to a goal: meditation -> Mind goal)

9. Habits¶

Changes:

Name title (currently Entry, rename to Name for consistency; brain writes the same composed string)
Add Linked Goal relation (optional)
Add Streak formula (looks back 30 days, counts consecutive Done = true)
Drop Category if duplicates the Habit select; keep if it groups (Health / Mind / Skill / Social actually does group, so keep)

Habit definition surface¶

Add a tiny Habit Definitions DB (separate from logs):

Property	Type
Name	title
Category	select
Cadence	select (Daily / Weekly / Custom)
Linked Area	relation
Active?	checkbox

The Habits DB then becomes a log of daily ticks, related to a Habit Definition. This is Marie Poulin's pattern and it's mobile-friendly (the daily-tick view is just 5 checkboxes).

10. Daily Log (rescue from graveyard)¶

Changes:

Name title (currently Date, normalize)
Add Tasks Done rollup: count of Tasks where Done At = today
Add Habits Hit rollup: count of Habits where Date = today AND Done? = true
Add Sleep Score rollup: from related Wellness Daily row
Add Linked Wellness relation -> Wellness Daily (one-to-one per date)
Add Post-mortem rich_text: AI-drafted "what mattered today" paragraph (from related rows)
Keep Mood, Energy, Wins, Lessons, Notes

Daily ritual¶

Pinned mobile view: today's row only, with all rollups + AI post-mortem. Two minutes per day to review.

11. Wellness Daily¶

Almost no changes. The 23 properties exist for the Forge-side wellness pipeline. Add one new property:

Linked Daily Log relation -> Daily Log (so Daily Log can rollup it)

Hide the DB in the sidebar (it's data plumbing, not a daily-touch surface).

12. JustinWieb-VR teamspace (full creator pipeline)¶

Existing DBs that change¶

Content Ideas: rename title to Name, replace 3-state Status with Captured / Sketched / Approved / Promoted to Production / Killed, add Format select (Long-form / Short / Series episode / Live stream), add Effort select (Quick / Medium / Heavy), add Linked Series relation
Production: rename title to Name, replace Stage (3-state) with Idea / Scripted / Filmed / Edited / Scheduled / Published, add Sponsor relation -> Sponsors (optional), add Deliverable relation -> Deliverables, add Linked Series relation, add Hero? checkbox (true = original; false = derivative), add Hero relation -> Production (self-relation, points at the parent if this is a derivative)
Published: ADD TO BRAIN'S NOTION_DBS MAP (this is a live bug). Rename title to Name. Add Source Production relation -> Production. Keep metrics (Views, Likes, Comments) but add Snapshot Date so you can append rows monthly without losing history
Pillars: keep, rename title to Name. Add Target Cadence select (Weekly / Bi-weekly / Monthly / Ad-hoc). Add KPI rich_text
Sponsors: rename title from Brand to Name. Stage enum becomes Outreach / Pitching / Negotiating / Active deal / Wrapped / Lost / Passed. (See new Deals DB below; Sponsors becomes the company directory, Deals is the per-deal pipeline)

New DBs¶

Series (small managed)¶

Property	Type
Name	title
Pillar	relation -> Pillars
Start	date
End	date
Status	status (`Planned / Live / Wrapped`)
Outcome	rich_text
Linked Productions	relation (reciprocal of Production.Linked Series)

Property	Type
Name	title (e.g., "Quest 4 launch sponsorship")
Sponsor	relation -> Sponsors
Stage	status (`Lead / Negotiating / Contract / In Production / Delivered / Invoiced / Paid / Lost`)
Value	number
Contract URL	url
Due	date
Linked Deliverables	relation (reciprocal)
Notes	rich_text

Deliverables (what you owe per deal)¶

Property	Type
Name	title (e.g., "1 dedicated YouTube video")
Deal	relation -> Deals
Production	relation -> Production (the actual content row)
Type	select (`Long-form video / Short / Story / Tweet / Newsletter / Live stream`)
Status	status (`Pending / Drafted / Approved by sponsor / Live`)
Due	date

Derivatives (repurposing)¶

Property	Type
Name	title
Hero	relation -> Production
Platform	select (`Shorts / Reels / TikTok / Tweet / LinkedIn / Newsletter`)
Status	status (`Idea / Drafted / Scheduled / Published`)
Posted	date
Notes	rich_text

Brand Reference (sub-page, not a DB)¶

A teamspace landing page with: - Audience profile - Brand voice + tone - Visual style (link to Drive folder) - Rate card - Standard disclaimer text - Press kit link

This is narrative content (tap-to-think), not structured data. Single page, edit when needed.

13. Nova Design teamspace (client-work shape)¶

Different from a creator pipeline. Proposed DBs:

Clients¶

Property	Type
Name	title
Status	status (`Lead / Active / On retainer / Wrapped / Lost`)
Contact Name	rich_text
Contact Email	email
Source	select
Lifetime Value	number
Notes	rich_text
Linked Projects	relation (reciprocal)

Project shape (lives in unified Projects DB, filtered to Brand=Nova)¶

Add property: Client relation -> Nova Clients (only visible when Brand contains Nova)

Style Guides (single page or DB if multiple clients each have one)¶

Invoices (defer until volume justifies; Notion is wrong tool early)¶

14. Wiebelhaus Fishing + Gus The Bass teamspaces (light)¶

Both are light teamspaces unless you tell me otherwise. Each gets:

Brand Reference page (narrative)
Filtered views into unified Tasks + Projects (Brand = Fishing or Bass)
Optional: light Content Pipeline if these brands publish content. Tell me whether Fishing and Bass produce content (videos, posts, audio) and I'll add Pillars + Production for whichever does.

If they're more like personas / projects / hobbies than active content brands, the light shape is enough.

15. Marie Poulin integration¶

Lifted primitives (woven into the design above, not a separate import):

Personal HQ daily dashboard: pinned mobile homepage with My Day tasks, today's calendar (linked from Notion Calendar), 3-5 active projects, quick capture button, habit ticks. The shape every credible creator template converges on.
Weekly Review template: a Notion page template you spawn each Sunday. Sections: completed projects, lessons captured, Areas health-check, next-week's top three. Lives at HQ, opens with one tap.
Monthly Review template: similar shape, Pillars cadence check (did each pillar hit target this month), Goals progress, financial roundup if relevant. Linked from HQ.
Areas as life lens: Areas drive the navigation, not folders. Tasks, Projects, Knowledge, Goals all relate back to Areas; clicking an Area surfaces all related items.

What I'm NOT lifting from Marie:

Her formula-heavy progress bars (mobile-hostile)
Her habit-tracker DB sprawl (her latest course consolidates this anyway)
Her client-management framework (she's a coach, you're a designer/creator; different shape)

16. Thomas Frank integration¶

Lifted:

My Day dashboard component: today + tomorrow + this week tabs, task hierarchy by Status. Already in the unified Tasks design.
Quick Capture pattern: already implemented (your iOS Shortcut + Telegram brain; nothing to add)
Status lifecycle naming: Inbox / Next / Doing / Waiting / Done. Cleanest in the field, already adopted in Section 2.

NOT lifting:

Full Ultimate Brain template import (locks you in; his decisions don't all fit yours)
His Goal -> Area -> Resource hierarchy (PARA-flex with Areas-as-lens beats it for your shape)
Sub-task DB nesting (mobile-hostile)

17. Brain tool changes (separate handoff to bot-refiner)¶

I'll write forge/memory/handoffs/bot-tool-additions-2026-04-29.md once you sign off, covering:

Fix tool_query_notion: replace {"property": "title", "rich_text": ...} with {"property": "Name", "title": {"contains": ...}}. With Name normalization, this works across all DBs.
Fix tool_update_task: same filter-shape fix; takes a brand arg to pick which Tasks DB to search.
Add jwvr_published to NOTION_DBS (live bug, missing currently).
Expand NOTION_DBS for the new 5-Tasks-DB and 5-Projects-DB world: add life_tasks / jwvr_tasks / nova_tasks / fishing_tasks / bass_tasks and life_projects / jwvr_projects / nova_projects / fishing_projects / bass_projects (rebuild the dict to match).
tool_create_task(task, brand, ...) brand routing: brand selects the Tasks DB (Life/JWVR/Nova/Fishing/Bass). Default = life.
New tool: tool_sort_inbox(count=5) for the Telegram-brain sort flow (Section 5). Reads unsorted Inbox rows, calls Claude per row, writes proposal back to row, replies in Telegram for one-tap approval.
New tool: tool_execute_inbox_sorts(ids=None) — executes pending sorts, either all approved or specific IDs. Creates target rows in the right DB, marks Inbox rows sorted, archives originals.
New tool: tool_link_task_to_project(task_query, project_query, brand) — for cross-DB linking within a brand.
New tool: tool_create_published(production_query, url, posted_date, platform) — handle the now-wired Published DB.
New tool: tool_create_deliverable(deal_query, type, due, ...) — for the new Sponsors + Deals + Deliverables pipeline.
New tool: tool_today_across_brands() — queries all 5 Tasks DBs in parallel, returns merged "what's on my plate today" list. Used when Justin asks the coordinator for the unified view.

These get queued for bot-refiner; I don't touch the brain directly.

18. Cleanup punch list¶

Archive TEST DELETE ME DB (3500950b-d7a9-816b-87e3-fe14d30fd136)
Archive jwvr_tasks DB after migration to unified Tasks
Archive jwvr_projects DB after migration to unified Projects
Update reference_notion_scaffold.md with new DB IDs + the new shape
Add jwvr_published to brain NOTION_DBS map
Add jwvr_series, jwvr_deals, jwvr_deliverables, jwvr_derivatives once created
Add nova_clients once created

19. Migration plan (when you greenlight apply)¶

Phase	What changes	Risk	Effort
19A. Property additions + renames	Rename all title fields to `Name`; expand status enums; add Brand multi-select to Areas/Goals/Knowledge/Reading; add Today formula to existing Tasks (then to new ones)	Low (DBs are nearly empty; brain code touches only renamed fields)	Half hour
19B. New DBs	Create new per-brand Tasks DBs (Life, JWVR, Nova, Fishing, Bass) and Projects DBs (same 5); create JWVR Series + Deals + Deliverables + Derivatives; create Habit Definitions, Nova Clients, Brand Reference pages. Archive old `tasks` and `jwvr_tasks` and old projects DBs once new ones are wired.	Low to medium (creating DBs via Notion API works; archiving old DBs needs your tap to confirm)	One hour
19C. Pinned views	Document the iPhone clicks needed to pin the My Day, Sort Inbox, Today's Doing views; you do this in 5 min	None (manual)	5 min
19D. Brain tool fixes	Hand to bot-refiner via handoff; bot-refiner ships fixes; capture+coordinator services restart	Medium (live bot fleet; hot-reload)	bot-refiner's call
19E. Archive old DBs	Move `jwvr_tasks`, `jwvr_projects`, `TEST DELETE ME` to Notion archive	Low (you confirm before each archive)	5 min

Total time-on-Justin: ~30 minutes of clicking; the rest is automation.

20. Open questions for sign-off¶

I genuinely need answers to these before applying:

Workspace shape: one workspace with teamspaces (recommendation), or do you want separate workspaces per brand?
Tasks consolidation: yes, kill JWVR Tasks DB, one unified DB with Brand property?
Title field naming: Name everywhere (recommendation), or keep semantic names (Task, Project, etc.) and have brain map them?
Wiebelhaus Fishing + Gus The Bass content shape: light brand teamspace only, or do either of these brands publish content (videos, audio, posts) and need a creator pipeline?
Notion AI Inbox sort: implement Seed 1 now (requires Notion AI subscription, you may already have it), or defer?
Marie Poulin templates: import her actual page templates (weekly + monthly review) from her shop, or build custom in her style?
Anything else in your Notion (free-floating pages, hand-built dashboards, sub-pages I don't know about) you want preserved or refactored?

21. What's NOT in this proposal (intentional)¶

Family / personal data layer beyond the framework (per your "framework not data" direction)
Pure life-coach surfaces (mood tracking beyond Daily Log, journaling templates, etc.)
Financial tracking DBs (different domain; if you want it, we add a Finance teamspace later)
Client invoicing for Nova Design (defer until volume justifies)
Gus Outdoor Co (preserved untouched per spawn handoff)

[Claude Code, Pure Phoenix Notion architect]

Notion Redesign Proposal, 2026-04-29¶

0. The TL;DR (revised 2026-04-29 after Justin's pushback)¶

1. Workspace shape (revised)¶

Why this shape¶

Personal HQ contents (the dashboard)¶

Want a true unified "today" list?¶

2. Per-brand Tasks DBs (5 of them, identical schema)¶

Shared schema (applied identically to Life Tasks, JWVR Tasks, Nova Tasks, Fishing Tasks, Bass Tasks)¶

Per-DB views (pinned in each brand's page; HQ shows the cross-brand stack)¶

Brain tool changes (handed to bot-refiner)¶

What this kills¶

3. Per-brand Projects DBs (5 of them, identical schema)¶

Shared schema¶

What this kills¶

4. Areas (mostly fine, one fix)¶

5. Inbox + Telegram-brain sort flow (no Notion AI)¶

Schema additions to Inbox¶

Flow¶

Manual sort (without brain)¶

Why this is better than Notion AI¶

6. Knowledge (Forge-grade source, Notion-grade index)¶

7. Reading & Watch (status fix + creator angle)¶

8. Goals¶

9. Habits¶

Habit definition surface¶

10. Daily Log (rescue from graveyard)¶

Daily ritual¶

11. Wellness Daily¶

12. JustinWieb-VR teamspace (full creator pipeline)¶

Existing DBs that change¶

New DBs¶

Series (small managed)¶

Deals (sponsor pipeline)¶

Deliverables (what you owe per deal)¶

Derivatives (repurposing)¶

Brand Reference (sub-page, not a DB)¶

13. Nova Design teamspace (client-work shape)¶

Clients¶

Project shape (lives in unified Projects DB, filtered to Brand=Nova)¶

Style Guides (single page or DB if multiple clients each have one)¶

Invoices (defer until volume justifies; Notion is wrong tool early)¶

14. Wiebelhaus Fishing + Gus The Bass teamspaces (light)¶

15. Marie Poulin integration¶

16. Thomas Frank integration¶

17. Brain tool changes (separate handoff to bot-refiner)¶

18. Cleanup punch list¶

19. Migration plan (when you greenlight apply)¶

20. Open questions for sign-off¶

21. What's NOT in this proposal (intentional)¶