Learning Relationships

Why This Exists

This document explains how the Learning Domain relates to other Algosure domains.

Owner

The owner is the Chief Product Officer and Enterprise Architect.

Business Value

Relationship clarity prevents duplication and ensures Learning improves procurement capability without taking ownership of adjacent domain facts.

Relationship Diagram

flowchart TD
    Org[Organization]
    Identity[Identity]
    Intel[Intelligence]
    Opp[Opportunity]
    Comp[Compliance]
    Bid[Bid]
    Contract[Contract]
    Notification[Notification]
    Analytics[Analytics]
    Memory[Organizational Memory]
    Learning[Learning]

    Org -->|OrganizationId and business context| Learning
    Identity -->|UserId and access context| Learning
    Intel -->|reasoning, tutor response, confidence| Learning
    Opp -->|tender learning triggers| Learning
    Comp -->|compliance gap triggers| Learning
    Bid -->|bid workflow learning triggers| Learning
    Contract -->|delivery learning triggers| Learning
    Learning -->|progress and certificate events| Notification
    Learning -->|learning metrics| Analytics
    Learning -->|learning evidence events| Memory

Relationship Catalogue

Domain	Relationship	Data ownership rule
Organization	Provides organization context, industry, capabilities, maturity needs, and user association.	Organization owns profile and business facts. Learning owns organization learning profile.
Identity	Provides user identity and access context.	Identity owns users and authentication. Learning owns user progress records.
Intelligence	Provides tutor reasoning, explanations, confidence scoring, and recommendation assistance.	Intelligence owns reasoning execution. Learning owns tutor session records and recommendations.
Opportunity	Triggers learning based on opportunity matching, qualification uncertainty, and tender reading needs.	Opportunity owns tender facts. Learning owns education response.
Compliance	Triggers learning based on compliance gaps, readiness issues, and document expiry education needs.	Compliance owns compliance state. Learning owns compliance education recommendations.
Bid	Triggers learning based on bid planning, proposal quality, SBD forms, approval discipline, and submission errors.	Bid owns workspace and submission state. Learning owns bid education records.
Contract	Triggers learning based on delivery risks, milestone issues, supplier coordination, and closeout lessons.	Contract owns contract state. Learning owns delivery education recommendations.
Notification	Sends reminders and learning prompts.	Notification owns message delivery state. Learning owns learning event cause.
Analytics	Measures adoption, completion, maturity, and learning effectiveness.	Analytics owns reporting views. Learning owns source learning records.
Organizational Memory	Receives learning evidence for future AI reasoning.	Memory stores governed knowledge. Learning remains source of learning records.

Cross-Domain Examples

• Compliance detects missing B-BBEE awareness and emits a trigger. Learning creates a beginner lesson recommendation.
• Opportunity identifies repeated bid/no-bid uncertainty. Learning recommends a tender qualification course.
• Bid records a late submission task pattern. Learning recommends a bid planning lesson.
• Contract records repeated milestone slippage. Learning recommends contract delivery basics.

Ownership Principle

Learning must not become a dumping ground for operational facts. It should store learning conclusions, progress, recommendations, certificates, and education evidence. Operational facts stay in their owning domains.