Corrections and contributions
Where a correction belongs
| You found a problem in… | Report it to |
|---|---|
| an imported chapter (any chapter with a "From cognokratos/…" line) | that project's repository. The chapter's source note has a Report a correction link that opens an issue pre-filled with the file and revision. |
| a project's code behaving differently from its lesson | that project's repository, naming the file, the revision and the test or command you ran |
| a book chapter (orientation, part introductions, Part VI, appendices) or a Book edition note | the CognoKratos maintainers via cognokratos.com. The book's own repository is not public at present. |
How upstream corrections reach the book
Imported chapters are maintained beside their code, on each project's current
branch (main for all five projects). The book shows a pinned
revision. A fix merged upstream appears in the book when the maintainers
update that project's pin, review the changed chapters and publish a new
build. Until then, the book keeps showing the pinned text, and the source note
says which revision that is.
When an upstream fix makes a Book edition note unnecessary, the note is removed in the same update.
What makes a good report
- The chapter title and the heading nearest to the problem.
- What the chapter says, and what you believe is true.
- Evidence: a file and line at the revision shown, a test, or a command and its output.
- For labs: your OS, tool versions and the model you used. Remember that model behaviour is observed, not guaranteed.