Persisted Prisma models, approved planned entities, and the relationships that cross context boundaries
Guided views
Explore this system
Step through curated paths without changing the source diagram.
Beat
Next
ReadyChapter 01 / 01
Guided chapter
Diagram guideExplore this system
Inspecting compiled semantics
E ExportT ThemeS Style0 Reset+ Zoom in- Zoom outEsc Close
Find a node
⌕/
No matching nodes
Semantic passport
Verified source
Authored reach
Route probeChoose a start node
Pick two semantic nodes on the diagram
Choose the source, then the destination. Direction matters.
Semantic lensCompare system roles
Choose up to two semantic kinds. One reveals its real traffic; two compare only direct authored relationships.
Choose a kind to inspect its nodes and touching relationships.
Semantic radar
Building overview
Click nodeDrag to pan
Status language
• Schema tags identify persisted Prisma ownership
• Planned means approved direction without a current model
• Conceptual means domain language, not implementation
Current alignment debt
• VipProfile, VITProfile, Assignment, and snapshots currently live in identity
• The business context remains authoritative even when the physical schema lags
Boundary safeguards
• Integrations normalizes provider facts before Delivery
• Clinical details do not leak into general operational entities
• Stable ids cross boundaries; private storage details do not
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