Errata and freshness
Every week:
- Read new reader reports (issues labelled
errata) and the weekly freshness report (issues labelledfreshness, opened by.github/workflows/freshness.ymlfromtools/check_freshness.py: broken or blocked source links, and as-of, checked and in-text dates over 180 days old). Close a finding that needs no change as not planned; it stays closed while the finding is unchanged. - Re-check every dated fact in published modules (model names, prices, limits, laws in force). A fact that has moved becomes an erratum.
- For each confirmed error, open a PR that fixes the passage, bumps the module's patch version and adds a dated line to
ERRATA.mdsaying what changed and why. The erratum guard (tools/check_erratum_guard.py, CI on every PR) fails until that row names the reviewer who re-signed. - Ask the review clerk to get one reviewer's sign on the changed passage. It is not live until signed.
The public site matches the re-sign name to an approved human reviewer in that module's review.yml. Until the row is signed it builds the prior signed module from the checkout's first-parent Git history, with a pending note on the errata page. Keep full history available when building the public site; a missing signed snapshot stops the build.
Never change an objective or a quiz answer without the review clerk routing it to both reviewers.