Impact & scale
Every number below is verifiable from the platform itself — nothing here is estimated or aspirational.
Platform scale
- 64core curriculum lessons, each with per-student IEP/WIDA supports, bilingual vocabulary, sentence frames, worked examples, and misconception alerts
- 1,997activity pages with cross-device, multi-day save/resume — students never lose work
- 1,754pages carrying the additive mobile-access layer for phones and small screens
- 58district-verbatim IEP and language accommodation lines a teacher can assign per student
- 22interactive unit-project pages with built-in manipulatives, exemplars, and self-assessment
- 4home languages supported in the learning-supports layer (English, Spanish, Vietnamese, Arabic)
Equity by design
- Supports are assigned per student and follow them to every lesson — differentiation is systemic, not per-worksheet.
- Tiered pathways (foundational support through enrichment) exist on every lesson without labeling any student publicly.
- Games are calm by design: no timers, no fail states that erase progress, scaffolded hints instead of answer reveals.
- Family communication ships bilingual by default, with interactive parent notes for every unit.
How outcomes are measured
The platform is fully instrumented: lessons emit anonymized-at-display struggle, misconception, and mastery signals; practice records carry progress and score data; and a standards-level rollup powers a live class heatmap and intervention radar. All of it is teacher-key-gated — student data is never public (privacy details).
Honest measurement note: the cloud outcome pipeline is newly deployed
(summer 2026). Aggregate, de-identified outcome results will be published here as they
accrue across the 2026–27 school year — this page will only ever report real data.
Quality engineering
- Automated validation gates every deploy: structural site validation, save/resume integrity across all activities, standards registry checks, and injection-layer balance audits.
- An end-to-end browser test suite (including automated WCAG scans of the supports UI) runs green: 18/18.
- Every layer is additive and reversible — a support-layer failure degrades to the plain lesson, never a broken page.