Assessment simulation
The model separates present-student academic scores from attendance and non-participation, so observed zeros are treated as administrative outcomes rather than readiness evidence.
Project Brief
A public-safe bootstrap layer for assessment analytics, LMS workflow prototyping, decision-support dashboards, and learning-systems development.
Overview
This project demonstrates how to build realistic education analytics infrastructure without publishing protected student data, raw LMS exports, real gradebooks, teacher names, section labels, or school-private records.
The generator creates a coherent simulated department system rather than isolated fake rows: students, teachers, courses, sections, enrollments, assessment scores, attendance behavior, Canvas-style course artifacts, SQL warehouse tables, and validation checks.
Statistical Design
The model separates present-student academic scores from attendance and non-participation, so observed zeros are treated as administrative outcomes rather than readiness evidence.
Assignment 02 applies the reusable score engine with readiness updates, school-year growth, course and track context, teacher and section effects, regression to the mean, and observation noise.
The validator checks row counts, schema, enrollment consistency, score bounds, assignment population policy, Canvas-style profile coverage, and banned private/source strings.
The DuckDB warehouse normalizes Canvas-like JSON into raw LMS tables, reconciles rosters against canonical enrollments, and exports star-schema facts and dimensions for downstream reporting.
The public build documents a Supabase/Postgres path for serving curated synthetic marts while preserving DuckDB as the reproducible local warehouse.
Relationship
education-data-simulation-engine is the simulation, validation, and SQL warehouse foundation. assessment-intelligence is the analytics and reporting layer that consumes SQL-backed extracts for dashboards, diagnostics, reports, and decision-support workflows.
Safety Boundary
Public artifacts may include fake identifiers, synthetic enrollments, synthetic assignment scores, generalized calibration parameters, and public-safe aggregate diagnostics. They must not include real students, rosters, LMS exports, private assessment artifacts, private teacher names, internal section labels, private paths, or credentials.
Warehouse Outputs
Exports include assessment facts, LMS enrollment facts, readiness, growth, missingness, roster reconciliation, teacher-section effects, and validation summaries.
The SQL layer provides student, course, section, teacher, assignment, assessment-score, and LMS-enrollment dimensions and facts.
The repo documents an optional Supabase/Postgres serving layer for public-safe synthetic analytics tables after private credentials are supplied locally.