Project

    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.

    DARHistorical

    Narrative

    01

    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.

    02

    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.

    03

    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

    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 artifacts
    data modelWork date: Date unknown

    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.

    10 entities1 diagram
    data modelWork date: Date unknown

    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.

    5 entities1 diagram
    data modelWork date: Date unknown

    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.

    7 entities1 diagram
    data modelWork date: Date unknown

    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.

    6 entities1 diagram
    data modelWork date: Date unknown

    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.

    8 entities1 diagram
    data modelWork date: Date unknown

    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.

    8 entities1 diagram
    data modelWork date: Date unknown

    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.

    6 entities1 diagram

    Workflows

    5 artifacts
    workflowWork date: Date unknown

    Build one connected product demo across three roles

    The September 5–8 Aerial demo followed the same fictional family, donor and institution through working product states. A synthetic roster supplied realistic scale while role-specific sharing and visible-versus-recorded counts kept the story truthful. Production evolved through versioned films, narration, transcripts, contact sheets and playback checks. Project 0086 identifies V12 as the latest technically delivered draft and explicitly pauses further video work pending user direction and editorial acceptance.

    7 steps1 record
    workflowWork date: Date unknown

    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.

    7 steps1 record
    workflowWork date: Date unknown

    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.

    7 steps1 record
    workflowWork date: Date unknown

    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.

    8 steps1 record
    workflowWork date: Date unknown

    Recover approved positioning before revising a product site

    Aerial’s September 8–13 work exposed a continuity gap: approved product and institutional positioning was present in demo materials but absent from the documents guiding marketing. The recovery combined conversation decisions, canonical docs, product evidence and the actual live baseline, then preserved audience-specific messaging and the Connected Atlas direction through HTML, Figma and browser review. The September 8 marketing draft remained a preview; later source checkpoints report PRs 183 and 184 merged. These are dated source claims, not a fresh production audit.

    6 steps1 record

    Images

    7 artifacts

    Chats

    1 artifact

    Notes

    7 artifacts

    Connected references

    Key dates

    2024-12-15
    Project initialization

    Initial repo setup established Family Shapes as an active product build rather than a concept stub.

    2025-03-20
    Graph and privacy-aware foundation

    Family-tree visualization, people, connections, Supabase, and RLS gave the project its core relationship-graph shape.

    2025-08-06
    Multi-surface platform baseline

    Interactive tree builder, organization maturity, donor portal, onboarding, and end-to-end testing made the product feel like a real ecosystem platform.

    2025-10-02
    Permissions system refactor

    The collaborator and invitation model became a first-class concern, showing how central privacy and access control are to the product.

    2025-10-03
    Platform separation and hardening

    The roadmap and changelog show explicit movement toward clearer family, donor, and SaaS boundaries plus continued RLS hardening.