Evidence-backed maintenanceDetect changes.
Detect changes.
Review before publishing.
A daily server process reads allowlisted primary sources through the bounded safe-fetch service, prepares source-evidenced private drafts and claims a small editorial queue. No detected text, generated draft or queue claim can publish itself.
What “fresh” means here
Pages display their genuine reviewed date and version. Source checks show whether upstream text changed. A first baseline is only a comparison point, not content approval. Checks do not prove every claim remains correct. Publication requires a named editorial decision, reviewed lesson change, Git commit, released version and public history record.
Published review history
2 detected changes remain private while editors review the evidence; 2 currently claimed for review.
No source-change review has been published yet.