Skip to content

Learning management

Generated from the architecture model

This page is rendered from model/**/*.yaml by tools/docs_model during mkdocs build. Edit the YAML, not this page; hand-written design lives on the linked service, platform and plane pages.

Vertical LMS
Prototype reference LMS prototype (ConnectSoft.DesignPrototypes)
Managed edition SelfOperated (D33, D34)
Data residency tenant-region (D31)
Catalog Examples catalog · Vision-to-Production path for this vertical

Business problem

Courses, enrolments and assessments live in a platform that cannot localize or integrate with HR.

Product intent

Courses, cohorts, enrolments, assessments and certificates with HR integration and three locales.

What the Factory makes different here: localization and accessibility from the blueprints; certificates as signed artifacts.

Vision-to-Production path for this vertical

Step Factory platform Agents Blueprints
Vision and product plan Agent Mesh, Control plane Product Manager Agent, UX Designer Agent vision
Architecture and domain Template & Library (BC-02) Enterprise Architect Agent service, module, integration
Experience Template & Library, Factory Studio UX track UX Designer Agent, Frontend Developer Agent ux, frontend, localization
Recipe and generation Template & Library (BC-15), Agent Mesh, Tools & MCP Product Manager Agent, UX Designer Agent, Backend Developer Agent, Frontend Developer Agent, QA Agent module plan from the context map
Quality Observability (BC-22), DevOps / GitOps QA Agent test
Delivery and provisioning DevOps / GitOps (BC-23, BC-24), Runtime Cloud (BC-25) DevOps Agent, Infrastructure Architect Agent —
Operations Product Fleet Operations (BC-35..37) — handover, objectives, rollouts, incidents, off-boarding

Delivery workflows exercised: research-and-ux-ui-design-workflows.

Generated product shape

C4Context
    title Learning management system context
    Person(user, "Users", "LMS users and operators")
    System_Ext(factory, "ConnectSoft AI Factory", "generates, delivers, provisions and operates the product")
    System_Boundary(product, "Learning management") {
        System(ctx_Catalog, "Catalog", "courses, modules, versions")
        System(ctx_Enrolment, "Enrolment", "cohorts, progress")
        System(ctx_Assessment, "Assessment", "quizzes, grading, certificates")
    }
    Rel(user, ctx_Catalog, "uses through the product gateway GW-07")
    Rel(factory, ctx_Catalog, "descriptor, health, rollouts, incidents, off-boarding")
Hold "Alt" / "Option" to enable pan & zoom

Bounded contexts

Context Responsibility Published events
Catalog courses, modules, versions CoursePublished
Enrolment cohorts, progress EnrolmentCompleted
Assessment quizzes, grading, certificates CertificateIssued

Modules and templates

Module Template Notes
Microservice ×3 connectsoft-microservice
Learner shell connectsoft-blazor-shell
HR connector client connectsoft-api-library
Every product also gets the SaaS foundations (tenants, editions, entitlements, billing, metering) and the product host shape (descriptor, health, operations handover) unless it is a library-only product.

Prototype reference

LMS prototype in ConnectSoft.DesignPrototypes shows the intended screens; the UX track (U1–U4) maps prototype destinations to the UX model's screens with keep, merge, rename, retire or new decisions.

Operations as a managed product

Self-operated.