Skip to content
Elimi Docs

Ecosystem map

Ecosystem map

Section titled “Ecosystem map”

Audience: leadership, domain
Status: specced
Owns: product / delivery lead
Depends on: Maturity, Domain overview, System architecture

Platforms at a glance

Section titled “Platforms at a glance”
Platform Role Primary users
CAP Competency assessment (RPL + NSQ) Candidates, centres, assessors, awarding bodies
LMS Vocational training / gap filling Learners, instructors, platform staff
WorkMasters Artisan portfolio for employers Artisans, employers
Orchestrator Shared auth, identity, notify, payment, storage All apps (platform services)

How they connect

Section titled “How they connect”
flowchart TB
  Orch[Orchestrator<br/>auth · ID · notify · pay · storage]
  CAP[CAP RPL / NSQ]
  LMS[LMS]
  WM[WorkMasters]
  Orch -->|JWT JWKS| CAP
  Orch -->|JWT JWKS| LMS
  Orch -->|JWT JWKS| WM
  CAP -->|gRPC recs| LMS
  Orch <-->|gRPC / events| CAP
  WM -.->|competency later| CAP
  • Orchestrator issues shared JWT; CAP / LMS / WorkMasters validate locally via JWKS.
  • Identity and storage are Orchestrator concerns; payment processing is Orchestrator, pricing is CAP (or LMS later) — Payment architecture; competency stays in CAP.
  • CAP → LMS over gRPC (RecommendCourses) when assessment shows gaps (GAP_TRAINING).
  • LMS → CAP asynchronously via lms.course.completed (LMS certificates stay independent of CAP).
  • WorkMasters should check competency against CAP later (not via Orchestrator).
  • Infra topology: System architecture · Backend stack ADR · OpenAPI in repo openapi/ · Orchestrator · CAP

Where to go next

Section titled “Where to go next”