Mechanically
Staff records, team assignment (A/B/C Team), and member onboarding. Activity tracking is stubbed — 'coming soon' at TeamMemberProfile.tsx:274.
Real, partial
Domain 11 · people · ~4,300 LOC
Team / employees
Staff records, team assignment (A/B/C Team), and member onboarding. Activity tracking is stubbed — 'coming soon' at TeamMemberProfile.tsx:274.
What it is and how it feeds the rest
How it connects
Supplies the staff identities that payroll, RBAC and gamification all key off.
Pages
src/pages/Team.tsxsrc/pages/TeamMemberProfile.tsxsrc/pages/TeamMemberEdit.tsxsrc/pages/TeamMemberOnboarding.tsx
Components
src/components/team/src/components/employees/
Convex modules
teamMembers.ts
Tables
teamsteamAssignmentsteamMemberRoles
Findings that touch this domain
medium No per-chatter revenue attribution — staff are paid but cannot be ranked
market gap, lane 07
The decision — what we do here
KEEP+BUILD — team model fine; the BUILD is per-chatter revenue attribution (no clean donor; real work).
Repos we analyzed for this domain
STUDY marmelab/atomic-crm
React/shadcn CRM relationship-UI patterns (his exact stack).
WRAP block/buzz
Collaboration/agent plane (Camron chose it). Team coordination + fan-adjacent, NOT money.
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 high. Agent findings splice in below this line and survive regeneration.