Elimi Docs
Elimi ecosystem documentation
Section titled “Elimi ecosystem documentation”This site is the single source of truth for Elimi’s product platforms, delivery status, and implementation context. Prefer these pages over reading multiple codebases. Shared language lives in the domain and glossary; role lenses hang off that core.
Start here by role
Section titled “Start here by role”| Role | Start here |
|---|---|
| Leadership | Maturity · Ecosystem map · Live status board |
| Product / Domain | Domain entities · CAP overview · RPL lifecycle · NSQ lifecycle |
| UI / UX | Experience overview · Personas |
| Backend | Architecture handover · Contracts hub · System architecture · Payment architecture · Backend stack ADR · Coding standards · Orchestrator · CAP backend |
| Frontend | Contracts hub · Frontend overview · Experience · API |
| QA | QA overview · Test cases · Lifecycle |
| Tech writing | Narrative overview · Experience |
| DevOps | CI/CD · Observability · System architecture |
Contributors: How to contribute.
Platforms
Section titled “Platforms”| Platform | Role | Docs depth now |
|---|---|---|
| CAP | Competency assessment (RPL + NSQ) | RPL layered template + NSQ lifecycle + workflow abstraction; validated OpenAPI + Prisma |
| LMS | Training / gap filling | Stub |
| WorkMasters | Artisan portfolio for employers | Stub |
| Orchestrator | Shared auth, identity, notify, payment, storage | Specced (api/ + backend/ + validated OpenAPI + Prisma + gRPC) |
Delivery & live tasks
Section titled “Delivery & live tasks”- Human board: Live status
- Checklist UI: CAP RPL checklist
- Machine feed for LLMs/tools:
GET /api/tasks(see Delivery overview)
Task definitions live on the deploy environment (TASKS_JSON_PATH). Completing a task updates Trello via the API — the server never commits to git.
Archive notes
Section titled “Archive notes”Brainstorm notes remain under raw/ and original-raw-ideas/ in the repo. Do not treat them as current source of truth; use the pages in this site instead. Architecture decisions from the 2026 backend discussion are reflected in System architecture, the Backend stack ADR, and the Architecture handover.