Marketplace Relationships¶
Why This Exists¶
This document explains how Marketplace relates to Supplier, Funding, Organization, Intelligence, Contract, Notification, and Analytics.
Owner¶
The owner is the Chief Product Officer and Enterprise Architect.
Business Value¶
Clear relationships allow marketplace discovery and request workflows to use provider and customer context without taking ownership of facts from other domains.
Relationship Diagram¶
flowchart TD
Organization[Organization]
Marketplace[Marketplace]
Supplier[Supplier]
Funding[Funding]
Contract[Contract]
Intelligence[Intelligence]
Notification[Notification]
Analytics[Analytics]
Organization --> Marketplace
Supplier --> Marketplace
Funding --> Marketplace
Contract --> Marketplace
Intelligence --> Marketplace
Marketplace --> Supplier
Marketplace --> Funding
Marketplace --> Notification
Marketplace --> Analytics
Relationship Map¶
| Domain | Relationship | Ownership boundary |
|---|---|---|
| Organization | Supplies customer profile, preferences, and procurement need context. | Organization owns business profile. |
| Supplier | Supplies supplier trust, performance, rating, response, and relationship signals. | Supplier owns supplier state. |
| Funding | Supplies funding partner display context. | Funding owns funding products, applications, assessments. |
| Contract | Requests provider support for delivery. | Contract owns contract state. |
| Intelligence | Recommends providers and explains matches. | Intelligence owns reasoning sessions. |
| Notification | Sends marketplace request and response alerts. | Notification owns delivery records. |
| Analytics | Consumes marketplace events. | Analytics owns projections. |
Ownership Rule¶
Marketplace owns listing and workflow state. It references provider and customer facts from owning domains.