Release 4 · Queued
DB Refactor
Foundational schema changes for the timeline model, linked pins, and grouped pins. No UI — purely gates Check-ins and Grouped Pins.
Summary
Schema migration to support the timeline model, linked pins, and network-aware grouping. Foundational infrastructure — no user-visible UI changes until later releases consume it. Gates Check-ins & Tags (R7a) and Grouped Pins (R7b).
What's in scope
pin_visitstable — timeline entries for revisits (Scenario C — owner revisits own pin, adds visit entry instead of creating a new pin)linked_pin_id+link_typecolumns onpins— track relationships between pins (independent_visit, tagged_copy, same_place)- Updated RLS policies for the new tables
- Updated
get_user_map_pins()RPC to support clustering with the new data model - Existing data migration + validation (backwards-compatible with live app v1.11.1)
Process
- All migrations run on staging first
- Tag Brad for review — migrations are the highest-consequence deploys
- Every migration has a rollback path
- Backwards-compatibility with the live app version is non-negotiable
Open questions
- Bundle with Pro (R5)? Historically listed as a bundle candidate since both are infrastructure. Newer thinking: Pro v0 doesn't actually depend on DB Refactor, so they can unbundle. R4 stays on the critical path for R7a.
- Data backfill strategy — for existing pins, retroactively create
pin_visitsentries, or start fresh from migration date?