How the Engine Picks the Next Step
How the Engine Picks the Next Step
How the engine works along a course's path through the knowledge graph: topics ranked by a fixed order of reasons with ties broken by the course's order, up to three offered for the child to choose; inside a topic, the next exercise or a stop; a sitting composed by need, wrong cards first, with locked rows dealt nothing. Checking prerequisites and routing errors to a missing skill is designed, not built.
The curriculum is a knowledge graph, in which every topic knows what
it builds on, and a course lays out a path through it. The
When a child starts, the engine ranks the course's topics, mainly by a fixed order of reasons. A topic whose review is due comes first. Next comes a topic the child left unfinished in the past day, then a topic not yet started, then one in progress. Where two topics are equal, the course's own order decides, never chance. The engine offers up to three topics, and the child picks one.
Inside a topic, the engine picks the next exercise, or it stops. It stops when the topic is mastered, when nothing is left to show, or when the child has had enough for now: after twelve attempts in one sitting, or five misses in a row. A child who is stuck moves on to something else instead of failing again and again.
In a course such as the times tables, the engine composes each sitting as a set of cards, chosen by need. Cards the child had learned and then got wrong come first. Next come cards that stand between the child and the next row of the course. Then come new cards and cards still climbing. A new row opens only once the cards before it reach the course's bar, and until then the sitting deals none of its cards.
One part of the design is not built yet. The engine is meant to check a topic's prerequisites itself and, when a child keeps making the same error, to send them back to the earlier skill that is missing. Today it follows the course's order and does neither. Spotting a missing earlier skill is, for now, the guide's job.