- product-portfolio
- ecosystem-catalog
- deep-dives
- vertical
Education, Learning, HR & Workforce - Analysis¶
Planning-layer analysis for category 18. It groups the 50 candidate services into capabilities, recommends what becomes a standalone service versus a module, and captures domain, interface, and non-functional notes. For the plain item list see the browse page.
Scope & Bounded Context¶
- Primary bounded context: Education & HR
- Group: vertical
- Default wave / cycle: Phase 4 · Cycle 4: AI Interaction & Verticals
- Items: 50 candidates
This category is anchored to the ConnectSoft DDD baseline in the SaaS framework DDD blueprint and the service classification model.
Classification Breakdown¶
| Classification | Count |
|---|---|
| AI Agent | 1 |
| Module-in-service | 38 |
| Platform Product | 5 |
| Portal/UI Module | 4 |
| Workflow Template | 2 |
Anti-fragmentation stance
Per ADR-0011, the 38 module candidates below are delivered inside the Education & HR bounded-context service, not as separate microservices. Only the 5 platform/service candidates justify an independent runtime.
Standalone Service / Platform Candidates¶
| ID | Service | Tier | Status |
|---|---|---|---|
| CS-SVC-0851 | Learning Management System | 3 | Planned |
| CS-SVC-0861 | Continuing Education Platform | 3 | Planned |
| CS-SVC-0862 | Corporate Training Platform | 3 | Planned |
| CS-SVC-0866 | School Administration Platform | 3 | Planned |
| CS-SVC-0871 | HRIS Platform | 3 | Documented |
AI Agent Candidates¶
- AI HR Assistant (
CS-SVC-0899) - runs on the shared AI Orchestration runtime.
Portal / UI Modules¶
- Student Portal (
CS-SVC-0854) - Instructor Portal (
CS-SVC-0855) - Candidate Portal (
CS-SVC-0886) - Workforce Analytics Dashboard (
CS-SVC-0897)
Domain, Interfaces & Data Ownership¶
- Aggregates are owned by the Education & HR context; cross-context reads go through published contracts, never shared databases.
- Integration is event-first (outbox + integration events) per the event-driven mindset.
- APIs are contract-first and versioned through the API & Integration context.
Non-Functional Posture¶
- Multi-tenancy & edition-awareness: required for all serious candidates.
- Security: Standard baseline; secrets via the platform secret store; least privilege.
- Compliance: standard audit logging.
- Observability: OpenTelemetry traces, metrics, and structured logs.
MVP vs Future¶
- MVP (Tier 0-1): Tuition Billing Service, Learning Content Authoring Tool
- Future (Tier 4-5): none
Open Questions¶
- Which module candidates, if any, develop independent scaling or ownership needs that would justify promotion to a standalone service?
- Where do this category's contracts overlap with adjacent contexts, and who owns them?