One Record, Everything Else Worked Out
One Record, Everything Else Worked Out
Everything a child does is recorded once, as an entry in an event log that is only ever added to, and every view of progress is worked out from it. A stepped figure follows one answer into the log and to the four things derived from it. Why it matters to a parent: one truth, nothing kept in a second place, the same answer on tablet and server, and practice that works offline. Prepares the rules that judge mastery.
Underneath the three decisions lies one idea. Everything a child does
is recorded once, as an entry in an
The figure follows one correct answer to 7 · 8. The tablet adds it to the log. From the log, the engine works out whether the fact now counts as known, when it should come back, and what the child should do next. On the server, code from the same engine works out the guide's view.
This matters to a parent in four ways.
- One truth. The child's screen and the guide's table read the same entries, with code from the same engine. When two parts of a program keep their own counts instead, they drift apart without anyone noticing: one says a card is known, the other says it is new.
- Nothing in a second place. No part of the software keeps a private note of what a child did. What is not in the log counts nowhere.
- The same answer on tablet and server. The engine is written once and built into both. Given the same entries and the same moment, it gives exactly the same answer.
- It works offline. The engine runs on the tablet itself. A child can practice a whole morning without a connection. The entries reach the server later, and none is lost or counted twice.
There is a quieter benefit. If we find a mistake in a rule, we fix the rule and work everything out again from the log. No child's history has to be rewritten.