Hearth: Multi-Member Foundation

Timeline

1. 1

   Start

   Architecture design

   Designed and iterated household-first multi-member model with Zeb + chat review

2. 2

   1h

   Schema written

   householdMembers, profiles, spaces, calendarSources + expanded routeItems

3. 3

   1.5h

   Access helpers built

   lib/access.ts — requireHouseholdMember, visibility queries, mutation guard

4. 4

   2h

   Schema pushed + backfill verified

   db:push clean, backfill confirmed 1 member / 6 profiles / 8 spaces

What shipped

• householdMembers table — authenticated users in a household, UNIQUE(householdId, userId)

• profiles table — household subjects (adult, child, pet, house, vehicle), optional member link

• spaces table — shared/personal/profile rooms with partial uniqueness constraints

• calendarSources table — replaces calendarSyncSettings, UNIQUE(householdId, externalCalendarId)

• routeItems expanded — spaceId, visibility, source, createdByMemberId, subjectProfileId, assignedToMemberId, sourceExternalId, calendar dedup index

• lib/access.ts — requireHouseholdMember, getCurrentMember, getSharedHearthItems, getMemberPersonalItems, getProfileItems, validateItemVisibility

• lib/db/backfill-members-spaces.ts — idempotent backfill for existing households

• docs/hearth-architecture.md — full architecture reference

• forgehome/IMPLEMENTATION_PLAN.md — phased build checklist

• Schema pushed to Neon DB — verified clean

• Backfill run — Zeb as owner member, 6 profiles, 8 spaces, all route items in Shared Hearth