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
Generates a coherent seven-year synthetic mathematics department, validates cross-table invariants, builds Canvas-style records and a DuckDB star schema, and exports marts consumed by Assessment Intelligence.
Overview
The deterministic synthetic education-data foundation connects a nested school structure, Canvas-style records, longitudinal assessment data, and a local analytics warehouse.
Validation reconciles enrollment, assessment, non-participation, and LMS-style records before downstream reporting.
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.
The active seven-year synthetic math-department foundation connects student, course, section, enrollment, assessment, attendance, and LMS-style records.
The validation layer reconciles enrollment, assessment, non-participation, and LMS-style records before downstream reporting.
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.
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.
Projects Qualification
Strong supporting architecture evidence and the privacy foundation for Assessment Intelligence; the local commit is demo-ready, but public featuring must wait for separately approved remote release synchronization.
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.