DB ↔ FRONTEND-FEATURE ↔ CONNECTIONS MAP

_The grounding layer for the semantic content audit. For each keeper DB: what it is (original template system), which platform frontend feature/page consumes it, and what it must connect (relate) to. Every STAY/MOVE/NEW-DB/RELATE decision in the row-audit is justified against this map._

_Built 2026-08-09. Source: SYSTEM-BLUEPRINT.md, orig_db_structures.json, dbkeep_map.json, platform-server/routes + public/app pages._




HOW TO READ

  • DB = current keeper database (the system).
  • Original System = what the template's version of this DB is *for* (the reference for "what belongs").
  • Frontend Feature/Page = the platform page(s)/route(s) that sync this data on the frontend.
  • Connects To (relations) = other DBs this must relate to for the platform to work as intended.
  • SPINE = the connected group this DB belongs to.



  • SPINE 1 — KITCHEN / FOOD (Lifestyle)

    Frontend: recipes.html, (meal planning), grocery/shopping, inventory. The recipe-flow vision lives here.

    DBOriginal SystemFrontend Feature/PageConnects To

    |---|---|---|---|

    Recipes (KEEP)Recipes: Recipe Name, Ingredients(relation), Steps, Prep/Cook, Cuisine, Meal Typerecipes.html + recipe-flow→ Ingredients (what's needed), → Meal Plan, → Groceries (buy missing), → Kitchenware/Products (NEW?) (utensils needed)
    Ingredients (KEEP)(relation target of Recipes) food items: name, category, qty, unitrecipes.html (ingredient list), inventory→ Recipes, → Groceries, → Kitchen Inventory (in-stock check), → Shopping
    Groceries (KEEP)Grocery: Needed, Item, Qty, Unit, Storeshopping list / grocery→ Ingredients (buy missing), → Recipes
    Meal Plan (KEEP)Meal Plan: Name, Day, Date, Breakfast/Lunch/Dinner/Snackmeal planner / calendar→ Recipes, → Groceries
    _PROPOSED: Kitchenware/Products_utensils/tools (pots, pans, strainers) that get mixed into Ingredients(products/inventory page)→ Recipes (tools needed), → Ingredients, → Inventory

    Recipe flow (end goal): upload recipe → extract Ingredients → check Kitchen Inventory (have it?) → if not → add to Groceries → utensils needed pulled from Kitchenware.




    SPINE 2 — MEDIA / CONTENT-INTEREST (Learning + Entertainment)

    Frontend: content-gallery, watchlist, discover, feed, posts. Media Library must connect to the Posting DB.

    DBOriginal SystemFrontend Feature/PageConnects To

    |---|---|---|---|

    Media Library (KEEP)Media: Title, Type, Link, Status, Area, Notes, Date (books/media the user consumes)watchlist.html, discover.html, libraryPosts/Posting DB (users post about favorite shows), → Feed/Discover
    Books Library (KEEP)Books: Title, Author, Genre, Status, Ratingreading list / library→ Media Library (sibling), → Posts
    _MIXED-IN in Media Library:_ TV shows / watch contentshould relate to Media, not be raw library rowswatchlist→ Posts (post about shows), → Media Library
    _PLATFORM: Posts/Posting DB_user posts (frontend social) — content users publishfeed.html, social.html, stories→ Media Library (post about a show/book), → Filmography, → Content Gallery

    Media flow (end goal): Media Library = what you watch/read; Posts DB = what you publish about it; they RELATE so a post can reference a show. Determine per cluster: shows stay in Media Library (as watch-items) and relate to Posts — NOT duplicated into Posts.




    SPINE 3 — BANK / FINANCE (Finance) — PROTECTED SPINE

    Frontend: financial.html, earnings, expenses, transactions, tax. SINGLE SOURCE OF TRUTH — no double-counting.

    DBOriginal SystemFrontend Feature/PageConnects To

    |---|---|---|---|

    Transactions (KEEP)Transactions: Name, Date, Type, Amount, Category, Account, Payeefinancial.html (transactions tab)→ Accounts, → Categories, → Customer Requests, → Tax
    Accounts (KEEP)Accounts: Name, Type, Balance, Transactions(rel)financial.html (accounts)→ Transactions
    Bills (KEEP)Bills: Bill, Frequency, Amount, Due, Accountbills / recurring→ Accounts, → Transactions
    Subscriptions (KEEP)Subscriptions: Service, Amount, Billing Cyclesubscriptions→ Accounts, → Transactions
    Savings Goals (KEEP)Saving Goals: Goal, Target, Progress, Accountsavings→ Accounts, → Transactions
    Total Balance (KEEP)rollup/summaryfinancial dashboard→ Accounts
    ⚠️ PROTECTED: do NOT restructure the bank spine in this audit beyond flagging misplaced rows. It already has a settled architecture (Entities/Contacts/Requests/Line Items).



    SPINE 4 — PRODUCTIVITY / PARA (Planning + PARA)

    Frontend: dashboard, tasks, calendar, notes, life-tracker.

    DBOriginal SystemFrontend Feature/PageConnects To

    |---|---|---|---|

    Tasks (KEEP)Tasks: Name, Status, Priority, Due, Project, Goals, Areas, Contextdashboard, tasks→ Projects, → Goals, → Areas, → Events
    Events (KEEP)Events: Title, Start, End, Type, Location, Project, Areacalendar (cal.html)→ Projects, → Areas
    Projects (KEEP)Projects: Name, Status, Start/End, Priority, Progress, Area, Tasksprojects→ Tasks, → Areas
    Goals (KEEP)Goals (flag: showed journal-like cols — verify)goals page→ Tasks, → Areas
    Daily/Weekly/Monthly/Yearly Plan (KEEP)planners: date-scoped planningplanner views→ Tasks, → Events
    Brain Dump (KEEP)capture inbox (bloated 172 props)notes/inbox→ Tasks (triage into)
    Quick Links (KEEP)bookmarks/linksbookmarks→ (Resources)
    Care Tasks (KEEP)recurring care tasks (from Pets/Plants + Cleaning)tasks/care→ Pets/Plants, → Cleaning
    Areas / Resources / Archive (KEEP)PARA backbone classifiers(PARA structure)← Tasks/Projects/Events relate here



    SPINE 5 — WELLNESS / HEALTH (Wellness)

    Frontend: fitness.html, wellness, health tracking.

    DBOriginal SystemFrontend Feature/PageConnects To

    |---|---|---|---|

    Habits / Habit Completions (KEEP)Habits + completion loghabits/fitness→ each other (parent/log)
    Workout (KEEP)Workout: Session, Type, Duration, Repsfitness→ Wellness dashboard
    Mood Log (KEEP)Mood: Date, Level, Triggerswellness/mood→ Journal?
    Sleep Log (KEEP)Sleep: Duration, Quality, timeswellness/sleep→ Wellness dashboard
    Period Tracker / Symptoms Tracker (KEEP)Periods + Symptomswellness/cycle→ each other
    Hydration Tracker (KEEP)water intakewellness→ Wellness dashboard
    Skincare (KEEP)Skincare routine stepswellness/skincareResults of skincare products, → Beauty Products
    Results of skincare products (KEEP)relation target of Skincareskincare results→ Skincare
    Beauty Products (KEEP)beauty product inventory(products)→ Skincare
    Medications / Energy / Baby Log / Health Trackerhealth sub-systemswellness→ Wellness dashboard



    SPINE 6 — PEOPLE / CONTACTS (Wellness cluster + cross-platform) — PROTECTED

    DBOriginal SystemFrontend Feature/PageConnects To

    |---|---|---|---|

    ❤️Contacts (KEEP)people (customers, agents, staff, family)address-book, CRM, fans→ Person Types, → Address Book, → Customer Requests, → Bookings
    ❤️Person Types (KEEP)classifier for contacts(classifier)← Contacts
    ❤️Address Book (KEEP)addressesaddress-book→ Contacts
    ⚠️ PROTECTED (Contacts spine).



    SPINE 7 — LIFESTYLE MISC (Lifestyle)

    DBOriginal SystemFrontend Feature/PageConnects To

    |---|---|---|---|

    Travel (KEEP)Travel: Trip, Dates, Destination, Bookings, Packing, Taskstravel→ Tasks, → (Airline/Rewards nearby)
    Cleaning (KEEP)Cleaning: Task, Area, Frequency, Last/Next Donecleaning/care→ Care Tasks, → Cleaning Supplies (relate, standalone)
    Pets/Plants (KEEP)Pets/Plants carepets→ Care Tasks
    Outfits (KEEP)Outfits: Items, Date, Occasionwardrobe/closet→ Closet, → Products
    Date Ideas (KEEP)Date: Idea, Location, Costdate ideas(standalone)
    Journal / Journal Entries (KEEP)Journal: Title, Date, Entry, Mediajournal→ Mood?, → Media
    Inspiration Board (KEEP)Card, Image, Tag, Notesvision board→ Goals
    Bucket List (KEEP) / ❤️Bucket ListItem, Category, Target Date, Statusbucket list→ Goals
    ❤️Venues / ❤️Venue Types / ❤️Gift Eventsvenues + giftingevents/gifts→ Events, → Shopping & Gifts



    SPINE 8 — LEARNING / EDU (Learning)

    DBOriginal SystemFrontendConnects To

    |---|---|---|---|

    Courses / Semester / Assignments / Exams / Gradebook (KEEP)school systemlearning→ each other (course spine)
    Notebooks / Notebook Main (KEEP)notes/resourcesnotes→ Courses, → Media/Books



    SPINE 9 — ASSISTANT / ANALYTICS (Assistant)

    DBOriginal SystemFrontendConnects To

    |---|---|---|---|

    Assistant for Wellness / Finance (KEEP)template's AI-assistant helper rows(assistant widgets)→ their subject DBs
    Analyticsanalytics dataanalytics.html→ platform-wide



    SPINE 10 — PRODUCTS / INVENTORY (exists already — same mixed-systems mess)

    Frontend: store-v2.html, products.html, closet/wardrobe, marketplace.html, used-items, vault. The "what I own / sell / stock" web.
    NOTE: do NOT build new here — audit + fold existing DBs. Kitchenware/utensils likely belong HERE (relate to Recipes), not a new DB.

    DBSystemFrontend Feature/PageConnects To

    |---|---|---|---|

    ❤️Inventory Items (KEEP)master inventory of owned itemsinventory / store→ Product Categories/Types/Subcat/Fabrics, → Closet, → Wishlist, → Shopping&Gifts
    ❤️Clothing Inventory (KEEP)wardrobe itemscloset/wardrobe, outfits→ Outfits, → Scenes/Filmography, → Product taxonomy
    ❤️IT Inventory (KEEP)tech/equipment ownedinventory→ Inventory Items
    Beauty Products (KEEP)beauty/cosmetic products ownedwellness/products→ Skincare, → Results of skincare products, → Inventory
    ❤️Product Categories / Types / Subcategories / Fabrics (KEEP)taxonomy classifiers(classifiers)← Inventory/Products relate here
    _plain Inventory (no KEEP — review)_duplicate/merge candidate(resolve: merge into Inventory Items?)
    _(DESIGNATED) Skincare Product Inventory_STANDALONE-RELATE (per rule)wellness→ Skincare (relate, keep standalone)
    _(DESIGNATED) Cleaning Supplies_STANDALONE-RELATE (per rule)cleaning→ Cleaning (relate, keep standalone)
    _utensils cluster (if found in Ingredients)_kitchen toolsproducts/recipes→ Recipes, → Ingredients, → Inventory Items

    Inventory web: Inventory Items = everything owned; Clothing→Closet/Scenes; Beauty→Skincare; Kitchenware→Recipes. All relate to Product taxonomy + Wishlist/Shopping (don't re-buy what you own).




    SPINE 11 — CAREER / PROFESSIONAL (page "Career — Film / Dance") — mostly PROTECTED

    Frontend: filmography.html, bookings.html, companion-services, dance/rate-calc, publicist, performer profile. The professional/business web.

    DBSystemFrontend Feature/PageConnects To

    |---|---|---|---|

    Agent Database Master (KEEP) ⚠️PROTECTEDagents/repsbookings/professional→ Contacts, → Bookings, → Funded Scenes
    Dance Database Master (KEEP) ⚠️PROTECTEDfeature dance gigsdance/bookings→ Contacts, → Venues, → Transactions (deposits)
    ❤️Booking Calendar (KEEP)bookings lifecyclebookings.html, cal→ Contacts, → Venues, → Transactions, → Agent/Dance
    ❤️Funded Scenes (KEEP)scenes funded/producedfilmography, funded-scenes→ Scene Styles/Types/Elements, → Contacts, → Transactions
    ❤️Scene Styles / Types / Elements (KEEP)scene taxonomy(classifiers)← Funded/Directed Scenes
    _(DESIGNATED) Directed Scenes_merge/relate candidatefilmography→ Scene taxonomy
    Professional Dashboard (KEEP)rollup/monitorprofessional dashboard→ all professional DBs
    ❤️Work Statistics / ❤️Co-Workers (KEEP)stats + collaboratorsanalytics/professional→ Contacts, → Scenes
    ⚠️ Agent + Dance masters = PROTECTED (settled spine). Flag-only in audit.





    CAREER HUB (professional/business backend)

    _The "Career (KEEP)" page (under Databases (KEEP)) = 13 subpages, ~355 DBs (179 KEEP). This is the platform's professional core. Each subpage below = a spine._


    SPINE 12 — CAREER: PEOPLE CORE / CRM (48 KEEP) — PARTLY PROTECTED

    Frontend: fans/CRM, customers, community, industry-contacts, address-book, safety. The relationship web.

    DB clusterFrontendConnects To

    |---|---|---|

    ❤️Customer Requests (KEEP) ⚠️PROTECTEDrequest-inbox, custom-requests→ Contacts/Clients, → Transactions, → Products, → Bookings
    ❤️Clients / Customer Profiles / ❤️Co-Workers / ❤️InteractionsCRM, fans→ Customer Requests, → Bookings
    CRM (Freelance/Fundraising/Personal/Recruiting/Startup) / Sales CRM / CRM Contacts TemplateCRM variants→ Contacts (consolidate? FLAG: 6 CRM DBs — one system or many?)
    Community Events/Groups/Posts / Poll Surveycommunity.html→ Members, → Posts
    Blocklist/safety / Blocked Users / safety activity logsafety.html→ Contacts
    Directors / Makeup Artists (+Certs/Specialties) / Photographers / Presenters (+Types/Rates/Specialties) / Talent Database / Staff/Employees / ❤️Studios / Strip Clubs / ❤️Positionsindustry crew/talent→ Bookings, → Scenes, → Contacts
    Testing Records/Providers/Results/Statusesmodel-releases/safety (STI testing)→ Talent, → Scenes
    Affiliate Tracking / Referrals (+Codes/Tracking) / Rewards / Points Rewards / Raffle Prizes / Members / Applicationsreferrals, affiliates, loyalty→ Contacts, → Payments
    Countries / Statesclassifiers← address/location relations
    ⚠️ Customer Requests + Contacts/Clients = PROTECTED. FLAG: 6 CRM template DBs likely consolidate into one CRM system relating to Contacts.

    SPINE 13 — CAREER: COMMERCE / STORE / INVENTORY (7 KEEP, 77 total — MESSIEST)

    Frontend: store-v2, products, marketplace, used-items, orders, closet. Overlaps SPINE 10 (Products/Inventory).

    DB clusterFrontendConnects To

    |---|---|---|

    ❤️For Sale Listings (KEEP) / ❤️Orders Ledger (KEEP) / ❤️Items (KEEP)store-v2, orders→ Inventory, → Customer Requests, → Transactions
    ❤️Inventions (KEEP) / ❤️IT Inventory (KEEP) / ❤️Costume Groups / ❤️Closet lifecycleinventory, closet→ Products taxonomy, → Scenes/Outfits
    _MESS: multiple Inventory, Simply Inventory items/stock, Freezer/Pantry/Fridge/Spices (DELETED), Business Inventory_CONSOLIDATE into ONE Inventory Items + a Kitchen/Pantry Inventory. FLAG.
    _Wishlists - Amazon/legacy/goals/items_wishlists→ SPINE 18 Wishlists (consolidate)
    _Tags/options - shot list/locations/types/fps/chapters_filmography shot-planning→ Scenes (these belong to Film/Dance spine, misplaced in Commerce)
    _Taxonomy - inventory/product statuses, categories, wardrobe seasons_classifiers← Inventory/Products
    This is the #1 cleanup target. Utensils/kitchenware land here → relate to Recipes.

    SPINE 14 — CAREER: FINANCE (34 KEEP) — BANK SPINE PROTECTED

    Frontend: financial, earnings-v2, expenses-v2, payments, payouts, tax-calculator, pricing.

    DB clusterFrontendConnects To

    |---|---|---|

    ❤️Statement Summaries / Bank Years / Bank Institutions / Bank Connections / Payout Records (KEEP) ⚠️PROTECTEDfinancial (bank)→ Transactions Line Items
    ❤️Expense Categories/Tags/Types / Recurring Transactions / Mileage Log / Budget Monthly Overview (KEEP)expenses-v2, budget→ Transactions
    ❤️Payment Channels/Methods/Statuses/Terms/Link Statuses / Currencies (KEEP)payments→ Transactions, → Customer Requests
    ❤️Custom Price Menus / Skype Price Menus / Price Tiers / Subscription Plans / Tier Benefits / Upsell Options / Promo Codes / Counter Offers (KEEP)pricing, service-menu→ Products, → Customer Requests
    ❤️FinDom Tributes / Funded Scenes / Issuance / Platform Fees / Debt Tracker / 52-Week Savings / Tax Reports / Earnings Dashboard Config (KEEP)findom, earnings, tax→ Transactions, → Scenes
    _MESS: Budget Planner/Targets/Tracking, Finances-Budget Tracker, FINANCE, Savings/Savings Tracker, Financial Goals, Untitled_CONSOLIDATE budget dupes. FLAG.
    ⚠️ Bank spine (Statement Summaries/Bank Years/Institutions/Connections/Payout Records) = PROTECTED.

    SPINE 15 — CAREER: SOCIAL MEDIA / CONTENT (26 KEEP)

    Frontend: social, feed, content-calendar, content-gallery, stories, smart-post, social-queue, press-releases.

    DB clusterFrontendConnects To

    |---|---|---|

    ❤️Content Planner / Posting Planner / Campaign planner / Social Media Tasks (KEEP)content-calendar, social-queue→ Social Media Platforms, → Scenes, → Posts
    ❤️Social Media Platforms (KEEP) / Apps / Biossocial, connections→ Content Planner (post destinations = Entities)
    Blog Posts / Landing Pages / Press PR Articles / Brand Assets (KEEP)press, publicist→ Campaigns
    Live Stream Archive / Video Playlists / Video Project (KEEP)cam, video-editor→ Media Library, → Scenes
    Media Types / Media Tags / Document Types (KEEP)classifiers← content
    Email Templates / Status Templates / Statuses / Scheduling/Content Scheduling Types (KEEP)classifiers/comms← content/posting
    Growth insights / Feedback (KEEP)analytics→ Social platforms
    ⚠️ Social Media Platforms should = Entities (per blueprint: OnlyFans etc = ONE Entity). FLAG possible overlap w/ Entities (KEEP).

    SPINE 16 — CAREER: SCHEDULING / BOOKINGS (12 KEEP)

    Frontend: bookings, cal, companion-services, shifts, house-girl, cam, appearances, vip-events.

    DBFrontendConnects To

    |---|---|---|

    Appointments / ❤️Appearances Database / Availability / Blocked Dates / Busy Scheduling Block (KEEP)bookings, cal→ Contacts, → Venues, → Transactions
    Collaborations (KEEP)collabs→ Co-Workers, → Scenes
    Shifts — House Girl (KEEP)house-girl, shifts→ Staff/Employees
    Video Call Sessions (KEEP)cam, video-calls→ Customer Requests
    Podcast Production Schedule / Travel Schedule (KEEP)podcast, travel→ Travel, → Media
    Main Assistant / Professional Dashboard (KEEP)dashboards→ all professional DBs

    SPINE 17 — CAREER: FILM / DANCE (0 KEEP — all DESIGNATED/DELETED)

    Frontend: filmography, scenes, rider, dance, scene-cascade.

    DBStatusConnects To

    |---|---|---|

    (DESIGNATED) Directed Scenesmerge/relate → Funded Scenes→ Scene taxonomy, → Contacts
    _Film/Dance tags, agents, rider reqs, coworkers (DELETED)_merge sources→ Funded Scenes / Agent/Dance Masters
    The live Scene spine = ❤️Funded Scenes + Scene Styles/Types/Elements + Agent/Dance Masters (found earlier). Film/Dance subpage = mostly cleanup residue.

    SPINE 18 — CAREER: WISHLISTS / GIFTS / SHOPPING (11 KEEP)

    Frontend: wishlists, smart-wishlists, wishlist-sync, gifts.

    DBFrontendConnects To

    |---|---|---|

    Wishlist / Wish List Names / ❤️Wish List Names (KEEP)wishlists→ Products/Inventory, → Shopping&Gifts, → Customer Requests
    Gift Planning / Gift Summary / Gifts Overview / Holiday Cards (KEEP)gifts→ Contacts, → Shopping
    Sold By / Manufacturer / Clothing Savings (KEEP)product metadata→ Inventory/Products
    Christmas movies (KEEP)(seasonal media)→ Media Library
    _(DESIGNATED) Christmas Checklist/Holiday Events/Cozy Festivities (staging)_seasonalmerge/relate
    FLAG: two "Wish List Names" (plain + ❤️) — dedupe. Wishlist overlaps Commerce Wishlists-* — consolidate.

    SPINE 19 — CAREER: BUSINESS OPS (26 KEEP)

    Frontend: admin-command-center, analytics, knowledge-base, portfolio, reviews, sponsors.

    DB clusterFrontendConnects To

    |---|---|---|

    ❤️Business Metrics Dashboard / All-Time Statistics / Work Statistics / Analytics Database / Dashboards (KEEP)analytics, command-center→ all spines (rollups)
    ❤️Knowledge Base / FAQ / Topics / Prompts / Functions (KEEP)knowledge-base, support, AI assistant→ Support Tickets
    ❤️Portfolio Database / Art Gallery / Characters / Video Projects (KEEP)portfolio, gallery→ Media, → Scenes
    ❤️Reviews Database / Sponsors / Service Category (KEEP)reviews, sponsors→ Products, → Contacts
    ❤️Support Tickets / Passwords / Webhooks / SEO Settings / Sitemap / Departments / Backlog Categories+Goals (KEEP)admin/platform ops→ platform config

    SPINE 20 — CAREER: PLATFORM CONFIG (13 KEEP)

    Frontend: settings, templates, custom-domains, notifications, file manager.

    DBFrontendConnects To

    |---|---|---|

    ❤️Categories (KEEP AS MAIN) / Tags / Appearance Types / Frequencies / Responsibilities / Visibility Options (KEEP)classifiers (platform-wide)← used by many DBs
    ❤️Templates / Custom Domains / Notification Center / File Manager / Home / OKRs / Accomplishments (KEEP)settings, templates, files→ platform
    ⚠️ Categories (KEEP AS MAIN) = the master Categories classifier (blueprint: shared across invoices/collaborations/transactions). Central.

    SPINE 21 — CAREER: LEGAL / PROGRESS / CRM-misc

    DBFrontendConnects To

    |---|---|---|

    Contracts (KEEP)legal, contracts→ Bookings, → Dance, → model-releases
    ❤️Progress Tracker Dashboard (KEEP)progress→ Goals, → Projects
    Payroll / Work Statistics (CRM subpage)payroll/analytics→ Staff/Employees



    CROSS-SPINE CONNECTIONS (the "everything connects" web)

  • Kitchenware/Products ↔ Recipes ↔ Ingredients ↔ Inventory ↔ Groceries (kitchen web)
  • Media Library ↔ Posts ↔ Feed/Discover (content-interest web)
  • Contacts ↔ Customer Requests ↔ Transactions ↔ Bookings (business web) [PROTECTED]
  • Closet/Outfits/Products ↔ Scenes/Filmography ↔ Wishlist ↔ Shopping&Gifts (wardrobe web)
  • Care Tasks ↔ Cleaning ↔ Pets/Plants (home-care web)
  • Tasks/Projects/Areas ↔ everything (PARA overlay — any row can relate to a Project/Area)



  • PROPOSED NEW DBs / RESOLUTIONS (revised — most "new" already exist)

  • Kitchenware new DBUSE EXISTING Products/Inventory (Inventory Items). Utensils cluster relates to Recipes. Do NOT build new.
  • (verify) Kitchen Inventory / Pantry — "what's in stock" for recipe-flow; a (DELETED) Pantry Inventory + Freezer/Fridge/Spices exist as merge sources. Decide: one "Kitchen/Pantry Inventory" (rebuild from merged sources) OR use Ingredients-with-stock. FLAG for Jillian.
  • (verify) Posts/Posting DB — confirm posting DB (feed/social) exists in Notion backend or is platform-only; Media Library must relate to it.
  • _(More surfaced as the row-audit runs. Prefer RELATE-to-existing over build-new, since the Products/Inventory + Career ecosystems already exist.)_




    AUDIT ORDER (recommended — FULL, 21 spines)

    Life-OS side (personal):

  • Media (proves method; frontend-connection example).
  • Kitchen (recipe-flow flagship; crosses into Commerce/Inventory for utensils).
  • Lifestyle misc, Wellness, Learning, Productivity/PARA.

  • Career hub (professional — the bigger job):

  • Commerce/Inventory (SPINE 13+10) — MESSIEST, top cleanup priority; resolve inventory duplicates, consolidate, relate to Kitchen/Wardrobe/Store frontend.
  • Social Media/Content (15) — map to feed/content-calendar; resolve Platforms vs Entities overlap.
  • Wishlists/Gifts (18) — dedupe wishlists, consolidate with Commerce wishlists.
  • Scheduling/Bookings (16), Business Ops (19), Platform Config (20), Legal/Progress (21).
  • Film/Dance (17) — mostly cleanup residue → fold into live Scene spine.

  • PROTECTED (flag-only, minimal touch):

  • People Core/CRM (12) — Customer Requests + Contacts protected; but 6 CRM template DBs need consolidation decision.
  • Career Finance (14) + Bank spine + Life-OS Finance/Contacts = PROTECTED.

  • TOTAL: 21 SPINES

    Life-OS (1-11): Kitchen, Media, Bank(P), Productivity, Wellness, Contacts(P), Lifestyle, Learning, Assistant, Products/Inventory, [Career overview].

    Career hub (12-21): People/CRM(P), Commerce/Inventory, Career-Finance(P), Social/Content, Scheduling/Bookings, Film/Dance, Wishlists/Gifts, Business Ops, Platform Config, Legal/Progress.


    KEY FLAGS SURFACED (need Jillian decisions during audit)

  • 6 CRM template DBs (Freelance/Fundraising/Personal/Recruiting/Startup/Sales + Contacts Template): one consolidated CRM relating to Contacts, or keep separate?
  • Inventory duplicates (multiple Inventory, Simply Inventory, Freezer/Pantry/Fridge/Spices): consolidate into ONE Inventory + ONE Kitchen/Pantry Inventory?
  • Budget duplicates (Budget Planner/Targets/Tracking, Finances-Budget, FINANCE, Savings x2, Financial Goals): consolidate?
  • Social Media Platforms vs Entities (KEEP): overlap — platforms should be Entities per blueprint. Merge/relate?
  • Two "Wish List Names" (plain + ❤️): dedupe.
  • Shot-list tags in Commerce: belong to Film/Dance spine (misplaced) → move.
  • Christmas movies in Wishlists → relate to Media Library.