TFD Bounded Context Map

Business ownership, public contracts, in-process events, projections, and planned boundaries

TFD Bounded Context Map Business ownership, public contracts, in-process events, projections, and planned boundaries Identity / Staff Access · StaffUser · roles · permissions · RBAC · Architecture component · Implemented Identity / Staff Access StaffUser · roles · permissions · RBAC Implemented Realtime Transport · Authorized projections after persistence · Architecture component · Not a domain context Realtime Transport Authorized projections after persistence Not a domain context Sales · Consultations · findings · evidence · Architecture component · Implemented Sales Consultations · findings · evidence Implemented VIP / CRM · VIP profile · onboarding · customer identity · Architecture component · Partial in Identity VIP / CRM VIP profile · onboarding · customer identity Partial in Identity Delivery · Programs · sessions · attendance · analysis · Architecture component · Implemented Delivery Programs · sessions · attendance · analysis Implemented Engagement · Snapshots · status · follow-ups · Architecture component · Implemented Engagement Snapshots · status · follow-ups Implemented Notifications · Durable outbound notification state · Architecture component · Implemented Notifications Durable outbound notification state Implemented Integrations · Provider inboxes · meeting linking · Architecture component · Implemented Integrations Provider inboxes · meeting linking Implemented Clinical · Sensitive notes · bounded summaries · Architecture component · Planned boundary Clinical Sensitive notes · bounded summaries Planned boundary consultation facts VIP + VIT references participation recorded follow-up facts staff actor + RBAC meeting linked · media stored session projections recorder projections delivery facts required signals only Legend Security Message bus Backend External

Synchronous communication

  • • Business modules consume another context only through its explicit public contract
  • • Composition roots may wire modules; internals remain private

Event communication

  • • MVP events are past-tense facts dispatched in process
  • • Owning modules persist durable state before events or realtime publication

Current alignment risks

  • • VIP/CRM and VIT operations still live partially inside the Identity source module
  • • Dashed relationships are planned or policy-level boundaries, not guaranteed runtime calls

Sensitive boundaries

  • • Clinical content stays isolated and exposes only required operational summaries
  • • Realtime transports authorized projections and never becomes a source of truth