Doc 2 — Reorganized Master Plan (strikethrough = also in Doc 3)

Start here What this page is: A live master plan + handoff doc for consolidating the workspace safely. It is both a policy/runbook and an execution log for database/planner consolidation, cleanup review, taxonomy normalization, finance cleanup, and frontend ↔ backend reconnect work. How to use it: Start here first, work only from ✅ NEXT ACTIONS / Master Checklist, and use Navigation map / Reference library for evidence, source material, databases, specs, cleanup lists, changelogs, and source references. Do-not-touch rule: The “Exact Duplicates — Verified Delete List” section is formatting-fragile in the source page; do not rewrite its internal formatting unless explicitly requested. Scope / goal Clean up and consolidate Notion workspace databases + planners, then ensure platform frontend ↔ Notion backend routing stays correct after moves/renames, with bidirectional syncing. Mission Build one clean, frontend-ready workspace backend without losing useful content, breaking existing planner layouts, deleting unapproved items, or disconnecting platform routes/forms/dashboards from the correct Notion sources. Guiding principles / standing rules No deletion before approval: Never delete or archive any database, page, property, row, template, view, or block unless Jillian has first seen a clear clickable approval list and explicitly approved the exact deletion/archive in chat. Inventory-first: Compile same/similar pages and databases with links first. Do not move, delete, or merge until inventory and dependency context is visible. Keeper-first: Choose the keeper before merging. Improve the keeper first, then migrate or mirror useful content into it. Labels are signals, not decisions: “ready to archive,” “DELETE?,” “dup check,” “merge,” “official,” “keeper,” and “do not delete” are review labels only. Soft-retire before delete: Legacy items stay until dependency sweep, data migration, frontend reconnect, and verification are complete. Preserve UX, layouts, content, and media: Preserve useful planner layouts, linked views, page contents, covers, icons, files, templates, comments where available, and meaningful media. Do not break connected views: If moving a database would break linked views or page layouts, keep the database in place and connect it through master inventory / linked views until reconnect is ready. Master inventory is source of truth: Use the Master Databases Inventory, Master Views Inventory, and Master Subject Sections databases as the working source of truth. Brown-square keeper marker: Confirmed keeper pages/databases use the brown-square keeper convention until the final icon pass. True merge / dedupe standard Treat every old section as if it was “floating,” assign it to one of the three top-level toggles, and merge it into the matching canonical section. Compare duplicate/similar sections line-by-line. Keep one canonical header/section. Keep unique lines. For exact duplicate lines, keep only one copy. For partial duplicates where one line is a subset of another, keep the fuller/superset version and add only the missing unique part if needed. Example: “apple” + “apple” = keep one “apple.” Example: “apple and banana” + “apple and banana and lime” = keep “apple and banana and lime.” Example: same base task + extra status/detail/date/context = keep the more complete version and merge any missing useful detail into it. Update checked/unchecked status so the canonical checklist is accurate. Remove only the now-empty duplicate shell. Do not delete unique content just because the heading was duplicated. Timestamp rule for tasks going forward Format: (added: YYYY-MM-DD h:mm AM/PM ET; done: YYYY-MM-DD h:mm AM/PM ET). When a task is completed, add a done: timestamp on the same line when checking it off. Do not invent exact timestamps for historical completed work. If the old page already has a timestamp, preserve it; otherwise leave historical items untimestamped or label them as historical only when needed. Operating standards — how work must be done Global hubs only when the concept is truly shared: Platforms, Addresses, Cities, States, Countries, and truly shared categories/types/tags can be canonical global hubs. Do not consolidate just because labels match: Same concept = consolidate. Same label but different lifecycle = keep separate and clarify the name. Normalize on touch: When opening or modifying a database for cleanup, review select/multi-select/text-option/relation/rollup/formula setup, convert option-like fields to relation-backed fields where appropriate, preserve legacy fields until reconnect is stable, and update views after renames. Ready-to-archive rule: A database is only safe to archive if a keeper exists, all needed properties/settings/rows/views/templates/content/media are preserved or migrated, relations/rollups/formulas still work, and Jillian approves the exact archive/delete list. Duplicate database merge rule: Compare purpose, schema, properties, relation targets, rollups, formulas, options, templates, views, rows/pages, page content, covers, icons, files, media, and frontend dependencies before any duplicate is retired. Identical duplicate rule: A possible duplicate can be deleted only if it is confirmed identical or fully migrated and no frontend dependency remains. Address normalization standard: Operational databases should point to the canonical Addresses database; City/State/Country/ZIP should not remain long-term free text/select when structured reusable relations are intended. Closet / owned item lifecycle standard: Physical items should be trackable from acquired → owned/in closet → packed/used/listed → sold/donated/archived, tied to purchases, sales, events, schedule blocks, customer requests, and inventory where applicable. Frontend reconnect governance: Any database/property renamed, replaced, merged, or made canonical must be logged, legacy references preserved until reconnect is stable, reconnect mapping updated, and routes/forms/dashboards verified before legacy removal. Permission-blocked items: Log as blocked, do not make destructive assumptions, do not delete/archive related items, and revisit after access is available. Frontend ↔ backend audit logic Frontend ↔ backend audit and gap logic belong together in one canonical section. Compare the platform blueprint/schema/routes/forms/connection docs against current canonical Notion databases. Build a reconnect delta list showing old DB/property, new canonical DB/property, affected feature/route/form, migration note, and status. Confirm no frontend references point to deleted or legacy databases before final cleanup. Product intent — unified personal + business operating system The backend should support one day-in-the-life operating model across personal + business work. Today surfaces should be able to connect tasks, schedule blocks, events, expenses, income, sales, subscriptions, purchases, inventory, wishlists, closet items, bookings, customer requests, and content work. Finance, commerce, scheduling, inventory, and customer-request routing should remain connected through canonical databases and relation-backed taxonomy. ✅ NEXT ACTIONS / Master Checklist Use this as the only “what do I do next?” checklist. Add new tasks here the moment they are discovered, check them off when finished, and add timestamps per the Start here rule. Current next actions Continue workspace-wide page/bookmark duplicate sweep beyond the first exact-empty batch. (added: 2026-06-21 10:45 PM ET) Build the next approval-ready cleanup batch with clickable keeper/delete/archive decisions and reasons; no deletions before approval. (added: 2026-06-21 10:45 PM ET) Continue similar-but-not-identical database merge review after exact duplicates, preserving unique rows/properties/views/templates/content/media first. (added: 2026-06-21 10:45 PM ET) Continue taxonomy/config duplicate sweep and confirm global-vs-lifecycle-specific taxonomy hubs. (added: 2026-06-21 10:45 PM ET) Continue frontend reconnect delta list after Genspark/platform mapping links are available. (added: 2026-06-21 10:45 PM ET) Done / completed work Inventory and section structure Master inventory databases created. Master Subject Sections database created. Subject section relations created between Master Databases Inventory, Master Views Inventory, and Master Subject Sections. Every captured database inventory row has a Subject Section relation. All “(Unnamed…)” database inventory rows resolved using underlying database names. Direct subject-page database/view coverage captured in Master Views Inventory. Workspace-wide scattered linked-view/location sweep completed for remaining planner, legacy, and duplicate locations. Views Inventory relation normalization completed: Audit Queue subject, Subject section, and Master database inventory item filled. Zero Views Inventory rows remain missing the three core relation fields. Cleanup / duplicate review Initial cleanup candidate scan completed from Master Databases Inventory. Duplicate inventory-row groups found by repeated underlying database link. Label-based review candidates found from ready-to-archive, DELETE?, dup, merge, official, legacy, and do-not-delete signals. First-pass comparison findings added for University & Education, Formats, Health/Habits, Email Templates, Shot List, Untitled Booking wrappers, Personal People vs Contacts, and same-underlying inventory-row duplicates. Exact duplicate linked-view comparison pass completed. Exact duplicate Weekly Planner Duplicate 1–5 databases removed after confirmation. Same-underlying inventory-row duplicate groups cleaned after confirmation while keeping active underlying databases. Email template/categories duplicate cleanup executed after preserving keeper fields. Shot List duplicate cleanup executed after preserving useful Booking Location relation. First exact-empty page/bookmark duplicate batch completed. Backend / reconnect / taxonomy / finance Genspark reconnect material reorganized into operating standards, integrated checklist/phases, and changelog source material. Platforms, Cities, States, Countries, Addresses, and Statuses canonical hubs documented. Address normalization standard documented. Global-vs-lifecycle-specific taxonomy rule documented. Customer Requests relation replacements and content modeling decisions documented. Scheduling canonical stack documented: Booking Calendar, Availability, Unified Schedule. Unified personal + business day-in-the-life intent documented. Finance sign convention and refund policy implemented. Legacy subscriptions and legacy income migrated into canonical keepers. Remaining work Cleanup review / merge / consolidation Continue workspace-wide page/bookmark duplicate sweep for non-empty and same-title pages. Compare remaining duplicate/similar database clusters by schema, relation targets, rollups, formulas, options, views, templates, rows/pages, page content, covers, icons, files, media, and frontend dependencies. Choose keepers only after comparison. Add missing useful schema/views/templates to keepers before retiring duplicates. Move or mirror unique rows/pages/content/media into keepers. Convert useful linked views into actual views on keeper databases where appropriate. Produce approval list before any archive/delete. Subject pages / planner structure Clear remaining subject pages into lightweight references after inventory is fully captured. Finish structural-page UI hygiene sweep: Operational, Taxonomy/Config, Dashboards/Reports, Protected Legacy, Review, Cleanup Queue. Continue final planner placement after merge/consolidation. Taxonomy/config and address normalization Continue taxonomy/config duplicate sweep. Confirm every taxonomy hub that should be global is global. Confirm lifecycle-specific taxonomies stay separate and are named clearly. Continue address normalization sweep for accessible databases. Revisit blocked legacy address-like source when access is available. Finance Identify remaining legacy embedded finance databases with unique rows. Migrate unique finance rows into canonical keepers. Only archive/delete legacy finance databases after confirmation and reconnect verification. Frontend reconnect Compare Connection Blueprint property maps against current canonical Notion databases. Build Reconnect Delta List: old DB/property, new canonical DB/property, feature/route/form affected, migration note, status. Verify every route/form/dashboard connects to canonical Notion sources. Confirm no frontend references point to deleted or legacy databases. Handoff final reconnect packet to Genspark. Blocked / needs access Extract “rules / instructions / steps” from Convo 1–3 PDFs and convert from chat-format into clean rules + tasks. Blocker: attachments were flagged as potentially risky / not viewable in the prior pass. Revisit blocked legacy Address-like data source when access is available. Add/confirm frontend/platform mapping fields for subject pages/sections after Jillian sends or confirms Genspark mapping links. Verification checklist Verify Master Databases Inventory, Master Views Inventory, and Master Subject Sections still agree after each cleanup batch. Verify no stale Views Inventory references point to deleted duplicate inventory rows. Verify no duplicate linked-view groups remain after each exact duplicate pass. Verify no repeated underlying database links remain in Master Databases Inventory after same-underlying row cleanup. Verify keeper databases contain all useful fields/views/templates/rows/content/media before any duplicate is retired. Verify frontend reconnect before deleting or archiving legacy sources. Navigation map / Reference library Use this as the map/reference library. The canonical rules are in Start here and the canonical tasks are in NEXT ACTIONS. Source details, database blocks, and evidence remain in the duplicate backup page and should be pulled into this reference library in true-merge passes as needed. Databases for planning 🟫 Master — Databases Inventory 🟫 Master — Views Inventory 🟫 Master — Subject Sections Linked Systems — Planners (Index) Audit Queue Main reference groups Cleanup Review List → comparison findings, approval gating, exact duplicate audit findings, merge/archive/delete evidence. Exact Duplicates — Verified Delete List → formatting-stable exact delete/keep pairs; do not reformat internally unless explicitly requested. Backend Rebuild Changelog → backend changes, completed migrations, reconnect notes, blocked items, high-impact historical changes. Taxonomy & Config → taxonomy/config lists, canonical global hubs, address normalization, global-vs-lifecycle-specific taxonomy reference. Dashboards & Reports → reporting surfaces and dashboard/analytics reference. Protected Legacy → protected/do-not-delete sets and legacy removal references. Finance reference/spec → finance canonical semantics, refund policy, finance verification source material, finance refactor notes. Linked Index → all-planners/databases inventory-only reference index. Source archive / prior structure Original duplicate backup page: 🟫🟫 Workspace Planner Consolidation — Master Plan (1) - Backup for Restructure in case anything ends up broken Use the original duplicate as the preserved source archive for full legacy detail, then true-merge source sections into this page only when needed. If moving archive material into this page later, keep it under this Navigation map toggle, not as new top-level toggles.