Editorial Policy

What we optimize for

A lesson should leave the reader with usable understanding. Ideas are introduced from first principles, in prerequisite order, with small examples and visible computation. Important abstractions should be earned through mathematics, code, diagrams, exercises, or experiments.

We prefer a precise explanation over a broad survey. When a statement is an intuition, empirical observation, engineering rule of thumb, or open research question, the lesson should say so.

Human review and AI assistance

AI may assist with drafting, rewriting, code, diagrams, exercises, consistency checks, and critical review. AI output is working material, not an authority and not an automatic publication decision.

Material marked available is reviewed by a human before publication. Review checks the explanation, prerequisite flow, notation, examples, code, exercises, diagrams, references, and rendered page. Automated audits support this work, but they do not certify that a reader has understood the lesson.

Sources and research references

Common Python and mathematical foundations may be taught without a citation for every standard fact. From Deep Learning onward, lessons include primary papers or official project sources when a research contribution, named method, historical claim, or implementation detail benefits from a traceable source.

References should appear near the relevant lesson rather than only in a distant bibliography. We prefer original papers and official project documentation. A citation provides a trail to the source; it does not replace the explanation or imply endorsement of every claim in that source.

Code, diagrams, and exercises

Code should make the idea inspectable and mirror the mathematics where practical. Examples are tested in proportion to their role, but they remain educational examples rather than production guarantees.

Diagrams must teach a relationship, computation, geometry, scale, or failure mode. Interactive figures should explain what to change and what to notice. Exercises are part of the teaching sequence; hints and solutions should explain the reasoning, not merely reveal an answer.

Corrections and revisions

Technical education is revisable. We correct factual, mathematical, code, accessibility, and presentation errors when they are confirmed. Larger revisions are reviewed in the context of neighboring lessons so a local fix does not create a new prerequisite gap.

To report a possible error, email contact@llmprimer.com with the page URL, the relevant passage or figure, and a short explanation. Reports are evaluated rather than accepted automatically.

Publication status

Available, draft, and planned material are distinguished in the curriculum. Draft and planned subjects may change substantially and should not be presented as finished starting points. See the curriculum for current availability.

Independence and commercial boundaries

Editorial explanations are not sold placements. If sponsorships, affiliate relationships, or other material conflicts are introduced, they will be disclosed where they could affect a reader's judgment. Essential explanations and accessibility features are not designed as artificial obstacles to a paid service.

Scope of this policy

This policy describes the editorial standard we apply; it is not a promise that every page is error-free. The Terms of Service govern use of the site, and the Privacy Policy explains how information is handled.