Help families understand a learning summary and ask for a correction when it misses the mark.
Extend the existing family note with a clearer explanation of the evidence behind it.
Add correction requests with a visible review status and a response from an authorized educator.
Explain uncertainty and suggest a practical next step for learning at home.
Release checks & dependencies+
Ready when
A linked parent can submit a request and follow it through a reviewed response.
An unrelated account cannot see the note, evidence, or request.
Accepted corrections survive later summary updates and are included in applicable export and deletion flows.
Depends on
Agreement on who reviews requests and how accepted corrections affect future AI summaries. Family visibility stays limited to information they are authorized to see.
Validate the existing Google Classroom connector in a real school setup and make connection problems easier to resolve.
Guide administrators through connecting an approved school account.
Show the last successful sync, what needs attention, and how to retry.
Pilot supported course, roster, and assignment imports before expanding to other providers.
Release checks & dependencies+
Ready when
The pilot school approves access and confirms imported records match the source.
Disconnecting stops future syncs, and retries do not create duplicate records.
A school administrator can understand and recover from an expired connection.
Depends on
School participation, Google permissions or verification where required, and the relevant plan. This target covers a limited pilot; grade write-back and broad provider rollout are outside this release.
Make saved daily review dependable on phones, including a clear path from offline practice back to a synced account.
Finish device testing of the existing iOS and Android apps.
Make download readiness, pending answers, and sync failures easy to understand.
Run a closed beta for offline daily review and reconnection.
Release checks & dependencies+
Ready when
Saved review works in airplane mode and answers sync once after reconnecting.
Signing out or changing accounts removes access to the previous learner’s saved data.
The beta passes real-device, keyboard, and assistive-technology checks for its core journey.
Depends on
Developer accounts, signing, device access, and beta distribution approval. Public app-store availability is a separate decision. New AI tutoring still requires a connection.
Complete the most-used student and family journeys in Spanish, including the messages that appear when something goes wrong.
Finish sign-in, class joining, daily review, and family-summary interface copy in Spanish.
Carry the language choice across those journeys and their notifications.
Have a fluent reviewer check learning terminology, clarity, and layout.
Release checks & dependencies+
Ready when
The scoped journeys have no unintended English labels or missing translation keys.
A fluent reviewer and pilot families can complete the journeys.
Longer text fits on phones and at 200% text size, and language metadata is correct.
Depends on
A fluent reviewer and Spanish-speaking pilot families. Existing language support is the base; this is a scoped completion pass, not a promise to translate the whole platform.
Give schools an evidence-based decision about expanding Limud, supported by clearer setup and progress reporting.
Turn pilot setup into a repeatable school onboarding checklist with readiness and issue ownership.
Review adoption, teacher time, support needs, and the learning measures collected by the pilot.
Expand access only where the pilot, support, accessibility, and privacy checks are ready.
Release checks & dependencies+
Ready when
A school administrator can complete setup and identify unresolved requirements.
Pilot results state sample size, limitations, and what was actually measured.
The school and Limud agree on support ownership and whether to expand, extend, or pause the pilot.
Depends on
School approval, enough pilot participation, and an agreed observation period. Learning-outcome reporting also needs reviewed assessment materials. This is a decision target, not a promised district-wide launch or learning gain.
Planned work: –
02 / What we are building on
Existing foundations
These workflows are already implemented. Access depends on your role, plan, and school setup; connected services may need additional configuration.
01
Personalized learning material
Teachers can provide material that is adapted for students, alongside a common graded assignment. Preview and editing tools already exist.
02
Daily review and learning evidence
Review activity feeds learning evidence. Student notes, teacher views, and family summaries already connect parts of the learning journey.
03
Teacher and student workspaces
Assignments, portfolios, concept maps, and group projects are implemented. The next releases focus on clearer workflows and review controls.
04
Family notes and student exports
Linked-family insights and student record export flows exist. A tracked correction request is the new step in this plan.
05
School connectors
Provider adapters and connection workflows exist for Google Classroom, Canvas, Schoology, and Clever. Availability depends on school permissions and configuration.
06
Offline review and mobile groundwork
Saved daily review and native app projects exist. Device validation and beta distribution come before a public mobile launch.
Unscheduled. These ideas need research and pilot evidence before they receive a delivery date.
More languages and school connectors
Expand after the first language and connector pilots show which journeys work and where support is needed.
Exploring
More capable teacher assistants
Research actions that save time while keeping teachers in control of consequential changes.
Exploring
Richer creative learning
Explore educational video, arts, and immersive activities after the core learning journey is dependable.
Exploring
Broader adaptive assessments
Validate question quality and learning measures before promising more precise assessment or stronger outcomes.
Exploring
A plan you can follow
How dates work
This schedule assumes two developers using AI assistance, with time reserved for testing, accessibility, maintenance, and feedback. Only the next release is intended to be in active delivery at a time.
Planned means scoped with a target date, not a claim that work has started. Conditional means the target also depends on a product decision, a partner, an earlier pilot, or external approval.
We plan to review this page every two weeks. A passed target stays visible until its status is reviewed; dates do not automatically turn into a “released” badge. If a release slips, the next update will explain the change and its effect on later dates.
School pilots, provider permissions, and app-store reviews can change availability. New features will carry their role and plan requirements when released.
Help shape the next release.
Tell us what gets in the way of teaching or learning, and who it affects.