Schemas and relationships

Data Models

Object shapes, relationship maps, and system boundaries that need a diagram-first artifact instead of a prose note.

15 published models

Catalog Generation Model

Prompt input, defaults, generated assets, products, releases, and background jobs form the repeatable generation loop for RPS Digital.

RPS Digital P3 Intake Archive

Secure Fulfillment Model

Orders, entitlements, releases, and signed download URLs create a traceable chain from purchase to delivery.

Shopify Headless Storefront

Agentic API Gate Model

External agent access is intentionally constrained by feature flags, catalog mode, checkout mode, allowed origins, path validation, Shopify token selection, and structured error contracts.

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.

Shopify Headless Storefront

Cutover And Catalog Evidence Model

The proof system separates source docs, generated run manifests, summaries, compare CSVs, review-board manifests, media upload reports, product-media ledger outputs, and human approval checkpoints.

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.

One-prompt intake artifact flow

The hardened process shows how a simple prompt with local paths becomes a dossier, packets, dry-run reports, local database records, and public review surfaces.

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.

Plugin Backup Model

Custom local plugin bundles stay in `plugins/` with plugin metadata and registry records so larger workflow surfaces are preserved without pretending they are ordinary standalone skills.

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.

Skill Suite Catalog Model

The source suite maps portable skill folders through an allowlist and lifecycle metadata into generated Markdown, JSON, and TypeScript catalog surfaces.

Shopify Headless Storefront

Storefront Commerce Model

The public app maps Shopify products, variants, collections, menus, blogs, articles, cart lines, checkout URLs, reviews, feeds, and customer-account state into customer-facing routes and machine-readable endpoints.

6entities

1proof