Opportunity Relationships

Why This Exists

This document explains how Opportunity relates to Organization, Compliance, Intelligence, Proposal, Notification, and Analytics.

Owner

The owner is the Chief Product Officer and Enterprise Architect.

Business Value

Clear relationships allow Algosure to match tenders accurately while preserving domain ownership boundaries.

Relationship Diagram

flowchart TD
    Sources[Tender Sources]
    Opportunity[Opportunity]
    Organization[Organization]
    Compliance[Compliance]
    Intelligence[Intelligence]
    Proposal[Proposal or Bid]
    Notification[Notification]
    Analytics[Analytics]

    Sources --> Opportunity
    Organization --> Opportunity
    Compliance --> Opportunity
    Intelligence --> Opportunity
    Opportunity --> Proposal
    Opportunity --> Notification
    Opportunity --> Analytics

Relationship Map

Domain	Relationship	Ownership boundary
Organization	Supplies profile, services, products, capabilities, regions, and procurement preferences.	Organization owns customer business context.
Compliance	Supplies readiness, risk, and compliance status.	Compliance owns readiness and compliance state.
Intelligence	Analyses opportunities and suggests recommendations.	Intelligence owns reasoning sessions, not opportunity facts.
Proposal or Bid	Receives qualified opportunity context.	Proposal owns proposal writing and bid response execution.
Notification	Sends deadline, briefing, watchlist, and saved tender alerts.	Notification owns delivery records.
Analytics	Consumes opportunity events and recommendation outcomes.	Analytics owns projections and dashboards.

Ownership Rule

Opportunity owns opportunity facts, matching state, qualification state, recommendation records, saved opportunities, watchlists, and lifecycle state.

Cross-Domain Reference Pattern

Other domains should reference TenderOpportunityId, MatchId, RecommendationId, and SavedOpportunityId instead of duplicating Opportunity state.