Domain overview
Domain overview
Section titled “Domain overview”Audience: domain, backend, product
Status: specced
Owns: product + backend
Depends on: Glossary, Ecosystem map, Entities
The team shares one ubiquitous language. Code, OpenAPI, UX flows, and test cases must use the same names for the same concepts (e.g. Application, Centre, stage PAYMENT). Do not invent parallel labels in tickets or UI copy without updating the glossary and entities.
Bounded contexts
Section titled “Bounded contexts”| Context | Responsibility | Owns (examples) |
|---|---|---|
| CAP RPL | Competency assessment via Recognition of Prior Learning | Application, lifecycle stages, evidence, interview, certification path |
| Orchestrator | Shared platform services | User/auth, JWT issuance, identity verification, notifications |
| LMS | Training / gap courses | Courses, enrolments; serves recommendations to CAP |
| WorkMasters | Employer-facing portfolio (future) | Portfolio presentation; competency checks against CAP |
CAP does not own shared login or NIN provider integration long-term—those belong in Orchestrator. CAP does own competency outcomes and application lifecycle.
Process spine
Section titled “Process spine”For CAP RPL, the canonical process model is the RPL application lifecycle (stages + statuses). Policies that constrain the domain live in RPL policies.
Role lenses (CAP RPL)
Section titled “Role lenses (CAP RPL)”Implementation views hang off this domain core—they do not redefine it: