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

Platforms at a glance

Section titled “Platforms at a glance”
Platform Role Primary users
CAP Competency assessment (RPL first) Candidates, centres, assessors, awarding bodies
LMS Training / gap filling Candidates with competency gaps
WorkMasters Artisan portfolio for employers Artisans, employers
Orchestrator Shared auth, identity verify, notifications All apps (platform services)

How they connect

Section titled “How they connect”
                    ┌─────────────────┐
                    │  Orchestrator   │
                    │ auth · ID · notify│
                    └────────┬────────┘
           JWT / identity    │
        ┌────────────────────┼────────────────────┐
        ▼                    ▼                    ▼
   ┌─────────┐         ┌─────────┐         ┌─────────────┐
   │   CAP   │──gRPC──▶│   LMS   │         │ WorkMasters │
   │  (RPL)  │  recs   │         │         │  (later)    │
   └────┬────┘         └─────────┘         └──────▲──────┘
        │                                         │
        └──── competency checks (future) ─────────┘
  • Orchestrator issues shared JWT; CAP / LMS / WorkMasters validate locally.
  • Identity verification is intended as a shared Orchestrator concern; competency stays in CAP.
  • CAP → LMS over gRPC for course recommendations when RPL shows gaps (GAP_TRAINING).
  • WorkMasters should check competency against CAP later (not via Orchestrator).

Where to go next

Section titled “Where to go next”