Family Shapes
Family Shapes is a multi-surface relationship platform for donor-conceived family ecosystems, spanning family, donor, clinic, and community experiences.
Table of contents
Narrative
Why it matters
Family Shapes tackles a messy and emotionally sensitive problem space: donor-conceived family ecosystems. The product is trying to hold together relationship discovery, privacy and consent, donor health stewardship, communication boundaries, and institutional workflows for clinics or cryobanks in one connected system. The live Supabase schema confirms that this is not just a landing-page story: the repo has real relationship, donor, organization, community, and media structures behind it.
What the product is
Family Shapes is a multi-surface relationship platform, not a single-purpose family-tree app. It spans family-facing tools, a dedicated donor experience, a clinic or cryobank SaaS layer, and a broader community surface for stories, forums, and resources. The linked Supabase schema shows those layers connect through family trees, donor profiles, organizations, memberships, invitations, forums, posts, and media tables rather than existing as disconnected marketing ideas.
System surfaces
Recipient or family platform
Family-facing onboarding, dashboards, family trees, people, and donor-relative connection management under privacy constraints.
Donor platform
A distinct donor experience for profile management, privacy controls, health updates, and communication settings.
Clinic or cryobank SaaS platform
Professional onboarding, organization dashboards, member management, and operational oversight for institutions.
Community layer
Stories, forums, resources, and broader community support around donor-conceived family experiences.
Implementation stack
Frontend
- • React 18
- • TypeScript
- • Vite
- • Tailwind CSS
- • Radix / shadcn-style UI primitives
Backend and data
- • Supabase Auth
- • Postgres
- • Edge Functions
- • Row-level security
- • Migration-first schema workflow
- • Linked remote type generation
Visualization
- • XYFlow / React Flow
- • Dagre
- • ELK
- • D3
Quality and operations
- • Playwright end-to-end coverage
- • Docs-first project governance
- • Permissions and privacy hardening
Evidence trail
Community Content And Media Model
The linked schema confirms that Family Shapes includes a real content and community system. Forums branch into threads and posts, blog posts branch into comments, resources stand on their own, and media albums link to media files through join rows.
Donor Boundary and Health Model
The donor surface is backed by a distinct donor profile model that connects privacy settings, health updates, and donor-recipient relationship state instead of treating donor controls as simple account preferences.
Donor Profile And Connection Model
The donor layer is real in the schema, not just the UI. `donor_profiles` stores donor-specific identity, privacy, and health fields, while `donor_recipient_connections` tracks the relationship state between donor profiles, organizations, and recipient-side users.
Organization and Oversight Model
The clinic and cryobank layer depends on organizations as the tenant and oversight anchor, tying professional users to shared operational views, people records, and family relationship context.
Organization Membership And Oversight Model
The remote schema makes the institutional layer much clearer: organizations connect to memberships, invitations, user profiles, groups, family trees, persons, and donor-recipient operations. That is a stronger SaaS and coordination story than the earlier editorial model captured.
Relationship Graph And Access Model
The linked Supabase schema shows Family Shapes as a graph product with explicit access control. Family trees can belong to groups or organizations, persons join trees through membership rows, connections link people, and collaborator plus invitation tables govern who can work inside a sensitive tree.
Relationship Graph Core
Family Shapes centers the product on family trees, people, and connections, then layers collaboration and invitations on top so sensitive relationship graphs can be explored and maintained safely.
Clinic / Cryobank Operational Oversight
How professional operators enter the clinic-facing surface, onboard an organization context, and use the dashboard for member management and donor-program oversight.
Donor Control and Health Update Workflow
How donors use Family Shapes to manage profile completeness, privacy choices, health history, and communication settings through a dedicated donor experience.
Family Discovery and Connection Journey
How recipient families move from discovery and onboarding into privacy-aware family-tree exploration, connection review, and relationship follow-up.
Gemini Donor Gamete Industry Research for Family Shapes
Gemini AI Mode thread researching cryobank workflows, donor-profile verification gaps, cross-bank registry blind spots, and technical requirements for a Family Shapes transparency and privacy platform.
Family Shapes Product Surfaces
A linked breakdown of the family, donor, clinic or cryobank, and community surfaces that make Family Shapes a multi-surface platform.
Project Master Plan
Product vision, scope, and system map for Family Shapes
"Product brief: Family Shapes"
One-page product summary covering users, problem, MVP scope, and success metrics
Donor Portal
Comprehensive documentation of the Donor Portal feature
Security/Sharing/Permissions/Privacy Audit (P1.1)
Inventory and rationalization across frontend and backend
1018 – SaaS Portal Platform
Plan and implement a multi-tenant SaaS portal for cryobanks and clinics with RBAC, billing, analytics, and professional workflows, separate from the Family and Donor apps
Connected references
Visual evidence
Key dates
Initial repo setup established Family Shapes as an active product build rather than a concept stub.
Family-tree visualization, people, connections, Supabase, and RLS gave the project its core relationship-graph shape.
Interactive tree builder, organization maturity, donor portal, onboarding, and end-to-end testing made the product feel like a real ecosystem platform.
The collaborator and invitation model became a first-class concern, showing how central privacy and access control are to the product.
The roadmap and changelog show explicit movement toward clearer family, donor, and SaaS boundaries plus continued RLS hardening.