Rules Written Down, Tests That Name Them
Rules Written Down, Tests That Name Them
Each capability has a spec: numbered requirements, each with a worked case. One rule, that a child sees a lesson only from their group's release stage on, followed to the test that names it and the check that runs it on every change, then the person's review. Why a test must name the rule it proves.
The first layer is writing the rules down. Each capability of the software has a spec: a short document that states what must be true now, as a list of numbered requirements. Each requirement comes with at least one worked case, in the form "when this happens, then that follows." As of November 2026 there are 58 specs, with 633 numbered requirements between them. A number is never reused, so a test or a report can point at a requirement for good.
Take one rule. A child sees a lesson only once it has reached their group's release stage. Its worked case: when a reviewer releases a newly drafted fractions lesson to testers, the testers can open it, marked as not yet checked by a person, while the school's children still find it locked. The test that proves this rule names it at its top, and it runs whenever the part of the software it guards changes.
When a spec and the code disagree, the change that finds it must fix one of them. Where the designs behind a spec disagree, the spec lists the question as open instead of hiding it.
A rule written down is not yet a rule tested. A test can sit under a rule and check something next door. So when a change adds or edits a requirement, every test listed under it must name that requirement. Whoever adds the name has to open the test and see that it drives the case the rule describes.