TFD Domain Entity Relationships Diagram

How to read this map

• Solid paths are current durable relationships or approved processing paths
• VIP experience ownership is read and changed only through the active Assignment; workload and package totals join those assignments to active VipProfiles
• Dashed paths are projections, future identity, or conceptual boundaries
• The original sample JSON was replaced by current schema-backed entity summaries
• SalesMembershipCapture has many SalesMembershipSilver rows and one SalesMembershipGold row. The unique day/revision selects an auditable observation; capture/VIP is unique. Silver technical VIP and subscription references are evidence, not cross-context database relations; source fields arrive through Identity and Engagement public contracts.
• Assets library shares private media across Program Assets and Studio; routines and VIT/VIP documents stay on ProgramAsset

Delivery flow

• ProgramAsset references shared media by tfd-media:library:id; saved programs retain their own versioned definitions
• A run generates SessionOccurrences and owns VIP, time-slot-specific Session Analysis VIT rosters, and an AddPipe level-code whitelist
• Only stored AddPipe videos whose normalized session code is whitelisted by the run enter its first future occurrence; every recording remains in the Integrations catalog
• Every Program Run VIP is eligible before live attendance finalizes; evidence records on-demand-only, missed-live, or run-assignment reasons
• Automatic and occurrence-scoped manual links persist OnDemandAttendance atomically; grouped invalid uploads leave the pending queue together
• Before analysis exists, live attendance may move or be invalidated with durable staff evidence
• Staff explicitly create Session Analysis from saved attendance; automatic distribution uses only active VITs configured for the occurrence start time

Engagement and Clinical

• Engagement derives session-granular report facts after Delivery persists attendance
• The Engagement projection preserves occurrence, day, status, participation mode, and assigned VIT dimensions for report drill-downs
• Notifications keeps per-staff inbox, event preferences, and outbound delivery separate
• Effective subscriptions gate future inbox materialization without changing source facts
• Clinical remains a planned isolated context and does not own general VIP operations

Audit P0 and P1 coverage

• Identity, Clinical, Sales, Delivery and Integrations retain their state; Audit receives bounded facts through the synchronous public contract
• Staff/RBAC, Clinical and attendance/evidence changes commit with Audit. Private media and sensitive VIP concessions await durable evidence before disclosure
• Integrations owns MediaDeletionJob: committed intent blocks playback, leased bounded retries remove private objects, completion and Audit commit together; terminal failure has an authorized repair path
• Audit HTTP queries use explicit independent read, restricted-metadata and export grants, server organization scope and validated unsigned pagination; every page reapplies authorization and query limits. No Audit secret is required. Retention is held without automatic purge or receipt expiry
• P1 adds manual VIP changes, VIT assignment decisions, Program Run creation, manual attendance and named soft archives; existing video decisions retain one P0 fact and owner histories remain independent

Architecture diagram • Built with Archify • Create yours ↗ • Hover to trace • R route • Click to focus • +/− zoom • M radar • [/] views • P play story • T theme • E export