Family Shapes
I began Family Shapes to explore family and donor relationships. This historical record preserves that earlier product and its screenshots; Aerial is now the current home for the work.
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.
Aerial: connected product proof and marketing continuity — September 2026
The project originally cataloged here as Family Shapes continued as Aerial; the source repository records the canonical Aerial infrastructure naming in August. September work connected product messaging to one synthetic family, donor and institutional story rather than three unrelated portal tours. The September 5 fixture expanded to 240 donor profiles and 600 recipient households, with three demonstration logins and explicit sharing boundaries. These fictional counts demonstrate the product and are not customer traction.
The video work evolved through versioned drafts and evidence packets. Project 0086’s September 8 handoff preserves V12 (2:00.69, 22 shots) as the latest technically delivered draft, with video production paused and final editorial acceptance still pending. Later role-specific scenarios distinguish recorded families from permitted visible subsets; older fixture totals remain a dated snapshot.
Marketing work first produced a September 8 preview, then recovered approved positioning and audience differences from earlier conversations into canonical documentation. The already-linked Aerial positioning chat preserves the September 8–10 context recovery. Its resumed September 12–13 source checkpoints report PR183 and PR184 merged, including Contact and Resources refinements and modal video playback. Those later checkpoints extend the historical record; this intake does not independently certify current production behavior or rename the canonical project route. The useful method is to retain actual baselines, selected design references, reusable assets and clear local/preview/merged/live boundaries.
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
27 artifacts grouped by type so each kind of proof can be scanned on its own.
Data models
7 artifactsCommunity Content And Media Model
Donor Boundary and Health Model
Donor Profile And Connection Model
Organization and Oversight Model
Organization Membership And Oversight Model
Relationship Graph And Access Model
Relationship Graph Core
Workflows
5 artifactsBuild one connected product demo across three roles
Clinic / Cryobank Operational Oversight
Donor Control and Health Update Workflow
Family Discovery and Connection Journey
Recover approved positioning before revising a product site
Images
7 artifacts
imageClinic or cryobank surface for professional donor oversight.
imageCommunity surface for stories, forums, and resources.
imageDonor surface focused on privacy, transparency, and control.
imagePublic home or umbrella entry point for the overall Family Shapes product.
imageSigned-in clinic or organization dashboard (`Rainbow Family Clinic`) showing organization metrics and operational overview.
imageSigned-in donor dashboard showing donor profile completeness, privacy level, and health-update status.
imageSigned-in family dashboard showing family-tree stats, privacy settings, and linked organizations.
Chats
1 artifactNotes
7 artifactsFamily Shapes Product Surfaces
Project Master Plan
"Product brief: Family Shapes"
Donor Portal
Security/Sharing/Permissions/Privacy Audit (P1.1)
1018 – SaaS Portal Platform
Aerial synthetic three-portal fixture — September 5 snapshot
Connected references
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.