Creator directory + profile

The root entity of the whole CRM — the creator record every other domain hangs off. Directory, profile, tags, social links, team assignment.

What it is and how it feeds the rest

Mechanically

The root entity of the whole CRM — the creator record every other domain hangs off. Directory, profile, tags, social links, team assignment.

How it connects

Everything. creators:add triggers Drive provisioning; invoicing, referrals, secure logins and content all key off creator identity.

Worth knowing

Added as #18 after exploration found the app's root entity was unnamed by the original 17-domain sweep. Highest raw-LOC-per-unit-of-research in the repo.

Components

src/components/creators/
src/components/creators-data/
src/components/profile/

Convex modules

creators.ts
creatorData.ts

Tables

creators
creatorTags
creatorSocialLinks
creatorTeamMembers
creatorTelegramGroups

The decision — what we do here

KEEP+FIX+ADD — the root entity, keep it. FIX invite-token expiry + hardcoded temp password. ADD the trust-passport later.

Repos we analyzed for this domain

STUDY marmelab/atomic-crm

React/shadcn CRM relationship-UI patterns (his exact stack).

STUDY pdovhomilja/nextcrm-app

React/shadcn CRM patterns.

WRAP twentyhq/twenty

Relationship timelines/custom objects as a wrapped CRM substrate — AGPL, run as service.

LIFT = copy the code into the fork · WRAP = run underneath as a service · STUDY = architecture only. Verdicts from the OFM sourcing campaign.

Open questions

Research priority for this domain is highest. Agent findings splice in below this line and survive regeneration.