How lessons are made
A lesson passes through writing, checks and a separate reading before it reaches you.
These steps catch different kinds of problems. They do not prove that every explanation or answer is right.
For the times and costs we measured, read How we build Quarry School.
1. Start with an outline and sources
The outline sets the ideas and their order. Source records identify borrowed material and its credit. A source link tells you where material comes from; its presence alone does not prove a claim.
2. Draft the lesson
AI models help write the explanations, worked examples and practice. The production records track writers and checking runs when recorded. Some older entries do not name a model.
3. Run automatic checks
Code checks the file structure, required lesson parts, references and publication requirements. Mathematics checks recompute supported answers and check supported answer forms. Other gates flag missing citations, copied wording, private material and reuse problems.
A passing check covers the thing it tests. It cannot establish that every sentence teaches the idea well. Inspect the material credited on the site.
4. Ask an independent second reader
A separate reader examines the unit and its findings. That reader may be an AI model. For example, the Complex Numbers sign-off names codex/gpt-6.1-sol; its writing record names claude-code/claude-fable-5-2. This is a separate model reading, not a claim that a person read every lesson.
Explore the unit this record describes. Internal review records are kept in the private repository.
5. Sign the version and publish
The sign-off records the reader, date and a fingerprint of the reviewed version. Publication checks compare that fingerprint with the version being exported. A changed lesson needs review of its changed version. Publication records and release checks track what is allowed to go live.
The published course is the result readers can inspect. The internal sign-off and release records are not public downloads.
6. Report and correct a mistake
Email [email protected] with the lesson address, the line or question, and what seems wrong. The correction goes through the content checks and review before a revised lesson is published.
If an exercise check gives the wrong mark, use “I got it” or “I missed it” to set your own practice record. See how practice works.
Correction history is kept with the repository changes. There is no public correction log on this page.