Overview

A high‑level map of the architecture proposed for the integration of MÜSLI into MaMpf. Each later layer depends only on stable persisted results from earlier phases (no hidden cross‑coupling).

flowchart LR
    A[Registration] --> B[Allocation];
    B --> C[Rosters];
    C --> D[Assessments & Grading];
    D --> E[Eligibility];
    E --> F[Exam Registration];
    F --> H[Exam Grading];
    H --> G[Reporting];

Core flow (see End-to-End Workflow):

1. Campaign setup & user registrations (Registration System)
2. Preference assignment (if needed) (Algorithm Details)
3. Allocation materialization to domain rosters (Rosters)
4. Ongoing roster administration (moves, late adds)
5. Coursework assessments, submissions, points & grades (Assessments & Grading)
6. Achievements & eligibility computation (exam gating) (Student Performance)
7. Exam registration (policy gated)
8. Exam assessment creation & grading (Grading Schemes)
9. Dashboards for students & staff (Student Dashboard, Teacher & Editor Dashboard)
10. Reporting, integrity checks (Integrity & Invariants)
11. Roadmap & extensibility (Future Extensions)

Book Structure

Core Architecture

• Overview (this)
• Domain Model
• Registration System
• Rosters
• Assessments & Grading
• Student Performance
• Grading Schemes
• End-to-End Workflow
• Algorithm Details
• Examples & Demos
• Integrity & Invariants
• Future Extensions

User-Facing Applications

• Teacher & Editor Dashboard
• Student Dashboard

Project Planning

• Implementation Plan

Design Tenets

• Single source of truth per concern (e.g., confirmed assignments live in UserRegistrations + domain rosters after materialization).
• Idempotent transitions (finalize!, materialize_allocation!).
• Append/extend rather than mutate history (overrides, policy traces).
• Pluggable strategies & policies