Product domains

Domain dependency map

Dealflow domains are centered around tenant-owned portfolios and deals.

Identity / tenancy / auth

Cognito identities are resolved into app users, tenant memberships, roles, teams, and platform access before any protected API route runs.

Tables: users, platform_users, tenants, tenant_users, roles, permissions, teams, auth_group_mappings, audit_logs

APIs: /api/me, /api/* via requireAuth

Gotchas: Membership sync happens during API auth. Platform and tenant powers are separate concepts.

Portfolios / workspaces

Workspace portfolios are the operating context for deals, config, maps, documents, CRM views, and analysis.

Tables: portfolios, resource_shares

APIs: /api/portfolios, /api/portfolios/:portfolioId/*

Gotchas: Deal access also depends on parent portfolio access. UI says workspace; schema still says tenant/portfolio.

Pipeline configuration

Portfolio-scoped pipelines, stages, deal types, and metadata shape deal workflows without hard-coded global enums.

Tables: pipelines, pipeline_stages, deal_types, metadata_fields, metadata_field_options

APIs: /api/portfolios/:portfolioId/config

Gotchas: Do not model client taxonomies as global enums.

Deals

Deals are the central business object: they sit inside a workspace, carry workflow state, link to properties, documents, CRM, tasks, maps, and analysis.

Tables: deals, deal_stage_history, deal_properties, resource_shares

APIs: /api/portfolios/:portfolioId/deals

Gotchas: Deal detail is highly coupled because it hosts many domain panels.

Properties

Reusable tenant property/location records can be linked to deals or grouped in property lists.

Tables: addresses, properties, deal_properties, property_lists, property_list_items

APIs: /api/properties, /api/property-lists, /api/geocoding

Gotchas: Latitude/longitude exist on both address and property for query convenience.

Documents / extraction

Documents have versions, generic links to resources, and queued extraction jobs that can be reviewed and applied.

Tables: documents, document_versions, document_links, document_extractions

APIs: /api/documents

Gotchas: The flow crosses UI, storage, DB rows, AI provider, worker, and deal/property updates.

CRM

Tenant CRM companies and contacts are reusable and can be linked to deals with roles such as sponsor, broker, lender, or counsel.

Tables: crm_companies, crm_contacts, deal_companies, deal_contacts

APIs: /api/crm, /api/portfolios/:portfolioId/crm

Gotchas: Global CRM and portfolio CRM share domain logic but have different views.

Tasks / comments / activity

Execution work and timeline events are deal-centered today and form the future notifications/inbox backbone.

Tables: tasks, comments, activity_events

APIs: /api/portfolios/:portfolioId/deals/:dealId/tasks, /comments, /activity

Gotchas: There is not yet a full realtime notification system.

Maps / explore / analysis

Maps combine app-owned deals/properties with read-only public geospatial/demographic/POI datasets for portfolio maps, deal analysis, and broad market exploration.

Tables: deals, properties, addresses, public.poi_chain_locations, public.poi_shopping_center, public.sti_block_group_*

APIs: /api/portfolios/:portfolioId/maps, /api/portfolios/:portfolioId/analysis, /api/explore/*

Gotchas: This area is performance-sensitive and SQL-heavy.

Comps

Comps are persisted Dealflow-owned market evidence records, with manual entry, source snapshots, private/workspace visibility, lists, and deal selections.

Tables: comps, comp_lists, comp_list_items, deal_comp_selections

APIs: /api/comps, /api/portfolios/:portfolioId/comps

Gotchas: Source search is runtime SQL against public tables; validate column names when adding new adapters. Portfolio-scoped comp views are narrower than the global comp library.

Sharing / permissions

Resource sharing overlays owner/visibility with explicit grants to users, roles, teams, or tenant-wide principals.

Tables: resource_shares, portfolios, deals, tenant_users, roles, teams

APIs: /api/portfolios, /api/portfolios/:portfolioId/deals

Gotchas: Parent portfolio visibility constrains deal visibility.

Interactive graph

Domain relationships

Identity and sharing guard every domain. Deals are the central joining point for property, documents, CRM, work, maps, and analysis.

Click a domain node to inspect files, tables, and pitfalls.

Use the right-side domain cards for edit guidance.

Deals and documents are the broadest/coupled surfaces.

Domain

Identity / tenancy / auth

9 tables2 APIs

Domain

Portfolios / workspaces

2 tables2 APIs

Domain

Pipeline configuration

5 tables1 APIs

Domain

Deals

4 tables1 APIs

Domain

Properties

5 tables3 APIs

Domain

Documents / extraction

4 tables1 APIs

Domain

CRM

4 tables2 APIs

Domain

Tasks / comments / activity

3 tables3 APIs

Domain

Maps / explore / analysis

6 tables3 APIs

Domain

Comps

4 tables2 APIs

Domain

Sharing / permissions

6 tables2 APIs

React Flow

Click nodes for files, rules, and relationship details.

No node selected