Enter the 4-digit access code.
Phase 2 turns the existing OpenLiteracy MVP into an AI-driven adaptive learning engine that adjusts in real time to each student — and each group. This is the master plan. Sign it off, and we build.
Phase 1 shipped a working tool. It runs in classrooms today. But it was built fast, and the seams show: lesson logic is hardcoded, remediation is repetition rather than adaptation, group sessions are treated like 1:1 sessions, and the data the AI could use to make better decisions often doesn't get captured.
Phase 2 is six weeks to fix that — without breaking what works. We spend the first sprint on planning. We map every assumption, surface every ambiguity, and lock the architecture before a line of new code ships. That's the Ferrari. Sprints 2 and 3 build it.
This site is Sprint 1's deliverable. It's the plan, the open questions, the matrix of what AI does vs what humans do, and the schedule. Read it. Push back where it's wrong. Sign off when it's right.
Every one of the 116 questions falls into one of these ten themes. Each theme has a single owner and a target sprint. Resolve them in order, and the engine designs itself.
Every capability in this system is tagged with one of four labels. Drawing the line clearly is part of the master plan — it's how we avoid building the wrong kind of AI feature.
The complete registry, filterable. Each question shows who owns it, what sprint it lands in, and how it's categorized.
| ID | Section | Question | Bucket | Owner | Sprint |
|---|
The team has organized questions by who's best positioned to answer them. Find your name and you'll know where to focus.
docs/02-open-questions/00_master-question-registry_Beth.md (registry),
docs/02-open-questions/01_sprint-plan_Beth.md (schedule),
docs/02-open-questions/why-we-ask.md (this overview),
prior-code-analysis/ (MVP audit). When something's wrong
here, fix the source; this page regenerates from it.