How a Quarry School lesson is made
A Quarry School lesson brings an explanation, a worked example and a chance to try the idea onto one page. Behind that page are structured lesson files, checks and review records. Following those pieces helps you see what has been checked, what a check can establish, and where to look when an explanation needs a second read.
Start with what the lesson teaches
The course sets the order of its units. Each unit holds lessons with their own titles and addresses. Inside a lesson, the explanation has named parts: plain words, a picture, a reason, a rule, a method, an example and a trap. Those names give the writer places to put different kinds of explanation. They also give you places to return to when one line is unclear.
Generative AI can draft words in that structure. Choosing the topic and deciding what belongs in the explanation remain editorial work. A draft needs a specific task: what should the reader be able to do after this lesson? An explanation of a rule needs an example that actually uses it. A trap needs to identify a mistake the surrounding explanation gives you a way to notice.
The structure is useful when revising. A change to an example can be read alongside its question, steps and answer. A change to the rule can be compared with the method below it. Putting words in named fields makes those relationships visible to the publishing tools. It also makes a missing part easier to identify than a missing idea buried in a long page.
Give checks a defined job
The exporter reads the files and checks them against the course's requirements. It reports findings when a file does not have the expected shape or a publication condition fails. The lesson renderer then turns the accepted parts into the page's headings, figures and exercises. A check that a field exists answers a narrow question. It does not establish that the explanation will make sense to every reader.
Exercise checking has a separate record. An entry says what kind of answer the page can accept: for example, a number, an expression or a choice. The page uses that record to offer the right input. Where an exercise has no supported checker, you work it out, reveal the answer and mark your own attempt. The interface should make that difference clear while you study.
That distinction matters when you inspect a result. A typed answer can match the recorded answer even if you reached it by an unreliable method. Read the worked steps and compare the reasoning with your own. If your answer differs, look for the first line where your work separates from the example. A result is a useful place to begin that comparison.
Read the record behind a review
A unit's review record identifies a reviewer and the version that was reviewed. The signing tool checks the version's fingerprint before recording it. This connects the review to particular lesson words. Changing those words requires the publication process to consider the changed version, rather than treating an earlier review as permission for any later text.
A reviewer field can name a model. The existence of a review record alone therefore does not mean a person read the lesson. We distinguish the tool that checks a file from the reviewer named in its record. People choosing subjects, curating material and deciding what to publish have responsibilities that a successful automated check cannot take over.
Sources need the same care. A source link gives a reader a place to examine a claim; the link's presence alone cannot prove the claim. When a page identifies source material, follow the reference and compare it with the explanation. The site's credits and licence page explains the attribution attached to source material used in the lessons.
Keep the spoken lesson connected to the page
The listening system reads a sequence of cues taken from the lesson. A recorded clip is matched to the display text by a fingerprint. This is how the tools distinguish a recording of the text you see from a recording made for different words. Narration has its own files, while the lesson remains readable as text.
That separation lets a reader move between the written example and the spoken explanation. It also creates a concrete maintenance task: when words change, the corresponding audio needs checking. A recording that sounds polished is not evidence that its explanation is sound. The writing, the answer and the audio each need attention for the job they do.
Use the page to inspect the explanation
Open a lesson from College Algebra and choose one example. Read its question, try the first step on paper and compare your work with the example's steps. Follow the source credit when you need its context. For the study controls themselves, read three ways through a lesson. That is the practical end of this process: a page whose explanation you can read, hear and examine one step at a time.