micro-learning-service-v2 — business features

1. What it is

micro-learning-service-v2 holds the training content — modules, sections, lessons, screens and blocks — and everything a learner does with it: opening a lesson, answering quiz questions, keeping a streak, earning points and getting a certificate. Admins build and publish content here (or push it in from authoring-service-v2), and the mobile app reads every lesson it plays from this service.

The same repository also ships tts-worker-v2, a separate Deployment built from app/tts_worker/ and Dockerfile.tts-worker. It turns lesson text into spoken narration. The top-level tts-worker-v2/ directory is an empty shell — it holds no tracked source (git ls-files tts-worker-v2 returns nothing); the code moved here in M4 (ARCHITECTURE.md §2).

2. Feature map

flowchart LR
  ADM["Admin web"] --> CONTENT["Content tree and publishing"]
  ADM --> DASH["Dashboards and reports"]
  MOB["Mobile app"] --> PLAY["Catalogue and lesson player"]
  MOB --> PROG["Progress, points, streaks, certificates"]
  SVC["Other services"] --> INGEST["Module ingest and translations"]
  BG["Schedulers and TTS worker"] --> AUDIO["Narration audio and streak nudges"]
  CONTENT --> A1["/v1/admin/modules ... /screens"]
  DASH --> A2["/v1/admin/overview, /v1/admin/progress"]
  PLAY --> A3["/v1/mobile/modules, /v1/mobile/lessons"]
  PROG --> A4["POST /v1/mobile/progress/events"]
  INGEST --> A5["/v1/internal/modules, /v1/internal/translations"]
  AUDIO --> A6["tts.audio.requested"]

3. Features

Admin

Employee (mobile)

Internal (other services)

Background

4. API reference

All 109 scanned routes. Admin and mobile routes reach the service through the shared auth.useoper.com ingress; /v1/internal/* has no ingress rule and is reachable only from inside the cluster.

5. Async contracts

Consumes

Publishes

Fifteen publish call sites. learning.streak.at_risk.ten.<tenant> is built from an instance attribute, so the scanner cannot resolve it and it is absent from the scan JSON — it is nonetheless a real published subject and is listed here.

Background jobs

6. Data it owns

Postgres logical DB microlearning, 35 alembic revisions under migrations/versions/. Every table is written by this service except where noted.

7. Dependencies

flowchart LR
  AV2["authoring-service-v2"] --> ML["micro-learning-service-v2"]
  CW["content-worker"] --> ML
  AS["assignment-service"] --> ML
  UA["users-auth-service"] --> ML
  ML --> UAO["users-auth: profiles and credits"]
  ML --> ASO["assignment-service: employee assignments"]
  ML --> AVO["authoring-service-v2: recent modules"]
  ML --> AM["asset-manager: uploads"]
  ML --> NATS["NATS: MICRO_LEARNING and TRAINING_AUDIO"]
  NATS --> TTS["tts-worker-v2"]
  TTS --> MODAL["Modal chatterbox TTS"]
  TTS --> AM
  TTS --> DB[("microlearning DB")]
  ML --> DB

Inbound edges H1 (authoring ingest / publish), H7 (content-worker translations), H16–17 (assignment-service progress and module validation) and H19 (users-auth analytics, billing, training stats). Outbound edges H11–12 (users-auth users and the publish-time credit debit), H13 (assignment-service on the mobile read path), H14 (authoring recent-modules card) and H9 (tts-worker-v2 to asset-manager) — ARCHITECTURE.md §3.2.

8. Dead-code verdicts

Every entry point with no in-repo caller. Deleting is a separate decision — see the hub roll-up.

Doc drift, not a code verdict: API_ENDPOINTS.md still documents PUT /v1/mobile/lessons/{lesson_id}/session, GET /v1/mobile/lessons/{lesson_id}/quiz/summary and POST /v1/mobile/progress/assignments/{assignment_id}/lessons/{lesson_id}/complete. None of those routes exist in the scan; they were replaced by the single POST /v1/mobile/progress/events endpoint (CHANGE_PROGESS_ROUTES.md).

9. Sources

• docs/API_ENDPOINTS.md — admin and mobile route inventory (with the drift noted above)
• docs/FRONTEND_INTEGRATION_GUIDE.md — mobile catalogue and player calls
• docs/MOBILE_FRONTEND_EVENTS_GUIDE.md, docs/CHANGE_PROGESS_ROUTES.md, docs/TEST_CASES_CHANGE_EVENTS_REOUTE.md, docs/mobile/progress-events-telemetry.md — the progress-events contract
• docs/QUIZ_SCORE_TRACKING.md, docs/QUIZ_GRAPH_FLUTTER_INTEGRATION.md, docs/QUIZ_GRAPH_BLOCK_EXAMPLES.md, docs/QUIZ_GRAPH_IMPLEMENTATION_PLAN.md — quizzes and the quiz graph
• docs/BLOCK_TYPES_REFERENCE.md, docs/SCREENS_RESPONSE_EXAMPLE.md — block and screen payloads
• docs/STREAKS_AND_POINTS.md, docs/STREAKS_AND_POINTS_IMPLEMENTATION_PLAN.md — streaks, points, leaderboards
• docs/ADMIN_OVERVIEW_DASHBOARD_FE.md — the nine overview cards
• docs/NARRATION_CREDIT_ESTIMATE_FE.md, docs/tenant-voice-fe.md, docs/tts-worker-v2.md — narration cost, voice selection, the TTS worker
• docs/CREATE_MODULE_DIRECT.md, docs/MODULE_DELETION_STRATEGY.md, docs/RANKING_MODULES.md — module lifecycle and home-screen ranking
• ARCHITECTURE.md §2, §3.2 (H1, H7, H9, H11–14, H16–17, H19), §3.3, §3.4, §4.1
• bug-hunt-reports/micro-learning-service-v2.md — 20 findings, 8 fixed
• global-configs/k8s/users-auth-ingress.yaml — which paths actually reach this service